Bug 853988
| Summary: | liveinstall: kernel panic - unable to mount root fs on unknown-block(0,0) | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kamil Páral <kparal> | ||||||||||||
| Component: | anaconda | Assignee: | Brian Lane <bcl> | ||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 18 | CC: | anaconda-maint-list, awilliam, g.kaviyarasu, jonathan, jreznik, robatino, vanmeeuwen+fedora, vpodzime | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | Unspecified | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | AcceptedBlocker | ||||||||||||||
| Fixed In Version: | anaconda-18.6.6-1 | Doc Type: | Bug Fix | ||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2012-09-17 22:53:56 UTC | Type: | Bug | ||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||
| Documentation: | --- | CRM: | |||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
| Embargoed: | |||||||||||||||
| Bug Depends On: | |||||||||||||||
| Bug Blocks: | 752654 | ||||||||||||||
| Attachments: |
|
||||||||||||||
Created attachment 609393 [details]
grub
Proposing as a blocker: " In most cases (see Blocker_Bug_FAQ), a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to the 'firstboot' utility on the first boot after installation, without unintended user intervention, unless the user explicitly chooses to boot in non-graphical mode. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied. The firstboot utility must be able to create a working user account " https://fedoraproject.org/wiki/Fedora_18_Alpha_Release_Criteria +1 blocker per criterion cited. +1 blocker. We need log files in order to debug installation problems. Created attachment 609905 [details]
anaconda.log
Created attachment 609906 [details]
storage.log
Created attachment 609908 [details]
program.log
program.log has 10MB, so I had to compress it. It is really intended to list every file on the filesystem in that log?
Anaconda calls grub2-mkconfig. But since there is only initrd-plymouth.img, which is ignored by grub2-mkconfig. Maybe anaconda should call 'dracut -f' in chroot before running grub2-mkconfig? Discussed at 2012-09-05 blocker review meeting. Accepted as a blocker per criterion "In most cases, a system installed according to any of the above criteria must boot to the 'firstboot' utility on the first boot after installation, without unintended user intervention, unless the user explicitly chooses to boot in non-graphical mode. The firstboot utility must be able to create a working user account". anaconda-18.6.6-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.6.6-1.fc18 Package anaconda-18.6.6-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-18.6.6-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-13611/anaconda-18.6.6-1.fc18 then log in and leave karma (feedback). This is fixed with F18 Alpha RC2. System boots, initrd is not missing. 18.6.7 went stable, so closing this. anaconda-18.6.6-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. |
Created attachment 609392 [details] kernel panic during boot Description of problem: I did an install of F18 Alpha TC5 i686 Live, all defaults. After reboot, I see: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) If I see grub menu, it has root=/dev/vda3 (is that correct for default anaconda install?), but it seems to lack any initrd item. Version-Release number of selected component (if applicable): F18 Alpha TC5 i686 Live How reproducible: always Steps to Reproduce: 1. install live using defaults 2. reboot