fsck.ext3: Unable to resolve 'LABEL=

pm02368 · 09-12-2006, 06:00 PM

Hi Guru's,
I recently Installed Fedore Core 5 and created few partitions but messed-up one label in /etc/fstab file. When I did reboot, it says -

fsck.ext3: Unable to resolve 'LABEL=/home/load'

*** An error occured during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
..etc

When I log in there as root, I can see the wrong label in /etc/fstab file but can't edit the file. It is read only. How do I fix the file?

Thanks in advance.

Brian1 · 09-12-2006, 06:18 PM

Boot up with the FC CD and use the boot option of ' linux rescue '. Then allow it to mount existing partitions and goto it and edit the file. Just to make sure you have it right you define the LABEL in /etc/mtab file? If not the partition needs to be define there before LABEL can be used. To me it would make better since just to define the /dev point right in /etc/fstab. Example:

Code:

# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/hda9               /                       ext3    defaults        1 1
/dev/hda2               /boot                   ext3    defaults        1 2
none                    /dev/pts                devpts  gid=5,mode=620  0 0
none                    /dev/shm                tmpfs   defaults        0 0
/dev/hda6               /dvdrw                  ext3    defaults        1 2
/dev/hda8               /home                   ext3    defaults        1 2
none                    /proc                   proc    defaults        0 0
# /dev/hda10              /sharevfat              vfat    defaults        0 0
/dev/hda5               /storage1               ext3    defaults        1 2
/dev/hda12              /storage2               ext3    defaults        1 2
none                    /sys                    sysfs   defaults        0 0
/dev/hda3               /usr                    ext3    defaults        1 2
/dev/hda7               /var                    ext3    defaults        1 2
/dev/hda11              swap                    swap    defaults        0 0
# /dev/hdd                /media/cdrecorder       auto    pamconsole,exec,noauto,managed 0 0
# /dev/hdc                /media/cdrecorder1      auto    pamconsole,exec,noauto,managed 0 0
# /dev/sda1               /media/usbdisk          vfat    pamconsole,noatime,sync,exec,noauto,managed 0 0
# Mounting of other local partitions
/dev/hda10              /sharevfat              vfat    umask=000,users,auto,owner,rw,dirsync   0 0  
/dev/hda1       	/winxp                  ntfs	umask=000,users,noauto,owner,rw 0 0
/dev/cdrom              /mnt/cdrom              auto    noauto,owner,rw 0 0 
/dev/cdrom1             /mnt/cdrom1             auto    noauto,owner,rw 0 0 
/dev/scd0		/mnt/cdrom2             auto    noauto,owner,rw 0 0 
/dev/fd0                /mnt/floppy             auto    noauto,owner 0 0 
# SD Block Mounts on local USB, Firewire, and Scsi using sync which is slow
# /dev/sda1               /mnt/sda1               auto    umask=000,users,noauto,owner,rw,sync,dirsync   0 0 
# SD Block Mounts on local USB, Firewire, and Scsi
/dev/sda1               /mnt/sd_block/sda1               auto    umask=000,users,noauto,owner,rw,dirsync   0 0 
/dev/sdb1               /mnt/sd_block/sdb1               auto    umask=000,users,noauto,owner,rw,dirsync   0 0 
/dev/sdc1               /mnt/sd_block/sdc1               auto

Brian1

michaelk · 09-12-2006, 07:03 PM

One option is to boot to rescue mode and edit the /etc/fstab file. The / partition will be mounted at /mnt/sysimage. /etc/mtab will not tell you anything unless the filesystem is mounted which it will not do since you have an error.

In maintenance mode (the dropping to shell part) you can remount the filesystem with rw permissions using the following command.
mount -n -o remount,rw /

You should now be able to edit the /etc/fstab and fix your error.

pm02368 · 09-12-2006, 07:07 PM

Yes! It worked. I appreciate prompt response.

Thanks

Brian1 · 09-12-2006, 07:15 PM

Glad to be of help and see you have it back up and working.

Brian1