OK, when I boot up my Red Hat 7.2 Linux (2.4.18-18.7) it complains that it can't find the file system "LABEL=/home".

I originally inherited this machine and it looks like some data or something got blown away. It has 6 SCSI drives in it and only the first one has any partitions on it. If I remove the following entry from fstab it boots fine:

LABEL=/home /home ext2 defaults 1 2

So, I can see /dev/sda and it has a primary boot and extended partition. All of the other drives' partition tables were blank. So, I created a single partition on /dev/sdb.

I then did a "mkfs.ext2 -L /home /dev/sdb" and it created it just fine. However, a side note here is that all of the other working filesystems are "ext3" but I cannot seem to find ANY "ext3" filesystem files on the system, just ext2, minix and a couple others. Bizarre. Anyone have a clue on that one?

So, anyway, if I do an "e2label /dev/sdb" it reports back as "/home" and I can mount this drive just fine and dandy using
"mount -t ext2 /dev/sdb /home". Works great. But, when I boot, I get the error "Couldn't find matching filesystem: LABEL=/home [FAILED]. What gives? I seem to be doing everything right that I have been able to find in books and on-line. But no luck.

Thanks in advance for any assistance!

Look in your /etc/mtab file and see what /home is suppose to point to. If you no longer have a partition that used to be /home then remove the line from mtab and fstab. If you know the correct partition for /home then correct the mtab file.

Brian1
" Google the Linux way @ http://www.google.com/linux "

Just a SWAG here. Normally when you create a partition it will be assigned an ID i.e. 1- whatever. I'm not sure what happens when you label an entire drive. Assuming partition 1:

mkfs.ext2 -L /home /dev/sdb1

You can use the device ID instead of a label in the fstab file if your not wanting to change anything.

/dev/sdb /mnt/home .....