June 23, 20233 yr Hey Unraid community, I recently upgraded to 6.12.0 and had switched my cache pool (2x2TB SSDs) to ZFS (mirrored). Everything was fine for a couple days but I just attempted to upgrade to 6.12.1 which seemed fine as well but when my server restarted, the array would now be stuck at "Mounting" the cache pool. I disabled array auto start now and can boot my Unraid server with the array stopped as well as start the array in Maintenance mode. However I cannot start the array normally nor can I generate diagnostics logs while my array is attempted to start while trying to mount the cache pool. Trying to generate the diagnostics logs while trying to start the array gets stuck at: /usr/sbin/zpool status 2>/dev/null|todos >>'/mark-nas-diagnostics-20230623-0107/system/zfs-info.txt' Here is the cache pool stuck at "Mounting" When having the array started in Maintenance mode, I can generate the diagnostics logs but looking through it, it doesn't seem like there's anything that sticks out as broken. I then checked the System Logs and see this which likely is an issue: However being a complete noob with ZFS, I'm not sure where to start. Could someone help point me in the right direction? Thank you
June 23, 20233 yr Author Hey @JorgeB thanks for getting back. I'm unable to generate diagnostics when the array is attempting to start and the cache pool gets stuck at Mounting. Would the diagnostics when the array is stopped be of some use? I did comb through them and didn't see anything that stood out which is why the screenshot of the system logs looks like the best information I can pull when the array is trying to start.
June 23, 20233 yr Community Expert 19 minutes ago, viper81 said: I have the same exact error since 6-12.1 upgrade 30 mins ago Please start your own thread, as the issue is not resolved for the OP it can get confusing.
June 23, 20233 yr Community Expert 16 minutes ago, BigBoyMarky said: Hey @JorgeB thanks for getting back. I'm unable to generate diagnostics when the array is attempting to start and the cache pool gets stuck at Mounting. Reboot, don't start the array (disable auto-start if enabled) and post the output of zpool import
June 23, 20233 yr Community Expert Oh, and still post the diags, mostly so I can see the hardware used.
June 23, 20233 yr Author Thanks @JorgeB here's the output of zpool import and diagnostics attached. I also added a screenshot of the System Logs when I try to run the import. Looks like it's bumping into the same issue and attempting to generate the diagnostics after I tried to run zpool import gets stuck at the same spot. mark-nas-diagnostics-20230623-0856.zip
June 23, 20233 yr Community Expert Solution 4 minutes ago, BigBoyMarky said: I tried to run zpool import gets stuck at the same spot. That's expected, since it's importing the pool the same way Unraid was trying to, pool corruption can be the result of a RAM issue, it would be a good idea to run a couple of memtest passes before proceding, then you can try importing the pool in read-only mode: zpool import -o readonly=on cache If it works backup and re-create the pool
June 23, 20233 yr Author Thanks @JorgeB . I omitted testing RAM first and jumped straight into mounting as read only and it looks like I'm able to access the cache share now. I'll go ahead and try to do a backup first and then run my memtests. I'm currently copying all of the files off to USB drives... With that said, since this is a mirrored ZFS cache pool, would there be alternatives to copying data off and then recreating the pool? Would un-assigning one of the cache drives and attempting to re-import be a potential workaround given the current state? If so, I would be able to change my cache only shares to dump to the array and then recreate the cache pool that way.
June 23, 20233 yr Community Expert 12 minutes ago, BigBoyMarky said: With that said, since this is a mirrored ZFS cache pool, would there be alternatives to copying data off and then recreating the pool? In a case like this of pool corruption would always recommend recreating, zfs doesn't have an fsck, even if you could make it import without recreating would likely run into more issues in the feature, of course still need to fix whatever corrupted the pool, most commonly it's RAM related.
June 23, 20233 yr Author Gotcha okay thanks @JorgeB ! I will do some reading to see if I could dump this data onto one of the disks in my array instead of over USB.
June 23, 20233 yr Author 36 minutes ago, JorgeB said: In a case like this of pool corruption would always recommend recreating, zfs doesn't have an fsck, even if you could make it import without recreating would likely run into more issues in the feature, of course still need to fix whatever corrupted the pool, most commonly it's RAM related. Hey @JorgeB sorry just for clarity, with the state of my cache pool, I am definitely going to recreate it. But I was wondering if it's possible to have a temp work around to backing up the data by un-assigning one of the mirrored drives and then trying to start the array and getting the shares completely off the cache first? That way it would be easier for me to have all of the shares on the array and then recreate the cache pool without having to backup the data manually over USB etc? Edit: I noticed @viper81 was able to start his array after mounting the cache pool as read only? I'm wondering if it's safe to start the array with the cache pool mounted as read only. That way I believe I can do the following... 1. Start array 2. Copy ALL shares/folders MANUALLY from cache pool into any of the disks on the array 3. Update ALL shares to use array of disks 4. Shutdown server and run memtest 5. If nothing is wrong with the memtest, start server and rebuild cache pool 6. Now with cache pool rebuilt, I can start the array @JorgeB would the above be plausible? Edited June 23, 20233 yr by BigBoyMarky
June 23, 20233 yr Community Expert 50 minutes ago, BigBoyMarky said: I'm wondering if it's safe to start the array with the cache pool mounted as read only. That way I believe I can do the following... Yes, you can start the array, no problem.
June 24, 20233 yr Author Thanks again @JorgeB for the help. I was able to follow the steps above and get my data out and rebuild the cache pool. Bumped into 5487623 different other issues with my containers but slowly worked through fixing each one of them. Running a memtest now but marking this thread as resolved.
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.