jovdk Posted April 23, 2021 Share Posted April 23, 2021 Hi Everyone I'm getting this error after replacing my cache drives and restoring appdata on them Invalid folder cache contained within /mnt when i go to the system log I see this error every second emhttpd: *** bug: 5286 /mnt/user/Cloud cache (cloud is probably my nextcloud instance) any idea how to fix this? dvelectro-diagnostics-20210423-2135.zip Quote Link to comment
Squid Posted April 24, 2021 Share Posted April 24, 2021 16 hours ago, jovdk said: I'm getting this error after replacing my cache drives and restoring appdata on them At the same time did you rename the pools or remove the cache pool? You have no "cache" pool, but appdata backup was set up to backup from the cache pool to the array. When you restored it, it dutifully put the backup exactly where it was told to, except that the cache pool doesn't exist, so it winds up in RAM Additionally, since this is what presumably happened, you also have docker containers that were referencing /mnt/cache/appdata/..., so the system is going to automatically create /mnt/cache every time the container starts. Quote Link to comment
jovdk Posted April 24, 2021 Author Share Posted April 24, 2021 I removed the pool and made a new one actually 2 new pools 5 hours ago, Squid said: You have no "cache" pool, but appdata backup was set up to backup from the cache pool to the array. When you restored it, it dutifully put the backup exactly where it was told to, except that the cache pool doesn't exist, so it winds up in RAM Additionally, since this is what presumably happened, you also have docker containers that were referencing /mnt/cache/appdata/..., so the system is going to automatically create /mnt/cache every time the container starts. so is there any way to make sure everything is using the new pool? I do see the appdata folder on the new pool Quote Link to comment
jovdk Posted April 24, 2021 Author Share Posted April 24, 2021 (edited) I think I've fixed it I removed the cache folder in terminal, since my cache pools now have another name and the error is gone tnx for the help @Squid, got me in the right direction Edited April 24, 2021 by jovdk Quote Link to comment
itimpi Posted April 24, 2021 Share Posted April 24, 2021 Did you figure out why that folder was created in the first place? If not it is likely to come back if you reboot. Quote Link to comment
jovdk Posted April 25, 2021 Author Share Posted April 25, 2021 @itimpithat folder was created when i used my old cache pool when I restored my appdata it wanted to write there but my new cache pool have a different name unraid changed the cache drive automaticly when i went in to the share options, but in the shares tab it still wanted to go to the old drive So I had to manually chanche the cache drives from my shares, let them copy ofcourse to the new pool, and I did a restart then the error in my system log was gone, so then i removed the folder and contents in terminal did a restart, and everythink is working fine now Quote Link to comment
itimpi Posted April 25, 2021 Share Posted April 25, 2021 3 minutes ago, jovdk said: @itimpithat folder was created when i used my old cache pool when I restored my appdata it wanted to write there but my new cache pool have a different name unraid changed the cache drive automaticly when i went in to the share options, but in the shares tab it still wanted to go to the old drive So I had to manually chanche the cache drives from my shares, let them copy ofcourse to the new pool, and I did a restart then the error in my system log was gone, so then i removed the folder and contents in terminal did a restart, and everythink is working fine now If you have done a reboot and the folder does not reappear then it sounds as if you DID correct the root cause. It was not clear to me that you had done the final reboot to confirm this was the case. Quote Link to comment
gnv9212 Posted March 12, 2022 Share Posted March 12, 2022 Hi - I received this error after upgrading to 6.10.0 RC3. Unable to locate problem. Have been running Unraid for years but first time seeing this after upgrade. Made no major changes since then. Diagnostics attached. nvdellunraid-diagnostics-20220312-0248.zip Quote Link to comment
Recommended Posts
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.