Re: Corrupted superblock

["Ian Wright" <Ian-at-iw63.freeserve.co.uk>]

Hi Clint,

I wonder if you have the same kind of problem I have just been experiencing?
I had RH6.1 set up on a 3.2Gb hard drive and it kept refusing to start.
What I found was that something (and I suspect LILO) was messing up the bios
setup for the hard drive and was changing the 'extended CHS' settign to
'normal CHS'. This had the effect of preventing the computer reading the
large blocks of the big drive. (I think some bios' use the term LBA mode).
In my case I found I could just go into the bios setup at startup ('F1 key')
and change the setting back and the thing would restart OK (I actually tried
reformatting a couple of times first without success before I found the real
problem).  The errors you are getting are not the same as in my case - my
machine just booted to the 'LI' stage and then hung - but the effect seems
similar and different machines always seem to behave in different ways so it
may be worth a look before you do anything more drastic.

Ian

--
Ian W. Wright
Sheffield  UK


----- Original Message -----
From: Clint Bach <clintbach-at-earthlink.net>
To: Multiple recipients of list <emc-at-nist.gov>
Sent: 03 March 2000 02:53
Subject: Corrupted superblock


>
> Hi,
>
> My EMC installation may or may not be toast... RTLinux won't boot,
> Serious stuff! The computer has forgotten its name and there is not a
> user called root. I get error 202 and error 204... and a message that
> inode bit 6 is already set and that the file system is not a file
> system.
>
> However... When I boot from the other hard drive and mount the drive
> with EMC and RTLinux everything is there... What can I do to recover
> this? Should I just reformat this hard drive and start over? Should I
> copy the whole drive to the other drive (there is room on the other for
> the whole drive) and try moving it back? Where can I find information on
> corrupted superblocks?
>
> The basic question is should I attempt to fix this drive or nuke it and
> start over?
>
> Thanks,
>
> Clint Bach
>
>