Bug 868473
Summary: | grub2-probe error cannot find a GRUB drive for /dev/sda1 on btrfs raid0 | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Chris Murphy <bugzilla> | ||||||||
Component: | grub2 | Assignee: | Peter Jones <pjones> | ||||||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | medium | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 18 | CC: | bcl, dcantrell, dennis, gczarcinski, jbacik, mads, pjones, vserbine | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | Unspecified | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2013-01-12 19:35:08 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: | |||||||||||
Attachments: |
|
Description
Chris Murphy
2012-10-20 04:05:12 UTC
OK so the resulting grub.cfg's are different but only the menuentry line appears affected. In the single disk btrfs case, the menuentry line includes the root UUID. Whereas in the 2 disk raid0 btrfs case, the menuentry line contains /dev/sda1 /dev/sdb1 instead; although the proper UUID appears within the entry on the search and linux lines. Weird. Appears benign. Attaching the two grub.cfg. Created attachment 630354 [details]
btrfs single disk grub.cfg
Created attachment 630355 [details]
btrfs raid0 2-disk grub.cfg
Created attachment 630624 [details]
bash -x grub2-mkconfig
I think this may be related.
grub2-probe --target=device /
returns this:
+ GRUB_DEVICE='/dev/sda1
/dev/sdb1'
Speculate that the CR in between these is tripping up grub2-probe later on when it's trying to figure out what to put in the menuentry, a /dev device or UUID?
Pretty sure for anything else, / would return just a single device? Whereas with btrfs volumes, / isn't mapped to something like /dev/md0, but rather each constituent physical device.
I think 4 devices returned for raid10 volume containing / is a realistic scenario in the near term.
I tried F18b TC7 and tried to: 1mb biosboot the rest a btrfs for /boot, swap, /. I just created a mount point for / with the desired size. Anaconda complained that /boot must be not a subvolume. Does actually grub2 support btrfs subvolumes? (in this case, it was a single disks setup). Sorry, this was for another bug-report. Yes Chris, this is a dup of my report although is was not obvious at first. Even more important is that there was some critical info here which says my initial patch which removed some double quotes so that the list of devices was on a single line is the correct fix. This is the same as line 133 in grub2-mkconfig. *** This bug has been marked as a duplicate of bug 890955 *** |