Re: Linuxconf Trashed RH9 Boot - Fix?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Colburn wrote:

> 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 think the key problem is that Linuxconf changed something to insist
> upon requiring ext2 when ext3 is the correct default.

What does /etc/fstab say?
When in the boot sequence does the error message appear?
Maybe an older grub got installed, which is not capable of reading ext3
partitions. Try this:
Boot from the first Red Hat Linux CD from RHL9
At the boot: promt, enter "linux rescue" (without quotes)
ls /mnt/sysimage
Look if every partition has been found. If so,
chroot /etc/sysimage
Check the content of /boot/grub/grub.conf
If it looks correct,
grub-install /dev/hda
If it doesn't look right, or doesn't work, post the content here.

Best regards,
Martin Stricker
-- 
Homepage: http://www.martin-stricker.de/
Linux Migration Project: http://www.linux-migration.org/
Red Hat Linux 8.0 for low memory: http://www.rule-project.org/
Registered Linux user #210635: http://counter.li.org/


-- 
Shrike-list mailing list
Shrike-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/shrike-list

[Index of Archives]     [Fedora Users]     [Centos Users]     [Kernel Development]     [Red Hat Install]     [Red Hat Watch]     [Red Hat Development]     [Red Hat Phoebe Beta]     [Yosemite Forum]     [Fedora Discussion]     [Gimp]     [Stuff]     [Yosemite News]

  Powered by Linux