Bear with me.. trying to make a point.. May be the cause..??? Snipping from
various posts in this thread
>>Could you post your /etc/fstab file? This might help in determining the
>>problem.
=======SNIP of your /etc/fstab=====================
LABEL=/ /hdb ext3 user,owner, exec,dev,suid,rw 1 1
LABEL=/boot /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/hda3 swap spwp defaults 0 0
/dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,kudzu 0 0
/dev/fd0 /mnt/floppy auto noauto,owner,kudzu 0 0
================/snip===============================
==========SNIP of /boot/grub/grub.conf================
efault=0
timeout=10
splashimage=(hd0,1)/grub/splash.wpm.gz
title Red Hat Linux (2.4.18-14)
root (hd0,1)
kernel /vmlinux-2.4.18-14 ro root=LABEL=/ hdc=ide-scsi
initrd initrd-2.4.18-14.img
title DOS
rootnoverify (hd0,0)
chainloader +1
============/snip================================
Okay my 2 cents.. In my experience, I feel that the line
LABEL=/ /hdb ext3 user,owner, exec,dev,suid,rw 1 1
Does ^$#&*# to your install. you know the "LABEL=/" line? Well, _I_ think
it's screws things up. (it did for me)
so.. change it to
/dev/hdb / ext3 user,owner, exec,dev,suid,rw 1 1
^^^^^ (1) ^^(2)
(1) The root partition of where you installed Linux. Also where grub is
installed. I've not seen a /dev/hdb install before. Are you installing into
the _whole_ of your secondary slave drive??? eg.. no /boot not /home no /usr
etc.. just / ??
(2) This tells linux that your root partition is in (1)
Also..change the labe on the grub.conf from
kernel /vmlinux-2.4.18-14 ro root=LABEL=/ hdc=ide-scsi
to
kernel /vmlinux-2.4.18-14 ro root=/dev/hdb hdc=ide-scsi
something like that..
If that doesn't work, can i get you to post your -> cat /proc/partitions
just to see how your partitions are done..
My 2 cents.
Cheers, .^.
Mun Heng, Ow /V\
H/M Engineering /( )\
Western Digital M'sia ^^-^^
DID : 03-7870 5168 The Linux Advocate
-----Original Message-----
From: Iain Buchanan [mailto:iain@xxxxxxxxxxxx]
Sent: Wednesday, October 08, 2003 9:47 AM
To: shrike-list@xxxxxxxxxx
Subject: Re: Linuxconf Trashed RH9 Boot - Fix?
On Mon, 2003-10-06 at 07:13, 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.
You may be barking up the wrong tree. You should be able to mount an
ext3 filesystem as ext2 no worries.
> 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>
Hmm, sounds like you have some more serious problems. Are you sure the
partition isn't corrupt? Are you sure you're mounting the correct
partition?
Could you post your /etc/fstab file? This might help in determining the
problem.
Regards,
--
Iain Buchanan <iain@xxxxxxxxxxxx>
--
Shrike-list mailing list
Shrike-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/shrike-list
--
Shrike-list mailing list
Shrike-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/shrike-list
