[vox-tech] Disk Failure - Data Retrieval?
Stephen Young
vox-tech@lists.lugod.org
Wed, 1 Oct 2003 15:59:50 -0700 (PDT)
--0-1771665596-1065049190=:21774
Content-Type: text/plain; charset=us-ascii
Pleaase take me off the email list. Thank you.
Michael J Wenk <wenk@praxis.homedns.org> wrote:On Tue, Sep 30, 2003 at 07:04:44AM -0700, Marc Elliot Hall wrote:
> As expected (and reported in my unresponded-to-post to this list on
> 09/15/2003), the hard disk I keep my media collection on has failed.
> Since this disk was the first one physically installed in my Mandrake
> box, it was /dev/hda1, all in one large partition. After an unclean
> shutdown, the system would not boot - I got an MBR: 0x?? error (nope,
> didn't write down the last two characters; so I don't know the specific
> cause) on power up. Tried a few more times: no luck, so it wasn't a
> transient error.
>
> Suspecting that the disk was hosed, I then:
>
> * swapped my IDE cables;
> * booted from the Mandrake 9.1 CD in rescue mode;
> * switched parameters in /etc/fstab to establish my mount points for
> various directories to /dev/hda and /dev/hdb instead of /dev/hdc and
> /dev/hdd, respectively;
> * wrote the MBR to /dev/hda (that had previously been /dev/hdc);
> * symlinked /etc/lilo.conf to /mnt/etc/lilo.conf;
> * ran LILO; and
> * rebooted.
>
> So, now I'm back in business.
>
> However, I still don't have my media collection online! Because I have
> the original CDs, I didn't keep backups of this particular disk.
> Unfortunate, but reasonable considering the expense of tape backup
> solutions and my current unemployment :^(
>
> Short of re-ripping my insanely large CD collection, is there an easy
> way to retreive the data from my disk? Based on what I've tried so far,
> it appears that the boot sector and/or partition table of the disk are
> corrupted.
>
> What I've tried so far:
>
> # fsck.ext3 /dev/hdc1
> e2fsck 1.32 (09-Nov-2002)
> fsck.ext3: No such file or directory while trying to open /dev/hdc1
>
> The superblock could not be read or does not describe a correct ext2
> filesystem. If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else), then the superblock
> is corrupt, and you might try running e2fsck with an alternate superblock:
> e2fsck -b 8193
>
> # fsck.ext3 /dev/hdc
> e2fsck 1.32 (09-Nov-2002)
> fsck.ext3: Attempt to read block from filesystem resulted in short read
> while trying to open /dev/hdc
> Could this be a zero-length partition?
>
> # fdisk -l /dev/hdc
>
> (Nothing except a blank line results. Just to check, I verified another
> disk:)
>
> # fdisk -l /dev/hda
>
> Disk /dev/hda: 40.0 GB, 40027029504 bytes
> 16 heads, 63 sectors/track, 77557 cylinders
> Units = cylinders of 1008 * 512 = 516096 bytes
>
> Device Boot Start End Blocks Id System
> /dev/hda1 * 1 507 255496+ 83 Linux
> /dev/hda2 508 77558 38833368 5 Extended
> /dev/hda5 508 1319 409216+ 82 Linux swap
> /dev/hda6 1320 20102 9466600+ 83 Linux
> /dev/hda7 20103 50911 15527704+ 83 Linux
> /dev/hda8 50912 77558 13429720+ 83 Linux
>
> (so it's not that I can't use fdisk...)
>
> # sfdisk -l /dev/hdc
>
> Disk /dev/hdc: 158816 cylinders, 16 heads, 63 sectors/track
> read: Input/output error
>
> sfdisk: read error on /dev/hdc - cannot read sector 0
> /dev/hdc: unrecognized partition
> No partitions found
>
> Does anyone have any ideas?
>
>
>
> --
> Marc Elliot Hall www.hallmarc.net/quick_resume.html
> P.O. Box 435
> Shingle Springs, CA 95682
> www.hallmarc.net Hire me!
>
>
> _______________________________________________
> vox-tech mailing list
> vox-tech@lists.lugod.org
> http://lists.lugod.org/mailman/listinfo/vox-tech
What does fsdb show for the disk?
First of all, if you can(Ie, have the space) do a dd image of the drive.
I suspect that you will not be able to do it. I would try looking at it
with the debugger, and perhaps looking at the disk with whatever diag
util the manufacturer makes. However, my best guess is that you are
screwed and should start reripping...
_______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech
--0-1771665596-1065049190=:21774
Content-Type: text/html; charset=us-ascii
<DIV>Pleaase take me off the email list. Thank you.<BR><BR><B><I>Michael J Wenk <wenk@praxis.homedns.org></I></B> wrote:
<BLOCKQUOTE class=replbq style="BORDER-LEFT: #1010ff 2px solid; MARGIN-LEFT: 5px; PADDING-LEFT: 5px">On Tue, Sep 30, 2003 at 07:04:44AM -0700, Marc Elliot Hall wrote:<BR>> As expected (and reported in my unresponded-to-post to this list on <BR>> 09/15/2003), the hard disk I keep my media collection on has failed. <BR>> Since this disk was the first one physically installed in my Mandrake <BR>> box, it was /dev/hda1, all in one large partition. After an unclean <BR>> shutdown, the system would not boot - I got an MBR: 0x?? error (nope, <BR>> didn't write down the last two characters; so I don't know the specific <BR>> cause) on power up. Tried a few more times: no luck, so it wasn't a <BR>> transient error.<BR>> <BR>> Suspecting that the disk was hosed, I then:<BR>> <BR>> * swapped my IDE cables;<BR>> * booted from the Mandrake 9.1 CD in rescue mode;<BR>> * switched parameters in /etc/fstab to establish my mount points for <BR>> var
ious
directories to /dev/hda and /dev/hdb instead of /dev/hdc and <BR>> /dev/hdd, respectively;<BR>> * wrote the MBR to /dev/hda (that had previously been /dev/hdc);<BR>> * symlinked /etc/lilo.conf to /mnt/etc/lilo.conf;<BR>> * ran LILO; and<BR>> * rebooted.<BR>> <BR>> So, now I'm back in business.<BR>> <BR>> However, I still don't have my media collection online! Because I have <BR>> the original CDs, I didn't keep backups of this particular disk. <BR>> Unfortunate, but reasonable considering the expense of tape backup <BR>> solutions and my current unemployment :^(<BR>> <BR>> Short of re-ripping my insanely large CD collection, is there an easy <BR>> way to retreive the data from my disk? Based on what I've tried so far, <BR>> it appears that the boot sector and/or partition table of the disk are <BR>> corrupted.<BR>> <BR>> What I've tried so far:<BR>> <BR>> # fsck.ext3 /dev/hdc1<BR>> e2fsck 1.32 (09-Nov-2002)<BR
>>
fsck.ext3: No such file or directory while trying to open /dev/hdc1<BR>> <BR>> The superblock could not be read or does not describe a correct ext2<BR>> filesystem. If the device is valid and it really contains an ext2<BR>> filesystem (and not swap or ufs or something else), then the superblock<BR>> is corrupt, and you might try running e2fsck with an alternate superblock:<BR>> e2fsck -b 8193 <DEVICE><BR>> <BR>> # fsck.ext3 /dev/hdc<BR>> e2fsck 1.32 (09-Nov-2002)<BR>> fsck.ext3: Attempt to read block from filesystem resulted in short read <BR>> while trying to open /dev/hdc<BR>> Could this be a zero-length partition?<BR>> <BR>> # fdisk -l /dev/hdc<BR>> <BR>> (Nothing except a blank line results. Just to check, I verified another <BR>> disk:)<BR>> <BR>> # fdisk -l /dev/hda<BR>> <BR>> Disk /dev/hda: 40.0 GB, 40027029504 bytes<BR>> 16 heads, 63 sectors/track, 77557 cylinders<BR>> Units = cylinders of 1008 * 51
2 =
516096 bytes<BR>> <BR>> Device Boot Start End Blocks Id System<BR>> /dev/hda1 * 1 507 255496+ 83 Linux<BR>> /dev/hda2 508 77558 38833368 5 Extended<BR>> /dev/hda5 508 1319 409216+ 82 Linux swap<BR>> /dev/hda6 1320 20102 9466600+ 83 Linux<BR>> /dev/hda7 20103 50911 15527704+ 83 Linux<BR>> /dev/hda8 50912 77558 13429720+ 83 Linux<BR>> <BR>> (so it's not that I can't use fdisk...)<BR>> <BR>> # sfdisk -l /dev/hdc<BR>> <BR>> Disk /dev/hdc: 158816 cylinders, 16 heads, 63 sectors/track<BR>> read: Input/output error<BR>> <BR>> sfdisk: read error on /dev/hdc - cannot read sector 0<BR>> /dev/hdc: unrecognized partition<BR>> No partitions found<BR>> <BR>> Does anyone have any ideas?<BR>> <BR>> <BR>> <BR>> -- <BR>> Marc Elliot Hall www.hallmarc.net/quick_resume.html<BR>> P.O. Box 435<BR>> Shingle Springs, CA 95682<BR>> www.hallmarc.net Hire me!<BR>> <BR>> <BR>>
_______________________________________________<BR>> vox-tech mailing list<BR>> vox-tech@lists.lugod.org<BR>> http://lists.lugod.org/mailman/listinfo/vox-tech<BR><BR>What does fsdb show for the disk? <BR><BR>First of all, if you can(Ie, have the space) do a dd image of the drive.<BR>I suspect that you will not be able to do it. I would try looking at it<BR>with the debugger, and perhaps looking at the disk with whatever diag<BR>util the manufacturer makes. However, my best guess is that you are<BR>screwed and should start reripping... <BR><BR><BR><BR>_______________________________________________<BR>vox-tech mailing list<BR>vox-tech@lists.lugod.org<BR>http://lists.lugod.org/mailman/listinfo/vox-tech</BLOCKQUOTE></DIV>
--0-1771665596-1065049190=:21774--