Hi all,
If, as is frequently the case, the sharespace becomes unresponsive (ie. no web interface, no ssh etc.), the only option is to cycle power to bring it back.
If, as often happens but not too frequently, a superblock on one of the disks is left marked as dirty the RAID5 volume will come up in degraded mode with the disk containing the stale super block removed.
My question is, how does one add the disk back into the array so it can be rebuilt using the web interface?
Ian
Hi Ian,
http://wdc.custhelp.com/app/answers/detail/a_id/2746
But this post, although dated, suggests that the instructions are flawed.
I don’t have a sharespace anymore but continue to document user experiences with it. Please let us know how your recovery attempts go.
GuiGuy wrote:
Hi Ian,
But this post, although dated, suggests that the instructions are flawed.
I don’t have a sharespace anymore but continue to document user experiences with it. Please let us know how your recovery attempts go.
Maybe my post wasn’t clear.
I’m not asking for help becuase, in the case above, an “mdadm /dev/md2 --add /dev/sdb4” (sdb4 for me in this case) initiates recovery and the disk is rebuilt without interruption to system usage.
The question I’m asking is how does one do this within the web interface.
There should be an option to attempt to add back a failed disk before replacing it and monitoring the rebuild would quickly alert the system to an actual faulty disk.
Ian
raven-au wrote:
Maybe my post wasn’t clear.
Yea, sorry, I misread the post
