Click to See Complete Forum and Search --> : fstab error ?
tachyonism
02-26-2001, 05:04 PM
Hi there,
My problem is when I run 'fsck' to checking my file system, it gives me this result :
[root@monyetserver /etc]# fsck /
Parallelizing fsck version 1.19 (13-Jul-2000)
Couldn't find matching filesystem: LABEL=/
On the first line of my '/etc/fstab/' stands:
LABEL=/ / ext2 defaults 1 1
My distro is Redhat 7.0, kernel 2.2.17-14.
Anybody there can help me ? pleasee :)
Dru Lee Parsec
02-26-2001, 05:28 PM
Hmm. I don't have "LABEL=" anywhere in my fstab file. In fact, I don't see how LABEL= is even a legit fstab command. The first thing on each line of /etc/fstab should be a device. i.e.
/dev/hde6 ext2 defaults 1 1
Then you would have a line for each hard drive partition. So something is seriously messed up OR you're confusing fstab with some other file.
Bradmont
02-27-2001, 04:22 PM
You forgot the mount point there, dru...
it should be something like:
/dev/hda3 /home ext2 rw 0 2 # my /home
/dev/hda6 none swap sw 0 0 # one of my swap partitions
<edit> the bits after the anoctothropes (#) are comments, in case you didn't know. They don't need to be there</edit>
[ 27 February 2001: Message edited by: Bradmont ]
USDA-BrianS
07-15-2002, 01:28 PM
I had the same problem, and after I fixed the file it would allow me to run the fsck command. However I know get the following message (I've put spaces between each line):
Couldn't find ext2 superblock, trying backup blocks...
fsck.ext3: Bad magic number in super-block while trying to open /dev/sda2
The superblock could not be read or does not describe a correct ext2 filesystem. If the devce is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), the the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
I have tried running this command many times. I have read about a mke2fs command, but have also been warned to backup my info before I do this. The site I read about the mke2fs (or something similar) command did mentioned something about hidden superblock locations or something to that effect.
The dumpe2fs command does not work on /dev/sda2 either.
Any help would be greatly appreciated. I would prefer if you would respond by email, but I will check back periodically.
slapNUT
07-15-2002, 03:49 PM
From man fstab
Instead of giving the device explicitly, one may indicate
the (ext2 or xfs) filesystem that is to be mounted by its
UUID or volume label (cf. e2label(8) or xfs_admin(8)),
writing LABEL=<label> or UUID=<uuid>, e.g., `LABEL=Boot'
or `UUID=3e6be9de-8139-11d1-9106-a43f08d823a6'. This will
make the system more robust: adding or removing a SCSI
disk changes the disk device name but not the filesystem
volume label.
So you could have a line in /etc/fstab like this LABEL=root / ext2 defaults 0 0
And you would use e2label to set the device /dev/sdaX = root like this
e2label /dev/sdaX root
Then the line would be OK in /etc/fstab. The purpose is that you could then move sda to sdb and the /etc/fstab would not have to be changed... cool.