icedragonslair Posted February 16, 2019 Share Posted February 16, 2019 I set my parity schedule for weekly and at 1am (0100), since I had to replace all cables, it now runs every morning even though the schedule says otherwise. What do i have to do to get this back on schedule? mediaserver1-syslog-20190216-0919.zip Quote Link to comment
Frank1940 Posted February 16, 2019 Share Posted February 16, 2019 See if this is your problem: https://forums.unraid.net/topic/77929-why-didnt-parity-check-run-with-these-settings/ Quote Link to comment
Squid Posted February 16, 2019 Share Posted February 16, 2019 (edited) Update unRaid to 6.6.6 - Quite probable that you have it set to run on Sundays - There's a bug in early 6.6 where Sunday wasn't a valid day Always post diagnostics instead of a syslog. It makes life easier for us to help, and we also can't determine what your settings are for the parity check schedule to boot. Edited February 16, 2019 by Squid Quote Link to comment
icedragonslair Posted February 16, 2019 Author Share Posted February 16, 2019 46 minutes ago, Squid said: Update unRaid to 6.6.6 - Quite probable that you have it set to run on Sundays - There's a bug in early 6.6 where Sunday wasn't a valid day Always post diagnostics instead of a syslog. It makes life easier for us to help, and we also can't determine what your settings are for the parity check schedule to boot. This setting (sunday at 0100) has worked without a hitch on this version until about a week ago. I will however, update and reset calendar to monday instead mediaserver1-diagnostics-20190216-1027.zip Quote Link to comment
icedragonslair Posted February 18, 2019 Author Share Posted February 18, 2019 Ran last night, will see if the glitch is over tonight Quote Link to comment
icedragonslair Posted February 18, 2019 Author Share Posted February 18, 2019 Nope still running every night, will change parity schedule to Monday Quote Link to comment
trurl Posted February 18, 2019 Share Posted February 18, 2019 29 minutes ago, icedragonslair said: Nope still running every night, will change parity schedule to Monday Assuming you updated Unraid, it might be necessary to make a change to the schedule just to get the old bad schedule cleared. Quote Link to comment
icedragonslair Posted February 18, 2019 Author Share Posted February 18, 2019 (edited) 2 hours ago, trurl said: Assuming you updated Unraid, it might be necessary to make a change to the schedule just to get the old bad schedule cleared. Trying that now, I have moved the scheduled day to Saturday. If it doesn't run tonight I will know and will post either way, thanks so much for the help, Ice Edited February 18, 2019 by icedragonslair Quote Link to comment
icedragonslair Posted February 23, 2019 Author Share Posted February 23, 2019 Parity check ran on new schedule last night except it is now finding a error Feb 23 01:00:01 mediaserver1 kernel: ata5.00: exception Emask 0x52 SAct 0x0 SErr 0x400c01 action 0x6 frozen Feb 23 01:00:01 mediaserver1 kernel: ata5.00: irq_stat 0x08000000, interface fatal error Feb 23 01:00:01 mediaserver1 kernel: ata5.00: exception Emask 0x52 SAct 0x0 SErr 0x400c01 action 0x6 frozen Feb 23 01:00:01 mediaserver1 kernel: ata5.00: irq_stat 0x08000000, interface fatal error With all the reading i have done this may just be a cable or power cable error (would make sense if there is a defective one, since I just changed them all). I have included diag mediaserver1-diagnostics-20190223-1205.zip Quote Link to comment
trurl Posted February 23, 2019 Share Posted February 23, 2019 Syslog says ata5 is Disk16. SMART looks OK for that disk. Quote Link to comment
icedragonslair Posted February 23, 2019 Author Share Posted February 23, 2019 (edited) 36 minutes ago, trurl said: Syslog says ata5 is Disk16. SMART looks OK for that disk. Yeah I saw that too, its why I am confused, is t maybe spinning down? and if so how do I stop that from happening? By the way Constructor, Thank you so much, and same to all here that help myself and others Edited February 23, 2019 by icedragonslair Quote Link to comment
trurl Posted February 23, 2019 Share Posted February 23, 2019 2 hours ago, icedragonslair said: With all the reading i have done this may just be a cable or power cable error (would make sense if there is a defective one, since I just changed them all). ^This seems likely 1 hour ago, icedragonslair said: By the way Constructor, Thank you so much NP, Advanced Member😉 1 Quote Link to comment
icedragonslair Posted March 13, 2019 Author Share Posted March 13, 2019 This topic is solved, the problem has not resurfaced Thank you all, Ice Quote Link to comment
Recommended Posts
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.