also check /boot/grub/device.map heres mine
(fd0) /dev/fd0
(hd0) /dev/hda
(hd1) /dev/sda
(hd2) /dev/sdb
(hd3) /dev/sdc
you may be missing something there i have had this problem of drives missing in this file
]]>Now it is telling me no BIOS drives correspond with the disk containing the root partition of my install.
I am running a livecd that uses devfs, could there be some /dev mismatch with my install running udev with regard to creating the /devs?
]]>mount -t proc none /mnt/arch/proc
chroot
cp /proc/mounts /etc/mtab
Err - how? I have not yet done it with chroot method - do you think that would help?
Well, seeing as grub specifically reads its files from /boot, you pretty much have to chroot. I think there's a way to specify the file directly, but chroot-ing is much cleaner
]]>mount -o bind /dev /directory_to_be_chrooted/dev
mount -o bind /proc /directory_to_be_chrooted/proc
That's what I forgot to do when I first chrooted my installation to reinstall grub.
]]>I still have no idea what went wrong. Chrooting into the install was out because the devs aren't mounted so I used a livecd to boot into the part - running grub-install /dev/hda or /dev/hdb resulted in the same errors about "the second sector of stage 2 is unknown"
I only actually discovered there was an error cos I ran sh -x grub-install - without that this little gem:
grep 'Error [0-9]*: ' /temp/grub-install.img.865
It would have totally passed me by and I never would have know grub was stuck in an infinite loop!
So, any suggestions please?
Basically the set up is:
/dev/hda1 - WinXp
/dev/hdb1 - swp
/dev/hdb2 - /
That's it, nothing complex
]]>