Help with a cx700 that is stuck transitioning/rebuilding
Hi Folks,
Hoping someone here can lend a hand. I am stuck and have reached my wits end, and was really hoping someone here might be able to help
1. I have a cx700
2. Last friday a disk failed in my 500gb lun. (raid 5 group w/hotspare)
3. fortunately the hotspare kicked in and started rebuilding the raid group.
4. While the transition has happening another disk failed.
5. I changed out both failed disks on sunday morning, but I knew the damage was done. Raid 5, so the data was lost, but its ok because i was going to kill it off soon anyway.
6. I thought the transition would stop, but it never did. It got stuck at 2% (im guessing this is where it was when the 2nd disk died).
Now my cx700 is stuck in transitioning state.
1. I tried pulling all of the host spares. this faulted the hostspare raid groups, and the lun that was rebuilding. I then tried to destroy the lun, but navisphere would not let me. it kept giving me errors, the only thing i was able to do was remove it from the storage group which i did hopeing that would release whatever was using the lun. no luck. now the lun is a private lun, and i still cant unbind it or destroy the raid group. Please help??
thank you,
Jason
I ran the getlun stack command and got nothing back.
To resolve the issue, these steps were followed: As per Article Number:000028251
Logged on to the array and attempted to unbind the hot spare currently replacing drive 1_1_15. Removing the hot spare should have caused the Flare driver to detect the hot spare being removed and then detect that drive 1_1_15 was present and start a rebuild directly to drive 1_1_15. This did not work.
Attempted to unbind the LUN (67) from flarecons on SP-A, but since the LUN was currently owned by SP-B this failed.
Trespassed the LUN to SP-A. After the trespass completed, a rebuild on drive 1_1_7 started and completed. After the rebuild to 1_1_7 completed, the equalize to drive 1_1_5 started and ultimately completed. Then LUN was unbound and its RAID group was destroyed.
When one disk in a Raid 5 fails the hot spare should kick in and start rebuilding to the hot spare, during this time if a second disk fails, the rebuild stops. Sometimes you can get the rebuild started again by re-seating the second disk that failed. If the second disk does not come on-line, then you're facing a double faulted raid group. EMC recommends that if you remove the disks, that you mark each disk as to its location if it needs to be re-inserted.
To recover or destroy the raid group would require EMC service to access the array directly - you'll need to open a service request with EMC.
B4FQqUoIrW12094
60 Posts
1175
0
Posted August 11th, 2015 22:00
To resolve the issue, these steps were followed: As per Article Number:000028251
Also refer below primus
https://emc--c.na5.visual.force.com/apex/KB_BreakFix_1?id=kA17000000017hX