Is my server restarting

[maxse]

Guys I need some help please. I have noticed that my mac mini keeps dropping mapped drives (running plex headless).

 

I think it is my unraid server restarting for some reason! Can someone please help determine if that's the case?

 

I am running V5.0.6

 

I have been having the macmini drop the mapped shares issue freuquently in the past few month. I have had the unraid server for 2 years about and only recently started having these issues. Not sure if it's the macmini, my router or unraid. Having trouble how to get the syslog file other then clicking log at the top right icon. All of my compuers are Apple.

 

Thanks so much.

[trurl]

About the only way your server could restart on its own would be if it lost power and the BIOS were configured to restart after a power outage. But even then it would automatically start a correcting parity check every time that happened. So its unlikely your server is restarting but you don't know it.

[Helmonder]

If its restarting you should see that in the uptime, upper-right corner of the webinterface.

[maxse]

Got it, forgot to check it.

 

I'll just upgrade to v6.0 if this happens again. Thanks guys

[maxse]

I don't see the uptime in the upper right corner. Where can I find it?

 

I was hoping this would last more then a day but now my macmini dropped the shares again and I couldn't use plex until I got home, had to login to the macmini and remount the shares.

 

This is what the "syslog" says. Is this normal? Could the fact that it's renewing the lease have anything to do with the shares dropping out?

 

This is the syslog from today. I last used plex last night so something happened on April 4

Apr  4 00:55:57 Tower kernel: mdcmd (92): spindown 6

Apr  4 01:31:58 Tower kernel: mdcmd (93): spindown 0

Apr  4 01:55:09 Tower kernel: mdcmd (94): spindown 3

Apr  4 01:55:29 Tower kernel: mdcmd (95): spindown 5

Apr  4 01:56:20 Tower kernel: mdcmd (96): spindown 4

Apr  4 01:56:30 Tower kernel: mdcmd (97): spindown 1

Apr  4 01:56:30 Tower kernel: mdcmd (98): spindown 2

Apr  4 02:46:41 Tower kernel: mdcmd (99): spindown 0

Apr  4 02:46:41 Tower kernel: mdcmd (100): spindown 7

Apr  4 03:40:01 Tower logger: mover started

Apr  4 03:40:01 Tower logger: skipping apps/

Apr  4 03:40:01 Tower logger: mover finished

Apr  4 04:35:42 Tower kernel: mdcmd (101): spindown 4

Apr  4 04:40:03 Tower kernel: mdcmd (102): spindown 0

Apr  4 04:40:14 Tower kernel: mdcmd (103): spindown 7

Apr  4 05:12:34 Tower kernel: mdcmd (104): spindown 3

Apr  4 05:12:45 Tower kernel: mdcmd (105): spindown 2

Apr  4 05:12:45 Tower kernel: mdcmd (106): spindown 5

Apr  4 07:13:06 Tower kernel: mdcmd (107): spindown 5

Apr  4 09:14:17 Tower kernel: mdcmd (108): spindown 3

Apr  4 09:14:27 Tower kernel: mdcmd (109): spindown 2

Apr  4 09:24:27 Tower dhcpcd[1105]: eth0: renewing lease of 192.168.1.2

Apr  4 09:24:27 Tower dhcpcd[1105]: eth0: acknowledged 192.168.1.2 from 192.168.1.1

Apr  4 09:24:27 Tower dhcpcd[1105]: eth0: leased 192.168.1.2 for 86400 seconds

Apr  4 10:34:28 Tower kernel: mdcmd (110): spindown 0

Apr  4 11:14:49 Tower kernel: mdcmd (111): spindown 1

Apr  4 11:15:09 Tower kernel: mdcmd (112): spindown 2

Apr  4 11:15:19 Tower kernel: mdcmd (113): spindown 4

Apr  4 11:15:20 Tower kernel: mdcmd (114): spindown 7

Apr  4 11:15:30 Tower kernel: mdcmd (115): spindown 3

Apr  4 13:15:21 Tower kernel: mdcmd (116): spindown 1

Apr  4 13:15:41 Tower kernel: mdcmd (117): spindown 3

Apr  4 13:15:42 Tower kernel: mdcmd (118): spindown 4

Apr  4 13:16:02 Tower kernel: mdcmd (119): spindown 5

Apr  4 13:16:13 Tower kernel: mdcmd (120): spindown 6

Apr  4 13:16:13 Tower kernel: mdcmd (121): spindown 7

Apr  4 15:16:34 Tower kernel: mdcmd (122): spindown 6

Apr  4 15:16:45 Tower kernel: mdcmd (123): spindown 1

Apr  4 15:16:45 Tower kernel: mdcmd (124): spindown 2

Apr  4 15:16:45 Tower kernel: mdcmd (125): spindown 3

Apr  4 15:16:46 Tower kernel: mdcmd (126): spindown 7

Apr  4 15:16:56 Tower kernel: mdcmd (127): spindown 4

Apr  4 15:17:07 Tower kernel: mdcmd (128): spindown 5

Apr  4 20:41:59 Tower kernel: mdcmd (129): spindown 0

Apr  4 20:42:00 Tower kernel: mdcmd (130): spindown 7

Apr  4 21:24:28 Tower dhcpcd[1105]: eth0: renewing lease of 192.168.1.2

Apr  4 21:24:28 Tower dhcpcd[1105]: eth0: acknowledged 192.168.1.2 from 192.168.1.1

Apr  4 21:24:28 Tower dhcpcd[1105]: eth0: leased 192.168.1.2 for 86400 seconds

[Helmonder]

Right upper corner of the webinterface...

 

I just noticed you wrote you were possibly going to -upgrade- to v6... Sorry to say but everything before V6 is so long ago for me that I do not remember how it al looked, maybe someone else can help..