On 12/12/2010 01:54 AM, David C. Rankin wrote:
I have managed to get myself in a number of messes over the years, but usually when I figure out what went wrong, I understand why. Here, I'm at a complete loss.
I was going to preserve my existing kernel through update and I described in an earlier email. (I'm still on kernel26-2.6.36.1) So I created a custom initramfs and preserved the module tree and added the entries to grub menu.lst. This box has always booted arch on (hd1,5) a device mapper array. (hd0) is another device mapper array with an old suse install on it. However, after I made may changes and went to reboot to test the custom initramfs, I got a grub 13 error for an invalid executable??
So I booted with the Arch 2010.05 install disk and chrooted my existing install and looked at grub. When I did my grub > find /boot/grub/stage1, grub reported stage1 on
(hd0,4) (hd2,4)
WTF? I don't have an hd2 and what the heck happened to hd1??
[01:42 archangel:/boot/grub] # cat device.map (hd0) /dev/mapper/nvidia_fdaacfde (hd1) /dev/mapper/nvidia_baaccaja (fd0) /dev/fd0
So I decided to give booting to hd2 a try. So I reconfigured the suse menu.lst file to call (hd2,5) to boot Arch, and I redid the Arch menu.lst to point everything at (hd2,5) instead of (hd1,5) and rebooted. To my shock and surprise - it booted just fine with all the drive number flipped from 1->2.
With great trepidation after the grub root number change, I went ahead and updated to 2.6.36-2 and all worked fine. Even though I'm still booting to hd2, it boots just fine. Dunno why or what caused the change... Oh well... -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com