Can someone help me with what the heck is happening? I keep seeing this error in the log and it keeps giving me a "starting services" constantly. I also noticed on my windows pc that the network link for my unraid keeps disappearing and reappearing.

tower-diagnostics-20230708-1419.zip

Delete that file form the flash drive.

Hi, did you find a solution to this?
I I have the same fault: Invalid argument (22): fopen: /boot/config/shares/appdata#015#015.cfg

I do not find that file, either in terminal or when browsing the flashdrive on my PC.

 

Post the output of:

 

ls -l /boot/config/shares

 

root@Server:~# ls -l /boot/config/shares
total 96
-rw------- 1 root root 449 May 18  2022 SSD\ 256GB.cfg
-rw------- 1 root root 443 Jul  2  2022 andreas.cfg
-rw------- 1 root root 452 Jul 27 14:01 appdata.cfg
-rw------- 1 root root 464 Feb 10  2022 domains.cfg
-rw------- 1 root root 447 Jan 24  2022 downloads.cfg
-rw------- 1 root root 451 Jul  2  2022 ftp.cfg
-rw------- 1 root root 444 Feb 17  2022 guacamole.cfg
-rw------- 1 root root 453 Dec  4  2022 isos.cfg
-rw------- 1 root root 433 Jul 23 23:52 media.cfg
-rw------- 1 root root 449 Jan 30  2022 nextcloud.cfg
-rw------- 1 root root 435 Jan 24  2022 nora.cfg
-rw------- 1 root root 449 Jul 15  2022 system.cfg
root@Server:~# 

There were some other old shares but used the "Clean up" button on the Shares tab to remove them.

This is causing an issue as I can't stop the array either as it can't unmount the cache. 

After reading many forum posts I saw that "Loop2" for the docker image could not be unmounted, even when trying to do it manually in terminal. Only way was to force an unclean reboot.

server-diagnostics-20240728-2356.zip

And it's still showing that invalid file after cleanup?

Yes it did.
After doing a "Compute all" under Shares I see that something has created an empty Appdata folder on the array.

Tried to delete it via the Unraid GUI but that was not possible. Using terminal I could delete it, and the faults in the log stopped and it was now possible to stop the array as it could unmount the cache drive.

Appdata share is created by default if the docker service is running.

Yes but strange there was an empty Appdata share folder created on the array on one of my disks. 
Appdata share was set to cache and secondary array, but the cache has never been even close to filled up.
Anyway all was good as soon as I deleted that Appdata folder. Thanks for the answers.