jj_uk

Is there any prospect of getting the cache drives back online? There were a few dockers used to run a smart home. We're currently sat in the dark. I have a backup of appdata from the day before, created by CA Backup. It contains a full /appdata/ backup and 'libvirt.img'.

Attached, diagnostics taken from a reboot a few mins ago. Thank you so much for your time helping me with this. I'm 'completely' stuck. tower1-diagnostics-20210913-0931.zip

All shares that were on the cache disk are empty. Seems the caches have unmounted or something? How can I instruct unraid to start using the cache disks again?

My appdata share is completely empty. Please help ! I'm starting to panic!

I've just restarted the server and all my dockers are gone ! I have no dockers installed! What's going on!

This morning, all dockers that are usually stopped as part of the CA backup process have failed to restart. Pages in the UnRAID gui have php error messages on them. Warning: file_put_contents(/var/lib/docker/unraid/images/home-assistant-icon.png): failed to open stream: Read-only file system in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 90 Warning: file_put_contents(/var/lib/docker/unraid/images/mariadb-icon.png): failed to open stream: Read-only file system in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 90 Warning: file_put_contents(/var/lib/docker/unraid/images/NginxProxyManager-icon.png): failed to open stream: Read-only file system in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 90 tower1-diagnostics-20210912-1235.zip

I just installed a new instance of the container and it set all created folders to r-x, as expected.

Thanks, yes, that's fixed it. I didn't change that permission on the folders. Maybe a bug?

I don't think it's that. If I try to navigate to an affected folder using the Krusader app, I get an access denied error. The permissions for the folders are: drw-rw-rw- 1 99 users 32 May 6 04:49 blueprints

Since updating to 6.10, some files and folders inside appdata are not visible on Windows. The whole appdata folder wasn't being exported as the update changed this from export: yes to export: yes(hidden). - why? I've changed it back to export: yes, but there are a few folders in there that are showing as empty in Windows explorer, but if i go into the affected container's colsole, I can see the files with `ls -la`. Any ideas?

Previously, using OpenVPN, a connected client could only access the internet, and not any lan addresses. This allowed for phones to connect back to my home network for internet access only; as my router dns is pointing to pihole, it allowed 4G/5G phones to have adblocking when not connected to my home wifi. I'm trying to reproduce this with wiregaurd, but I can't figure it out. I can connect, but I still have access to all LAN addresses. How can I block access to LAN addresses?

Ok thanks. I've updated to 6.10.0 rc1. Hopefully that'll fix it, but if not, I'll move pihole to a RPI, as the other methods of fixing this are beyond me.

Attached are the diagnostics. I've not run a memtest. tower1-diagnostics-20210811-0911.zip

I used the drag and drop method on the forum. I've redone it now with the "select files" option. Seems that drag/drop doesn't work for me. Attached. syslog-192.168.1.230.log

Aug 14 13:39:48 tower1 kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000 That's interesting. Attached the syslog. syslog-192.168.1.230.log

I've just performed a hard reset as the server locked up earlier today.

Dang. I was logging to flash a while back but disabled it. I've now set up a syslog server to ssd. Thanks.

Server was unresponsive this morning. I couldn't ping the server IP address, no web gui and dockers didn't seem to be working. I've looked in the diagnostics (attached) that were generated once the server had restarted from a hard reset, but don't know what I'm looking for. Any help appreciated.

It doesn't have to stop the dockers. You can select which dockers are stopped, or not. Files that are in use won't be backed up if the dockers isn't stopped- that's the difference.

It appears that the backup looks for a match in the path, rather than an absolute path. Maybe the developer could confirm this? I've added this, which should be the same for all plex dockers regardless of maintainer. My backup runs at 2:30am, so we'll see tomorrow what the results are. Plex Media Server/Cache/,Plex Media Server/Crash Reports/,Plex Media Server/Logs/,Plex Media Server/Media/,.DS_Store,*.log,*.log.*,*.tmp,.Recycle.Bin

Did you get this working? I'm thinking of doing the same. Plex database is just too large for backups.

The plugin stops all dockers, then begins the backup. I'm assuming this is done so there's a complete snapshot at that point in time? My problem is the backup is now taking 4 hrs to complete. I was wondering if it would be possible to stop a container, back it up, then start it, move on to the next. If that's a good idea or not I don't know? Or maybe stop docker, make incremental backup (fast), start docker, then recreate the tar from the incremental and delete the incremental? There's not really a good time to stop docker for 4 hrs. It takes down my smart home. If one of the kids get up in the night during the backup, the lights don't work. I can't think of a solution?

I've changed my USB stick to a ZZH and it's using ttyUSB0. Problem is, my docker cannot access it. I believe its something to do with permissions: # ls -l /dev/ttyUSB0 crw-rw---- 1 root dialout 188, 0 Jun 24 20:32 /dev/ttyUSB0 I'm not sure what to do to allow the docker (zigbee2mqtt) to access the device. My docker extra params has --device=/ttyUSB0 Earlier in this thread, its mentioned that: "For these devices all needed is to add the user running the software in the container to the dialout group." But I don't know how to do that.

So if I add this to the go file, will that work at restart? echo "SUBSYSTEM==\"tty\", ATTRS{idVendor}==\"0451\", ATTRS{idProduct}==\"16a8\", ATTRS{serial}==\"serial num removed\", SYMLINK+=\"zigbee2mqtt\"" > /etc/udev/rules.d/99-usb-serial.rules

I think an invalid cert should work, although not sure. I can set this up with a reverse proxy accessible from the internet but like you I want this local only. Hopefully someone will know the answer on how to access the docker over https locally.