[[6.8.3] shfs error results in lost /mnt/user]

Not sure if this is already known, but today I suddenly had this issue happening and started looking for solutions. I stumbled on this post:

I changed the path for my media share from /mnt/user/media to /mnt/user0/media in the Tdarr docker containers and just to be sure I also made sure the /temp is now on a share that has no mover running on it. 

 

I have no tdarr related errors anymore in the logs, so fingers crossed!
I have NFS disabled and still have Hard Links enabled under Global Share Settings.

[6.9.0/6.9.1 - Kernel Panic due to netfilter (nf_nat_setup_info) - Docker Static IP (macvlan)]

I'm stable running on 6.10.0-rc1 with ipvlan for over a week now. An uptime of more than 7 days is a record in the past couple of months. 

[6.9.0/6.9.1 - Kernel Panic due to netfilter (nf_nat_setup_info) - Docker Static IP (macvlan)]

This morning I had another crash again related to br_netfilter/nf_nat. So I have upgraded to 6.10.0-rc1 and switched to ipvlan for Docker. Hoping this solves this issue.

[6.9.0/6.9.1 - Kernel Panic due to netfilter (nf_nat_setup_info) - Docker Static IP (macvlan)]

1 hour ago, codefaux said:

Sorry to hear it -- I'm still running the configuration posted and still stable save the recent power bumps in our area, but I had nearly a month of uptime at one point and even that power cycle was scheduled. I've also moved additional Docker containers onto the system so I could shut down the other for power/heat savings during the heat wave. I haven't had the spoons to convince myself to change anything since it became stable, so I'm not on the RC yet.

 

I might suggest that if there is a panic, it could be unrelated -- post its details just to be sure. Various hardware have errata that could cause panics, including both Intel and AMD C-state bugs on various generations, and even filesystem corruption from previous panics -- something Unraid doesn't forward to the UI from the kernel logs, by default.

 

Good luck all.

I finally enabled syslog etc. and it seems it is not related to this issue at all anymore that my server crashes. I had the macvlan problem earlier, so I made the assumption (yes, I know! Assumtions are the mother of all f*ups) that it was still the same issue. 

 

That probably means that the macvlan issue is gone on my machine. 

[6.9.0/6.9.1 - Kernel Panic due to netfilter (nf_nat_setup_info) - Docker Static IP (macvlan)]

On 8/3/2021 at 10:15 AM, VlarpNL said:

Well, knock on wood, but my system seems to be stable after making these changes. I had trouble even keeping Unraid up for more than 2 days, but it has now been running without issues for about a week.

Well, there you have it. I jinxed it. My server just froze up. 

I'm disabling host access to custom networks to see if that improves anything. Fingers crossed.

[6.9.0/6.9.1 - Kernel Panic due to netfilter (nf_nat_setup_info) - Docker Static IP (macvlan)]

On 7/6/2021 at 1:14 PM, codefaux said:

Yes, I am well aware of the significance of VLAN 0. I'm also well aware that it happens when VLANs are enabled for an interface.

 

However, upon reading my message, the following things stand out as unusual -- which may be why I wrote them in detail, and provided screenshots --

 

1 -- There are no currently enabled interfaces with VLANs enabled so..."perfectly normal when" goes right out the window, yeah?

2 -- Before (when I was crashing) I did not have VLAN 0 messages in my log

3 -- After (now that I'm NOT crashing) I DO have VLAN 0 messages in my log

 

The first point I was trying to raise, in this case, was that I'm not using VLANs on any of my enabled network interfaces, and none of my disabled interfaces have VLANs configured but they are enabled -- the system seems to still be activating VLAN 0 as if preparing for VLAN operation, which seems to be abnormal thus commenting on it, if it were normal I wouldn't have taken the time.

 

The second point I was trying to raise, specifically, was that I seem to have stumbled upon a potential solution for this crash problem while Docker/Kernel/Limetech find a solution.

 

What I'd like to see is if anyone experiencing these crashes could do the following;

A) Enable VLAN but do not configure it on an unused network interface

B) DISABLE that interface (IPv4/IPv6 Address Assignment None, not a member of bridge or bond)

C) Reboot, start your array, check if you see "VLAN 0" related log messages

D) Report if your system becomes stable

 

I've got uptime around a month now, perfectly stable, with no changes to my system beyond what's mentioned above and in greater detail in my previous message.

Well, knock on wood, but my system seems to be stable after making these changes. I had trouble even keeping Unraid up for more than 2 days, but it has now been running without issues for about a week.

[6.9.0/6.9.1 - Kernel Panic due to netfilter (nf_nat_setup_info) - Docker Static IP (macvlan)]

Checking in here that I have the exact same problem on Unraid 6.9.2. I have an AdGuard docker on br0 and have the random crashes with the same error messages in the logs. 

 

Running Unraid on a HPE MicroServer Gen10. 

[6.9.0 beta 35 Dashboard ui broken for docker & Vm's]

I'm also here seeing the exact same thing on 6.9.0 beta 35. I only have 2 VM's that both have VNC graphics. No matter what (none running, only one running or both running) the VM Dashboard section is empty and when I open up the view with the down arrow the whole middle column distorts (and Dockers only show in 2 columns). Closing the VM view clicking ^ makes display normal (and Dockers showing in 3 columns).