From Bugzilla Helper: User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/412 (KHTML, like Gecko) Safari/412 Description of problem: Installation completes correctly, however, upon attempting to mount the / partition it gives the error >Checking filesystems [ FAIL ] >fsck.ext3: Unable to resolve 'LABEL=/' in /etc/fstab line 1 LABEL=/ / ext3 defaults 1 1 should be: /dev/hdaX / ext3 defaults 1 1 (where X is where / is located) to fix from the recovery prompt you must remount the / partition in read/write mode, edit /etc/fstab, remount / in read only, reboot. to do this do thus: 1. enter password 2. $> mount -o remount,rw / 3. $> vi /etc/fstab 4. change LABEL=/ to just have it pointing to /dev/hdaX 5. $> mount -o remount,ro / 6. $> Ctrl-D Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. install fedora core 4 test 3 2. let machine reboot 3. see error Actual Results: Checking filesystems [ FAIL ] >fsck.ext3: Unable to resolve 'LABEL=/' in /etc/fstab line 1 LABEL=/ / ext3 defaults 1 1 Expected Results: The machine should finish the booting normally. in /etc/fstab line 1 /dev/hdaX / ext3 defaults 1 1 (where X is where / is located) Additional info: I have only tried this on my iBook 500 dual usb thus far, I will attempt to reproduce it on on other PPC machines.
*** Bug 158500 has been marked as a duplicate of this bug. ***
What does e2label /dev/hdaX show?
Note: I just tried this on my 400 mhz imac and it works fine. Used partitions instead of LVM and thus LABEL=/ is being mounted as / and fsck was fine.
Created attachment 114913 [details] Strace of findfs I've just hit this here: e2label /dev/hda3 /boot findfs LABEL=/boot fails Unable to resolve 'LABEL=/boot'
/etc/blkid.tab is empty.
In addition blkid -c /tmp/foo generates an empty cache file
Found the problem: It was a strange date: # date Sat Jan 9 01:34:48 EST 1904
"unable to resolve LABEL=/boot" My date of /etc/blkid.tab is 01/01/1904. I edited /etc/fstab by hand to use /dev/hda3 so I could get fc5t2 to finish installing (and rawhide has the same issue btw) but this is obviously a bug for FC5. Powerbook has no cmos battery anymore, and relies on ntp for the time and date, which probably explains the dodgey date.
This report targets the FC3 or FC4 products, which have now been EOL'd. Could you please check that it still applies to a current Fedora release, and either update the target product or close it ? Thanks.
Fedora Core 3 and Fedora Core 4 are no longer supported. If you could retest this issue on a current release or on the latest development / test version, we would appreciate that. Otherwise, this bug will be marked as CANTFIX one month from now. Thanks for your help and for your patience.
User pnasrat's account has been closed
Fedora Core 4 is no longer maintained. Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the current Fedora release, please reopen this bug and assign it to the corresponding Fedora version.