January 4, 20206 yr Dear all I need your help, I think (my feeling only) that my unRaid started to restart at random intervals, 3-5-7-10 days and this started to happen after update to v6.8, is it possible? I have not touched machine configuration at all. obviously there could be problem with hardware but it is hard to believe that the only symptom of hardware failure to be random restart. How should I diagnose? Last reboot was 1 hour ago and it looks as clean restart as machine did not start to check parity after reboot. Many thanks for your kind help Vladimir
January 5, 20206 yr Author I switched reporting of logs to syslog server to keep them all and I noticed that there is big number of errors saying CIFS VFS: Close unmatched open. Can this be a problem leading to restarts? Thanks Vladimir Date Time Level Host Name Category Program Messages 5.1.2020 8:20:45 Warning Tower kern kernel mdcmd (239): spindown 6 5.1.2020 8:16:32 Warning Tower kern kernel mdcmd (238): spindown 29 5.1.2020 8:16:32 Warning Tower kern kernel mdcmd (237): spindown 0 5.1.2020 8:07:54 Error Tower kern kernel CIFS VFS: Close unmatched open 5.1.2020 8:05:25 Warning Tower kern kernel mdcmd (236): spindown 8 5.1.2020 8:05:24 Warning Tower kern kernel mdcmd (235): spindown 7 5.1.2020 8:05:23 Warning Tower kern kernel mdcmd (234): spindown 5 5.1.2020 8:05:21 Warning Tower kern kernel mdcmd (233): spindown 3 5.1.2020 8:05:19 Warning Tower kern kernel mdcmd (232): spindown 6 5.1.2020 7:55:18 Error Tower kern kernel CIFS VFS: Close unmatched open 5.1.2020 7:42:44 Warning Tower kern kernel mdcmd (231): spindown 6 5.1.2020 7:40:15 Error Tower kern kernel CIFS VFS: Close unmatched open 5.1.2020 7:22:40 Error Tower kern kernel CIFS VFS: Close unmatched open 5.1.2020 7:22:40 Error Tower kern kernel CIFS VFS: Close unmatched open 5.1.2020 7:17:39 Error Tower kern kernel CIFS VFS: Close unmatched open 5.1.2020 7:17:39 Error Tower kern kernel CIFS VFS: Close unmatched open 5.1.2020 6:58:30 Error Tower kern kernel CIFS VFS: Close unmatched open 5.1.2020 6:57:00 Error Tower kern kernel CIFS VFS: Close unmatched open 5.1.2020 6:56:00 Error Tower kern kernel CIFS VFS: Close unmatched open 5.1.2020 6:53:58 Error Tower kern kernel CIFS VFS: Close unmatched open 5.1.2020 6:53:58 Error Tower kern kernel CIFS VFS: Close unmatched open 5.1.2020 6:52:58 Error Tower kern kernel CIFS VFS: Close unmatched open 5.1.2020 6:48:36 Warning Tower kern kernel mdcmd (230): spindown 29 5.1.2020 6:48:35 Warning Tower kern kernel mdcmd (229): spindown 0 5.1.2020 6:24:12 Error Tower kern kernel CIFS VFS: Close unmatched open 5.1.2020 6:23:42 Error Tower kern kernel CIFS VFS: Close unmatched open 5.1.2020 6:21:11 Error Tower kern kernel CIFS VFS: Close unmatched open 5.1.2020 6:17:39 Error Tower kern kernel CIFS VFS: Close unmatched open 5.1.2020 6:15:38 Error Tower kern kernel CIFS VFS: Close unmatched open 5.1.2020 6:15:08 Error Tower kern kernel CIFS VFS: Close unmatched open 5.1.2020 6:11:36 Error Tower kern kernel CIFS VFS: Close unmatched open 5.1.2020 6:09:36 Error Tower kern kernel CIFS VFS: Close unmatched open
January 5, 20206 yr Community Expert Try enabling syslog server/mirror feature to see if it catches anything: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=781601
January 5, 20206 yr Author yes, I did it, today restart at about 20.44, log shows these entries but I cannot see anything which would give me hint about reason of restart 05.01.2020 21:27:03 Warning Tower kern kernel mdcmd (60): set spinup_group 29 0 05.01.2020 21:27:03 Warning Tower kern kernel mdcmd (59): set spinup_group 8 0 05.01.2020 21:27:03 Warning Tower kern kernel mdcmd (58): set spinup_group 7 0 05.01.2020 21:27:03 Warning Tower kern kernel mdcmd (57): set spinup_group 6 0 05.01.2020 21:27:03 Warning Tower kern kernel mdcmd (56): set spinup_group 5 0 05.01.2020 21:27:03 Warning Tower kern kernel mdcmd (55): set spinup_group 4 0 05.01.2020 21:27:03 Warning Tower kern kernel mdcmd (54): set spinup_group 3 0 05.01.2020 21:27:03 Warning Tower kern kernel mdcmd (53): set spinup_group 2 0 05.01.2020 21:27:03 Warning Tower kern kernel mdcmd (52): set spinup_group 1 0 05.01.2020 21:27:03 Warning Tower kern kernel mdcmd (51): set spinup_group 0 0 05.01.2020 21:27:03 Warning Tower kern kernel mdcmd (50): set md_write_method 05.01.2020 21:27:03 Warning Tower kern kernel mdcmd (49): set md_sync_limit 5 05.01.2020 21:27:03 Warning Tower kern kernel mdcmd (48): set md_queue_limit 80 05.01.2020 21:27:03 Warning Tower kern kernel mdcmd (47): set md_num_stripes 1280 05.01.2020 21:27:03 Information Tower user emhttpd shcmd (2641): echo 128 > /sys/block/sdb/queue/nr_requests 05.01.2020 21:27:01 Information Tower user emhttpd req (1): startState=STOPPED&optionCorrect=correct&csrf_token=****************&cmdStart=Start&luksKey=************************************ 05.01.2020 21:26:53 Notice Tower user webGUI Successful login user root from 192.168.1.96 05.01.2020 20:50:18 Information Tower syslog rsyslogd action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ] 05.01.2020 20:50:18 Information Tower daemon ntpd kernel reports TIME_ERROR: 0x41: Clock Unsynchronized 05.01.2020 20:33:22 Warning Tower kern kernel mdcmd (424): spindown 7 05.01.2020 20:33:21 Warning Tower kern kernel mdcmd (423): spindown 5 05.01.2020 20:31:55 Warning Tower kern kernel mdcmd (422): spindown 3 05.01.2020 20:31:53 Warning Tower kern kernel mdcmd (421): spindown 2 05.01.2020 20:31:52 Warning Tower kern kernel mdcmd (420): spindown 4 05.01.2020 20:31:01 Warning Tower kern kernel mdcmd (419): spindown 8 05.01.2020 20:30:50 Warning Tower kern kernel mdcmd (418): spindown 6 05.01.2020 20:23:20 Error Tower kern kernel CIFS VFS: Close unmatched open 05.01.2020 20:13:17 Error Tower kern kernel CIFS VFS: Close unmatched open
January 6, 20206 yr Community Expert Downgrade back to v6.7.2 to see if the problem really is related to the upgrade, if it still crashes it's likely hardware related.
January 7, 20206 yr Author Thanks, I downgraded to 6.72, but it is the same unfortunatelly, so clearly not a problem of Unraid as such. Any other ideas?
January 7, 20206 yr Community Expert Very difficult to diagnose remotely, you'll need to start swapping some hardware.
February 7, 20206 yr I have found that my UNRAID NAS is shutting down without my request. I had added the UNRAID diagnostics to I hope will shed light on why this is happening. sutterstuff-diagnostics-20200207-0620.zip
February 7, 20206 yr Community Expert 11 minutes ago, rsutter said: I have found that my UNRAID NAS is shutting down without my request. I had added the UNRAID diagnostics to I hope will shed light on why this is happening. sutterstuff-diagnostics-20200207-0620.zip 66.58 kB · 1 download Please start your own thread!
Archived
This topic is now archived and is closed to further replies.