June 20, 20197 yr I'm very happy with unRAID and later today I will be purchasing a new USB key to replace my existing trial USB key, before I purchase my unRAID Pro license. Donations for users that have assisted me will be made later today as well. I have also ordered 2 new hard drives - one an Ironwolf 10TB for replacement of the 2 month old 8TB that's currently my parity drive. Sorry for the detailed, lengthy post that follows. Questions: 1. I'd like to re-organize my array so that I can group similar drives (same model and/or capacity). The FAQ has mildly conflicting info on re-assigning disks to new slots in the array. The 'Move unRAID to a New System' section states: "make sure you have notes of which disks (model and serial number) are assigned to which disk number (logical slot) in your array". The FAQ section 'Can I reorder my drives within my array?' states that you can change slot assignments on a single-parity system. As the drives are identified by model/serial number, I'm confident I can re-arrange the slot layout, but can I also leave empty slots so that I can group drives of similar model/capacity after the parity rebuild? This is more an OCD thing where I'ld like my newer 10TB drives to appear 1st, my 8TB drives next, my 6TB drives 3rd and my older 4TB drives to appear at the end of the array. But it will be a long process of adding the 10TB drives as I have to first migrate the data off each drive to the array. 2. I'm upgrading the parity to a 10TB with the Ironwolf 7200rpm drive as I have 5 external USB 10TB drives to eventually migrate the data off to the array; the 8TB parity isn't large enough to allow this. These 10TB drives are attached via the Unassigned Devices plugin, and have all been tested and used with my Plex docker container. I'm assuming I can shuck them and attach them to SATA controllers instead of USB, which should improve the latency while I migrate the data from each of the drives to the array? 3. As I'm replacing the existing 8TB parity with the new 10TB drive, is it safer to assign the new 10TB to another slot, make it the parity drive, then let it rebuild, or is it better to pull the existing 8TB parity drive and just replace it with the new 10TB drive? I know that a parity rebuild will be necessary but if the new 10TB should fail, I should be able to re-install the 8TB drive to use the array. I assume this would work ONLY if I do not add more new data to the array until the 10TB parity rebuild is complete? Or can I continue to add data to the array while the new 10TB parity is rebuilding? That would make the 8TB parity invalid, so it means I'd have to rebuild the 8TB parity drive too. So here's my plan: 1. Stop the array and make my slot assignment changes, leaving empty slots for the eventual 10TB drives and grouping my drives of similar model/capacity together. Restart the array and confirm that everything is still working as expected. 2. Add the new pre-cleared/stress tested 8TB data drive to the empty slot left for it during my slot re-assignment. Shuck the 5 x 10TB drives and connect them to SATA controllers rather than continue to use them as USB. The 10TB drives won't be assigned to slots but will be mounted using UD. 2. After pre-clearing/stress testing the new 10TB drive, make it the parity drive by shutting down the array and replacing the existing 8TB drive. Restart of the array will trigger a parity rebuild on the new 10TB drive, which I will need to wait for completion before adding any more disks or data to the array. 3. After the parity rebuild is successful, pre-clear the 2 month old 8TB parity drive and add it to the array as a data disk, in the empty slot left for that group. 4. At this point I'll have at least 16TB of free array space to start migrating the data off the 10TB UD mounted drives. As each 10TB drive has their data moved to the array, pre-clear them and assign them to the empty slots left for them in the array. Each 10TB drive added to the array will increase the array size, allowing successive 10TB drives to have their data migrated. When all is said and done, I should end up with a layout like this: Slot 1: 1st shucked and pre-cleared 10TB drive, after data migration to the array Slot 2: 2nd shucked and pre-cleared 10TB drive, after data migration to the array Slot 3: 3rd shucked and pre-cleared 10TB drive, after data migration to the array Slot 4: 4th shucked and pre-cleared 10TB drive, after data migration to the array Slot 5: 5th shucked and pre-cleared 10TB drive, after data migration to the array Slot 6: 1st 8TB data drive (already part of the array) Slot 7: 2nd 8TB data drive (new, pre-cleared and tested) Slot 8: reserved for eventual addition of the current 8TB parity drive Slot 9: 4th 8TB data drive (already part of the array) Slot 10: 1st 6TB data drive (already part of the array) Slot 11: reserved for eventual addition of another 6TB drive, currently UD mounted when needed Slot 12: 1st 4TB data drive (already part of the array) Slot 13: 2nd 4TB data drive (already part of the array) Slot 14: 3rd 4TB data drive (already part of the array) Slot 15: 4th 4TB data drive (after migration of its data to the array, and pre-clear/stress test) Slot 16: 5th 4TB data drive (already part of the array) Slot 17: empty - reserved for future expansion Slot 18: empty - reserved for future expansion Slot 19: empty - reserved for future expansion Slot 20: empty - reserved for future expansion In addition I currently have a single 1TB SSD as a cache drive, and plan to add a 2nd 1TB SSD for cache redundancy. So does this plan seem OK, or are there any suggestions? Thanks in advance for any comments! Dale Edited June 20, 20197 yr by AgentXXL Clarified disk/slot locations since parity drives aren't in this list in unRAID
June 20, 20197 yr Author I just attempted to stop the array and move 1 disk (currently Disk/Slot 1) to its proposed location of Disk/Slot 6. I must be missing a step required to re-organize the array grouping as the Disk/Slot 1 shows as 'Missing' with a red X, even when I re-assign that drive to Disk 6. unRAID won't let me restart the array in this configuration. As the FAQ states that a re-organization is possible, what step am I missing? I'm sure I can only do one drive at a time, but does it mean that I would have to let each device rebuild from parity in its new location? I'm sure it's just something I'm overlooking.
June 20, 20197 yr Tools: New Config Preserve current assignments set to all, or something like that. If you only have single parity and are rearranging only current disks, you can safely check the box where parity is already valid before you start the array. If you are adding or removing drives, you must let parity be recalculated with the new disk arrangement. After you are done and have started the array, if there are any unmountable disks, don't format them unless you want to have a blank disk there. Post back with screenshots and questions if you have any. This is one of the areas where you can lose data if you mess things up.
June 21, 20197 yr Author 1 hour ago, jonathanm said: Tools: New Config Preserve current assignments set to all, or something like that. If you only have single parity and are rearranging only current disks, you can safely check the box where parity is already valid before you start the array. If you are adding or removing drives, you must let parity be recalculated with the new disk arrangement. After you are done and have started the array, if there are any unmountable disks, don't format them unless you want to have a blank disk there. Post back with screenshots and questions if you have any. This is one of the areas where you can lose data if you mess things up. Just to confirm, you're saying you have to reset the config to a new config to re-organize/arrange the disk assignments? I just picked up a new 32GB USB key to migrate my trial to before purchasing my Pro license. I assume I can use the 'Replace USB key' procedure to also accomplish the 'New Config'? The screenshot shows my current config.... the only disk in the correct slot is Disk 16, which I added there knowing I wanted to re-organize my layout. All disks have data on them, so yes I definitely want to ensure the procedure won't cause data loss. What I want to end up with is: Parity upgraded to 10TB Ironwolf - currently stress-testing this new drive Disks 1 - 5: empty/unassigned - to be used for my 10TB drives after their data is migrated to the array. Currently mounted via UD. Disk 6: move current Disk 1 to this slot Disk 7: new 8TB that's currently being pre-cleared/stress tested Disk 8: 2 month old 8TB parity drive from current setup, after ensuring the 10TB parity is OK Disk 9: OLD 8TB drive that will be replaced by another new 8TB, as soon as I can afford it. Disk 10: move current Disk 2 to this slot Disk 11: another 6TB that has to have its data migrated to the array before pre-clear/stress testing. Currently mounted via UD. Disk 12: move current Disk 3 to this slot Disk 13: move current Disk 6 to this slot Disk 14: move current Disk 5 to this slot Disk 15: another 4TB Hitachi that also needs its data migrated to the array before pre-clear/stress testing. Currently mounted via UD. Disk 16: no changes Disks 17 - 20: empty/unassigned When I can afford it, I'll also add a 2nd Ironwolf 10TB for dual parity. Any suggestions as to a procedure would be appreciated. Thanks again! Dale
June 21, 20197 yr Author BTW - this is all in a Norcotek 20 bay hot-swap SATA case, with the 1st 4 drives (including the parity drive) being connected to motherboard SATA ports, and the remaining 16 drives to a LSI 9201-16i in IT mode, v19.0 firmware. My current 1TB cache SSD is also connected to the primary motherboard SATA port (port 0) and the 2nd redundant cache SSD will be attached to the motherboard SATA port 1. Dale Edited June 21, 20197 yr by AgentXXL
June 21, 20197 yr 48 minutes ago, AgentXXL said: Just to confirm, you're saying you have to reset the config to a new config to re-organize/arrange the disk assignments? I just picked up a new 32GB USB key to migrate my trial to before purchasing my Pro license. The new config is purely in reference to disk assignments, it tells unraid that you wish to change slot assignments to different drives. Trial configurations can't be migrated to new trials intact, as an encouragement to purchase instead of continually changing USB and applying for new trials. Your data is safe, but you will need to redo any docker and VM configurations. I'm unsure just how much you can copy over intact vs. setting up fresh, but I assume you could back up VM and docker XML's and apply them to your existing data no problem. If you purchase a license for the new key, you should be able to copy your backed up trial configuration to the new licensed key no problem. Purely concerning your drive assignments, with that much change anticipated, you need to evaluate how much time you want to take to keep parity valid through the entire procedure. It would be MUCH faster to simply assign ALL the drives in their final position and build parity based on that, vs. doing the additions one at a time to keep parity valid. If you wish to keep parity valid, you can put only the current data drives in any slot number you wish, and the current parity1 drive in the parity1 slot. That will allow you to use the "parity is valid" option and simply do a non-correcting parity check to make sure things are working ok.
June 21, 20197 yr Author 12 minutes ago, jonathanm said: Trial configurations can't be migrated to new trials intact, as an encouragement to purchase instead of continually changing USB and applying for new trials. Your data is safe, but you will need to redo any docker and VM configurations. I'm unsure just how much you can copy over intact vs. setting up fresh, but I assume you could back up VM and docker XML's and apply them to your existing data no problem. If you purchase a license for the new key, you should be able to copy your backed up trial configuration to the new licensed key no problem. The unRAID purchase page differs from your comment on moving the trial to a new USB key BEFORE purchasing a licence. The attached screenshot is from https://unraid.net/pricing. As for parity, I'm not too concerned about it as I have to rebuild parity on the new 10TB drive anyhow. I assume this would be no different than a user that had their single parity drive fail, but all the data disks were still intact. Assuming that's the case, once I finish stress-testing the new 10TB parity drive, I have to then insert it in place of the existing 8TB drive and on the next array start, let it rebuild parity for the data disks. But if it's like you say, I should be able to use the 'Starting Over' procedure where I'm starting with a fresh USB key created by the unRAID creation tool. The procedure is listed here in the wiki: https://wiki.unraid.net/Files_on_v6_boot_drive under the 'Starting Over' section. As you can see, this section also details the files on the boot drive that you can transfer to a new key to retain your configs for network, Docker, VM's, etc. I'll keep reading up on it as I don't plan to make a single change until the new 10TB and 8TB drives are finished their pre-clear/stress testing. I'm expecting that won't be until sometime later tomorrow at the earliest, but I may just wait until Saturday morning to start.
Archived
This topic is now archived and is closed to further replies.