January 22, 20251 yr Pretty new with Unraid and starting on 7.0, so this may be a newbie issue. That said: I'm using an SSD pool as store for my docker apps and VMs. Initially, the pool consisted of a single 4 TB drive, I've now added a 2nd 4TB drive. The intent is to mirror these for redundancy, RAID1. Paused the arrays, added the drive to the pool, started the array... But the stats looked like that 2nd drive isn't really being used. I also didn't notice a rebalancing or anything, even though I triggered it manually. It also only shows the first drive in the status and file system, and "allocation profile: single" which I cannot change. How can I add the 2nd drive and have it properly be used in RAID1? Thank you Edited January 22, 20251 yr by mattesW
January 22, 20251 yr Author Here it is, thank s for checking. nexus-nas-diagnostics-20250122-0756.zip
January 22, 20251 yr Community Expert Can't see what happened since the pool was already missing a device at last boot, but try this, stop the array, click on the first device of that pool, then "Remove Pool", back on main add a new pool with the same name a single slot, assign only the Apps1 device (serial ending in 522), start the array, post new diags.
January 22, 20251 yr Author OK, I did that. What seems odd is that when I went through the steps and re-added the new pool (same name) with a single slot, assigned the 522 drive, and started the array - it automatically shows me "Apps 2" as not installed. Did it reuse the old pool config somehow? Attached also the new created diagnostics. nexus-nas-diagnostics-20250122-1113.zip
January 22, 20251 yr Community Expert 24 minutes ago, mattesW said: it automatically shows me "Apps 2" as not installed It's normal, because the other device was "missing", now stop the array, assign the other device as apps2 and start the array, it should start a balance, when the pool activity stops, post new diags.
January 22, 20251 yr Author Stopped the array. Assigned the second drive as app2, but now it cannot even start the array and gives the following error... nexus-nas-diagnostics-20250122-1204.zip
January 22, 20251 yr Community Expert The problem is that the pool is a single in the cfg: diskFsProfile="single" But not sure why it is that way, doing what I asked should import the poor as "raid1", and I just tested to confirm, and it did that. To fix the issue: stop the array unassign apps2 edit /boot/config/pools/apps.cfg and change diskFsProfile="single" to diskFsProfile="raid1", sve and exit reassign the apps2 device, start the array.
January 22, 20251 yr Author Thank you, the array started back with that change. After assigning the second drive and starting the array, I see diskFsProfile=single again in the pool, even though it started back up with both assigned... Is that normal? I do see the second drive listed now but I want to make sure it actually is running in RAID1. Diagnostics attached. Thanks again for all your help! nexus-nas-diagnostics-20250122-1302.zip
January 22, 20251 yr Community Expert Solution It balanced to single, not sure why, but just click on the pool and balance to raid1, it should then remain a mirror.
January 22, 20251 yr Author That worked now, it shows Raid1 allocation profile. The same balance conversion had no effect prior going through this process of re-adding the pool. Looks like it's all in great shape now. Thank you so much for your help!
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.