Hi there,
I'm running a 5-drive software RAID5 array across two controllers.
The motherboard in that PC recently died - I sent the board back for
RMA. When I refitted the motherboard, connected up all the drives,
and booted up I found that the array was being reported as degraded
(though all the data on it is intact). I have 4 drives on the on
board controller and 1 drive on an XFX Revo 64 SATA controller card.
The drive which is being reported as not being in the array is the one
connected to the XFX controller.
The OS can see that drive fine, and "mdadm --examine" on that drive
shows that it is part of the array and that there are 5 active devices
in the array. Doing "mdadm --examine" on one of the other four drives
shows that the array has 4 active drives and one failed. "mdadm
--detail" for the array also shows 4 active and one failed.
Now I haven't lost any data here and I know I can just force a resync
of the array which is fine. However I'm concerned about how this has
happened. One worry is that the XFX SATA controller is doing
something funny to the drive. I've noticed that it's BIOS has
defaulted to RAID0 mode (even though there's only one drive on it) - I
can't see how this would cause any particular problems here though. I
guess it's possible that some data on the drive got corrupted when the
motherboard failed...
Any ideas what could cause mdadm to report as I've described above
(I've attached the output of these three commands)? I'm running
Ubuntu Edgy, which is a 2.17.x kernel, and mdadm 2.4.1. In case it's
relevant here, I created the array using EVMS...
Thanks,
James
[EMAIL PROTECTED]:~$ sudo mdadm --examine /dev/hde1
Password:
/dev/hde1:
Magic : a92b4efc
Version : 00.90.00
UUID : 33d5338b:d2d6baf0:424498ad:47d05087
Creation Time : Sun Jan 15 16:47:51 2006
Raid Level : raid5
Device Size : 312496128 (298.02 GiB 320.00 GB)
Array Size : 1249984512 (1192.08 GiB 1279.98 GB)
Raid Devices : 5
Total Devices : 5
Preferred Minor : 0
Update Time : Sat Nov 4 16:29:06 2006
State : clean
Active Devices : 5
Working Devices : 5
Failed Devices : 0
Spare Devices : 0
Checksum : d628e17e - correct
Events : 0.4232131
Layout : left-asymmetric
Chunk Size : 256K
Number Major Minor RaidDevice State
this 4 254 6 4 active sync
0 0 254 2 0 active sync
1 1 254 3 1 active sync
2 2 254 4 2 active sync
3 3 254 5 3 active sync
4 4 254 6 4 active sync
[EMAIL PROTECTED]:~$
[EMAIL PROTECTED]:~$
[EMAIL PROTECTED]:~$
[EMAIL PROTECTED]:~$ sudo mdadm --examine /dev/sda1
/dev/sda1:
Magic : a92b4efc
Version : 00.90.00
UUID : 33d5338b:d2d6baf0:424498ad:47d05087
Creation Time : Sun Jan 15 16:47:51 2006
Raid Level : raid5
Device Size : 312496128 (298.02 GiB 320.00 GB)
Array Size : 1249984512 (1192.08 GiB 1279.98 GB)
Raid Devices : 5
Total Devices : 4
Preferred Minor : 0
Update Time : Sun Nov 5 11:56:29 2006
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 1
Spare Devices : 0
Checksum : d629ee25 - correct
Events : 0.4232204
Layout : left-asymmetric
Chunk Size : 256K
Number Major Minor RaidDevice State
this 1 8 1 1 active sync /dev/sda1
0 0 8 17 0 active sync /dev/sdb1
1 1 8 1 1 active sync /dev/sda1
2 2 8 33 2 active sync /dev/sdc1
3 3 8 49 3 active sync /dev/sdd1
4 4 0 0 4 faulty removed
[EMAIL PROTECTED]:~$
[EMAIL PROTECTED]:~$
[EMAIL PROTECTED]:~$
[EMAIL PROTECTED]:~$ sudo mdadm --detail /dev/md0
/dev/md0:
Version : 00.90.03
Creation Time : Sun Jan 15 16:47:51 2006
Raid Level : raid5
Array Size : 1249984512 (1192.08 GiB 1279.98 GB)
Device Size : 312496128 (298.02 GiB 320.00 GB)
Raid Devices : 5
Total Devices : 4
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Sun Nov 5 11:56:29 2006
State : clean, degraded
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Layout : left-asymmetric
Chunk Size : 256K
UUID : 33d5338b:d2d6baf0:424498ad:47d05087
Events : 0.4232204
Number Major Minor RaidDevice State
0 8 17 0 active sync /dev/sdb1
1 8 1 1 active sync /dev/sda1
2 8 33 2 active sync /dev/sdc1
3 8 49 3 active sync /dev/sdd1
4 0 0 4 removed
[EMAIL PROTECTED]:~$
