Hi,
I've just upgraded to F17 from F16 using preupgrade. I've just tried running "sudo grub2-mkconfig -o /boot/grub2/grub.cfg" and there are a host of warnings:
Looking at the suggested file /boot/grub2/device.map:
Looks fine to me. /dev/sdb1 is my partition containing my Fedora root.
Any ideas?
---------- Post added at 12:10 PM ---------- Previous post was at 11:01 AM ----------
Nevermind, I've removed the offending line (with /dev/sdb1) on the grounds that it wasn't the "root" (sorry don't know the proper term) of the device. Seems to work OK now.
I've just upgraded to F17 from F16 using preupgrade. I've just tried running "sudo grub2-mkconfig -o /boot/grub2/grub.cfg" and there are a host of warnings:
Code:
/usr/sbin/grub2-probe: warning: the device.map entry `hd1,1' is invalid. Ignoring it. Please correct or delete your device.map.
/usr/sbin/grub2-probe: warning: the device.map entry `hd1,1' is invalid. Ignoring it. Please correct or delete your device.map.
Generating grub.cfg ...
/usr/sbin/grub2-probe: warning: the device.map entry `hd1,1' is invalid. Ignoring it. Please correct or delete your device.map.
/usr/sbin/grub2-probe: warning: the device.map entry `hd1,1' is invalid. Ignoring it. Please correct or delete your device.map.
/usr/sbin/grub2-probe: warning: the device.map entry `hd1,1' is invalid. Ignoring it. Please correct or delete your device.map.
/usr/sbin/grub2-probe: warning: the device.map entry `hd1,1' is invalid. Ignoring it. Please correct or delete your device.map.
/usr/sbin/grub2-probe: warning: the device.map entry `hd1,1' is invalid. Ignoring it. Please correct or delete your device.map.
/usr/sbin/grub2-probe: warning: the device.map entry `hd1,1' is invalid. Ignoring it. Please correct or delete your device.map.
/usr/sbin/grub2-probe: warning: the device.map entry `hd1,1' is invalid. Ignoring it. Please correct or delete your device.map.
Found linux image: /boot/vmlinuz-3.5.0-2.fc17.x86_64
Found initrd image: /boot/initramfs-3.5.0-2.fc17.x86_64.img
/usr/sbin/grub2-probe: warning: the device.map entry `hd1,1' is invalid. Ignoring it. Please correct or delete your device.map.
/usr/sbin/grub2-probe: warning: the device.map entry `hd1,1' is invalid. Ignoring it. Please correct or delete your device.map.
/usr/sbin/grub2-probe: warning: the device.map entry `hd1,1' is invalid. Ignoring it. Please correct or delete your device.map.
/usr/sbin/grub2-probe: warning: the device.map entry `hd1,1' is invalid. Ignoring it. Please correct or delete your device.map.
Found linux image: /boot/vmlinuz-3.4.6-1.fc16.x86_64
Found initrd image: /boot/initramfs-3.4.6-1.fc16.x86_64.img
/usr/sbin/grub2-probe: warning: the device.map entry `hd1,1' is invalid. Ignoring it. Please correct or delete your device.map.
No volume groups found
Found Arch on /dev/sda1
/usr/sbin/grub2-probe: warning: the device.map entry `hd1,1' is invalid. Ignoring it. Please correct or delete your device.map.
/usr/sbin/grub2-probe: warning: the device.map entry `hd1,1' is invalid. Ignoring it. Please correct or delete your device.map.
/usr/sbin/grub2-probe: warning: the device.map entry `hd1,1' is invalid. Ignoring it. Please correct or delete your device.map.
/usr/sbin/grub2-probe: warning: the device.map entry `hd1,1' is invalid. Ignoring it. Please correct or delete your device.map.
Found Windows 7 (loader) on /dev/sda3
/usr/sbin/grub2-probe: warning: the device.map entry `hd1,1' is invalid. Ignoring it. Please correct or delete your device.map.
/usr/sbin/grub2-probe: warning: the device.map entry `hd1,1' is invalid. Ignoring it. Please correct or delete your device.map.
/usr/sbin/grub2-probe: warning: the device.map entry `hd1,1' is invalid. Ignoring it. Please correct or delete your device.map.
/usr/sbin/grub2-probe: warning: the device.map entry `hd1,1' is invalid. Ignoring it. Please correct or delete your device.map.
doneCode:
# this device map was generated by anaconda
(hd0) /dev/sda
(hd1) /dev/sdb
(hd1,1) /dev/sdb1Any ideas?
---------- Post added at 12:10 PM ---------- Previous post was at 11:01 AM ----------
Nevermind, I've removed the offending line (with /dev/sdb1) on the grounds that it wasn't the "root" (sorry don't know the proper term) of the device. Seems to work OK now.