[gentoo-user] Problems with AMD64 GRUB booting nvidia SATA JBOD

[gentoo-user] Problems with AMD64 GRUB booting nvidia SATA JBOD

[Neil Leathers]

I attempting to transfer from PATA to SATA on my AMD64 box. The main problem I am having is that GRUB is not booting my new partition. The (one) SATA (Wsetern Digital WD740GD-00FLC0) drive is setup as JBOD (to get windows to install) on an nvidia controller (asus A8N-E bios rev 13). This is AMD64.

I mounted sda2 and installed. Now I cannot get GRUB to launch sda2.

The bootsector grub is installed on is hda.

Thanks,
Neil Leathers
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Problems with AMD64 GRUB booting nvidia SATA JBOD

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 630 bytes --]

On Mon, 2 Oct 2006 20:00:15 -0400, Neil Leathers wrote:

> I mounted sda2 and installed. Now I cannot get GRUB to launch sda2.

The error number would be helpful, as would the contents of menu.lst.

> The bootsector grub is installed on is hda.

It's probably a drive numbering issue, with GRUB numbering the drives
differently to how you expect. Drop to a GRUB shell and do
"find /boot/vmlinuz" (or wherever your kernel is) to see what GRUB calls
your SATA drive. I'd expect it to be (hd1) but that depends on the BIOS
ordering.


-- 
Neil Bothwick

Drive not ready: (R)etry (G)o to Impulse (C)all Engineering

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Problems with AMD64 GRUB booting nvidia SATA JBOD

[Neil Leathers]

[-- Attachment #1: Type: text/plain, Size: 1265 bytes --]

>> I mounted sda2 and installed. Now I cannot get GRUB to launch sda2.
> 
> The error number would be helpful,

17: unable to mount partition

> as would the contents of menu.lst.

Attached (menu.lst points to grub.conf). I also attached the file called device.map that I found in the grub folder.

>> The bootsector grub is installed on is hda.
> 
> It's probably a drive numbering issue, with GRUB numbering the drives
> differently to how you expect. Drop to a GRUB shell and do
> "find /boot/vmlinuz" (or wherever your kernel is) to see what GRUB calls
> your SATA drive. I'd expect it to be (hd1) but that depends on the BIOS
> ordering.

Running

"find /boot/vmlinuz-2.6.17-gentoo-r8"

Produces 15: unable to find file

However:

localhost ~ # mount /dev/sda2 /mnt/floppy/
localhost ~ # ls /mnt/floppy/boot/
boot  config  config-2.6.17-gentoo-r8  grub  kernel.current  kernel.old  System.map  System.map-2.6.17-gentoo-r8  vmlinuz  vmlinuz-2.6.17-gentoo-r8

Also, the floppy seeks for some reason when running find despite not being in the "device.map" file that I found. It is supposed to?

Thanks,
Neil Leathers

> -- 
> Neil Bothwick
> 
> Drive not ready: (R)etry (G)o to Impulse (C)all Engineering

Err engineering... could you you get that drive online?


[-- Attachment #2: grub.conf --]
[-- Type: application/octet-stream, Size: 637 bytes --]

#
# Sample boot menu configuration file
#

# Boot automatically after 30 secs.
timeout 10

# By default, boot the first entry.
default 0

# Fallback to the second entry.
# fallback 1

# For booting GNU/Linux
title gentoo
kernel (hd0,6)/boot/kernel.current root=/dev/hda7

# For booting GNU/Linux
title old
kernel (hd0,6)/boot/kernel.old root=/dev/hda7

# For booting GNU/Linux
title newInstall
kernel (hd1,1)/boot/vmlinuz root=/dev/sda2

# For booting Windows NT
title Windows NT
rootnoverify (hd0,0)
chainloader +1
makeactive

# For installing GRUB into the hard disk
title Install GRUB into the hard disk
root    (hd0,6)
setup   (hd0)

[-- Attachment #3: device.map --]
[-- Type: application/octet-stream, Size: 33 bytes --]

(hd0)	/dev/hda
(hd1)   /dev/sda

Re: [gentoo-user] Problems with AMD64 GRUB booting nvidia SATA JBOD

[Neil Leathers]

> >> I mounted sda2 and installed. Now I cannot get GRUB to launch sda2.
> > 
> > The error number would be helpful,
> 
> 17: unable to mount partition

After poking around I found that the partion was not marked as being of type 0x83. Changing this fixed the problem. It had nothing to do with the software raid or sata.

Thanks for pointing out things to check.
Neil Leathers
-- 
gentoo-user@gentoo.org mailing list