May 24, 20242 yr I recently formatted the cache drive because of permanent errors. I am in the middle of addressing that and noticed this message. It mentions "zpool upgrade" can be executed. Is this something we should do?
May 24, 20242 yr Community Expert If the cache was formatted with the same release it should not show that, you can upgrade the pool, just note that if you downgrade back to the releases used to format the pool, it will no longer work.
May 24, 20242 yr Author What do you mean by same release? 1. i had stopped the array 2. Cleared the cache drive 3. Formatted the drive with zfs but yeah I’ll fully upgrade.
May 24, 20242 yr Community Expert It doesn't make sense that a pool that was created with one release would ask to update with the same release, post the diagnostics.
May 24, 20242 yr Author Yeah not sure what's going on but I did upgrade and the message went away. After setting up dockers again, things seem to be working ok? 🤷♂️ Diagnostics attached homeserver-diagnostics-20240524-1011.zip Edited May 24, 20242 yr by andyd
May 24, 20242 yr Community Expert Solution You formatted the device with UD, hence the warning, UD uses a different option to maintain compatibility if a user formats a pool with v6.13-beta and wants to go back to 6.12, you could have formatted using Unraid, and that would not have happened. P.S. you also need to see what's going on with disk3: May 24 04:22:44 HomeServer emhttpd: pool: disk3 May 24 04:22:44 HomeServer emhttpd: state: ONLINE May 24 04:22:44 HomeServer emhttpd: status: One or more devices has experienced an error resulting in data May 24 04:22:44 HomeServer emhttpd: #011corruption. Applications may be affected. May 24 04:22:44 HomeServer emhttpd: action: Restore the file in question if possible. Otherwise restore the May 24 04:22:44 HomeServer emhttpd: #011entire pool from backup. Having two pools with data corruption, since the cache pool also had some before the format, suggests a hardware issue, like bad RAM
May 24, 20242 yr Author Makes sense. I upgraded and things seem to be ok. As for disk 3, yeah I know. I did have bad RAM which I have removed from system. I was reformatting the cache drive for corruption in the docker image and some other folders. That's resolved now. I will start another thread about the drive as I'm not sure how to handle that. Thanks!
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.