RE: [suse-autoinstall] Disk detection order
-----Original Message----- From: Karsten Künne [mailto:kuenne@rentec.com] Sent: Friday, September 22, 2006 10:55 AM To: suse-autoinstall@suse.com Cc: Marlier, Ian Subject: Re: [suse-autoinstall] Disk detection order
On Friday 22 September 2006 10:11, Marlier, Ian wrote:
Hey, all --
This is returning to an old question for me, as I've started creating 10.1 installation profiles now that the zypp/zmd issues seem to be fixed.
I'm trying to install onto a server with the following: - 2 x 80GB SATA, on a Silicon Image controller, exported as JBOD. - 3 x 250GB SATA, on a 3ware 9550 controller, exported as a single RAID 5
I'm creating a software RAID 1 on the 80GB drives, and using that as the root partition. The RAID5 being partitioned for LVM, though not allocated yet.
When autoyast starts the install, it autodetects the installed hardware (in, I think, alphabetical order?). The 3ware RAID array is detected as /dev/sda, and the two SiI disks as /dev/sdb and /dev/sdc
When the install is complete and the system reboots, this order has switched; the SiI disks are /dev/sda and /dev/sdb, and the 3ware RAID is /dev/sdc.
You have to load the modules for your controllers in the right order. Put them into the <initrd_modules> section in your profile in the proper order, the 3ware module first and then the other one.
Well, I'm hoping to have the 3ware RAID as /dev/sdc, so I have my initrd_modules section set up this way: <initrd_modules config:type="list"> <initrd_module> <module>amd74xx</module> </initrd_module> <initrd_module> <module>sata_sil</module> </initrd_module> <initrd_module> <module>3w_9xxx</module> </initrd_module> <initrd_module> <module>processor</module> </initrd_module> <initrd_module> <module>thermal</module> </initrd_module> <initrd_module> <module>fan</module> </initrd_module> <initrd_module> <module>jbd</module> </initrd_module> <initrd_module> <module>ext3</module> </initrd_module> <initrd_module> <module>raid1</module> </initrd_module> </initrd_modules> But it looks like it doesn't apply to the autoinstall process; the detection order is correct after the first installed boot, but not during the install process itself...
On Friday 22 September 2006 11:11, Marlier, Ian wrote:
-----Original Message----- From: Karsten Künne [mailto:kuenne@rentec.com] Sent: Friday, September 22, 2006 10:55 AM To: suse-autoinstall@suse.com Cc: Marlier, Ian Subject: Re: [suse-autoinstall] Disk detection order
On Friday 22 September 2006 10:11, Marlier, Ian wrote:
Hey, all --
This is returning to an old question for me, as I've started creating 10.1 installation profiles now that the zypp/zmd issues seem to be fixed.
I'm trying to install onto a server with the following: - 2 x 80GB SATA, on a Silicon Image controller, exported as JBOD. - 3 x 250GB SATA, on a 3ware 9550 controller, exported as a single RAID 5
I'm creating a software RAID 1 on the 80GB drives, and using that as the root partition. The RAID5 being partitioned for LVM, though not allocated yet.
When autoyast starts the install, it autodetects the installed hardware (in, I think, alphabetical order?). The 3ware RAID array is detected as /dev/sda, and the two SiI disks as /dev/sdb and /dev/sdc
When the install is complete and the system reboots, this order has switched; the SiI disks are /dev/sda and /dev/sdb, and the 3ware RAID is /dev/sdc.
You have to load the modules for your controllers in the right order. Put them into the <initrd_modules> section in your profile in the proper order, the 3ware module first and then the other one.
Well, I'm hoping to have the 3ware RAID as /dev/sdc, so I have my initrd_modules section set up this way: <initrd_modules config:type="list"> <initrd_module> <module>amd74xx</module> </initrd_module> <initrd_module> <module>sata_sil</module> </initrd_module> <initrd_module> <module>3w_9xxx</module> </initrd_module> <initrd_module> <module>processor</module> </initrd_module> <initrd_module> <module>thermal</module> </initrd_module> <initrd_module> <module>fan</module> </initrd_module> <initrd_module> <module>jbd</module> </initrd_module> <initrd_module> <module>ext3</module> </initrd_module> <initrd_module> <module>raid1</module> </initrd_module> </initrd_modules>
But it looks like it doesn't apply to the autoinstall process; the detection order is correct after the first installed boot, but not during the install process itself...
In that case you have to pull apart the initrd which is loaded during the installation and fix the order there. I believe it's a gzipped cpio archive. Karsten. -- Experience is what you get when you were expecting something else.
Karsten Künne wrote
But it looks like it doesn't apply to the autoinstall process; the detection order is correct after the first installed boot, but not during the install process itself...
In that case you have to pull apart the initrd which is loaded during the installation and fix the order there. I believe it's a gzipped cpio archive.
No you haven't. If anyone would ever check the archives. There was a long thread "Preload modules before hardware detection? (wrong scsi order)" about that topic that contained an easy solution: Use the SLES10 installer for installing 10.1. The SLES10 installed contains a bugfix so that you can (as you should with 10.1, too!) use "insmod=module1 insmod=module2 .." for an append line in pxelinux.cfg or on the command line when booting the installation DVD. Just point to the 10.1 sources with the install= parameter, and the SLES10 linuxrc will load the modules in the order you specfied them via the insmod parameters before starting hardware detection. cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *
participants (3)
-
Frank Steiner -
Karsten Künne -
Marlier, Ian