[ale] How to fix a crashed disk with fsck or debugfs

[Joe Knapka]

I had something similar happen once (to an IDE disk, tho).
System crashed, partition table got nuked. So I
fdisk'd the HD and replaced the same partitioning scheme
that had been there before. Then just for the hell of it,
I tried to mound those partitions, and lo and behold,
the filesystems were still intact. So if you can reproduce
the partition table, you might find all your data safe
and sound (but "might" is the operative word).

-- Joe

Malcolm.Silberman at BassHotels.com wrote:
> 
> no fdisk /dev/sda does not show the partitioning scheme.... <with tears in
> my eyes>
> 
> -----Original Message-----
> From: Gary Maltzen [mailto:maltzen at MM.COM]
> Sent: Wednesday, July 12, 2000 9:47 PM
> To: Malcolm.Silberman at BassHotels.com
> Cc: ale at ale.org
> Subject: Re: [ale] How to fix a crashed disk with fsck or debugfs
> 
> Based on your description so far, you may be SOL.
> 
> Question: does 'fdisk /dev/sda' properly show the partitioning scheme?
> (I'm wondering if the MBR is intact)
> 
> >Here is the problem, had a pwoer failure and fcsk reported errors. It got
> >the ide drives up and working but not the scsi. Here are the details;
> >
> >sda is 8746MB which is a IBM DNES 309170W SCSI (1115cyl 255head 63sec)
> >- sda6 is /m01 6087MB
> >- sda7 is /home 1655MB
> >
> >Somehow I lost power and crashed the drives. Tried to run
> >fsck -A -V ; echo == $? ==
> >got ==8== which is defined as an OPERATOR ERROR
> >
> >Then tried fsck -t ext2 -b 8193 /dev/sda6 and got
> >'bad magic number in super-block when trying to open /dev/sda6...superblock
> >does not describe a correct ext2 filesystem"
> >
> >Tried superblocks at 16385 and 24577 same message...
> >
> >Also tried dumbe2fs /dev/sda6 and got the same bad magic number stuff...
> --
> To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.

-- Joe Knapka
--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.