January 10, 20224 yr Hello. I'm not sure where this error is coming from. If someone could please help. I've attached my log. Thank you! importimage-syslog-20220110-1831 (1).zip
January 10, 20224 yr Community Expert That would occur if you had something like a docker container configured to use /mnt/cache but do not have a pool called ‘cache’ which would result in /mnt/cache being a location in RAM. since you did not provide your full system’s diagnostics zip file it is not possible to be certain if that is actually what is happening.
January 11, 20224 yr Community Expert Looks like you probably got rid of or renamed your cache pool Jan 10 01:58:09 Importimage emhttpd: shcmd (393): mkdir -p /mnt/appdata_ssd Jan 10 01:58:10 Importimage emhttpd: shcmd (394): mount -t btrfs -o noatime,space_cache=v2 /dev/sdl1 /mnt/appdata_ssd ... Jan 10 01:58:10 Importimage emhttpd: shcmd (395): mkdir -p /mnt/cache_ssd Jan 10 01:58:10 Importimage emhttpd: shcmd (396): mount -t xfs -o noatime /dev/sdk1 /mnt/cache_ssd but didn't fix all references to it. 2 hours ago, itimpi said: That would occur if you had something like a docker container configured to use /mnt/cache but do not have a pool called ‘cache’ which would result in /mnt/cache being a location in RAM. Probably you have some container with appdata that won't survive reboot because it is in RAM.
January 11, 20224 yr Author Thank you. I just recently upgraded a cache pool and named it something else. How could I fix this? Would I have to go back and name it the same as it was before?
January 11, 20224 yr Community Expert You need to change anything that specifies a path to /mnt/cache. Probably a host path in one or more of your containers.
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.