[Bug 637226] New: Hard disk ordering change that affects the install.
https://bugzilla.novell.com/show_bug.cgi?id=637226 https://bugzilla.novell.com/show_bug.cgi?id=637226#c0 Summary: Hard disk ordering change that affects the install. Classification: openSUSE Product: openSUSE 11.4 Version: Milestone 1 of 6 Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain@novell.com ReportedBy: stiening@comcast.net QAContact: jsrain@novell.com Found By: --- Blocker: --- User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; InfoPath.2) I have a system with 9 disks. The system disk is attached to an AMD controller on the motherboard. The remaing 8 disks (raid) are attached to two pcie controller cards (adaptec). In versions of openSUSE 11.1 and earlier the system disk is reported as /dev/sda. In openSUSE 11.4 milestone 1 the system disk is reported as /dev/sdi. The install fails with a notice to the effect that the bios can report only 8 disks and that manual intervention is required to specify a place for the boot loader. The workaround is to remove the 8 raid disks and reinstall the system. When the raid controllers are plugged in again the newly installed system boots just fine. I'll provide more detailed information if requested to do so. The same hardware was used in all of the tests described here. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=637226 https://bugzilla.novell.com/show_bug.cgi?id=637226#c1 Jiri Srain <jsrain@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsrain@novell.com AssignedTo|jsrain@novell.com |juhliarik@novell.com --- Comment #1 from Jiri Srain <jsrain@novell.com> 2010-09-06 06:37:08 UTC --- Rae, if you use disks connected to multiple adapters, I strongly recommend you should use persistent device names. The system disk (/dev/sda) may turn to /dev/sdi and back with any upgrade, as the naming depends on the order of driver initialization, which is not defined anywhere. BIOS reports only 8 disks, but the one you boot is always included - just reorder the disks so that the one which you boot is the first (it always is, from the BIOS POV). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=637226 https://bugzilla.novell.com/show_bug.cgi?id=637226#c2 --- Comment #2 from Rae Stiening <stiening@comcast.net> 2010-09-06 15:07:29 UTC --- Thank you for replying. I am using an ASUS M4A785TD-V EVO motherboard. I start with a wiped system disk (dd if=/dev/zero of=/dev/...) attached to the motherboard interface and have chosen the AHCI interface option in the motherboard BIOS. There are 8 raid disks attached to two Adaptec 1430SA controller cards installed as well. I start the install from the CDROM. I decline the "use auto configuration option." I select the other/minimal server selection option. The installer chooses /dev/sdi for the system disk. (the right choice) In the next window I get the message under "Booting": "Configure a valid boot loader location before continuing. The device map includes more than 8 devices and the boot device is out of range. The range is limited by the BIOS to the first 8 devices". It isn't clear how to respond to this instruction. If I repeat the install process with the 8 raid disks removed the openSUSE installs normally. If I then reconnect the 8 raid disks openSUSE boots normally. In regard to using persistant device names I normally load the system disk by volume label. I have done this in the past because it allows the simple backup method of using dd to copy the system disk to a backup disk. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=637226 https://bugzilla.novell.com/show_bug.cgi?id=637226#c Jozef Uhliarik <juhliarik@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|juhliarik@novell.com |jreidinger@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=637226 https://bugzilla.novell.com/show_bug.cgi?id=637226#c3 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |stiening@comcast.net --- Comment #3 from Josef Reidinger <jreidinger@novell.com> 2010-10-01 07:14:20 UTC --- OK, explanation why this happen: some BIOS has restriction to use for boot just first eight disks. This error mean, that BIOS is limited to recognize 8 discs. So what you need do, is to fill up in device.map section in bootloader 8 discs which see your BIOS. ( of course you can change order in BIOS to provide enough information. If your /dev/sdi disc is really first in BIOS (it can happen as some BIOS doesn't correct provide required information), then just correct BIOS order in device map settings. What message you find useful in this case? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=637226 https://bugzilla.novell.com/show_bug.cgi?id=637226#c4 --- Comment #4 from Rae Stiening <stiening@comcast.net> 2010-10-01 12:54:36 UTC --- (In reply to comment #3)
OK, explanation why this happen: some BIOS has restriction to use for boot just first eight disks. This error mean, that BIOS is limited to recognize 8 discs. So what you need do, is to fill up in device.map section in bootloader 8 discs which see your BIOS. ( of course you can change order in BIOS to provide enough information. If your /dev/sdi disc is really first in BIOS (it can happen as some BIOS doesn't correct provide required information), then just correct BIOS order in device map settings. What message you find useful in this case?
I would like to be able to install SuSE without having to disconnect disks during the install procedure. The order in which Linux gives disks device names is dependent on the order in which driver modules are loaded. The problem occurs because the SuSE installer loads the module for the system disk after it has loaded driver modules for the hardware used for the eight other disks. If SuSE is installed with the eight other disks disconnected the system boots with the eight other disks reconnected because the installed SuSE loads the system disk driver first. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=637226 https://bugzilla.novell.com/show_bug.cgi?id=637226#c5 --- Comment #5 from Josef Reidinger <jreidinger@novell.com> 2010-10-01 13:02:26 UTC --- It should not be related to assigned name. Correct BIOS order is importent, so in grub it can be hd0 for /dev/sdi . So boot order in BIOS should be important information (BIOS order mean in which order BIOS check bios for boot information). If you have properly set BIOS order so first disk is one from which you boot, then it is enough if you just change order of disks in grub device map in yast2-bootloader -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=637226 https://bugzilla.novell.com/show_bug.cgi?id=637226#c6 --- Comment #6 from Rae Stiening <stiening@comcast.net> 2010-10-01 13:20:29 UTC --- (In reply to comment #5)
It should not be related to assigned name. Correct BIOS order is importent, so in grub it can be hd0 for /dev/sdi . So boot order in BIOS should be important information (BIOS order mean in which order BIOS check bios for boot information). If you have properly set BIOS order so first disk is one from which you boot, then it is enough if you just change order of disks in grub device map in yast2-bootloader
The motherboard BIOS has always been set to boot from the system disk. The SuSE install halts with an error message. What procedure should be used when the error message appears? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=637226 https://bugzilla.novell.com/show_bug.cgi?id=637226#c7 --- Comment #7 from Josef Reidinger <jreidinger@novell.com> 2010-10-01 13:40:42 UTC --- (In reply to comment #6)
(In reply to comment #5)
It should not be related to assigned name. Correct BIOS order is importent, so in grub it can be hd0 for /dev/sdi . So boot order in BIOS should be important information (BIOS order mean in which order BIOS check bios for boot information). If you have properly set BIOS order so first disk is one from which you boot, then it is enough if you just change order of disks in grub device map in yast2-bootloader
The motherboard BIOS has always been set to boot from the system disk. The SuSE install halts with an error message. What procedure should be used when the error message appears?
You should modifu device map and place system disk as first disk in device map. Boot Loader Installation (tab) -> Boot Loader Installation Details and move system disc up. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=637226 https://bugzilla.novell.com/show_bug.cgi?id=637226#c8 --- Comment #8 from Rae Stiening <stiening@comcast.net> 2010-10-01 16:14:44 UTC --- (In reply to comment #7)
(In reply to comment #6)
(In reply to comment #5)
It should not be related to assigned name. Correct BIOS order is importent, so in grub it can be hd0 for /dev/sdi . So boot order in BIOS should be important information (BIOS order mean in which order BIOS check bios for boot information). If you have properly set BIOS order so first disk is one from which you boot, then it is enough if you just change order of disks in grub device map in yast2-bootloader
The motherboard BIOS has always been set to boot from the system disk. The SuSE install halts with an error message. What procedure should be used when the error message appears? You should modifu device map and place system disk as first disk in device map. Boot Loader Installation (tab) -> Boot Loader Installation Details and move system disc up.
I am still working with 11.4 Milestone 1 If I allow the SuSE installer to use its default partitioning... swap /dev/sdi1 root /dev/sdi2 home /dev/sdi3 I get the error message that we have been discussing. On the other hand if I choose the "create partition setup" and "custom (for experts) and partition as follows swap /dev/sdi1 root /dev/sdi2 (i.e. without creating a separate partition for home) the installation proceeds without errors. Is this behavior consistent with your analysis of the problem? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=637226 https://bugzilla.novell.com/show_bug.cgi?id=637226#c9 --- Comment #9 from Josef Reidinger <jreidinger@novell.com> 2010-10-04 07:43:16 UTC --- OK, it is strange. Then could you please attach yast logs from both case to compare what happen? http://en.opensuse.org/openSUSE:Bugreport_YaST -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=637226 https://bugzilla.novell.com/show_bug.cgi?id=637226#c10 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|stiening@comcast.net | Resolution| |NORESPONSE --- Comment #10 from Josef Reidinger <jreidinger@novell.com> 2010-12-03 16:28:32 UTC --- no response for 2 months. If you find logs, then please attach it and reopen bug -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com