March 7, 201313 yr This is good. The parity updates should reflect the latest writes to the array. Once the check is done then perform the parity-swap-disable procedure.
March 7, 201313 yr Author Ok, thanks for confirming that. Will report back once parity checking is complete and (hopefully) I can access all my data.
March 8, 201313 yr Author Parity check completed with some 800,000 odd errors. Tried parity swap disable, but it said too many wrong disks. This post helped. http://lime-technology.com/forum/index.php?topic=8343.msg80683#msg80683 Finally got the parity swap message on web GUI. However now when I press start the array, the screen refreshes, and the array does not start! It is back to the disk assignment state. syslog attached. syslog-2013-03-08.txt
March 9, 201313 yr Author I gave up on the parity swap disable procedure since it would not start, and I did not want to risk breaking a working array only to be able to replace 2 disks at once. So I have gone the conventional route and upgraded just the parity disk after I had a working array. It seems to progressing just fine at the moment, and after weeks of unREST I finally report having rescued my rig and not lost any data whatsoever! I am very thankful to all those who have contributed to my thread and helped me with this! I am glad I have chosen unRAID, and hope to build many more servers (currently the number is 5 - 4 with Plus licenses and 1 Basic)
Archived
This topic is now archived and is closed to further replies.