August 30, 20178 yr I have 9 existing drives in my array. I just put a new SSD in the box and would like it assigned as Drive position 2 rather than 10. This is just to keep some logical sequence to where drives are in the case. I think you used to be able to change 1 drive position at a time. Meaning I would have to assign it as drive 10, start the array, stop the array, swap 9 and 10 positions, start/stop, swap 8/9... etc.... I think I did this once way back in unRAID 5.X, though I can't remember when for sure. Is there a new way to do this now without having to completely re-build parity? Thanks for any help.
August 30, 20178 yr As long as you are using the first parity slot, and only the first parity slot, you can set a new config, tell it to retain only parity, and assign the data drives any way you wish. You are given the option to select that parity is already valid, and you should be fine. I'd recommend a non-correcting parity check, just to be sure, but it's not necessary. The 2nd parity slot, even if it's the only one in use, is drive position sensitive, so if you are using parity2, either by itself or in conjunction with parity1, parity will have to be rebuilt. Having an SSD in the parity protected array is not optimal, it will degrade in performance over time with use, as you can't trim an array member. It's not currently recommended to use SSD's as part of the parity protected array, much better to use it as a cache drive or unassigned device.
August 30, 20178 yr Author 52 minutes ago, jonathanm said: As long as you are using the first parity slot, and only the first parity slot, you can set a new config, tell it to retain only parity, and assign the data drives any way you wish. You are given the option to select that parity is already valid, and you should be fine. I'd recommend a non-correcting parity check, just to be sure, but it's not necessary. The 2nd parity slot, even if it's the only one in use, is drive position sensitive, so if you are using parity2, either by itself or in conjunction with parity1, parity will have to be rebuilt. Thanks for the info. I have two parity drives running so it seems as if I'll have to re-build parity to get the drive where I want it. I'm going to run a parity check tonight so I might take that path tomorrow. 52 minutes ago, jonathanm said: Having an SSD in the parity protected array is not optimal, it will degrade in performance over time with use, as you can't trim an array member. It's not currently recommended to use SSD's as part of the parity protected array, much better to use it as a cache drive or unassigned device. I saw this warning not to long ago and posted this thread asking for clarification on the subject. https://forums.lime-technology.com/topic/57872-ssd-not-supported-for-a-data-drive/ At the end it seemed like as long as you stayed away from certain drives that were problematic they performed fine in unRAID. I did take the advice and got another Samsung 850EVO drive just like my existing SSD. For the conceivable future, I wont be adding any other SSD's to the array. Edited August 30, 20178 yr by TODDLT
Archived
This topic is now archived and is closed to further replies.