AxelTerizaki
n00b
Joined: 12 Apr 2003
Posts: 33
|
 Posted: Sun Jan 01, 2006 2:58 pm Post subject: [SOLVED] RAID 5 not rebuilding after some changes |
 |
|
Hello there and first of all, happy new year to everyone 
My RAID configuration was as follows:
RAID 5 on hdb,hdc,hde,hdf,hdg,hdh
One of the drives (hdf) went faulty, so I decided to replace it, and at the same time, add one more IDE controller to the server to lighten the weight on the second one.
The server had one main IDE controller on the motherboard (A7N8X) and two PROMISE PCI controllers.
So, before rebooting, I did use raidsetfaulty on hdf, and modified my raidtab as usual.
However, now that I have moved drives around a bit and replaced the faulty one, my RAID5 won't start anymore for some unknown reason. New configuration is as follows:
| Code: | raiddev /dev/md0
raid-level 5
nr-raid-disks 6
nr-spare-disks 0
persistent-superblock 1
parity-algorithm left-symmetric
chunk-size 64
device /dev/hdb1
raid-disk 0
device /dev/hdc1
raid-disk 1
device /dev/hde1
raid-disk 2
device /dev/hdg1
raid-disk 3
device /dev/hdi1
failed-disk 4
device /dev/hdk1
raid-disk 5
|
As you can see, I moved hdh to hdk, and hdf to hdi. I kept it faulty so I could make a raidhotadd laters.
However, when I do this...
| Code: |
mahoro ~ # raidstart /dev/md0
|
I get this on mdstat:
| Code: | mahoro ~ # cat /proc/mdstat
Personalities : [raid5]
unused devices: <none>
|
So I looked into /var/log/messages and found this:
| Code: |
Jan 1 16:10:42 mahoro md: could not open unknown-block(34,65).
Jan 1 16:10:42 mahoro md: could not open unknown-block(33,65).
Jan 1 16:10:42 mahoro md: autorun ...
Jan 1 16:10:42 mahoro md: considering hdg1 ...
Jan 1 16:10:42 mahoro md: adding hdg1 ...
Jan 1 16:10:42 mahoro md: adding hde1 ...
Jan 1 16:10:42 mahoro md: adding hdc1 ...
Jan 1 16:10:42 mahoro md: adding hdb1 ...
Jan 1 16:10:42 mahoro md: created md0
Jan 1 16:10:42 mahoro md: bind<hdb1>
Jan 1 16:10:42 mahoro md: bind<hdc1>
Jan 1 16:10:42 mahoro md: bind<hde1>
Jan 1 16:10:42 mahoro md: bind<hdg1>
Jan 1 16:10:42 mahoro md: running: <hdg1><hde1><hdc1><hdb1>
Jan 1 16:10:42 mahoro raid5: device hdg1 operational as raid disk 4
Jan 1 16:10:42 mahoro raid5: device hde1 operational as raid disk 2
Jan 1 16:10:42 mahoro raid5: device hdc1 operational as raid disk 1
Jan 1 16:10:42 mahoro raid5: device hdb1 operational as raid disk 0
Jan 1 16:10:42 mahoro raid5: not enough operational devices for md0 (2/6 failed)
Jan 1 16:10:42 mahoro RAID5 conf printout:
Jan 1 16:10:42 mahoro --- rd:6 wd:4 fd:2
Jan 1 16:10:42 mahoro disk 0, o:1, dev:hdb1
Jan 1 16:10:42 mahoro disk 1, o:1, dev:hdc1
Jan 1 16:10:42 mahoro disk 2, o:1, dev:hde1
Jan 1 16:10:42 mahoro disk 4, o:1, dev:hdg1
Jan 1 16:10:42 mahoro raid5: failed to run raid set md0
Jan 1 16:10:42 mahoro md: pers->run() failed ...
Jan 1 16:10:42 mahoro md: do_md_run() returned -5
Jan 1 16:10:42 mahoro md: md0 stopped.
Jan 1 16:10:42 mahoro md: unbind<hdg1>
Jan 1 16:10:42 mahoro md: export_rdev(hdg1)
Jan 1 16:10:42 mahoro md: unbind<hde1>
Jan 1 16:10:42 mahoro md: export_rdev(hde1)
Jan 1 16:10:42 mahoro md: unbind<hdc1>
Jan 1 16:10:42 mahoro md: export_rdev(hdc1)
Jan 1 16:10:42 mahoro md: unbind<hdb1>
Jan 1 16:10:42 mahoro md: export_rdev(hdb1)
Jan 1 16:10:42 mahoro md: ... autorun DONE.
|
So you'll say "hdi and hdk aren't found" but they are present on the system since I did fdisk on hdi to create a new Linux auto raid partition.
/sbin/fdisk /dev/hdk works fine too.
So I wonder, what prevents md from accessing these? Where did I do wrong and is there anything I can do?
Thanks in advance.
Last edited by AxelTerizaki on Sun Jan 01, 2006 7:28 pm; edited 1 time in total |
|
Kernel & Hardware
