Like a dummy I tinkered with the boot sequence using Linuxconf (hoping
to fix the problem with the failure to access the second hdd) and now
cannot figure out how to repair the damage (I have disconnected the new
hdd with RH9 and am back booting from the RH8 hdd). I have tried Rescue
from the floppy and from the KRUD CD to no avail -- I always end up at a
command prompt.
The problem is that while booting it insists upon looking for a ext2
filesystem type instead of the correct ext3, and of course, it fails.
The error reads "The superblock could not be read or does not describe a
correct ext2 filesystem" Then it suggests running e2fsck -b 8193
<DEVICE>
I tried several different devices, e.g. hda, hda1, etc. to no avail. i
think the key problem is that Linuxconf changed something to insist upon
requiring ext2 when ext3 is the correct default.
fsck -ANVt ext3 shows:
[/sbin/fsck.ext3 (1) -- /hdb] fsck.ext3 /dev/hda2
[/sbin/fsck.ext3 (1) -- /boot] fsck.ext3 /dev/hda1
MOUNT:
/dev/hda2 on 1 type ext3 (rw) none on /proc type proc (rw)
grubedit>kernel /vmlinux-2.4.20-20.9 ro root=LABEL=/ hdc=ide-scsi
Help, please?
--
~~~
o['|']o Thanks! dmc
\~/
~~~~~~~~~~~~~~~~~~~~~~~~~
|
Jesus === Freedom
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
Shrike-list mailing list
Shrike-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/shrike-list
