| View previous topic :: View next topic |
| Author |
Message |
julmust
n00b
Joined: 13 Oct 2002
Posts: 57
Location: Landskrona, Sweden
|
 Posted: Mon Jul 10, 2006 12:41 am Post subject: mdadm - raid device not started at boot |
 |
|
I have a bunch of raid devices, and added another one. The problem is that it's not recognized at boot.
The raid device is /dev/md4.
This is how I created the array:
| Code: |
# mknod /dev/md4 b 9 4
# mdadm --create --verbose /dev/md4 --level=1 --raid-devices=2 /dev/hdg1 /dev/hdk1
# mdadm --detail --scan > /etc/mdadm.conf
|
First I thought this was because the driver to the disk controller card was compiled as a module and loaded after the md devices was recognized. So, I recompiled the kernel with the driver compiled in. dmesg shows that the drives are found before raid devices are detected.
/etc/mdadm.conf:
| Code: |
ARRAY /dev/md4 level=raid1 num-devices=2 UUID=42dd5a9f:8e283efc:d2a0fc71:3090e945
ARRAY /dev/md1 level=raid1 num-devices=2 UUID=395fd7aa:ff24dadd:d6cfab6f:3ce7f71c
ARRAY /dev/md2 level=raid1 num-devices=2 UUID=fe59f3ab:d1d96776:469dae87:0713b9ec
ARRAY /dev/md3 level=raid1 num-devices=2 UUID=5ef64450:ceafed28:4dec84d8:4b0cd6fc
|
dmesg:
| Code: |
ide5: BM-DMA at 0xe408-0xe40f, BIOS settings: hdk:DMA, hdl:pio
hdk: ST3160827AS, ATA DISK drive
hdk: max request size: 512KiB
hdk: 312581808 sectors (160041 MB) w/8192KiB Cache, CHS=19457/255/63, UDMA(33)
hdk: cache flushes supported
hdk: hdk1
ide5: BM-DMA at 0xe408-0xe40f, BIOS settings: hdk:DMA, hdl:pio
hdk: ST3160827AS, ATA DISK drive
hdk: max request size: 512KiB
hdk: 312581808 sectors (160041 MB) w/8192KiB Cache, CHS=19457/255/63, UDMA(33)
hdk: cache flushes supported
hdk: hdk1
...
...
md: raid1 personality registered for level 1
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid5: automatically using best checksumming function: pIII_sse
pIII_sse : 1611.000 MB/sec
raid5: using function: pIII_sse (1611.000 MB/sec)
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
...
...
md: Autodetecting RAID arrays.
md: autorun ...
md: considering sdb3 ...
md: adding sdb3 ...
md: sdb2 has different UUID to sdb3
md: sdb1 has different UUID to sdb3
md: adding sda3 ...
md: sda2 has different UUID to sdb3
md: sda1 has different UUID to sdb3
md: created md3
md: bind<sda3>
md: bind<sdb3>
md: running: <sdb3><sda3>
raid1: raid set md3 active with 2 out of 2 mirrors
md: considering sdb2 ...
md: adding sdb2 ...
md: sdb1 has different UUID to sdb2
md: adding sda2 ...
md: sda1 has different UUID to sdb2
md: created md2
md: bind<sda2>
md: bind<sdb2>
md: running: <sdb2><sda2>
raid1: raid set md2 active with 2 out of 2 mirrors
md: considering sdb1 ...
md: adding sdb1 ...
md: adding sda1 ...
md: created md1
md: bind<sda1>
md: bind<sdb1>
md: running: <sdb1><sda1>
raid1: raid set md1 active with 2 out of 2 mirrors
md: ... autorun DONE.
|
All of the other RAID devices are recognized except the md4. How can this be? If I redo this line:
| Code: |
# mdadm --create --verbose /dev/md4 --level=1 --raid-devices=2 /dev/hdg1 /dev/hdk1
|
it's up and running again.
_________________
hm.. help me. |
|
| Back to top |
|
 |
troymc
Guru
Joined: 22 Mar 2006
Posts: 553
|
| Posted: Mon Jul 10, 2006 1:34 am Post subject: |
|
|
How about the quick obvious question:
Are /dev/hdg1 & /dev/hdk1 type fd - Linux RAID Autodetect?
troymc |
|
| Back to top |
|
|
julmust
n00b
Joined: 13 Oct 2002
Posts: 57
Location: Landskrona, Sweden
|
| Posted: Mon Jul 10, 2006 1:48 am Post subject: |
|
|
Yes, they are..
_________________
hm.. help me. |
|
| 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
|
|
Kernel & Hardware
