nivagator

Unfortunately, I wasn't able to find a solution to keep my existing containers. I wiped the docker image entirely and started over deploying them all from the saved templates. It worked ok and only required a bit of manual tweaking to get it all back. The biggest challenge was the downtime. I can't prove it but I think it was something to do with the btrfs cache I had spanning two SSDs. After the wipe, I started over with a single, XFS cache and more robust backups.

Where are Volumes stored? For example, this is declared by the Immich docker compose stack. If left as is and bind mounts are not declared, where would the pgdata volume be stored in the unraid system? volumes: pgdata: model-cache: tsdata:

After a reboot, the Docker will not start. The error on the GUI is: Docker Service failed to start. Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 712 Couldn't create socket: [111] Connection refused Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 898 docker.txt log shows: failed to start daemon: Error initializing network controller: could not delete the default bridge network: network bridge id 96d4f72b55fb181998c3639f0946f75e3ced5a47a4e76b9af0218118c109432a has active endpoints Diagnostics attached. Any help to resolve would be greatly appreciated. galaxy-diagnostics-20230412-2048.zip

Having trouble with my cache. Cache is two 1TB SSDs. Original symptom was docker failing and unable to start. Find Common Problems stated the cache was read-only. I assumed (probably incorrectly) that one of the drives was failing. After disabling docker and vms, I changed the appropriate shares to Cache: Yes and ran the Mover. Not all data was able to move with errors in the mover logs. Once the mover finished, I removed the (I thought) offending drive from the cache pool and allowed BTRFS to being rebuild, but that failed and again forced it into readonly. Jan 11 21:25:16 galaxy kernel: BTRFS info (device sdk1): balance: ended with status: -5 Jan 11 21:25:16 galaxy kernel: BTRFS info (device sdk1: state EA): forced readonly Full diagnostics attached. Starting to think my cache is corrupted. I'm happy to jettison the cache and start fresh, but i'm not exactly clear where to begin. Yes, I ran this server with overclocked memory and I may be paying the price for that now. I have removed the memory overclock since the diagnostics were taken. Thanks galaxy-diagnostics-20230111-2137.zip

Disabled memory overclocking, updated to 6.11, updated all plugins and docker, removed NerdPack. Still occurring. Using Thunar File Manager on the client system. I said the error occurred when deleting files, but technically, i was clicking "Move to Trash". I enabled Delete in the Context Menu and have had no issues when choosing Delete and not Move to Trash. I'm assuming this is relevant, though I'm not experienced enough to know what it means.

Updated to 6.11.0 and it crashed immediately on the first attempt deleting files over nfs. This effectively makes the Unraid shares unusable... Anything else I can look into? Same segfault on shfs Oct 4 21:41:47 galaxy kernel: shfs[12888]: segfault at 10 ip 000015002048f5c2 sp 000015001f05fc20 error 4 in libfuse3.so.3.12.0[15002048b000+19000] Oct 4 21:41:47 galaxy kernel: Code: f4 c8 ff ff 8b b3 08 01 00 00 85 f6 0f 85 46 01 00 00 4c 89 ee 48 89 df 45 31 ff e8 18 dc ff ff 4c 89 e7 45 31 e4 48 8b 40 20 <4c> 8b 68 10 e8 15 c2 ff ff 48 8d 4c 24 18 45 31 c0 31 d2 4c 89 ee Oct 4 21:41:47 galaxy kernel: ------------[ cut here ]------------ Oct 4 21:41:47 galaxy kernel: nfsd: non-standard errno: -107

I saw that shfs crash and found your post here. Different service, but could it be memory overclocking related? I am using NFS almost exclusively to access shares on my local network. I can replicate this failure nearly on command modifying or deleting images on a Linux client connected via NFS. Its typically on my third or fourth save or delete, the shares crash. Rebooting does restore the shares, but again, I happens consistently. I haven't had this issue with any other usecase and all other services are working as expected. I've been running this system for almost two years with no problems until this error.

Diagnostics attached. galaxy-diagnostics-20221004-1110.zip

Running into this issue multiple times today editing photos in a share. Unraid 6.10.3 Here is my output: $ ls -la /mnt/user /bin/ls: cannot access '/mnt/user': Transport endpoint is not connected