Gibbo592

I have found a work around to the random crashing which may help someone else, I added initrd=/bzroot acpi=off kernel option in the syslinux configuration. This worked for both 6.9.2 and 6.10.0rc You can temporarirly try by selecting tab at the boot menu and manually add acpi=off to the line to make it permanent add the acpi=off option to the syslinux config. I also found issues with the NTP service and syslog was being flooded with "nchan: a message from the past has just been published. unless the system time has been adjusted, this should never happen." I tried several NTP servers close to home but still the error persisted - I have now stopped the NTP service and the issue is no longer apparent.

@craigr did you ever get the new kernel compiled if so could you share the steps ?

@mkono87 I added BOOT_IMAGE=/bzimage initrd=/bzroot acpi=off it has been running for 10 hours so far lots of time errors still but at least it is alive

Hi Jonp Appriciate your help. I Emailed you some more information - I have tried to run the system with nothing running just the USB and still the same outcome random crash just hangs only physical restart will solve it.

Hi Jonp yes all the screenshots are from when the system becomes unresponsive gui is still there but only hard reset gets it working. it is becoming very frustrating- love the simplicity of unraid operation but this new build is going bad. any suggestion greatly appreciated.

Hi Jon, kernel reports TIME_ERROR: 0x41: Clock Unsynchronized appears ? in the syslog tower-syslog-20210907-0217.zip

something weird with the time going on tried changing the NTP servers root@Tower:~# hwclock --show 2021-09-07 20:47:19.137429+10:00 root@Tower:~# ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== LOCAL(0) .LOCL. 10 l 438 64 100 0.000 +0.000 0.000 +Server.local 216.239.35.0 2 u 46 64 177 0.533 -3.040 1.881 -resolv.internod 203.35.83.242 2 u 27 64 177 13.468 +5.395 2.128 +time.cloudflare 10.85.8.92 3 u 35 64 177 11.104 -0.635 2.659 *time4.google.co .GOOG. 1 u 34 64 177 158.321 +1.003 2.384

just managed to get diagnostic to download before it became unresponsive tower-diagnostics-20210907-1027.zip

tried setting bios time to UTC and then get this error

no i have a trial key going with nothing just to try and figure out whats going on

hi Jon Syslog tail attached - the only thing I can see is there is a time difference 10 hours which is the difference between UTC and Australian EST

Still no luck I have tried all the available versions as a trial, from 6.8.3 to 6.10. all randomly hang curser keeps flashing but won’t respond only reboot works no errors in Syslog. installed several different os windows 10, Ubuntu server, truenas and currently Slackware 14.2 all run fine so I don’t believe a hardware problem it all points to unraid itself I’m trying to find an upto date guide on custom kernel and remove all the amd stuff and keep it generic Intel and Nvidia.

Temporarily installed Truenas and Ubuntu server both run OK only unraid has the issue - of shutting down so I assume it is a driver issue ?

Seems to be similar I will try going back to 6.8.3 and see what happens

Hi we seem to be in the same boat have you tried different versions with 6.9.0 it ran for more than an hour and the unresponsive if you check the terminal the curser is still flashing but nothing in Syslog. 6.10.1 only runs for minutes and the hangs.