Jump to content

SOLVED: Spontaneous Parity Check


kamhighway

Recommended Posts

Are there any conditions under which UR would spontaneously start a parity check on its own?

 

Yesterday, a server that had been running URv6b14b spontaneously started a parity check 2 times.  The first time, I thought I must have kicked it off by mistake.  But about 30 minutes after the parity check finished, the server kicked off another parity check. I'm sure I didn't start the second one. 

 

This morning I upgraded to URv6b15 to see if that would fix the problem.  It did not. Here is the tail of my syslog after the update to v6b15:

 

Apr 22 17:44:23 Media kernel: device vethab52d97 entered promiscuous mode

Apr 22 17:44:23 Media kernel: docker0: port 5(vethab52d97) entered forwarding state

Apr 22 17:44:23 Media kernel: docker0: port 5(vethab52d97) entered forwarding state

Apr 22 17:44:23 Media avahi-daemon[6999]: Withdrawing workstation service for vetheeff233.

Apr 22 17:44:23 Media kernel: eth0: renamed from vetheeff233

Apr 22 17:44:23 Media kernel: docker0: port 5(vethab52d97) entered disabled state

Apr 22 17:44:23 Media kernel: docker0: port 5(vethab52d97) entered forwarding state

Apr 22 17:44:23 Media kernel: docker0: port 5(vethab52d97) entered forwarding state

Apr 22 17:44:23 Media logger: SickBeard: started succesfully!

Apr 22 17:44:23 Media logger: PlexMediaServer: started succesfully!

Apr 22 17:44:23 Media emhttp: unclean shutdown detected

Apr 22 17:44:23 Media kernel: mdcmd (37): check CORRECT

Apr 22 17:44:23 Media kernel: md: recovery thread woken up ...

Apr 22 17:44:23 Media kernel: md: recovery thread checking parity...

Apr 22 17:44:23 Media kernel: md: using 1536k window, over a total of 2930266532 blocks.

Apr 22 17:44:24 Media ntpd[1445]: Listen normally on 3 docker0 172.17.42.1:123

Apr 22 17:44:24 Media ntpd[1445]: new interface(s) found: waking up resolver

Apr 22 17:44:25 Media emhttp: shcmd (42): :>/etc/samba/smb-shares.conf

Apr 22 17:44:25 Media avahi-daemon[6999]: Files changed, reloading.

Apr 22 17:44:25 Media emhttp: Restart SMB...

Apr 22 17:44:25 Media emhttp: shcmd (43): killall -HUP smbd

Apr 22 17:44:25 Media emhttp: shcmd (44): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service

Apr 22 17:44:25 Media avahi-daemon[6999]: Files changed, reloading.

Apr 22 17:44:25 Media avahi-daemon[6999]: Service group file /services/smb.service changed, reloading.

Apr 22 17:44:25 Media emhttp: shcmd (45): pidof rpc.mountd &> /dev/null

Apr 22 17:44:25 Media emhttp: shcmd (46): /etc/rc.d/rc.atalk status

Apr 22 17:44:25 Media rc.unRAID[7948][7949]: Processing /etc/rc.d/rc.unRAID.d/ start scripts.

Apr 22 17:44:26 Media avahi-daemon[6999]: Service "Media" (/services/smb.service) successfully established.

Apr 22 17:44:37 Media kernel: docker0: port 1(veth8fb4d0a) entered forwarding state

Apr 22 17:44:37 Media kernel: docker0: port 2(veth416b786) entered forwarding state

Apr 22 17:44:37 Media kernel: docker0: port 3(vethb081527) entered forwarding state

Apr 22 17:44:37 Media kernel: docker0: port 4(veth076b769) entered forwarding state

Apr 22 17:44:38 Media kernel: docker0: port 5(vethab52d97) entered forwarding state

Apr 22 17:47:19 Media kernel: mdcmd (38): nocheck

Apr 22 17:47:19 Media kernel: md: md_do_sync: got signal, exit...

Apr 22 17:47:19 Media kernel: md: recovery thread sync completion status: -4

Apr 22 17:47:22 Media emhttp: Spinning down all drives...

Apr 22 17:47:22 Media kernel: mdcmd (39): spindown 0

Apr 22 17:47:23 Media kernel: mdcmd (40): spindown 1

Apr 22 17:47:23 Media kernel: mdcmd (41): spindown 2

Apr 22 17:47:24 Media kernel: mdcmd (42): spindown 3

Apr 22 18:07:03 Media emhttp: /usr/bin/tail -n 42 -f /var/log/syslog 2>&1

 

 

The log says that it detected an unclean shutdown, but I had rebooted the machine from the web interface after upgrading to b15. Is that an unclean shutdown?

 

 

 

 

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...