Bug 586607
Summary: | anaconda unable to find a single storage device | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Michal Jaegermann <michal> | ||||||||||||
Component: | udev | Assignee: | Harald Hoyer <harald> | ||||||||||||
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
Severity: | medium | Docs Contact: | |||||||||||||
Priority: | low | ||||||||||||||
Version: | rawhide | CC: | harald, hdegoede, jonathan, vanmeeuwen+fedora | ||||||||||||
Target Milestone: | --- | ||||||||||||||
Target Release: | --- | ||||||||||||||
Hardware: | All | ||||||||||||||
OS: | Linux | ||||||||||||||
Whiteboard: | |||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||
Clone Of: | Environment: | ||||||||||||||
Last Closed: | 2010-04-28 07:36:52 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
Michal Jaegermann
2010-04-28 00:14:58 UTC
Created attachment 409624 [details]
an output of blkid run from anaconda shell
Created attachment 409627 [details]
anaconda.log from a "rescue" boot
Created attachment 409628 [details]
syslog from a "rescue" boot
Created attachment 409630 [details]
storage.log from a "rescue" boot
Created attachment 409631 [details]
program.log from a "rescue" boot
Loads of messages like this in your storage.log. [2010-04-27 23:34:36,426] DEBUG: db entry /dev/.udev/db/\x2fdevices\x2fpci0000:00\x2f0000:00:08.0\x2fhost0\x2ftarget0:0:0\x2f0:0:0:0\x2fblock\x2fsda does not exist [2010-04-27 23:34:36,427] DEBUG: db entry /dev/.udev/db/\x2fdevices\x2fpci0000:00\x2f0000:00:08.0\x2fhost0\x2ftarget0:0:0\x2f0:0:0:0\x2fblock\x2fsda\x2fsda1 does not exist [2010-04-27 23:34:36,428] DEBUG: db entry /dev/.udev/db/\x2fdevices\x2fpci0000:00\x2f0000:00:08.0\x2fhost0\x2ftarget0:0:0\x2f0:0:0:0\x2fblock\x2fsda\x2fsda2 does not exist [2010-04-27 23:34:36,428] DEBUG: db entry /dev/.udev/db/\x2fdevices\x2fpci0000:00\x2f0000:00:08.0\x2fhost0\x2ftarget0:0:0\x2f0:0:0:0\x2fblock\x2fsda\x2fsda3 does not exist [2010-04-27 23:34:36,429] DEBUG: db entry /dev/.udev/db/\x2fdevices\x2fpci0000:00\x2f0000:00:08.0\x2fhost0\x2ftarget0:0:0\x2f0:0:0:0\x2fblock\x2fsda\x2fsda4 does not exist (In reply to comment #6) > Loads of messages like this in your storage.log. Yes, I know. Only I do not know what to make of these. what's the output (in the installer shell) of: # udevadm info --query=all --name=/dev/<insert name of device node> for the sd* disks The "db entry %s does not exist" message is not present in any recent F-13 install.img, it looks like you were using an F-13 stage1 (vmlinuz + initrd) with an F-12 (or old F-13) stage2 (install.img). (In reply to comment #9) > it looks like you were using an F-13 stage1 (vmlinuz + initrd) > with an F-12 (or old F-13) stage2 (install.img). You are right. My bad. This was wrong install.img and after correcting that indeed disk partitions were found. Although on the first try anaconda got spooked by a typo in one of "noauto" fstab entries and refused to mount from there anything save a top level file system from an installation to be "rescued". That took me a bit by surprise. Following fstab edit the next attempt fared better. |