Hi Adam, Please don't direct emails to me directly - that's what the slug email list is for :-)
Thanks, Sonia. On Mon, 29 Aug 2011 10:10:45 +1200, "adam.bogacki" <adam.boga...@clear.net.nz> said: > I am trying to reinstall GNU GRUB 1.97~beta4 on an Ubuntu > WattOS RC1 (/dev/sda) / Debian 6 (/dev/sdb) dual-boot > system. > > sudo fdisk -l > > Disk /dev/sda: 200.0 GB, 200049647616 bytes > 255 heads, 63 sectors/track, 24321 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > Disk identifier: 0x00000001 > > Device Boot Start End Blocks Id > System > /dev/sda1 * 1 23572 189342058+ 83 > Linux > /dev/sda2 23573 24321 6016312 5 > Extended > /dev/sda5 23573 24321 6016311 82 > Linux swap / Solaris > > Disk /dev/sdb: 320.1 GB, 320072933376 bytes > 255 heads, 63 sectors/track, 38913 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > Disk identifier: 0x00060463 > > Device Boot Start End Blocks Id > System > /dev/sdb1 1 38127 306246656 83 > Linux > /dev/sdb2 38127 38914 6322177 5 > Extended > /dev/sdb5 > > I mount dev, proc, sys, and usr on /dev/sda (aka w1), and > > guest@guest:~$ sudo chroot /mnt/w1 /bin/bash > root@guest:/# update-grub2 > root@guest:/# grub-install /dev/sda > /usr/sbin/: Not found. > > I'm stumped. > > I have previously done > > root@guest:/# grub-install /dev/sda1 > > getting ... > > init[1]: segfault at 0 ip (null) sp bfd65e44 error 4 > kernel panic - not syncing: Attempted to kill init ! > Pid: 1 comm: init Not tainted > 2.6.31-23-generic # 75-Ubuntu > > .. but have since become aware I should not specify > partition number. > > Inspecting files on the WattOSRC1 drive (w1), it seems I > have two GRUB folders > > guest@guest:/mnt/w1$ ls > bin debootstrap grub initrd.img.old man1 > openbox proc sbin sys var > boot dev home lib media opt > resolv.conf selinux tmp vmlinuz > cdrom etc initrd.img lost+found mnt opt1 > root srv usr vmlinuz.old > > > and > > guest@guest:/mnt/w1/boot$ ls > bin debootstrap grub initrd.img.old man1 > openbox proc sbin sys var > boot dev home lib media opt > resolv.conf selinux tmp vmlinuz > cdrom etc initrd.img lost+found mnt opt1 > root srv usr vmlinuz.old > > The best way to get a working dual-boot GRUB2 seems to be to > delete one of the grub folders, and tell GRUB2 where the > kernel and root fs are. > > I have been messing around with rescue prompt boot > instructions and have been able to > boot into the debian drive, initially in graphic (with > stationary mouse) and later in text mode, but it seems a bit > hit and miss, lately mostly miss. Dunno why .. maybe too > many changes. > > I'd appreciate any constructive advice as I am about to move > house and will be off-line for a while. I'm starting to > appreciate Live-CDs. > > Cheers, > > Adam Bogacki, > > adam.boga...@clear.net.nz > > -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
