[[6.12.8] Network Failure Issue after upgrade from Unraid 6.12.6]

Please post the diags with the stock kernel.

[[6.12.6 / 6.12.8] Random crash]

I'm not seeing anything relevant logged, is that the full persistent syslog? It only covers 20 minutes uptime.

 

Try enabling the mirror to flash drive option in the syslog server and post that one after the new crash.

[[6.12.8] No WebGUI - /run full]

12 hours ago, Manyak said:

Gui very very slow

That doesn't look like the same issue being reported here, but please post the diagnostics. 

[After upgrade to 6.12.8 wrong pool state poolname - invalid config]

There should be partitions for all pool devices or they wouldn't work with Unraid, but I've seen some discrepancies with zpool status also, sometimes shows the whole device, possibly when the pools were created using the command line and the whole device, but it should still have partitions, in that case two.

[After upgrade to 6.12.8 wrong pool state poolname - invalid config]

Try reimporting the pool, that should fix it, if it doesn't post new diags.

 

Make sure the pool is exported first (zpool export)

Unassing all pool devices

Start array, stop array

Reassign all pool devices (they should be assigned in the same order as the zpool import/status shows)

Start array

 

 

 

[[6.12.8] Parity drive won't start, no error]

Changed Status to Closed

Changed Priority to Other

[[6.12.8] Parity drive won't start, no error]

This is a general support issue, please lets continue here:

 

 

 

[[6.12.8] Out Of Memory Crash]

Doesn't look exactly the same but see if this helps:

https://forums.unraid.net/topic/129514-high-cpu-load-caused-by-kworker-and-ksoftirqd-usb-auto-suspend/?do=findComment&comment=1179867

 

[[6.12.8] Out Of Memory Crash]

1 hour ago, JorgeB said:

did you try booting in safe mode?

 

[[6.12.8] Out Of Memory Crash]

Not that I know off, make sure you don't have for example a container using an incorrect mapping, in that case it would use the RAM.

[[6.12.8] Out Of Memory Crash]

I cannot see what is using that RAM in the diags, maybe someone also can, did you try booting in safe mode?

[[6.12.8] Out Of Memory Crash]

I'm not seeing any OOM events in the logs, did they happened in these last two boots?

[6.12.8 Call traces and crashes still]

IIRC every time I've seen those errors they were caused by flash drive issues, I guess it could also be RAM related.

 

 

 

 

[Docker Scrub]

@bonienlwill need to take a look

[Docker Scrub]

Looks like it's working since the scrub finished, possibly not updating the GUI in real-time, if you go to main and then back to the Docker settings page, does it update?

[6.12.8 Call traces and crashes still]

Quote

Feb 19 20:47:17 NAS846 kernel: SQUASHFS error: xz decompression failed, data probably corrupt
Feb 19 20:47:17 NAS846 kernel: SQUASHFS error: Failed to read block 0x2e91a60: -5

 

These usually indicate a flash drive problem

[[6.12.6 => 6.12.8] Some settings reset after update & Docker disabled]

1 hour ago, Nedevski said:

The power never stopped, I never unplugged the computer and I didn't use the physical buttons on the machine, that's why I thought I'd post here.

There was still an unclean shutdown:

 

Feb 19 23:12:07 unraid emhttpd: unclean shutdown detected

 

[[6.12.8] No WebGUI - /run full]

Changed Status to Open

[[6.12.8] No WebGUI - /run full]

2 hours ago, bubbl3 said:

Believe the SOLVED label should be removed from this report

Yeah, not really solved, I guess the OP marked it solved.

[[6.12.6 => 6.12.8] Some settings reset after update & Docker disabled]

Quote

Also an unscheduled parity check started by itself.

 

This suggests there was an unclean shutdown, and the docker settings have be known to sometimes revert to defaults after an unclean shutdown.

[[6.12.4] Server hangs once a day since updating to 6.12.4]

13 hours ago, David Grenon said:

restarted the array and started only Plex.

If it still crashes try again without Plex, since that one has been known to be the culprit for some users.

[[6.12.4] Server hangs once a day since updating to 6.12.4]

3 minutes ago, David Grenon said:

would that help you identify ?

You can start the containers one at a time a retest to see if you find the culprit.

[[6.12.4] Server hangs once a day since updating to 6.12.4]

Those I see in a lot of diags, so I assume they are harmless.

[[6.12.4] Server hangs once a day since updating to 6.12.4]

5 minutes ago, David Grenon said:

I guess its a container issue, but even if it is... a Docker glitch/missconfig or w/e shouldn't lock the whole system to the point that we need to hard reset. No ?

It shouldn't, but it's been known to happen.

[[6.12.8] No WebGUI - /run full]

3 minutes ago, bubbl3 said:

The puzzling thing is that according to the conversation we were having yesterday this is not affecting everyone with 64 cores / 128 threads CPUs

That is strange, and the user had SMT enabled for sure? It would be good to see the diags to confirm.

 

All 3 affected cases I've sound so far have a 128 thread CPU, RAM appears to not play a part, since I've seen 1TB and 128GB, the remaining devices may, but the thread count still seems the main issue.