February 9, 20233 yr As in title. It seems to happen around when the monitor i have hooked up switches off, so im wondering if there is a sleep state bug or something. Its unresponsive via webgui and locally. If I launch in safe mode the same thing happens... But strangely if I launch in GUI mode it runs fine. Im running Version 6.11.5 sys log attached syslog (NAS).zip
February 9, 20233 yr Community Expert Setup the syslog server using the 'Mirror syslog to Flash' method. See here for instructions: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#comment-781601 Upload the file in a new post in this thread/forum_topic. (If you do not make a new post, no one will ever know you added requested additional info!) EDIT: wait until problem occurs before grabbing the file. Edited February 9, 20233 yr by Frank1940
February 10, 20233 yr Community Expert The last few entries in the syslog was this: Feb 4 22:43:23 NAS ool www[3631]: /usr/local/emhttp/plugins/dynamix/scripts/rsyslog_config Feb 9 23:32:13 NAS rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="2604" x-info="https://www.rsyslog.com"] start Feb 9 23:34:40 NAS ntpd[937]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized How long after the server was started did the lock-up occur? Approximately what was the local time when the lock-up occurred? Was the server running 'normally' until the lock-up occurred? I don't see anything to indicate a problem. Could well be a hardware issue. Make sure that the case, CPU cooler and fans are clean. Verify that all fans are running. Get the Diagnostics file and upload it in your next post. (Don't edit an earlier post and put it in that post. It makes it easier for folks to assist if everything is in chronological order!)
February 13, 20233 yr Author 1 hour ago, Frank1940 said: The last few entries in the syslog was this: Feb 4 22:43:23 NAS ool www[3631]: /usr/local/emhttp/plugins/dynamix/scripts/rsyslog_config Feb 9 23:32:13 NAS rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="2604" x-info="https://www.rsyslog.com"] start Feb 9 23:34:40 NAS ntpd[937]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized How long after the server was started did the lock-up occur? Approximately what was the local time when the lock-up occurred? Was the server running 'normally' until the lock-up occurred? I don't see anything to indicate a problem. Could well be a hardware issue. Make sure that the case, CPU cooler and fans are clean. Verify that all fans are running. Get the Diagnostics file and upload it in your next post. (Don't edit an earlier post and put it in that post. It makes it easier for folks to assist if everything is in chronological order!) Hmm, thats weird. I didnt notice the date is wrong till the last entry. I am attaching another log from today along with the diagnostic file. Typically i think its about 30 minutes till it locks up. I booted up the machine today and noted when i saw it had locked up. 18:35 boot - 19:11 noticed lockup. 21:56 boot - 22:12 lockup The server runs normally till lock up. I have started it up many times and it does the same thing each time. I do not think its a hardware issue becaues of the fact the machine seems to run fine if I boot it in GUI mode and i let run for several hours. All fans are fine. I switched out the RAM and the PSU to no effect. I have all drives disconnected at the moment and removed my HBA card. nas-diagnostics-20230213-2120.zip syslog (NAS).zip
February 13, 20233 yr Hmmm so if you boot to gui mode it's fine but not a normal boot... when you booted into the GUI did you have everything still plugged in and running when you do this? have you added any disks into the array recently? Have you made any changes to the system recently... updates?
February 13, 20233 yr Author When i tried with the gui I had already unpluged all the drives, swapped the ram out etc. I hadnt made any hardware changes. It wondered if it might have started after i installed the last update but that was a few weeks ago now so I cant remember how long it was between updating and noticing there was a problem.
February 13, 20233 yr I question the PSU then... I would connect everything up again and boot into the GUI... and while your there run a parity check
February 13, 20233 yr Community Expert Continue with what @mathomas3 suggested... What plugins and Dockers do you have installed? I noticed you only had 4GB of RAM installed. While that is just enough to run Unraid, it does not provide much of a cushion. (You said swapped out RAM so you must have some extra sticks around. Try to get 8Gb installed--- matched sets are preferred especially since you have stability problems.) If you are running anything that might being using temporary storage on anything except a physical device, you could be running out of memory. (Make all Dockers have all their storage mounts pointing to a directory on /mnt/disk# or /mnt/disks or /mnt/user or /mnt/user0 or /mnt/cache as anything else will be stored in RAM. )
February 14, 20233 yr Community Expert The syslog posted stops 5 minutes after the server booted, was it locked at that time?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.