-
Errors during parity check after hardware upgrade - Unsuccessful self-config (-ETIMEDOUT) key 0x906 value 0x1123800
I updated the bios during the initial build so it’s already on the latest version. Does disabling GuC mean I lose the ability to do hardware video transcoding (intel quick sync)?
-
Errors during parity check after hardware upgrade - Unsuccessful self-config (-ETIMEDOUT) key 0x906 value 0x1123800
Me test passed. No errors
-
Errors during parity check after hardware upgrade - Unsuccessful self-config (-ETIMEDOUT) key 0x906 value 0x1123800
I migrated my unraid into a new chassis with new proc, mobo, and mem over the weekend. Basically the hard drives in the storage array are the only thing that is the same. The system locked up the other day and after rebooting it did a parity check. Upon completion it said there were 6087 errors. I looked at the log and saw a lot of errors that said Unsuccessful self-config (-ETIMEDOUT) key 0x906 value 0x1123800. I'm not sure what this error means, any insight? Am I looking at some bad hardware? diagnostics-20260107-1323.zip
-
-
Moving cache contents to new cache drive
I think I have it all figured out. The steps in the guide are what I had done. The issue I found is that I had mapped most of my docker apps as well as the docker image directly to the cache ie /mnt/cache/docker/appdata/blahblahblah. To fix I set my docker and appdata shares back to cache and ran the mover. Then I modified all of the necessary paths and pointed them through the docker share ie /mnt/user/docker/blahblahblah. I confirmed all of my docker apps were able to run then shut them down again and disabled docker. I then set the docker and appdata share along with all others to move cache->array and ran mover again. Everything moved this time. I removed my cache disk pool and confirmed all the docker apps are still able to run. So now I think I'm ready to move into the new server chassis/hardware then add the new cache disk and do the process in reverse (excluding hard coding paths to the cache of course) to get these items back onto cache. Thank you for the help
-
Moving cache contents to new cache drive
-
Moving cache contents to new cache drive
Unraid 7.2.3 I am preparing to move my unraid into a new server (new proc, mobo, mem, nvme cache drive). The array storage will remain the same, I'll just move them into the new case. My old cache drive is a pool of small m.2 SSDs. They will not be moving to the new server. So I'm trying to ensure everything stored on them is moved off. I had three shares set to store in cache (array->cache) : appdata, system, and domains. I changed those to cache>array and ran the mover. The problem is my docker image and all of the appdata for my docker apps is still sitting on the cache drive. Not just a copy but that appears to be the only location. If I look at the shares it only lists cache for these files and folders. The funny thing is the Docker share was set to array only. I never changed it yet the docker.img is only located on the cache. My plan had been to move items from the cache to the array. Remove the cache drive and confirm everything still works. Move into the new server. Confirm everything works again. Move those items to the new cache drive. How can I get these items to move into the array? Is there a step I'm missing?
hairybuffalo
Members
-
Joined
-
Last visited