Bug 739691
Summary: | grub2-mkconfig - wrorg UUID for new linux instalation | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Flóki Pálsson <flokip> |
Component: | grub2 | Assignee: | Peter Jones <pjones> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | dennis, extras-orphan, mads, notting, pjones |
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: | 2011-10-24 23:15:39 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: |
Description
Flóki Pálsson
2011-09-19 19:39:01 UTC
(In reply to comment #0) > Description of problem: > After instaling Linux Mint 11 to /dev/sdb8 and runing > grub2-mkconfig -o /boot/grub/grub.cfg /boot/grub ? Fedora grub2 uses /boot/grub2. That is where it places files and that is where it looks for device.map and so on. If you have a shared /boot where some other distro has installed /boot/grub then I guess you should use that distro for updating the config file and you will have to do a lot of manual work to ensure that the distros doesn't step on each others files. (Separate /boot and chain loading will probably be less trouble.) > Fedora F16 form /boot/grub2/grub.cfg > menuentry "linux (on /dev/sdb8)" --class gnu-linux --class gnu --class os { > insmod part_msdos > insmod ext2 > set root='(hd1,msdos8)' > search --no-floppy --fs-uuid --set=root 4b20feaf-9cf7-49b2-896d-94602ce1cded > linux /boot/vmlinuz BOOT_IMAGE=linux > root=UUID=4b20feaf-9cf7-49b2-896d-94602ce1cded resume=/dev/vg_flokid/lv_swap > splash=silent vga=788 > initrd (hd1,7)/boot/initrd.img > } How do the full grub.cfg look like? Is this one of the 10_linux entries or is it from 30_os-prober ? > ubuntu 11.04 form /boot/grub/grub.cfg > menuentry "Linux Mint 11, 2.6.38-8-generic (/dev/sdb8) (on /dev/sdb8)" --class > gnu-linux --class gnu --class os { > insmod part_msdos > insmod ext2 > set root='(/dev/sdb,msdos8)' This is (AFAIK) not valid syntax for grub 1.99 used by Fedora 16. If that works for you then you are using a boot loader that is incompatible with grub 1.99. > search --no-floppy --fs-uuid --set=root 0a9a63db-a434-42e9-9446-fc45776f4d4c > linux /boot/vmlinuz-2.6.38-8-generic > root=UUID=0a9a63db-a434-42e9-9446-fc45776f4d4c ro quiet splash vt.handoff=7 > initrd /boot/initrd.img-2.6.38-8-generic So the Fedora mkconfig also got the initrd wrong? > /dev/sdb8: LABEL="Mandriva" UUID="0a9a63db-a434-42e9-9446-fc45776f4d4c" Mint was installed on the "Mandriva" partition? Yo got me. This bug should bee closed as NOTABUG. >> grub2-mkconfig -o /boot/grub/grub.cfg >/boot/grub ? Fedora grub2 uses /boot/grub2. Yes this is wrong output file an no wonder why F16 could not boot Linux Mint. >How do the full grub.cfg look like? Is this one of the 10_linux entries or is >it from 30_os-prober ? It was from 30_os-prober. But entry from before installation off LINUX mint. >This is (AFAIK) not valid syntax for grub 1.99 used by Fedora 16. If that works >for you then you are using a boot loader that is incompatible with grub 1.99. This is from ubuntu /boot/grub/grub.cfg With grub2-mkconfig -o /boot/grub2/grub.cfg then there is no problem booting to linux Mint on /dev/sd8 I am sorry fore this error bug report. Thanks for pointing that out. I must say that the syntax in Ubuntu is simpler ( update-grub). (In reply to comment #2) > I must say that the syntax in Ubuntu is simpler ( update-grub). Ok, so when we get to the root cause it was really a duplicate of Bug 740953 - RFE: Provide command to easily update grub.cfg ;-) *** This bug has been marked as a duplicate of bug 740953 *** |