| Summary: | Second install of F24 on second hard drive will not boot | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Don Swaner <Gecko8211> | ||||||
| Component: | grub2 | Assignee: | Peter Jones <pjones> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 25 | CC: | lkundrak, pjones | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2016-11-30 21:07:38 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: | |||||||
| Attachments: |
|
||||||||
Created attachment 1226442 [details]
rdsosreport.txt from attempted boot
It's working now - I have no idea why. I got the above error half a dozen times, and ran grub2-mkconfig almost as many times. A comparison of "worked" and "didn't work" versions of grub.cfg are identical, except that hd0/hd1 and sda/sdb are switched - maybe that's it? Note that the first menu entry for the new test Fedora 24 is the rescue kernel, which seems wrong to me, and different than the other instances. However, both F24 rescue kernel and regular kernel both boot now. |
Created attachment 1226441 [details] grub.cfg with old (/dev/sda7) and new (/dev/sdb5) F24 instances Description of problem: I have 2 hard drives. One drive has my "production" instance of F24 installed, working fine. I installed a second "test" instance of F24 on the second hard drive, specifying that there be no boot loader installed. In my new F25, which has the functional grub2 bootloader, I ran grub2-mkconfig to regenerate grub.cfg and tried to boot into the new "test" F24. It fails to switch root. I believe the problem is with grub.cfg. The menuentries generated for the new test F24 look a little peculiar and different than the menuentries for the working production F24. Version-Release number of selected component (if applicable): current F25 grub2-tools (sorry, I'm in F24) How reproducible: Always. Steps to Reproduce: 1. See "Description of problem" Actual results: Unable to boot new test F24 instance. Expected results: Able to boot new test F24 instance. Additional info: