Bug 438888
| Summary: | fedora can't find uuid at first boot attempt | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | cornel panceac <cpanceac> | ||||||||
| Component: | mkinitrd | Assignee: | Peter Jones <pjones> | ||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | urgent | Docs Contact: | |||||||||
| Priority: | low | ||||||||||
| Version: | 9 | CC: | amlau, davidz, dcantrell, hdegoede, james, maurizio.antillon, wtogami | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2009-02-04 21:38:43 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
cornel panceac
2008-03-25 19:51:31 UTC
Is it reproducible? I talked with the user on IRC and another install attempt will be done. If that attempt reproduces the problem, the user will attach the initrd.img the installer produced. From discussion on IRC it sounded like possibly the necessary modules were not loaded and thus the disks weren't seen. after reinstall same error. i'll attach the initrd. Created attachment 299183 [details]
the initrd after install
Can you please try to get a picture of what's on the screen when you boot. The initrd looks pretty sane Created attachment 299196 [details]
the point where system hangs
Created attachment 299204 [details]
i suppose here is the problem.
as reported elsewhere, x86_64 livecd switches sda with sdb, but after install
fedora returns to the "normal" situation. so maybe that's the reason. you can
see the line wich states that
unable to access resume device /sys/block/sdb//sdb3
out of ideas :)
is there any other info you need? same thing happens with 686 kde livecd (f9beta). i believe the reason is this: https://bugzilla.redhat.com/show_bug.cgi?id=431638 anyway, to get over it, i disabled in bios the second hard disk (sata, seen by the f9beta as /dev/sda _before_ install, and /dev/sdb _after_ install). this way i was able to boot x86_64. unable to access resume device /dev//sys/block/sda//sda3 stil, the system is booting. f9beta x86_64, [guzu@localhost ~]$ rpm -q anaconda anaconda-11.4.0.71-1.x86_64 [guzu@localhost ~]$ rpm -q initscripts initscripts-8.69-1.x86_64 [guzu@localhost ~]$ rpm -q upstart upstart-0.3.9-17.fc9.x86_64 [guzu@localhost ~]$ rpm -q fedora-release fedora-release-8.93-1.noarch [guzu@localhost ~]$ rpm -q kernel kernel-2.6.25-0.204.rc8.git4.fc9.x86_64 kernel-2.6.25-0.218.rc8.git7.fc9.x86_64 [guzu@localhost ~]$ uname -r 2.6.25-0.218.rc8.git7.fc9.x86_64 [guzu@localhost ~]$ uname -a Linux localhost.localdomain 2.6.25-0.218.rc8.git7.fc9.x86_64 #1 SMP Wed Apr 9 19:55:19 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux [guzu@localhost ~]$ is interesting to note that the message is not found in dmesg or /var/log/messages f9 preview live cd x86_64 performed an working install with both hard disks enabled in bios, so, even if someone somewhere (fedora-test list) said that drives order is chosen randomly, i believe this bug was fixed. btw, even on the working pre-preview fully updated x86_64 rawhide, still i could see the message: unable to access resume device /dev//sys/block/sda//sda3 ... Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Closing per comment #11 . |