public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dan Farrell <dan@spore.ath.cx>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Corrupt USB pen drive
Date: Thu, 17 May 2007 10:49:41 -0500	[thread overview]
Message-ID: <20070517104941.66af199f@pascal.spore.ath.cx> (raw)
In-Reply-To: <200705171638.54090.michaelkintzios@gmail.com>

On Thu, 17 May 2007 16:38:44 +0100
Mick <michaelkintzios@gmail.com> wrote:

> On Thursday 17 May 2007 15:45, Dan Farrell wrote:
> > On Thu, 17 May 2007 12:36:25 +0100
> >
> > Mick <michaelkintzios@gmail.com> wrote:
> 
> > >
> > > I tried to dd the boot sector so that I can look at it on my hard
> > > drive, but it cannot access /dev/sda.  Is there anything that I
> > > can do with my Gentoo to recover the files on this USB?
> >
> > have you tried reading raw from the device like
> >
> > | dd if=/dev/sda of=sda.image
> >
> > ?  That might do the recovery.  How to get it out of the image is
> > the same problem but once the backup succeeds you can plug it into a
> > windows xp box and reformat, and you will probably end up with the
> > same partition structure as originally.  Then you can try to read
> > the right part of the image out of the image, once you get the
> > numbers from fdisk on the newly formatted drive, and end up with an
> > image of sda1.  From there you should be able to mount sda1 and
> > read out the data, if it isn't corrupted.
> 
> Thanks Dan, as I said above I tried to extract the MBR out of it by
> running:
> 
> dd if=/dev/sda of=/tmp/r1 bs=512
> 
> But couldn't access it whatsoever.
> 
> > I also am wondering what happened to the partition table.  I bet
> > your coworker has a security-compromised box at home (oh, runs
> > windows? right...)  At any rate, if the data is recoverable, it may
> > be possible to rebuild the partition table if you can find out
> > where the partition started and ended.  People have done it before,
> > i've read online about it.
> 
Hmm!  Perhaps its broken.
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-05-17 15:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-17 11:36 [gentoo-user] Corrupt USB pen drive Mick
2007-05-17 11:51 ` Elias Probst
2007-05-17 12:56   ` Mick
2007-05-17 14:45 ` Dan Farrell
2007-05-17 15:38   ` Mick
2007-05-17 15:49     ` Dan Farrell [this message]
2007-05-17 16:03     ` Tim Allingham
2007-05-17 16:04     ` Mick
2007-05-17 16:25       ` Dan Farrell
2007-05-17 16:26       ` Tim Allingham
2007-05-17 22:27       ` Etaoin Shrdlu
2007-05-18  8:29         ` Mick
2007-05-18  9:24           ` Etaoin Shrdlu
2007-05-18 11:50             ` Mick
2007-05-18 12:25               ` Hans-Werner Hilse
2007-05-18 13:11                 ` Mick
2007-05-18 14:09                   ` Dan Farrell
2007-05-18 14:48                   ` Hans-Werner Hilse
2007-05-18 15:30                     ` Etaoin Shrdlu
2007-05-18 15:16                   ` Etaoin Shrdlu
2007-05-21  9:47                     ` Mick
2007-05-21 12:30                       ` [gentoo-user] Corrupt USB pen drive [ot] Dan Farrell
2007-05-17 16:35 ` [gentoo-user] Re: Corrupt USB pen drive Francesco Talamona
2007-05-17 21:27 ` [gentoo-user] " Etaoin Shrdlu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070517104941.66af199f@pascal.spore.ath.cx \
    --to=dan@spore.ath.cx \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox