On 9.1 machines it seems SCSI disks get swapped, compared with 8.1, 8.2, and 9.0. This is on a Dell poweredge 2650, the onboard Perc3/Di was /dev/sda, now it's sdb. The Perc4DC PCI card with an external enclosure was /dev/sdb, now it's sda. Anyone know enough about 2.4 and 2.6 kernels to say if the new kernel is (or isn't) the reason for the swap? TIA, michaelj -- Michael James michael.james@csiro.au System Administrator voice: 02 6246 5040 CSIRO Bioinformatics Facility fax: 02 6246 5166
I've noticed the same thing with 9.0 and Red Hat 7.3 & Win4Lin. I used to use Win4Lin with RH 7.3, but when I installed SuSE 9.0. the disk order was different. Then when I tried to install Win4Lin, it saw the disks the same way as RH, and in the process, made my system unusable. Both RH 7.3 and SuSE 9.0, use a 2.4 kernel. Michael James wrote:
On 9.1 machines it seems SCSI disks get swapped, compared with 8.1, 8.2, and 9.0.
This is on a Dell poweredge 2650, the onboard Perc3/Di was /dev/sda, now it's sdb.
The Perc4DC PCI card with an external enclosure was /dev/sdb, now it's sda.
Anyone know enough about 2.4 and 2.6 kernels to say if the new kernel is (or isn't) the reason for the swap?
TIA, michaelj
Michael James wrote:
On 9.1 machines it seems SCSI disks get swapped, compared with 8.1, 8.2, and 9.0.
This is on a Dell poweredge 2650, the onboard Perc3/Di was /dev/sda, now it's sdb.
The Perc4DC PCI card with an external enclosure was /dev/sdb, now it's sda.
Anyone know enough about 2.4 and 2.6 kernels to say if the new kernel is (or isn't) the reason for the swap?
I doubt it - the order in which SCSI controllers are recognized depends on the order in which the respective modules are loaded. It sounds like you might need to have a look at /etc/modules.conf. This identifies your first or only adapter: alias scsi_hostadapter aic7xxx try this (YMMV): alias scsi_hostadapter allmyadapters probeall allmyadapters <perc3> <perc4> Also 'man modules.conf'. /Per Jessen -- Let your spam stop here - http://www.spamchek.com
Per Jessen writes:
Anyone know enough about 2.4 and 2.6 kernels to say if the new kernel is (or isn't) the reason for the swap?
I doubt it - the order in which SCSI controllers are recognized depends on the order in which the respective modules are loaded. It sounds like you might need to have a look at /etc/modules.conf. ...
Plausible explanation. However you should also look at the INITRD_MODULES= line in your /etc/sysconfig/kernel file. This specifies kernel modules that should be loaded early in the boot process, before the root filesystem is mounted. The order of these also determines which disks come up as sda, sdb, etc (that is, if the disks are connected to separate SCSI adapters controlled by different kernel modules).
Also 'man modules.conf'.
With a 2.6 kernel this has been changed to modprobe.conf. -Ti
Ti Kan wrote:
Plausible explanation. However you should also look at the INITRD_MODULES= line in your /etc/sysconfig/kernel file. This specifies kernel modules that should be loaded early in the boot process, before
Ah yes, very true. I never use a stock SuSE kernel and almost never use an initrd, so it didn't occur to me to mention that. /Per Jessen, Zurich -- Let your spam stop here - http://www.spamchek.com
Torsdag den 19. august 2004 10:16 skrev Per Jessen:
Ti Kan wrote:
Plausible explanation. However you should also look at the INITRD_MODULES= line in your /etc/sysconfig/kernel file. This specifies kernel modules that should be loaded early in the boot process, before
Ah yes, very true. I never use a stock SuSE kernel and almost never use an initrd, so it didn't occur to me to mention that.
Trying to summarize is this the issue/reason when ide-devices is "found" before SATA devices (ASUS P4C800E-Deluxe board). And what about the case with Promise ide-controllers they're also detected before drives on regular controllers (read controllers on the main board) ?? Johan
/Per Jessen, Zurich
-- Let your spam stop here - http://www.spamchek.com
Johan Nielsen writes:
Torsdag den 19. august 2004 10:16 skrev Per Jessen:
Ti Kan wrote:
Plausible explanation. However you should also look at the INITRD_MODULES= line in your /etc/sysconfig/kernel file. This specifies kernel modules that should be loaded early in the boot process, before
Ah yes, very true. I never use a stock SuSE kernel and almost never use an initrd, so it didn't occur to me to mention that.
Trying to summarize is this the issue/reason when ide-devices is "found" before SATA devices (ASUS P4C800E-Deluxe board).
SuSE's standard kernels have the IDE module linked statically into the kernel, so it stands to reason that the IDE drives are first found before any other disk controller driver modules are loaded. However I am pretty sure this behavior could be modified via boot parameters.
And what about the case with Promise ide-controllers they're also detected before drives on regular controllers (read controllers on the main board) ??
I don't know, how is the Promise IDE controller different than the one on the motherboard? If they use the same IDE kernel driver, then the kernel will "discover" each controller in some order, perhaps by the hardware slot. If your motherboard's PCI bus appears in a lower "slot" than the embedded IDE controller, that would explain it. Some BIOS setups might allow you to modify the order with which the slots are ordered. -Ti
Torsdag den 19. august 2004 10:58 skrev Ti Kan:
Johan Nielsen writes:
Torsdag den 19. august 2004 10:16 skrev Per Jessen:
Ti Kan wrote:
Plausible explanation. However you should also look at the INITRD_MODULES= line in your /etc/sysconfig/kernel file. This specifies kernel modules that should be loaded early in the boot process, before
Ah yes, very true. I never use a stock SuSE kernel and almost never use an initrd, so it didn't occur to me to mention that.
Trying to summarize is this the issue/reason when ide-devices is "found" before SATA devices (ASUS P4C800E-Deluxe board).
SuSE's standard kernels have the IDE module linked statically into the kernel, so it stands to reason that the IDE drives are first found before any other disk controller driver modules are loaded. However I am pretty sure this behavior could be modified via boot parameters.
Sound reasonable
And what about the case with Promise ide-controllers they're also detected before drives on regular controllers (read controllers on the main board) ??
I don't know, how is the Promise IDE controller different than the one on the motherboard? If they use the same IDE kernel driver, then the kernel will "discover" each controller in some order, perhaps by the hardware slot. If your motherboard's PCI bus appears in a lower "slot" than the embedded IDE controller, that would explain it. Some BIOS setups might allow you to modify the order with which the slots are ordered.
Probably - I'll have some fun with that on another PC next week (hopefully)
-Ti
Ti Kan wrote:
Johan Nielsen writes:
Torsdag den 19. august 2004 10:16 skrev Per Jessen:
Ti Kan wrote:
Plausible explanation. However you should also look at the INITRD_MODULES= line in your /etc/sysconfig/kernel file. This specifies kernel modules that should be loaded early in the boot process, before
Ah yes, very true. I never use a stock SuSE kernel and almost never use an initrd, so it didn't occur to me to mention that.
Trying to summarize is this the issue/reason when ide-devices is "found" before SATA devices (ASUS P4C800E-Deluxe board).
SuSE's standard kernels have the IDE module linked statically into the kernel, so it stands to reason that the IDE drives are first found before any other disk controller driver modules are loaded. However I am pretty sure this behavior could be modified via boot parameters.
And what about the case with Promise ide-controllers they're also detected before drives on regular controllers (read controllers on the main board) ??
I don't know, how is the Promise IDE controller different than the one on the motherboard? If they use the same IDE kernel driver, then the kernel will "discover" each controller in some order, perhaps by the hardware slot. If your motherboard's PCI bus appears in a lower "slot" than the embedded IDE controller, that would explain it. Some BIOS setups might allow you to modify the order with which the slots are ordered.
-Ti
On my Asus motherboard, both the regular IDE and Promise controllers are built in. I don't recall any setting that would have allowed a change of order. I was looking for such a setting, after I started using that system.
Johan Nielsen wrote:
Torsdag den 19. august 2004 10:16 skrev Per Jessen:
Ti Kan wrote:
Plausible explanation. However you should also look at the INITRD_MODULES= line in your /etc/sysconfig/kernel file. This specifies kernel modules that should be loaded early in the boot process, before
Ah yes, very true. I never use a stock SuSE kernel and almost never use an initrd, so it didn't occur to me to mention that.
Trying to summarize is this the issue/reason when ide-devices is "found" before SATA devices (ASUS P4C800E-Deluxe board).
And what about the case with Promise ide-controllers they're also detected before drives on regular controllers (read controllers on the main board) ??
This is probably the cause of the problem on my system. I have the hard drives connected to the Promise controller. In Red Hat 7.3, they were seen as hde & hdg. Now, with SuSe 9.0, they're hda & hdc. Then, when I try to install Win4Lin, they appear as hde & hdg again and clobbers the system, when I try to boot.
Torsdag den 19. august 2004 16:25 skrev James Knott:
Johan Nielsen wrote:
Torsdag den 19. august 2004 10:16 skrev Per Jessen:
Ti Kan wrote:
Plausible explanation. However you should also look at the INITRD_MODULES= line in your /etc/sysconfig/kernel file. This specifies kernel modules that should be loaded early in the boot process, before
Ah yes, very true. I never use a stock SuSE kernel and almost never use an initrd, so it didn't occur to me to mention that.
Trying to summarize is this the issue/reason when ide-devices is "found" before SATA devices (ASUS P4C800E-Deluxe board).
And what about the case with Promise ide-controllers they're also detected before drives on regular controllers (read controllers on the main board) ??
This is probably the cause of the problem on my system. I have the hard drives connected to the Promise controller. In Red Hat 7.3, they were seen as hde & hdg. Now, with SuSe 9.0, they're hda & hdc. Then, when I try to install Win4Lin, they appear as hde & hdg again and clobbers the system, when I try to boot.
Oh let me clarify a thing ..... I was talking about promise ide-cards. But the same goes when you use the built-in controller on the board ..... But as of now I don't think that there's support for the use of all "SATA and IDE-devices" at one time on a P4C800E-Deluxe board yet (work in progress I suspect) As I understand it right now you can use one of the "regular" IDE-interfaces and the promise interface that's built in at the same time. Linux doesn't mind which of the two regular IDE-interfaces that is (This alltogether with the SATA interfaces in use). When "full" support for the chipset is achieved it should be possible to use all 8 devices (so lets see what the future brings ;-) Johan
Johan Nielsen wrote:
Torsdag den 19. august 2004 16:25 skrev James Knott:
Johan Nielsen wrote:
Torsdag den 19. august 2004 10:16 skrev Per Jessen:
Ti Kan wrote:
Plausible explanation. However you should also look at the INITRD_MODULES= line in your /etc/sysconfig/kernel file. This specifies kernel modules that should be loaded early in the boot process, before
Ah yes, very true. I never use a stock SuSE kernel and almost never use an initrd, so it didn't occur to me to mention that.
Trying to summarize is this the issue/reason when ide-devices is "found" before SATA devices (ASUS P4C800E-Deluxe board).
And what about the case with Promise ide-controllers they're also detected before drives on regular controllers (read controllers on the main board) ??
This is probably the cause of the problem on my system. I have the hard drives connected to the Promise controller. In Red Hat 7.3, they were seen as hde & hdg. Now, with SuSe 9.0, they're hda & hdc. Then, when I try to install Win4Lin, they appear as hde & hdg again and clobbers the system, when I try to boot.
Oh let me clarify a thing .....
I was talking about promise ide-cards. But the same goes when you use the built-in controller on the board .....
But as of now I don't think that there's support for the use of all "SATA and IDE-devices" at one time on a P4C800E-Deluxe board yet (work in progress I suspect)
As I understand it right now you can use one of the "regular" IDE-interfaces and the promise interface that's built in at the same time. Linux doesn't mind which of the two regular IDE-interfaces that is (This alltogether with the SATA interfaces in use).
When "full" support for the chipset is achieved it should be possible to use all 8 devices (so lets see what the future brings ;-)
Johan
I don't have any SATA ports on this motherboard. However, there are two each standard and Promise controller connectors. Both hard drives are plugged into their own Promise connector. The CD-RW and DVD drives share one standard IDE connector.
participants (5)
-
James Knott -
Johan Nielsen -
Michael James -
Per Jessen -
ti＠amb.org