awediohead Posted January 30, 2022 Share Posted January 30, 2022 So yesterday with the high winds we had a powercut for about 15 minutes - when power was restored and I rebooted my server I got the notifications shown in the attachment. I call them weird because I haven't changed anything for months: I haven't renamed a pool as far as either appdata or system shares are concerned. I have 2 cache SSDs called cache_standard and cache_vms with the latter being used for VM related stuff - isos, domains etc. Been that way for well over a year. Re the domains share it's possible that there maybe some files/folders VM related stuff I did over 18 months ago, but that begs the question why this hasn't been flagged up since? Obviously I suspect the power outage has messed something up and I'm wondering what to do about it? Apart from these alerts in Fix Common Problems everything seems to be working as normal. I rarely boot up the sole Windows 10 VM I have installed, as this is only a 4-core CPU and it's got its work cut out to keep up with media server duties. I am a novice with regard to the CLI but perfectly willing to learn if someone can walk me through what to do. Thank you PS Yes I have a UPS arriving tomorrow! Quote Link to comment
Squid Posted January 30, 2022 Share Posted January 30, 2022 Post your diagnostics because the implication is that a drive is no longer present on your system (if only because I need to see if there's a mistake in the detection code) 1 Quote Link to comment
awediohead Posted January 30, 2022 Author Share Posted January 30, 2022 Thanks Squid Diagnostics attached - if you need them un-anonymised let me know. cheers singthesis-nas-diagnostics-20220130-1717.zip Quote Link to comment
Squid Posted January 30, 2022 Share Posted January 30, 2022 So, I looked at the appdata share shareUseCache="prefer" shareCachePool="cache" # Share exists on disk1,disk2,disk3,cache_standard And these are your cache pools Jan 29 12:14:35 SINGTHESIS-NAS emhttpd: shcmd (43): mount -t btrfs -o noatime,space_cache=v2 /dev/sdb1 /mnt/cache_standard Jan 29 12:14:35 SINGTHESIS-NAS emhttpd: shcmd (45): mount -t btrfs -o noatime,space_cache=v2 /dev/sdc1 /mnt/cache_vms Net result here is that any new files for appdata are being written to the array because the "cache" pool does not exist at all. Once you change the settings to properly reflect which cache you want to actually use, disable all the services in settings and run mover. After it's done re-enable the services and you should be good to go. 1 Quote Link to comment
awediohead Posted January 30, 2022 Author Share Posted January 30, 2022 Hi Squid - what I don't understand is I haven't changed anything - When I look at the attached screenshots, User Shares shows that this mysterious 'Cache' is assigned to appdata and system, but when I select those shares they both show themselves to have been assigned to cache_standard as shown below: That's how it's been for as long as I can remember - the cache_standard ssd having been there since I first installed unraid - I added the cache_vms drive a year or more ago. It might be that when I added the cache_vms drive I renamed the original cache to cache_standard - I don't remember. Either way though, nothing has changed for months as I recall, and until the power cut the server had been up with no errors from FIx Common Problems for a couple of months. Does a bad shutdown maybe cause the system to do a deeper level of self-check ? i.e. that might reveal something I messed up months ago? Anyway, by 'disable all the services" does that mean turn docker off? Not running any VMs . . . anything else to disable? And once off - given the share settings that have always been in place for appdata and system, I should just run mover? Thanks very much for your help! Quote Link to comment
Solution Squid Posted January 30, 2022 Solution Share Posted January 30, 2022 Both your shares screenshot and the diagnostics show that the system isn't what the individual shares may say. (They may be showing that because there is no "cache" drive and that's what it's defaulting to). Make a change (any change) and revert it then apply and the continue with my directions. And yes by disable all services I mean to disable the docker service, disable the VM service in settings, not just stop the individual apps. appdata for sure contains files on the array due to how this was working for you and it is going to significantly affect your performance. 1 Quote Link to comment
awediohead Posted January 30, 2022 Author Share Posted January 30, 2022 Hi Squid - thanks to your instructions no more errors re appdata and system, but the process doesn't seem to have done anything for the domains error - I tried switching the cache, running the mover and then switching back and running the mover again. But it still says "Share domains set to use pool cache_vms, but files / folders exist on the cache_standard pool" However when I look at the /mnt/cache_standard/domains folder contents it says it contains 0 objects: 0 directories, 0 files (0 B total) The three vdisk1.img containing folders for Windows XP, 7 and 10 are all on cache_vms What do you suggest please? Thanks Quote Link to comment
itimpi Posted January 30, 2022 Share Posted January 30, 2022 17 minutes ago, awediohead said: However when I look at the /mnt/cache_standard/domains folder contents it says it contains 0 objects: 0 directories, 0 files (0 B total) Even though it is empty just the presence of the domains folder could cause that warning so delete the empty folder. 1 Quote Link to comment
thainadian Posted January 31, 2022 Share Posted January 31, 2022 Thanks for these details. I was able to reset the error as I had renamed my cache after reconfiguring the array, but the OS held on to the initial cache_name Quote Link to comment
awediohead Posted January 31, 2022 Author Share Posted January 31, 2022 Sorry to say but I don't actually know how to delete the folder as it's specific to the one cache ssd I think it'll be something like rm /mnt/cache_standard/domains - but obviously I'm not going experiment in CLI !!! Can someone walk me through it please? Quote Link to comment
awediohead Posted February 1, 2022 Author Share Posted February 1, 2022 Midnight Commander to the rescue - marked as solved. No more errors Thanks very much Squid 1 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.