On Sun, 2012-11-25 at 18:48 -0700, Michal Jaegermann wrote: > On Sun, Nov 25, 2012 at 03:31:46PM -0800, Chuck Forsberg WA7KGX N2469R wrote: > > Here are the two device.map files. > .... > > > [root@omen grub2]# cat dev*map > > # this device map was generated by anaconda > > (hd0) /dev/sdf > > Hm, grub2 device maps which I have seen looked like that: > > (hd0) /dev/disk/by-id/ata-WDC_WD6401AALS-00L3B2_WD-WCASYA950915 > (hd1) /dev/disk/by-id/ata-WDC_WD1200JS-22MHB0_WD-WCANM9149524 > > with possibly less or more entries but which were allowing to identify > unambiguouslsy about which disks we are really talking about. Why you > are seeing something else I have no idea. Grub2 has for me many dark > corners. Are you getting the same what you quoted if you will run > > grub2-mkdevicemap -n -m /var/tmp/device.map > > Michal He mentioned he disables (or whatever it was) the other drives when installing F18. So assuming F18 works, he adds them back (in whatever way he is doing this) to continue dual booting. Is this maybe causing an issues when they get added back, and redoes the boot order and/or drives or something? -- Mike Chambers Madisonville, KY "Best little town on Earth!" -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
