Re: Hard Drive Problems

["Mikkel L. Ellertson" <mikkel Infinity-ltd com>]

On Fri, 31 Aug 2001, Dave Lewis wrote:

> I have a friend who is just starting into linux and hit this problem..
> wondering if  anyone has any ideas??
> here is a snippit of his email that he sent me.. I have no clue.. never saw
> these errors before so I thought I'd
> ask around :)
> -----
>
> Modprobe: can't locate module block-major-22.
>
This is saying it is trying to load a driver to access drives on the
second IDE controller.  Definitly strange.
>
> Fsck.ext2(null):
> 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 alternative superblock:
>
> e2fsck -b 8193 (device)
>
> no such device while trying to open /dev/hdd1
>
Is his hard drive configured as the slave device on the second IDE
controller?
>
> -----
> This error occured after a 15 minute power ottage in my city (ottawa).  Now
> my hard drive is whipped clean.
>
>
> Is there anyway to restore the contents of my EXT hard drive?  The contents
> of this drive are irreplacable.
>
There are a lot of different possibilities here.  The first is that
/etc/fstab may have become corrupted when the power failed.  But it is
more likely from the errors that the partition table of the drive was
messed up when the power failed.  With more information, we can probably
figure out how to recover from this.  If the system will boot at all, or
if it can be booted from something like Tom's boot disk, or one of the
rescue CDs, and the command "fdisk -l /dev/hdd" run, it would help.
(Unless the hard drive giving the problem is not the slave on the second
IDE controller - then there are other problems...)

Mikkel
 --

    Do not meddle in the affairs of dragons,
 for you are crunchy and taste good with ketchup.