October 20, 201312 yr Hi all, One of my drives appears to have failed (started clicking when I tried to shut the server down). Had a read on simply removing the drive from the array as there is sufficient storage to simply remove it and continue, so I booted it up with the intention of following the steps listed in the FAQ, identified the drive (it was red balled, everything else green) however I decided against completing the switch and put it off until today (turned the array off). However today when I have started the array, the failed drive is showing green however when I click on the individual drive there is no file system or partition format associated. I'm hesitant to replace the drive and begin a sync as the system seems to think the drive is fine, but the parity drive is incorrect? Could replacing the dead drive in this state lead to corruption of the data? Any suggestions greatly appreciated.
October 20, 201312 yr the system seems to think the drive is fine, but the parity drive is incorrect ... Why do you think the parity drive is incorrect? Does the Web GUI say that? when I click on the individual drive there is no file system or partition format associated. Does the Web GUI show there's no file system? ... or are you getting an error from Windows Explorer when you attempt to access the drive? Could replacing the dead drive in this state lead to corruption of the data? It sounds like you may have already lost all of the data on the drive -- but don't panic yet. Answer the two questions above, and post a picture of the Web GUI.
October 20, 201312 yr Author Thanks for your reply. I believe the parity drive is correct as it was green originally, and even with the failed disk, the data was still accessible. Attached is an image showing the webgui as it sits right now.
October 20, 201312 yr Did you change you disk assignments; or perhaps reseat the cables when the system was shut down? The system apparently "thinks" you have a new parity drive => when you Start the array it's probably going to start a new parity sync. If that happens, you'll have no way to rebuild a bad drive -- the new parity will reflect the current state of all your drives. Disk3's indicated "unknown" state is normal -- all the disks will show that with the array stopped. When you Start the array, that should change. The display you're looking at isn't the stock GUI, but the concept is the same. I don't know what happened that resulted in the "New parity disk" state. You can TRY the following if you're CERTAIN that you haven't changed any assignments or cabling: But do NOT proceed too far or you can lose all chance of recovering any data from disk3 [Hopefully you have backups of your data, and can restore from those -- but it always amazes me how many folks don't bother]: => Unassign disk3 => Start the array and confirm it shows a "Missing" disk for disk3 ... and see if it now shows valid parity [if it prompts you to start a parity sync, do NOT let that happen] => IF the parity was shown as valid with the array started; then Stop the array; assign your new replacement disk to disk3; and then Start the array. This should then start a rebuild of the disk.
October 20, 201312 yr One other note: I assumed from your comment r.e. disk3 that this is the one that was "red balled" yesterday -- correct? Otherwise, do what I suggested above with the disk that had failed. [You never actually said which specific disk that was]
Archived
This topic is now archived and is closed to further replies.