August 27, 20241 yr I'm new to Unraid. I set up a 6-disk raidz2 that I'm happy with. After that I had a couple of extra nvme's so I added them as cache, and slog drives to the pool. After learning more I found that I don't need them as Ram handles so much of that duty and I have enough of that. So I went to remove the two drives. I started with removing the cache drive and the pool mounted fine. Next, I tried to remove the slog and it wasn't happy and won't mount the pool without reformatting. Can anyone tell me the correct way to remove this slog without reformatting? Thanks so much, everyone.
August 27, 20241 yr Author I have attached the diagnostic file as requested. Thanks so much! unraid-diagnostics-20240827-0747.zip
August 27, 20241 yr GUI does not yest support removing sub pools, it needs to be done manually, since the pool will need to be re imported and it's degraded, I would recommend you fix that first: NAME STATE READ WRITE CKSUM pool_40tb DEGRADED 0 0 0 raidz2-0 DEGRADED 0 0 0 sdf1 ONLINE 0 0 0 sde1 ONLINE 0 0 0 sdd1 ONLINE 0 0 0 sdc1 ONLINE 0 0 0 sdb1 ONLINE 0 0 0 spare-5 DEGRADED 0 0 0 7931583891141304603 FAULTED 0 0 0 was /dev/sdb1 sdg1 ONLINE 0 0 0 logs nvme2n1p1 ONLINE 0 0 0 spares sdg1 INUSE currently in use I can then post the instructions to removed the slog
August 27, 20241 yr Author Thanks. I had a bad drive last night but I had a spare drive on hand and I have fixed that issue. That brings me to another question if possible. I had a drive in the pool as a hot spare. When a drive in the main pool failed I waited and was expecting the system to just do its thing and replace the failed drive. but it didn't. I then just manually replaced it so that the problem was fixed. it now shows as healthy. Does having a hot spare mean it will do anything automatically? or will I always have to move it up to the main pool? Feel free to send those steps. Again, I can't thank you enough!
August 27, 20241 yr 16 minutes ago, cmoney said: but it didn't Currently Unraid doesn't activate the spares automatically, see the release notes.
August 27, 20241 yr Author "I can then post the instructions to removed the slog" Can you send me these? Thanks again.
August 27, 20241 yr Only recommend doing this when the pool is no longer degraded, with the array started type: zpool remove pool_40tb /dev/nvme2n1p1 confirm it was removed with zpool status If yes, stop the array and re-import the pool, to do that, unassign all pool devices, start array, stop array, re-assign all pool devices (except the removed slog), start array
August 27, 20241 yr Author So I just got home and re checked and it still says the pool is degraded when I click on it. But on the main page it shows all the drives green and healthy. Which is correct?
August 27, 20241 yr 2 minutes ago, cmoney said: Which is correct? Zpool status is the correct one, GUI won't currently show most issues, do you have a spare to replace the faulted disk? Or do you want to use the spare permanently and remove it from the spares pool?
August 27, 20241 yr Author So I had a "Hot spare" already assigned to the pool when the drive failed. When the system didn't automatically swap out the faulted drive for the spare, I just removed the spare, and added it as the 6th drive in the pool. I figured it would re-silver and be all set. So there should be 6 good drives in the pool right now, and no hot spare. So to answer your question I thought I already did replace the faulted disk, with the hot spare. Did I do something wrong?
August 27, 20241 yr There's still a spare, see if you can offline the spare, then remove the spare, then use it to replace the faulted disk, I'm don't have a chance to confirm the commends at the moment, but it should be: zpool offline pool_40tb /dev/sdg1 then zpool remove pool_40tb /dev/sdg1 then zpool replace pool_40tb 7931...etc /dev/sdg1
August 27, 20241 yr With the array running, or if you stop it you need to import the pool manually, either way, pool needs to be re-imported after, same procedure described above.
August 27, 20241 yr Author Roger that. I did it with the array started and The first command was fine. The second is kicking out this. "cannot remove /dev/sdg1: Pool busy; removal may already be in progress"
August 27, 20241 yr Author OKay now im getting this "cannot replace 7931583891141304603 with /dev/sdg1: already in replacing/spare config; wait for completion or use 'zpool detach'"
August 27, 20241 yr Author Yes I ran that command but it doesn't seem to give any feedback on if it was successful or not
August 27, 20241 yr Looks like it, you should then be able to remove the slog following the post above.
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.