Hi team,

 

I've tried 3 times the upgrade to 6.12 on my hardware.

 

Each time on every 6.12.x release. On each I get no more than hours or 1 day of uptime. On each I've been reverting to the previous 6.11.5 which gives a lot of uptime (24 days before today's upgrade ☺️ that's a really good version!).

 

I know I don't have the normal hardware for unRAID:

 

Mac mini Late 2012

i7-3615QM CPU @ 2.30GHz

16 GiB DDR3

Almost all array drives are connected via USB.

USB NIC for br0 (eth0)

Built-In NIC for br1 (tg3, eth1 for VMs and Docker only)

 

Took this diagnostic after the latest unattended and unclean shutdown happened Today. I was not around when it happened.

 

Any input will be greatly appreciated. ☺️

 

I have currently set 2 of the 3 VMs (created but not running VMs for some months now) to br1 as the other was set. Let's hope it does something even though the 3 VMs are off by default.

 

mini-diagnostics-20230822-0022.zip

Enable the syslog server and post that after a crash.

 

4 hours ago, JorgeB said:

Enable the syslog server and post that after a crash.

 

 

Hi,

Local syslog server activated and the remote setup using the trickery  option: Logging to file local to Unraid server Using a bit of trickery

 

Will attach here the logs upon getting a crash/shutdown.

Hi team,

 

I've been hammering the server a little more than usual these past 2 days under 6.12.3.

• Setting up a lancache VM
• Saw mentions of macvlan traces on the Fix Common Problems plugin
  • So I changed the docker network to ipvlan, although I do have the 2nd NIC fix applied since before those traces appeared, no biggie.

So far Uptime 2 days 11 hours 57 minutes! We got past the 1 day mark now! And I see the possible 6.12.4 has a fix for macvlan traces and a possible revert to the usual macvlan with a single br0 link! These seem to be good times. I'll keep it as it is for now until 6.12.4 drops or a crash/shutdown happens.

 

I deem this one as resolved for now. 😉