mdadm issues - active, degraded, Not Started
I have/had a RAID5 array with four 250GB drives. As a result of some poking around inside the computer while it was running, the system froze and I had to hard reset it. After booting up it looks like the RAID array got messed up. It looks as if one of the drives were removed. Here's what mdadm says:
Code:
# mdadm -D /dev/md0 Code:
# dmesg | grep md0 Code:
# mdadm -E /dev/md0 Any help would be greatly appreciated. - George |
When you say "poking around inside the computer", do you mean physically?
Go into the bios. Does the computer physically detect the forth drive? You might want to check the cables and determine whether there is a hardware problem with the drive/cable/controller before proceeding. |
Oh, yes, I forgot to mention that the drive shows up ok and it looks like it's working. It was removed from the array. But the array should recover without that drive, right?
And yes, it was a physical poking. I didn't really get inside, I was just playing around the fan on the side but I guess by moving the fan's power cord I moved something else too. |
Try replacing the drive (/dev/hdh) and run "mdadm --query /dev/hdh". Does it recognize it as a member of an array?
I think you will want to monitor mdadm and determine if it is trying to rebuild the array. Did you have 3 drives & 1 spare? If it is rebuilding, then leave it alone until finished. |
How do I replace the drive? Do I do the following?
Code:
mdadm --manage /dev/md0 --add /dev/hdh |
Or do I have to do
Code:
mdadm --manage /dev/md0 --re-add /dev/hdh |
OK, I was impatient so I had to try something and it worked. :) Here's what I did in case someone else has the same problem.
Code:
[root@LECBackup ~]# mdadm --manage /dev/md0 --re-add /dev/hdh |
All times are GMT -5. The time now is 04:07 AM. |