May 3, 20197 yr Parity check is scheduled to run on the 1st of each month, but it started on the 28th April, never finished, and has been restarting for the last few days. If I refresh the Main page the parity check seems to restart, and then becomes unresponsive after a few minutes. Logs are attached - any assistance gratefully received tower-diagnostics-20190503-2215.zip Edited May 8, 20197 yr by Steviewunda More info
May 3, 20197 yr Community Expert Syslog says you had just booted from an unclean shutdown. Is that correct?
May 3, 20197 yr Author Yes - I couldn't access the web page or any unRaid shares from my Win10 pc, so I did a hard reset. Should I attempt another parity check and try to save the syslog? When I start a parity check I soon get a warning about 40 reallocated sectors on disk 1, and the check seems to stall. If I refresh the Main web page, the parity check seems to restart. Would an extended smart test on disk 1 be an option?
May 3, 20197 yr Author I have started another parity check which has run ok for 15 minutes so far - good speed and no errors reported. The only changes I made were to disable my adblocker, and shutdown all dockers. I will see how it goes and submit another log if necessary. Cheers
May 4, 20197 yr Author The parity check finished in about 11 hours, and reported 31 errors. 'Auto-correct errors 'was turned on, so I decided to do another parity check with 'auto-correct errors' off, to check whether the drives were actually error-free. But when I access the unRaid server web page to check progress from my PC, the parity check restarts . (I had no such problems with the above-mentioned parity check) Log files attached tower-diagnostics-20190504-2355.zip
May 4, 20197 yr Community Expert Just now, Steviewunda said: But when I access the unRaid server web page to check progress from my PC, the parity check restarts . Your syslog is showing you just rebooted from another unclean shutdown. You might try putting your flash in your PC and letting it checkdisk. While there make a backup of its config folder.
May 4, 20197 yr Author Chkdsk found no errors - I tried a different USB port, but it keeps rebooting from an unclean shutdown. What's the next step? Get a new key and replace the flash drive? Memtest? Both?
May 4, 20197 yr Author The unclean shutdown happens soon after starting the parity check. Disk 1 shows 40 reallocated sectors - is that significant?
May 4, 20197 yr Community Expert The reallocated aren't insignificant, but shouldn't cause your issue and is probably not something to worry about for now. Disks have spare sectors just for that purpose. Keep an eye on it and if you get any more or you get another type of SMART warning for that disk it might need replacement. What happens if you stop the parity check, then try to shut down cleanly? Will it shutdown cleanly? Will it boot up again and know that it shutdown cleanly? There is some data on flash where it records if the array is stopped or started, and that is what it uses to try to determine if the array was stopped before shutting down. If the stop isn't recorded then it will think you had an unclean shutdown on next boot.
May 5, 20197 yr Author I stopped the parity check, shut down cleanly, and booted up cleanly (as far as I can tell .... logs attached) tower-diagnostics-20190505-1304.zip
May 5, 20197 yr Author Unraid server is still rebooting as soon as I start a parity check - any other suggestions?
May 5, 20197 yr Author I'll need to buy one tomorrow in order to test - it won't hurt to have a spare on hand ;-). And I'll run memtest+ for a day.
May 6, 20197 yr Author No problems with memtest...replaced psu and I'm currently halfway thru parity check with no reboots or errors Looking good so far, I'll hopefully be marking this solved before long
May 6, 20197 yr PSU failure can drive you nuts. It would be so convenient if there was a red light that would tell us it was the PSU. But no, we have to figure it out in the strangest ways. Sent from my chisel, carved into granite
May 7, 20197 yr Author Parity check completed with new PSU and corrected 27 errors. Only problem now is that binhex_Sabnzbd and binhex_sonarr will not start (binhex_radarr starts up ok) - logs attached tower-diagnostics-20190507-1815.zip
May 7, 20197 yr Community Expert 6 hours ago, Steviewunda said: Only problem now Disable Docker service and delete docker image. Make sure your appdata, domains, and system share are all set to cache-prefer. Run mover and let it complete. Enable Docker Service and turn on Log rotation. Reinstall all your dockers using the Previous Apps feature on the Apps page.
May 7, 20197 yr Author Ok - I rebuilt docker.img and reinstalled my dockers, which now start up. binhex_sabnzbd seems ok, but sonarr and radarr have connection errors. I have attached their logs, if someone could have a look I would be grateful. Edit - sorry I posted this before seeing Trurl's reply - I will follow your advice. Log for binhex-radarr.txt Log for binhex-sonarr.txt Edited May 7, 20197 yr by Steviewunda
May 8, 20197 yr Author I have followed trurl's instructions and can run binhex_sabnzbd, radarr and sonarr, but I'm having connection problems (logs attached) Log for binhex-radarr.txt Log for binhex-sabnzbd.txt Log for binhex-sonarr.txt tower-diagnostics-20190508-1307.zip
May 8, 20197 yr Author I will mark this thread solved, as the original problem (unclean shutdowns) was resolved with a new power supply. I will start a new thread in the SABNZBD forum (Sonarr and Radarr cannot connect). Thanks for everyone's help
Archived
This topic is now archived and is closed to further replies.