This post is more than 5 years old
5 Posts
0
13274
Need advice!! Best procedure for a physical disk failure in PowerVault MD3000i?
Hello there,
before anything, I appologize for my poor english.
I'm pretty new in Dell hardware, but I already had a problem with a MD3000i and I tried to solve it based on Dell documentation on the web and followed steps described in the Recovery Guru.
The original problem: physical disk failure detected in one disk of a RAID5 array, hardware started to use the spare. Amber LED on hardware and failed disk slot.
Following Dell documentation, I removed the disk and I put it back. After that, disk LED turned green and the physical disk started OK and online, and began the data recovery.
After finished, the MDSM tells me that the physical disk has lost Redundancy Path or something like this (I'm sorry for this imprecision but I'm reading spanish messages)
My questions are;
1.Did I proceed correctly? Or is not recommended to do this?
2.There's any possibility of data transfer occurs using both physical failed and hot spare without giving me an alarm? Kind of switching between them constantly?
3.It is really necessary to lost data in the virtual disk or shutting down the entire LUN just to make this disk fail from SMcli, so we can replace it?
Thanks a lot!!
JOHNADCO
847 Posts
1
August 24th, 2011 15:00
I have seen drive FW create this error.....
JOHNADCO
847 Posts
0
August 24th, 2011 09:00
Are you blinking amber still?
The proceedure you performed was sound. Dell always makes you pull the drive and re-insert it.
Sounds like the drive itself may still have an issue though.
AnvbiZ
5 Posts
0
August 24th, 2011 13:00
Now the problem is that we replaced the disk (it was hot removed, while blinking green and active) with a brand new one and still having this redundancy path issue.
What could it be?
AnvbiZ
5 Posts
0
August 27th, 2011 07:00
FW refers to firmware, right? So... your advice is to update the firmware? Because support people even cleaned the slots and tried everything but i'm not pretty sure about them. Imagine... the person who came here didn't know how to send commands to SMcli interface... he kept waiting for 30 minutes for the "executing script" message "finish" the script.
Anyway, thanks a lot for the idea, if that's the problem, I'll told you when it's solved... or well I'll be back with another question.
AnvbiZ
5 Posts
0
October 1st, 2011 06:00
Well, thanks for the advice!! FW update solved this issue.
Anyway, I would like to know... could be a drive malfunction in the old one, that show this error the first time? Because it was ok until the drive reported to be offline, and then when I re-inserted, why can it be a FW error?
Thanks a lot JOHNADCO.
JOHNADCO
847 Posts
0
October 3rd, 2011 09:00
The firmware talks to the controller. Lots of communitication goes on during failures and re-insertions. Not sure, but seems somewhat logical, that one of the bugs fixed had soemthing to do with failure, recovery, or initialization.