Bug 158499
Summary: | findfs fails to find label after install | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Adam Hitchcock <adam.hitchcock.05> | ||||
Component: | anaconda | Assignee: | Peter Jones <pjones> | ||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Mike McLean <mikem> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 4 | CC: | mattdm, richard | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | powerpc | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2008-02-16 15:47:15 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Adam Hitchcock
2005-05-23 02:30:33 UTC
*** 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. |