Find the answer to your Linux question:
Results 1 to 7 of 7
Hi I have installed Fedora Core 3 and on booting up it gives the error fsck.ext3:Unable to resolve "LABEL=/" An error occured during filesystem check Dropping you to a shell, ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Linux Newbie
    Join Date
    May 2005
    Location
    Chennai,TamilNadu, India
    Posts
    141

    fsck.ext3 : Unable to resolve "LABEL=/"


    Hi

    I have installed Fedora Core 3 and on booting up it gives the error

    fsck.ext3:Unable to resolve "LABEL=/"
    An error occured during filesystem check
    Dropping you to a shell, the system will reboot
    when you leave shell


    Ok I searched on the net regarding this...

    My /etc/fstab had the following entries

    LABEL=/ / ext3 defaults 1 1
    LABEL=/var/log /var/log ext3 defaults 1 2
    .....
    ....


    My grub.conf had the following entries

    title StorTrends iTX 2.0 (2.6.9-1.667smp)
    root (hd0,0)
    kernel /boot/vmlinuz-2.6.9-1.667smp ro root=LABEL=/ elevator=deadline vga=0x318 quiet
    initrd /boot/initrd-2.6.9-1.667smp.img

    ************************************************** **
    In maintenance mode i mounted the / in read - write mode

    mount -n -o remount,rw /

    I changed the /etc/fstab entries to the following

    /dev/sda1 / ext3 defaults 1 1
    /dev/sda3 /var/log ext3 defaults 1 2

    and the grub entry to

    kernel /boot/vmlinuz-2.6.9-1.667smp ro root=/dev/sda1 elevator=deadline vga=0x318 quiet

    The output of "mount" command in maintenance mode gave me the following

    /dev/sda1 on / type ext3 (rw)
    none on /proc type proc (rw)
    none on /sys type sysfs (rw)
    none on /dev/pts type devpts (rw,gid=5,mode=620)
    usbfs on /proc/bus/usb type usbfs (rw)
    none on /dev/shm type tmpfs (rw)
    /dev/sda3 on /var/log type ext3 (rw)
    none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
    sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)



    and it worked.....

    ************************************************** *****

    But since i needed the LABEL=/ option to work

    I first thought that the label are not be assigned correctly

    I tried the command

    e2label /dev/sda1 /
    e2label /dev/sda3 /var/log

    But still on reboot it did not work.

    Why does it not work when giving the LABEL=/ and works when giving directly the /dev/sda1 value??

    I searched in the net but could not find the answer why it does not work this way....

    Anybody have any thoughts on this why the LABEL=/ does not work

  2. #2
    Linux Newbie
    Join Date
    May 2005
    Location
    Chennai,TamilNadu, India
    Posts
    141
    I verified if the labels are correct also

    [root@ITX003048826c22 ~]# e2label /dev/sda1
    /
    [root@ITX003048826c22 ~]# e2label /dev/sda3
    /var/log


    One more check i made was that i left the grub entry as it is to LABEL=/

    and changed the fstab entries to /dev/sda1 for / and /dev/sda3 for /var/log ...

    It worked

    So why is the label not working for fstab but works for grub....???

  3. #3
    Linux Newbie
    Join Date
    May 2005
    Location
    Chennai,TamilNadu, India
    Posts
    141
    I would take this to mean that fsck can't find a partition whose label is "/".
    but /boot/grub/grub.conf is using "root=LABEL=/" then I myself am surprised
    how i got to boot linux at all, yet I am able to.

  4. $spacer_open
    $spacer_close
  5. #4
    Linux Newbie
    Join Date
    May 2005
    Location
    Chennai,TamilNadu, India
    Posts
    141
    [root@ITX003048826c22 ~]# e2label /dev/sda1
    /
    [root@ITX003048826c22 ~]# e2label /dev/sda3
    /var/log
    [root@ITX003048826c22 ~]# fsck.ext3 LABEL=/
    fsck.ext3: Unable to resolve 'LABEL=/'
    [root@ITX003048826c22 ~]# echo $?
    8
    [root@ITX003048826c22 ~]# rpm -qa e2fsprogs
    e2fsprogs-1.35-11.2


    The above information may provide more insight to this issue

    http://bugs.donarmstrong.com/cgi-bin...91;archive=yes

    The above link shows that this was a bug in the debian bug tracking system and supposed to be fixed....

    but still it seems to exist on FC3 .....

  6. #5
    Linux Newbie
    Join Date
    May 2005
    Location
    Chennai,TamilNadu, India
    Posts
    141

    Thumbs up

    Ok I found the problem

    The same has been posted in a rehat bug in bugzilla

    https://bugzilla.redhat.com/bugzilla....cgi?id=158499


    It was a problem with the system date

    when i gave the date command it showed me a date in 1902

    when i rebooted the machine and went to bios it showed me a date in 2038

    so while boot up i was getting an error message that not able to set system clock because the hardware clock was not in synchronisation or something like that

    Now i changed the hardware clock in bios to the current time 2006, Jan... and the error about clock sync disappeared and the system clock was set...

    The entry in fstab LABEL=/ worked without a problem

  7. #6
    Just Joined!
    Join Date
    Mar 2006
    Posts
    1

    Label =/

    Hi sharon
    you could also change the label from the grub screen by editing the install commands

  8. #7
    Just Joined!
    Join Date
    Oct 2008
    Location
    Jodhpur,INDIA
    Posts
    1
    Quote Originally Posted by maverick666 View Post
    Hi sharon
    you could also change the label from the grub screen by editing the install commands
    LABEL=/ / ext3 defaults 1 1

    LABEL=/var/log /var/log ext3 defaults 1 2


    instead of doing all that , you must have tried

    putting

    LABEL=/1 / ext3 defaults 1 1
    i.e.a 1 after the /
    it worked for me

    and same for the /var/log1
    i dont know the reason still but i got it solved om\n my own

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •