View previous topic :: View next topic |
Author |
Message |
longship Apprentice
Joined: 04 Jun 2005 Posts: 294 Location: Ontario, CA USA
|
Posted: Tue Mar 07, 2006 10:48 pm Post subject: [Solved] Added two more SATA -- drive order changed (RAID) |
|
|
This is really worrisome. I have two Raptors with software (kernel) RAID. They are humming right along. (They are configured with mdadm.)
/dev/sda == Raptor 1
/dev/sdb == Raptor 2
RAID is like this:
/dev/md/0 == /boot /dev/sda1 RAID 1 ---> /boot /dev/sdb1
/dev/md/1 == / /dev/sda3 RAID 0 ---> /dev/sdb3
I have now added two more Hitachi SATA drives which I will be putting in as /home on RAID 0.
The problem is, after installing the drives they are recognized as /dev/sda and /dev/sdb.
I now have
/dev/sda == Hitachi 1
/dev/sdb == Hitachi 2
/dev/sdc == Raptor 1
/dev/sdd == Raptor 2
What in the Sam Hell happened? I have the Raptors on ports 1 and 2 and the Hitachi on ports 3 and 4. Why, oh why do they get reordered like this. It's stupid.
Now here's what will really trip your trigger. The kernel RAID and GRUB recognize the Raptors in spite of all this. The sytem still boots and still runs beautifully. The kernel RAID code finds /dev/sdc and /dev/sdd as the Raptor RAID volumes.
Heres' my mdadm.conf:
Code: | ARRAY /dev/md1 level=raid0 num-devices=2 UUID=37f756ff:abcf9929:8a0f4a33:c72dc703
devices=/dev/sda3,/dev/sdb3
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=36a73a36:36c8641c:91016a02:98f4644c
devices=/dev/sda1,/dev/sdb1 |
I am at a stand still here. I will not be using fdisk or configuring the RAID for the Hitachi's until I find out what the f*ck is happening here.
Thanks much. _________________ AMD 64 X2 4400+, ASUS A8N-Sli Premium + Lian Li PC-V1000A Plus
AMD Duron 800, ABit KT7E, junk case
VIA C3-Nehemiah, VIA EPIA MII12000 + Scythe e-Otonashi fanless case
Last edited by longship on Wed Mar 08, 2006 2:13 am; edited 1 time in total |
|
Back to top |
|
|
widan Veteran
Joined: 07 Jun 2005 Posts: 1512 Location: Paris, France
|
Posted: Tue Mar 07, 2006 11:15 pm Post subject: Re: Help! Added two more SATA -- drive order changed (RAID) |
|
|
longship wrote: | What in the Sam Hell happened? I have the Raptors on ports 1 and 2 and the Hitachi on ports 3 and 4. Why, oh why do they get reordered like this. It's stupid. |
I assume it's on that machine:
Quote: | AMD 64 X2 4400+, ASUS A8N-Sli Premium + Lian Li PC-V1000A Plus |
For some reason, the port numbers are wrong. The nForce4 contains two separate SATA controllers, which appear as different PCI devices to the OS. The Linux kernel enumerates them in the order they are on the bus. On Asus boards, ports "1" and "2" are the second controller, and ports "3" and "4" are the first controller. Which explains the drives are enumerated in 3-4-1-2 order... I have 4 disks on such a board (in RAID5), and I did some tests to know which disk was connected to which ata port (so that if, say, /dev/sdb fails, I know which physical drive to replace), and discovered this fact.
The BIOS (and grub, that uses BIOS functions to access the disk) doesn't care about that. It know that you boot on (for example) port 1 of controller 2. It doesn't know what is written on the connectors.
For your mdadm.conf, md is probably autodetecting the array at boot time (if you have the RAIDed partitions as type 0xfd), so it doesn't use mdadm.conf at all (when I was testing, I did not even have an mdadm.conf, and the RAID still worked). |
|
Back to top |
|
|
longship Apprentice
Joined: 04 Jun 2005 Posts: 294 Location: Ontario, CA USA
|
Posted: Tue Mar 07, 2006 11:29 pm Post subject: Re: Help! Added two more SATA -- drive order changed (RAID) |
|
|
widan wrote: | longship wrote: | What in the Sam Hell happened? I have the Raptors on ports 1 and 2 and the Hitachi on ports 3 and 4. Why, oh why do they get reordered like this. It's stupid. |
I assume it's on that machine:
Quote: | AMD 64 X2 4400+, ASUS A8N-Sli Premium + Lian Li PC-V1000A Plus |
For some reason, the port numbers are wrong. The nForce4 contains two separate SATA controllers, which appear as different PCI devices to the OS. The Linux kernel enumerates them in the order they are on the bus. On Asus boards, ports "1" and "2" are the second controller, and ports "3" and "4" are the first controller. Which explains the drives are enumerated in 3-4-1-2 order... I have 4 disks on such a board (in RAID5), and I did some tests to know which disk was connected to which ata port (so that if, say, /dev/sdb fails, I know which physical drive to replace), and discovered this fact.
The BIOS (and grub, that uses BIOS functions to access the disk) doesn't care about that. It know that you boot on (for example) port 1 of controller 2. It doesn't know what is written on the connectors.
For your mdadm.conf, md is probably autodetecting the array at boot time (if you have the RAIDed partitions as type 0xfd), so it doesn't use mdadm.conf at all (when I was testing, I did not even have an mdadm.conf, and the RAID still worked). |
I gathered that md was autodetecting. It's just disconcerting to find things happening like this. The A8N-SLi Premium is an absolutely awesome motherboard. But being so complex it's got its quirks. Apparently the ordering of the SATA controllers is just one of them.
Thanks. Will mark [Solved] after I test it.
Switching the cables on the mobo was going to be my next step. I will try and re _________________ AMD 64 X2 4400+, ASUS A8N-Sli Premium + Lian Li PC-V1000A Plus
AMD Duron 800, ABit KT7E, junk case
VIA C3-Nehemiah, VIA EPIA MII12000 + Scythe e-Otonashi fanless case |
|
Back to top |
|
|
|
|
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
|
|