August 15, 20169 yr Hi all, I've just upgraded my parity drive from 3TB to 4TB, and am trying to generate parity for the new drive. A few hours into the parity check, the server appears to reboot itself, as when I log in to check on it, I get the prompt to start the array. Is there a way to get Unraid to automatically save the syslog to the cache drive as it generates it, or some other non-volatile location, so that I can troubleshoot this? The logs are cleared on reboot when it crashes. Can anyone think of a reason why it would be crashing? I completed a full parity sync on the 3TB drive fine, so maybe there is an issue with the new 4TB drive?
August 15, 20169 yr Try this suggestion: http://lime-technology.com/wiki/index.php/Troubleshooting#If_you_cannot_copy_your_syslog
August 15, 20169 yr Either install the fix common problems plugin and click on troubleshooting mode, or from the local keyboard & monitor tail -f /var/log/syslog > /boot/syslog.txt Either method will continually update the the flashdrive (logs folder if using FCP or root folder if using the command) with the syslog as it changes Hopefully something will be discernable, but assuming your powersupply is up to the task, its probably going to be an issue with memory.
August 15, 20169 yr Author Thanks guys, great plugin! It's been scanning for a few minutes now and the web GUI is now unresponsive, hopefully it finds something. I've telnetted in and kicked off that syslog dump to the flash drive. Either way hopefully we'll get something logged The server has ECC RAM so I'd assume it isn't a memory issue? I have a bag of spare sticks I can pop in if needed though.
August 15, 20169 yr Community Expert A bit of a wild shot but be sure that all of the fans are running. Also, make sure the CPU cooler fins aren't clogged with dirt.
August 15, 20169 yr Author Shall do, good tip! I've added a few plugins and notifications as recommended by the "Fix common problems" plugin, rescanning now. I'ts been up for around 150 minutes and is 7.2% parity sync, waiting for it to crash so I get some logs.
August 15, 20169 yr Author It just went down, but nothing really useful: Aug 15 11:20:54 NAS logger: plugin: running: /boot/config/plugins/fix.common.problems/fix.common.problems-2016.08.06-x86_64-1.txz Aug 15 11:20:54 NAS logger: plugin: running: anonymous Aug 15 11:21:05 NAS logger: Fix Common Problems Version 2016.08.06 Aug 15 11:21:11 NAS logger: Fix Common Problems: Error: Plugin Update Check not enabled Aug 15 11:21:11 NAS logger: Fix Common Problems: Warning: Docker Update Check not enabled Aug 15 11:21:11 NAS logger: Fix Common Problems: Warning: Community Applications not installed Aug 15 11:21:11 NAS logger: Fix Common Problems: Error: Powerdown plugin not installed Aug 15 11:21:13 NAS logger: Fix Common Problems: Warning: PlexMediaServer docker application has its /config folder set to /mnt/user/appdata/PlexMediaServer Aug 15 11:25:05 NAS in.telnetd[26616]: connect from 10.1.1.4 (10.1.1.4) Aug 15 11:25:07 NAS login[26617]: ROOT LOGIN on '/dev/pts/0' from '10.1.1.4' Aug 15 11:33:02 NAS emhttp: need_authorization: getpeername: Transport endpoint is not connected Aug 15 11:33:02 NAS emhttp: need_authorization: getpeername: Transport endpoint is not connected Aug 15 11:33:02 NAS emhttp: need_authorization: getpeername: Transport endpoint is not connected Aug 15 11:33:02 NAS emhttp: need_authorization: getpeername: Transport endpoint is not connected Aug 15 11:33:02 NAS emhttp: need_authorization: getpeername: Transport endpoint is not connected Aug 15 11:38:11 NAS php: /usr/local/emhttp/plugins/dynamix/scripts/notify 'cron-init' Aug 15 11:39:23 NAS emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin install https://github.com/dlandon/powerdown/raw/master/powerdown-x86_64.plg Aug 15 11:39:26 NAS logger: plugin: creating: /boot/config/plugins/powerdown/powerdown-2016.04.23.tgz - downloading from URL https://github.com/dlandon/powerdown/raw/master/powerdown-2016.04.23.tgz Aug 15 11:39:28 NAS logger: plugin: checking: /boot/config/plugins/powerdown/powerdown-2016.04.23.tgz - MD5 Aug 15 11:39:28 NAS logger: plugin: creating: /boot/config/plugins/powerdown/powerdown-2.20-noarch-unRAID.txz - downloading from URL https://github.com/dlandon/powerdown/raw/master/powerdown-2.20-noarch-unRAID.txz Aug 15 11:39:30 NAS logger: plugin: checking: /boot/config/plugins/powerdown/powerdown-2.20-noarch-unRAID.txz - MD5 Aug 15 11:39:30 NAS logger: plugin: running: /boot/config/plugins/powerdown/powerdown-2.20-noarch-unRAID.txz Aug 15 11:39:31 NAS init: Re-reading inittab Aug 15 11:39:31 NAS logger: plugin: running: anonymous Aug 15 11:39:31 NAS logger: plugin: creating: /boot/config/plugins/powerdown/powerdown.conf - from INLINE content Aug 15 11:41:43 NAS emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin install https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg Aug 15 11:41:45 NAS logger: plugin: running: anonymous Aug 15 11:41:45 NAS logger: plugin: running: anonymous Aug 15 11:41:45 NAS logger: plugin: creating: /boot/config/plugins/community.applications/community.applications-2016.08.13.txz - downloading from URL https://raw.github.com/Squidly271/community.applications/master/archive/community.applications-2016.08.13.txz Aug 15 11:41:51 NAS logger: plugin: checking: /boot/config/plugins/community.applications/community.applications-2016.08.13.txz - MD5 Aug 15 11:41:51 NAS logger: plugin: running: /boot/config/plugins/community.applications/community.applications-2016.08.13.txz Aug 15 11:41:51 NAS logger: plugin: running: anonymous Might run a Memtest when I get home.
August 16, 20169 yr Author When running Memtest I noticed a stick of RAM was a different brand to all the others, I've swapped it out and am re-running a parity check. Also had Disk 3 disappear when I rebooted from doing this, re-seated the SATA cable (seemed snug, but just in case), and it's reappeared. Given that it is another one of the dodgy Seagates I'm copying the data across to another drive just in case. Parity sync at 10% and progressing well, see if it crashes again with the new RAM.
August 17, 20169 yr Author OK I ran the Memtest and attached a diagnostics log, I can't see anything that stands out though? Syslog: http://ribfeast.no-ip.com/syslog.txt
August 19, 20169 yr Author Anyone? Otherwise I'll need to find a way to capture the screen somehow, as I reckon whatever the fault is is not being logged.
August 29, 20169 yr Author Installed a different motherboard and upgraded the TX650 to a TX850 Corsair power supply, parity check completed without issue. Not sure which of them was at fault, probably leaky caps or something else failing in the old motherboard I suspect.
Archived
This topic is now archived and is closed to further replies.