View previous topic :: View next topic |
Author |
Message |
duderonomy Guru
![Guru Guru](/images/ranks/rank_rect_3.gif)
Joined: 20 Mar 2004 Posts: 349 Location: SF Bay Area
|
Posted: Sun Nov 06, 2005 7:49 am Post subject: help understanding affect of 2nd SATA controller on grub |
|
|
I have a ASUS K8N-E Deluxe:
Nvidia chipset provides:
- 2 x Serial ATA
Silicon Image Sil 3114 SATA controller:
- 4 x Serial ATA
Currently I have two drives connected to the main SATA controller.
Grub works fine booting the kernel at this grub identifier (hd0,1).
(hence first disk, 2nd partition)
I simply connect an additional disk to the sil-3114 controller,
then attempt to reboot... I get a kernel panic exactly like those one
gets with grub attempts to access a drive without the appropropriate
driver, for the controller, loaded in the kernel.
It is odd that this is happening... I thought when I went into the checked
in interactive grub menu. the correct drive and partition are indeed at
(hd0,1), just like when the motherboard had only the two drives connected
to the main SATA (and things work perfectly).
Any suggestions? What am I missing? I'm happy to post details
if anyone thinks they can help...
Cheers
D
PS: the Sil-3114 controller is enabled in both scenarios. I am not disabling
the controller in the BIOS when I disconnect the data path cable. |
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
widan Veteran
![Veteran Veteran](/images/ranks/rank_rect_5_vet.gif)
![](images/avatars/142533236243680bda6f27b.jpg)
Joined: 07 Jun 2005 Posts: 1512 Location: Paris, France
|
Posted: Sun Nov 06, 2005 12:03 pm Post subject: Re: help understanding affect of 2nd SATA controller on grub |
|
|
duderonomy wrote: | I simply connect an additional disk to the sil-3114 controller, then attempt to reboot... I get a kernel panic exactly like those one
gets with grub attempts to access a drive without the appropropriate driver, for the controller, loaded in the kernel. |
If you get a kernel panic it's not a grub problem. What happens is that SCSI drive order depends on the order the drivers are loaded. When both are built-in, it depends on the linking order. In your case, sata_sil is initialized before sata_nv, so the drive on the SiI controller shows up as /dev/sda, and the drives on the nVidia controller show up as /dev/sdb and /dev/sdc.
You can either make the sata_sil driver modular (since it's not the boot drive), so the kernel will not see the additional drive until after the sata_nv driver is initialized, or simply change the "root=/dev/sdaX" in grub.conf into "root=/dev/sdbX". |
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|