January 2, 20242 yr Community Expert 1 hour ago, unraid newbie 55 said: The server can start now and mount the problem pool. The pool was encrypted, hence why it wasn't found before, it needed to be decrypted first, you didn't mentioned that, or I missed it. 1 hour ago, unraid newbie 55 said: I have to manually import the zpool after reboot and the pool is still degraded (currently resilvering). I would recommend fixing the pool manually and only re-import with the GUI once it's fixed.
January 2, 20242 yr Author OK - I think it is all fixed. Could you please look at the logs to confirm? Thanks Quote root@UnSAS:~# zpool status pool: cache state: ONLINE config: NAME STATE READ WRITE CKSUM cache ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 sdm1 ONLINE 0 0 0 sdl1 ONLINE 0 0 0 errors: No known data errors pool: disk1 state: ONLINE config: NAME STATE READ WRITE CKSUM disk1 ONLINE 0 0 0 md1p1 ONLINE 0 0 0 errors: No known data errors pool: disk2 state: ONLINE config: NAME STATE READ WRITE CKSUM disk2 ONLINE 0 0 0 md2p1 ONLINE 0 0 0 errors: No known data errors pool: sas state: ONLINE scan: resilvered 265G in 01:12:27 with 0 errors on Tue Jan 2 09:31:50 2024 config: NAME STATE READ WRITE CKSUM sas ONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 sdd1 ONLINE 0 0 0 sde1 ONLINE 0 0 0 sdn1 ONLINE 0 0 0 sdx1 ONLINE 0 0 0 sdy1 ONLINE 0 0 0 sdv1 ONLINE 0 0 0 sdr1 ONLINE 0 0 0 sdb1 ONLINE 0 0 0 sdc1 ONLINE 0 0 0 sdf1 ONLINE 0 0 0 raidz2-1 ONLINE 0 0 0 sdi1 ONLINE 0 0 0 sdt1 ONLINE 0 0 0 sdq1 ONLINE 0 0 0 sdw1 ONLINE 0 0 0 sdh1 ONLINE 0 0 0 sdg1 ONLINE 0 0 0 sds1 ONLINE 0 0 0 sdu1 ONLINE 0 0 0 sdp1 ONLINE 0 0 0 sdo1 ONLINE 0 0 0 errors: No known data errors root@UnSAS:~# unsas-diagnostics-20240102-1750.zip
January 2, 20242 yr Community Expert Looks fine, make sure the pool devices are assigned in the same order as the zpool status output: sdd, sde, sdn, etc
January 2, 20242 yr Author Yes - confirmed same order on zpool status as in the main tab of unraid. Problem solved! On reflection, I don't think I get much value from unraid itself. All of the above seems to have been an unraid bug which I have been dealing with through the command line. I mainly use unraid because SpaceInvaderOne has some good tutorials e.g. latest one on sleep states. I wonder if the power issue would have caused the same drama in ProxMoxx. In future, I will try to leave the unraid platform
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.