Success!. Thank you, Gary. I downloaded the 64 bit verison of the boot repair disk and it works; the 32 bit version did not.
Somehow the MBR seems to have gone out of sync with grubsdevices. It looks as if, especially when you chroot to a mountpoint this can happen. If root is mounted on /mnt I think one has to do the following: mount /proc .mnt/proc mount /run /mnt/run mount /sys /mnt/sys mount /dev /mnt/dev mount /dev/pts /mnt/ded/pts before doing chroot. I am not sure of this but I found this in the aptosid manual. Somewhere along the line I did a chroot without this and this may have been the problem, but I am npot sure. Sebastian On Thu, May 23, 2013 at 7:09 PM, Gary Roach <gary719_li...@verizon.net>wrote: > On 05/23/2013 11:30 AM, Sebastian Canagaratna wrote: > > Thank you Klaus. /dev/sda is hd0 and is the permanent hard disk. It has > the MBR on which I want to install > Grub. /dev/sdb is the removable hard disk.Its first partition is, as you > say, hd1,msdos1 on which grub2 is installed > under /boot/grub. After I boot into /dev/sdb1 with supergrub I run > grub-instsll. I am not running any grub or grub rescue > Commands. Grub-install says installation finished. NO errors reported, the > version of grub installed is 1..99 when my > system has grub 2.00-14. On booting, the order is cd, usb ( my removable > harddisk is on usb, and then permanent hard disk. Maybe, as Goh says, > supergrub is messing > up something, but I am mystified as to why even if there were an error, > it is not overwritten by the latest grub-install. > > Sebastian > > > On Thu, May 23, 2013 at 4:14 AM, Klaus Doering <klaus.doering...@gmail.com > > wrote: > >> >> On 23/05/13 00:45, Sebastian Canagaratna wrote: >> >>> I meant to say /dev/sda >>> >> > set root=(hd1,msdos1) >> > >> >> Is your removable hd still attached? IIRC grub counts discs from "0", >> so your "hd1" would then refer to your second hd. Do you have grub >> installed on the aptosid system? What's your BIOS boot preference? >> A mix-up like this could explain why when you reinstalled grub to >> version 2.xx you still get reported back v 1.99 by bootinfoscript. >> >> Klaus >> >> >> >> -- >> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a >> subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org >> Archive: http://lists.debian.org/519dcfee.4090...@gmail.com >> >> > > Hi all, > > Well I just fixed my boot loader problem in about 15 minutes The easy way > is to go to www.sourceforge.net/p/boot-repair/home/Home/ and download the > .iso file of their boot loader repair disk. Burn a disk, stuff it in your > CD/DVD player, reboot your system and sit back and watch the wheels turn. > Punch the Repair button when presented. Remove the disk and reboot. Your > done. This is supposed to work for a range of boot loaders. Great package. > > Gary R. >
