kanotix.com :: Thema anzeigen - Grub cannot find 2nd HD after Thorhammer install

kanotix.com

Installation - Grub cannot find 2nd HD after Thorhammer install

gtpeacock - 14.09.2007, 04:08 Uhr
Titel: Grub cannot find 2nd HD after Thorhammer install

I have Mint installed on a second hard drive. The command

chainloader (hd1,0)+1 worked fine to get to the Mint GRUB on my older Kanotix install, but now with Thorhammer this does not work. Grub-install found the Mint kernels and set them up, but they also fail. For some reason the new Grub installation cannot find the second drive.

I have several other partitions on my first drive that all work great, for example

chainloader (hd0,5)+1

works fine. The only one that does not work is the one pointing to the second drive. Any ideas?

ockham23 - 14.09.2007, 07:41 Uhr
Titel: Grub cannot find 2nd HD after Thorhammer install

Please post the output of

Code:

cat /boot/grub/menu.lst

su

fdisk -l

blkid

Kano - 14.09.2007, 12:09 Uhr
Titel: Grub cannot find 2nd HD after Thorhammer install

Check BIOS if the drive is mentioned there.

gtpeacock - 15.09.2007, 01:30 Uhr
Titel: output of menu.lst, fdisk -l, and

root@Frankenputer:/home/gtp# cat /boot/grub/menu.lst

title Debian GNU/Linux, kernel 2.6.22-10-generic
root (hd0,9)
kernel /boot/vmlinuz-2.6.22-10-generic root=UUID=dbd4ea2a-5284-4fc2-8fa7-318c2c7c8427 ro splash vga=791 quiet
initrd /boot/initrd.img-2.6.22-10-generic

title Debian GNU/Linux, kernel memtest86+
root (hd0,9)
kernel /boot/memtest86+.bin

### END DEBIAN AUTOMAGIC KERNELS LIST
title Windows 95/98/Me
chainloader (hd0,0)+1

title hda5 Mepis
chainloader (hd0,4)+1

title hda6 Ubuntu
chainloader (hd0,5)+1

title hda7 PCLinuxOS
chainloader (hd0,6)+1

title hda8 Xubuntu
chainloader (hd0,7)+1

title hdb1 Mint
map (hd0)(hd1)
map (hd1)(hd0)
chainloader (hd1,0)+1

#title Mint, kernel 2.6.20-16-generic
#root (hd1,0)
#kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=dbd4ea2a-5284-4fc2-8fa7-318c2c7c8427 ro quiet splash
#initrd /boot/initrd.img-2.6.20-16-generic

#title Mint, kernel 2.6.20-15-generic
#root (hd1,0)
#kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=dbd4ea2a-5284-4fc2-8fa7-318c2c7c8427 ro quiet splash
#initrd /boot/initrd.img-2.6.20-15-generic

root@Frankenputer:/home/gtp# fdisk -l

Disk /dev/sda: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 365 2931831 b W95 FAT32
/dev/sda2 366 370 40162+ 83 Linux
/dev/sda3 371 433 506047+ 82 Linux swap / Solaris
/dev/sda4 434 4865 35600040 5 Extended
/dev/sda5 434 1042 4891761 83 Linux
/dev/sda6 * 1043 1651 4891761 83 Linux
/dev/sda7 1652 2260 4891761 83 Linux
/dev/sda8 2261 2869 4891761 83 Linux
/dev/sda9 2870 4086 9775521 b W95 FAT32
/dev/sda10 4087 4865 6257286 83 Linux

Disk /dev/sdb: 13.6 GB, 13601193984 bytes
255 heads, 63 sectors/track, 1653 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 1653 13277691 83 Linux

root@Frankenputer:/home/gtp# blkid

/dev/sda1: LABEL="WIN98" UUID="0000-0E53" TYPE="vfat"
/dev/sda2: UUID="54ed655b-3d0c-4401-83f4-b87a430b470a" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda6: UUID="4aaf3175-8ecb-44c6-9f69-2530ef77e2d2" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda7: LABEL="home" UUID="28e1399c-ef5a-4ff0-83d2-82d2e5434d4a" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda8: UUID="070f2e00-9542-4aab-ae8a-6e98c93ef2cd" LABEL="Xubuntu" TYPE="reiserfs"
/dev/sda10: UUID="dbd4ea2a-5284-4fc2-8fa7-318c2c7c8427" TYPE="reiserfs"
/dev/sdb1: UUID="a8b9f22f-ea48-4972-9046-291f0bc48c92" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda3: UUID="a2eb84dc-f740-44e5-9eab-d88c0c74e1ef" TYPE="swap"
/dev/sda5: UUID="a5e4e5ea-ec5c-4569-852b-c367de699df1" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda9: LABEL="HDA9" UUID="E9F1-0200" TYPE="vfat"

You can see in the menu.lst that I have commented out some of the options that did not work. I can mount the second drive with no problem, so I assume it is not a bios issue. This worked fine before I upgraded to Thorhammer, so it seems to have something to do with grub on this new version.

Kano - 15.09.2007, 01:45 Uhr
Titel: output of menu.lst, fdisk -l, and

You can not use map command for Linux. As soon as the kernel loads it must use the saved root=... value. map is only for Win/Dos and other easy systems which have no root Option.

gtpeacock - 16.09.2007, 02:36 Uhr
Titel: RE: output of menu.lst, fdisk -l, and

I added the mapping commands in desperation after it would not work. Can you recommend a chainloader command that will get me to the second hard drive? This worked fine with no problems before I upgraded.

eco2geek - 16.09.2007, 06:07 Uhr
Titel:

gtpeacock hat folgendes geschrieben::

#title Mint, kernel 2.6.20-16-generic
#root (hd1,0)
#kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=dbd4ea2a-5284-4fc2-8fa7-318c2c7c8427 ro quiet splash
#initrd /boot/initrd.img-2.6.20-16-generic

#title Mint, kernel 2.6.20-15-generic
#root (hd1,0)
#kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=dbd4ea2a-5284-4fc2-8fa7-318c2c7c8427 ro quiet splash
#initrd /boot/initrd.img-2.6.20-15-generic

That's the UUID for sda10, no? Not the UUID for sdb1, which is what you want?

gtpeacock hat folgendes geschrieben::

/dev/sda10: UUID="dbd4ea2a-5284-4fc2-8fa7-318c2c7c8427" TYPE="reiserfs"
/dev/sdb1: UUID="a8b9f22f-ea48-4972-9046-291f0bc48c92" SEC_TYPE="ext2" TYPE="ext3"

It may not be in keeping with this newfangled UUID thing, but you still should also be able to use something like

title Mint, kernel 2.6.20-15-generic
root (hd1,0)
kernel /boot/vmlinuz-2.6.20-15-generic root=/dev/sdb1 ro quiet splash
initrd /boot/initrd.img-2.6.20-15-generic

to start it.

gtpeacock - 20.09.2007, 01:56 Uhr
Titel:

I can try that, but I am really trying to get chainloader to work so that I can address grub installed on the second disk (for Mint). I have tried:

root (hd1,0)
chainloader +1

and

chainloader (hd1,0)+1

Neither worked. I get a Grub error #13.

ockham23 - 20.09.2007, 21:20 Uhr
Titel:

Maybe the chainloader command fails because there's no bootloader installed in partition #1 on hd1. If grub is located in the MBR of hd1, the chainloader command pointing to partition #1 won't find it.

gtpeacock - 21.09.2007, 03:17 Uhr
Titel:

Yes! That was it. Mint Grub was on HD1 instead of HD0,1. It was time for Mint to go anyway, so now the second drive has Vector Linux with LILO installed on the partition, and chainloader (hd1,0)+1 gets me there.

Looks like Kanotix and grub were fine all along... imagine that...

Thanks for your help!