November 26, 201114 yr Hi, I have set up an unRaid system (v5.0beta12a) wit 3 2TB WD drives a while ago and ran into some problems because one of the (data) disks was failing - obviously dead on arrival. My situation so far: - precleared all 3 drives - added the data disks to the array - copyied over data (I did this before parity for performance reasons...yes, that wasn't very clever ) - added 3rd drive - build parity Now while building parity one of the data drives started showing read errors, this is the one that I am in the process of returning. In the meantime I really would like to use the array with only the remaining data disk and the parity disk though, but I am afraid that the parity building process was faulty because of the read errors. What I did since then: - removed faulty drive from unRaid assignment - removed and precleared the faulty drive to send it back (precleared it to erase my data - it will do this, right?) When I know start the unRaid all seems normal, the remaining data drive and parity drive come up green (although unRaid tells me that the array will be unprotected when I start it). What I really need help with: - obviously unRaid still thinks I will return the disk i unassigned some day (it still shows how much space was left on the device even though the line for the drive says unassigned) - I would really like to rebuild parity just with the one remaining drive - after rebuilding parity I will check (via checksums) if the data that is in the remaining drive still is the one I initially copied over, this should suffice for keeping it? or would you scrap it altogether and recopy it (I assumed bitwise checking it would result in the same thing and most likely be faster). A lot of questions, I hope somebody will be so kind to give me a quick rundown on what to do next thanks! Markus
November 26, 201114 yr If you trust the data on the drive you can use the initconfig command as detailed here: http://lime-technology.com/wiki/index.php?title=FAQ#How_do_I_remove_a_hard_disk_that_I_do_not_plan_on_replacing.3F
Archived
This topic is now archived and is closed to further replies.