Unsealed0019

That would explain it, thanks. I am indeed using btrfs. Does running the mover while the cache is still being used lead to such corruptions as well?

Thanks for checking. Well it was within an hour or so before the original post. It's working now after reboots, and maybe a relevant adjustment to NFS but more importantly (I think) a stricter control over the cache and monitoring it to make sure it doesn't fill up. So hoping to get some more definitive answers on how a full cache could negatively affect shares in this manner, or how NFS parameters may as well. I changed the NFS params to: IP(ro,sync,root_squash,all_squash,no_subtree_check) IP2(rw,sync,root_squash,all_squash,no_subtree_check) async > sync (looks like async can sometimes cause issues based on the description for it though I never seem to have issues unless the cache drive fills up) :~# ls -la /mnt/user total 0 drwxrwxrwx 1 nobody users 119 May 19 17:48 ./ drwxr-xr-x 19 root root 380 May 19 16:50 ../ drwxrwxrwx 1 nobody users 752 May 18 16:53 appdata/ drwxrwxrwx 1 nobody users 102 May 17 16:09 backups/ drwxrwx--- 1 nobody users 137 Dec 22 16:10 data/ drwxrwxrwx 1 nobody users 82 May 17 15:57 domains/ drwxrwxrwx 1 nobody users 24 May 18 06:44 share1/ (used shared that caused dropoff) drwxrwxrwx 1 nobody users 48 May 17 15:35 isos/ drwxrwxrwx 1 nobody users 28 May 19 17:07 share2/ (used shared that caused dropoff) drwxrwxrwx 1 nobody users 26 Sep 13 2021 system/

I have 2 main shares which are more or less equally important which keep having this issue.

They are still there on disk and when I reboot UNRAID things appear to be working again. Been seeing this issue more and more lately and it's causing concern but I'm in the middle of doing some transfers or something with shares and then it drops them all (NFS/SMB all gone, no systems can access). Seems like it might have to do with a cache drive that keeps filling up too quick (it's small) but I really am not sure. Or maybe related to NFS issues but SMB also drops out. I have the NFS shares more or less like these: IP(ro,async,root_squash,all_squash,no_subtree_check) IP2(rw,async,root_squash,all_squash,no_subtree_check) Nothing crazy. Maybe I am doing too much with the file systems over the network but it's maybe 4-5 parallel actions sometimes... doesn't seem crazy. Other weird situation is that if I do ls -l on /mnt/user/downloads or /mnt/user/media the permissions/owners are crazy, all over the place with different user names, or sometimes just numbers, or nobody. I've had to reboot UNRAID many times in the past week where normally it would easily remain up for months so the issue is becoming worse or it's related to using the system more... which shouldn't break the system... right? I can't even stay up a whole day lately. If it's not a complete share meltdown (all smb/nfs dropped/gone stale), it is sometimes just NFS, and sometimes just specific systems using NFS. Never seen SMB only drops so far.

Latest stable - 6.11.5 I think

How do you get unraid to launch to the virt-viewer (Remote Viewer) app directly instead of the buggy web interface? Copy-paste still doesn't work in web or virt-viewer... Seamless integration on Proxmox.

I can't blindly post the diagnostics without picking through it thoroughly so still working on that. Are there segments in particular you would look at? I can say that by commenting out the lxc.mount entries and trying to start, the container starts fine again. These are the three mount entries (which worked fine in debian container) (Created the media/subdir1, etc paths - all owned by root - same as the debian container) I do see a warning in fix common problems plugin (ignored as this should be proper default config for LXC): I set up LXC with /mnt/cache/lxc/ (cache:no) EDIT: Had a typo in the 3rd entry container map name... Definitely need those pre-created correctly. Would be nice if there were a relevant error for that somewhere

The issue is with the container post-upgrade (bullseye > bookworm). Started a new ubunutu jammy instance and it has working dns. So for now I am just going to re-configure that one, reboot, & hope it sticks. Seems like the issue (if you want to reproduce) was regarding the upgrade itself. EDIT: Ran into another issue (ubuntu jammy container wont start up again after initial startup) - I added the lxc.mount.entry lines to the config after shutting it down. The debian bookworm container starts up with the same entries.

So I hit the same python 3.10 requirement (glibc2.35+) on debian bullseye (no surprise). I upgraded from bullseye to bookworm and added the unraidcgroup2 param & rebooted. All looks fine in the system except the WAN stopped working (apt, wget, etc). Worked fine prior to the upgrade. LAN connections still work fine. Looks like the resolv.conf file (resolve service) got removed. /run/systemd/resolve is missing. Manually grabbed the .deb and installed but domain resolution is still broken >.< Any ideas? Manually adding IP <> domain entries into /etc/hosts works but is unsustainable.

Ahh, I noticed the missing / but thought it was a typo - thanks for clarifying that it wasn't haha. Working now!

What would mimic the Read/Write - Slave access type? (two of my maps are remote shares - /mnt/remotes/... Alright so mkdir first in lxc container - as root? The host is root user AFAIK. EDIT: Hmm... I've added 3 and none worked (not seeing any mounted data in the container Should it be mnt/user/YOURSHARE mnt/PATHINLXC or /mnt/user/YOURSHARE /mnt/PATHINLXC

I added a new ubuntu jammy container (added fine) but it cannot start. Only log data I see is: Says it started but it doesn't start. Edit: seems to work fine with debian bullseye How does one map paths like docker?

6.11.5 - running it on bare metal works fine but the two dockers I tried have an issue with python3. (complaining about glibc). Installed python `sudo apt install python3` - something like that

Oh oops - the Debian Bullseye one

I'm unable to run python functions due to the GLIBC version being too low (2.31 - should be 2.35+) How can that be updated?

Is there any way to recover from an unresponsive UI via terminal? I can SSH in but the web UI is totally unresponsive. All I did was hit apply after changing one option on a docker container...

So here's where it's at now form zero usage since restarting a couple days ago: 1.3% 1.204GiB / 30.82GiB After restarting it's around 190MB Logging shows this and timeouts: [22-06-06 11:51:49.0415] Slim::Networking::Discovery::Players::_players_error (144) Unable to get players: Connect timed out: [22-06-06 11:51:21.0983] Slim::Networking::Discovery::Players::_players_error (144) Unable to get players: Invalid JSON response: [

It's very tiny, mostly just use it for the streaming service integrations. I can post a screen again when it bloats but I restarted it as it was too high.

The Docker advanced view (shows current usage)

This has some pretty severe memory leak issues. Even when running unused from startup, after not very long (several days to a week) it goes from 190MB memory usage up to over 2GB.

How do you enable supervisor/add-ons menu on this docker... https://github.com/linuxserver/docker-homeassistant Why would there even be a gimped docker that doesn't have all the features...?

Enabling internal node and setting IP/name still not seeing it show up. Any ideas? Edit: had to use localhost instead of IP

What does 'Verify all the disk" do specifically? Is it good practice to run this after a clear?

How do you change the timezone for this ? Tried adding -e TZ= but it didn't appear to work.

Is there an alternative you can recommend for the posted question?