November 1, 201411 yr So I had a drive failure - disk8. The good news is that I have a complete backup of this drive. My failure on disk8 was an ata error and I assumed it was cabling...so I took the opportunity to replace all sata cables before attempting a rebuild. While attempting to rebuild the disk8 data on the same disk - the parity disk was having read errors (new cable wasn't seated properly)...so I stopped the rebuild and then power cycled the server. Now I have two disks that have issues....disk8 is orange, which I assume is this color because the data rebuild was started and after the power cycle parity shows as a new disk. Does anyone know how to set the parity as good? I would love to reset parity as good and have it rebuild the data on disk 8. Any suggestions would be greatly appreciated. Dan Syslog_2014-10-30.zip
November 3, 201411 yr See here: http://lime-technology.com/forum/index.php?topic=32491.msg298738#msg298738
November 3, 201411 yr Author dgaschk, You have been so helpful in the past and I appreciate your response! Here is my confusion after reading the post...and maybe some of my confusion is remembering the old 4.7 unraid method of mdcmd set invalidslot 99. Below is the quote from the link you provided. I edited the instruction to reflect the disk8 that I am having an issue with. What I want to double check is what sets the parity disk as good. Does the Utilities/New Config do this??? or is there some telenet command line to set parity as good, since it does not have a disk number...I just want to make sure I understand before proceeding. Thanks, Dan <quote> > 1. Execute Utilities/New Config. > > 2. on Main, assign all your drives, being very careful to assign Parity and your new disk (disk10) correctly. > > 3. From a console or a telnet session type this command: > > mdcmd set invalidslot 8 > > (the 8 corresponds to disk8) > > 4. Click 'Start' on the webGui. > > What should happen now is array gets started with disk8 reconstruct in process. > > IMPORTANT: between steps 3 and 4 do NOT refresh your browser or navigate to any other pages in the webGui - just click the Start button which is already being displayed there (if you navigate to a different page or even refresh the browser after step 3 it will "cancel" the effect of that 'mdcmd' and result in your parity disk getting written - not good). </quote>
November 3, 201411 yr Author This is the link I was thinking of from the bottom of the trust my array wiki page: http://lime-technology.com/forum/index.php?topic=19385.msg172365#msg172365 I just want to make sure that the new config utility sets parity to good...versus having to do the procedure in the above link. Dan
November 4, 201411 yr This is the link I was thinking of from the bottom of the trust my array wiki page: http://lime-technology.com/forum/index.php?topic=19385.msg172365#msg172365 I just want to make sure that the new config utility sets parity to good...versus having to do the procedure in the above link. Dan I believe you need to folllow the procedure that dgaschk pointed to.
November 4, 201411 yr Author Thanks Guys, I am in the process of rebuilding disk8...thanks for all of the help! Hopefully by morning it will be back to normal. Dan
November 4, 201411 yr Author Disk8 rebuilt sucessfully. I ran a parity check afterwards and no errors were found. I purchased a new 3 TB drive and am in the process of preclearing it. Once done this will become my new parity drive. I will then rotate parity drive to disk8 and then preclear disk8 and this will become my spare drive. Thanks again! Dan
Archived
This topic is now archived and is closed to further replies.