Leaderboard

Last night I took the painful step of just blowing up the networks altogether. I deleted the network.cfg and the local-kv.db for Docker, then set up eth0, updated to 6.12.10, added the other interfaces and Docker networks back, and then set up my dozens of containers all over again. Three hours later I'm up on a current working state on 6.12.10 - still running macvlan as is my preference. I just hope that I get more stability on 6.12 this time than I ever did when I could update through 6.12.5. I'llmark this as the solution, but note that there are others who have had other successful workarounds.

It would be great to finally fix it

I can confirm, 6.12.10, also crashing nginx, server unresponsive and the only way to get it back to life is a hard reboot, which then triggers a parity scan

Bumping this because it keeps popping up on the forum from time to time, note that it also happens with single parity, if the user tries to add a new disk at the same time as parity or before parity finishes syncing, and while it's just an annoyance it shouldn't be a complicated fix, if parity isn't valid and a new data disk is added give an error that actually gives a clue to the user what the problem is.

The Samba team has a habit of changing defaults, and in effort to banish SMBv1 looks they they are "encouraging" users to do likewise. https://www.samba.org/samba/history/samba-4.11.0.html We'll have to rethink some config settings but for now this might do the trick: First make sure NetBIOS is enabled in Settings/SMB Next add this to your config/smb-extra.conf file: server min protocol = NT1 if that doesn't work use server min protocol = LANMAN1 (and please post if you have to use LANMAN1 to get it to work)