I'm getting what looks like an error in my syslog.  It shows Red in umenu's syslog section so it definitely has me worried.  The main unraid page looks all green with no errors at all.  I have included a copy of my syslog below the error appears to be coming up every 3 minutes.  I appriciate any help you can offer me. 

 

[glow=red,2,300]Jun 23 11:21:05 Tower kernel: ata2: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen

Jun 23 11:21:05 Tower kernel: ata2: irq_stat 0x00400040, connection status changed

Jun 23 11:21:05 Tower kernel: ata2: SError: { PHYRdyChg DevExch }[/glow]

Jun 23 11:21:05 Tower kernel: ata2: hard resetting link

Jun 23 11:21:11 Tower kernel: ata2: link is slow to respond, please be patient (ready=0)

Jun 23 11:21:15 Tower kernel: ata2: COMRESET failed (errno=-16)

Jun 23 11:21:15 Tower kernel: ata2: hard resetting link

Jun 23 11:21:17 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Jun 23 11:21:17 Tower kernel: ata2.00: configured for UDMA/33

Jun 23 11:21:17 Tower kernel: ata2: EH complete

Jun 23 11:21:17 Tower kernel: mdcmd (148405): spindown 1

[glow=red,2,300]Jun 23 11:24:16 Tower kernel: ata2: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen

Jun 23 11:24:16 Tower kernel: ata2: irq_stat 0x00400040, connection status changed

Jun 23 11:24:16 Tower kernel: ata2: SError: { PHYRdyChg DevExch }[/glow]

Jun 23 11:24:16 Tower kernel: ata2: hard resetting link

Jun 23 11:24:22 Tower kernel: ata2: link is slow to respond, please be patient (ready=0)

Jun 23 11:24:26 Tower kernel: ata2: COMRESET failed (errno=-16)

Jun 23 11:24:26 Tower kernel: ata2: hard resetting link

Jun 23 11:24:28 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Jun 23 11:24:28 Tower kernel: ata2.00: configured for UDMA/33

Jun 23 11:24:28 Tower kernel: ata2: EH complete

Jun 23 11:24:28 Tower kernel: mdcmd (148424): spindown 1

Jun 23 11:26:27 Tower kernel: ata2: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen

Jun 23 11:26:27 Tower kernel: ata2: irq_stat 0x00400040, connection status changed

Jun 23 11:26:27 Tower kernel: ata2: SError: { PHYRdyChg DevExch }

Jun 23 11:26:27 Tower kernel: ata2: hard resetting link

Jun 23 11:26:33 Tower kernel: ata2: link is slow to respond, please be patient (ready=0)

Jun 23 11:26:37 Tower kernel: ata2: COMRESET failed (errno=-16)

Jun 23 11:26:37 Tower kernel: ata2: hard resetting link

Jun 23 11:26:40 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Jun 23 11:26:40 Tower kernel: ata2.00: configured for UDMA/33

Jun 23 11:26:40 Tower kernel: ata2: EH complete

Jun 23 11:26:40 Tower kernel: mdcmd (148437): spindown 1

Jun 23 11:28:38 Tower kernel: ata2: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen

Jun 23 11:28:38 Tower kernel: ata2: irq_stat 0x00400040, connection status changed

Jun 23 11:28:38 Tower kernel: ata2: SError: { PHYRdyChg DevExch }

Jun 23 11:28:38 Tower kernel: ata2: hard resetting link

Jun 23 11:28:44 Tower kernel: ata2: link is slow to respond, please be patient (ready=0)

Jun 23 11:28:48 Tower kernel: ata2: COMRESET failed (errno=-16)

Jun 23 11:28:48 Tower kernel: ata2: hard resetting link

Jun 23 11:28:51 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Jun 23 11:28:51 Tower kernel: ata2.00: configured for UDMA/33

Jun 23 11:28:51 Tower kernel: ata2: EH complete

Jun 23 11:28:51 Tower kernel: mdcmd (148450): spindown 1

Jun 23 11:30:49 Tower kernel: ata2: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen

Jun 23 11:30:49 Tower kernel: ata2: irq_stat 0x00400040, connection status changed

Jun 23 11:30:49 Tower kernel: ata2: SError: { PHYRdyChg DevExch }

Jun 23 11:30:49 Tower kernel: ata2: hard resetting link

Jun 23 11:30:55 Tower kernel: ata2: link is slow to respond, please be patient (ready=0)

Jun 23 11:30:59 Tower kernel: ata2: COMRESET failed (errno=-16)

Jun 23 11:30:59 Tower kernel: ata2: hard resetting link

Jun 23 11:31:02 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Jun 23 11:31:02 Tower kernel: ata2.00: configured for UDMA/33

Jun 23 11:31:02 Tower kernel: ata2: EH complete

Jun 23 11:31:02 Tower kernel: mdcmd (148463): spindown 1

Jun 23 11:34:00 Tower kernel: ata2: exception Emask 0x50 SAct 0x0 SErr 0x4010800 action 0xe frozen

Jun 23 11:34:00 Tower kernel: ata2: irq_stat 0x00400040, connection status changed

Jun 23 11:34:00 Tower kernel: ata2: SError: { HostInt PHYRdyChg DevExch }

Jun 23 11:34:00 Tower kernel: ata2: hard resetting link

Jun 23 11:34:06 Tower kernel: ata2: link is slow to respond, please be patient (ready=0)

Jun 23 11:34:10 Tower kernel: ata2: COMRESET failed (errno=-16)

Jun 23 11:34:10 Tower kernel: ata2: hard resetting link

Jun 23 11:34:13 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Jun 23 11:34:13 Tower kernel: ata2.00: configured for UDMA/33

Jun 23 11:34:13 Tower kernel: ata2: EH complete

Jun 23 11:34:13 Tower kernel: mdcmd (148482): spindown 1

Jun 23 11:36:11 Tower kernel: ata2: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen

Jun 23 11:36:11 Tower kernel: ata2: irq_stat 0x00400040, connection status changed

Jun 23 11:36:11 Tower kernel: ata2: SError: { PHYRdyChg DevExch }

Jun 23 11:36:11 Tower kernel: ata2: hard resetting link

Jun 23 11:36:17 Tower kernel: ata2: link is slow to respond, please be patient (ready=0)

Jun 23 11:36:21 Tower kernel: ata2: COMRESET failed (errno=-16)

Jun 23 11:36:21 Tower kernel: ata2: hard resetting link

Jun 23 11:36:24 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Jun 23 11:36:24 Tower kernel: ata2.00: configured for UDMA/33

Jun 23 11:36:24 Tower kernel: ata2: EH complete

Jun 23 11:36:24 Tower kernel: mdcmd (148495): spindown 1

Jun 23 11:42:22 Tower kernel: ata2: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen

Jun 23 11:42:22 Tower kernel: ata2: irq_stat 0x00400040, connection status changed

Jun 23 11:42:22 Tower kernel: ata2: SError: { PHYRdyChg DevExch }

Jun 23 11:42:22 Tower kernel: ata2: hard resetting link

Jun 23 11:42:28 Tower kernel: ata2: link is slow to respond, please be patient (ready=0)

Jun 23 11:42:33 Tower kernel: ata2: COMRESET failed (errno=-16)

Jun 23 11:42:33 Tower kernel: ata2: hard resetting link

Jun 23 11:42:35 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Jun 23 11:42:35 Tower kernel: ata2.00: configured for UDMA/33

Jun 23 11:42:35 Tower kernel: ata2: EH complete

Jun 23 11:42:35 Tower kernel: mdcmd (148532): spindown 1

Jun 23 11:43:27 Tower kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen

Jun 23 11:43:27 Tower kernel: ata1: irq_stat 0x00400040, connection status changed

Jun 23 11:43:27 Tower kernel: ata1: SError: { PHYRdyChg DevExch }

Jun 23 11:43:27 Tower kernel: ata1: hard resetting link

Jun 23 11:43:33 Tower kernel: ata1: link is slow to respond, please be patient (ready=0)

Jun 23 11:43:38 Tower kernel: ata1: COMRESET failed (errno=-16)

Jun 23 11:43:38 Tower kernel: ata1: hard resetting link

Jun 23 11:43:40 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Jun 23 11:43:40 Tower kernel: ata1.00: configured for UDMA/33

Jun 23 11:43:40 Tower kernel: ata1: EH complete

Jun 23 11:43:40 Tower kernel: mdcmd (148539): spindown 0

Jun 23 11:45:34 Tower kernel: ata2: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen

Jun 23 11:45:34 Tower kernel: ata2: irq_stat 0x00400040, connection status changed

Jun 23 11:45:34 Tower kernel: ata2: SError: { PHYRdyChg DevExch }

Jun 23 11:45:34 Tower kernel: ata2: hard resetting link

Jun 23 11:45:39 Tower kernel: ata2: link is slow to respond, please be patient (ready=0)

Jun 23 11:45:44 Tower kernel: ata2: COMRESET failed (errno=-16)

Jun 23 11:45:44 Tower kernel: ata2: hard resetting link

Jun 23 11:45:46 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Jun 23 11:45:46 Tower kernel: ata2.00: configured for UDMA/33

Jun 23 11:45:46 Tower kernel: ata2: EH complete

Jun 23 11:45:46 Tower kernel: mdcmd (148552): spindown 1

Jun 23 11:48:45 Tower kernel: ata2: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen

Jun 23 11:48:45 Tower kernel: ata2: irq_stat 0x00400040, connection status changed

Jun 23 11:48:45 Tower kernel: ata2: SError: { PHYRdyChg DevExch }

Jun 23 11:48:45 Tower kernel: ata2: hard resetting link

Jun 23 11:48:50 Tower kernel: ata2: link is slow to respond, please be patient (ready=0)

Jun 23 11:48:55 Tower kernel: ata2: COMRESET failed (errno=-16)

Jun 23 11:48:55 Tower kernel: ata2: hard resetting link

Jun 23 11:48:57 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Jun 23 11:48:57 Tower kernel: ata2.00: configured for UDMA/33

Jun 23 11:48:57 Tower kernel: ata2: EH complete

Jun 23 11:48:57 Tower kernel: mdcmd (148571): spindown 1

Jun 23 11:49:39 Tower kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen

Jun 23 11:49:39 Tower kernel: ata1: irq_stat 0x00400040, connection status changed

Jun 23 11:49:39 Tower kernel: ata1: SError: { PHYRdyChg DevExch }

Jun 23 11:49:39 Tower kernel: ata1: hard resetting link

Jun 23 11:49:44 Tower kernel: ata1: link is slow to respond, please be patient (ready=0)

Jun 23 11:49:49 Tower kernel: ata1: COMRESET failed (errno=-16)

Jun 23 11:49:49 Tower kernel: ata1: hard resetting link

Jun 23 11:49:51 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Jun 23 11:49:51 Tower kernel: ata1.00: configured for UDMA/33

Jun 23 11:49:51 Tower kernel: ata1: EH complete

Jun 23 11:49:51 Tower kernel: mdcmd (148577): spindown 0

Jun 23 11:51:56 Tower kernel: ata2: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen

Jun 23 11:51:56 Tower kernel: ata2: irq_stat 0x00400040, connection status changed

Jun 23 11:51:56 Tower kernel: ata2: SError: { PHYRdyChg DevExch }

Jun 23 11:51:56 Tower kernel: ata2: hard resetting link

Jun 23 11:52:01 Tower kernel: ata2: link is slow to respond, please be patient (ready=0)

Jun 23 11:52:06 Tower kernel: ata2: COMRESET failed (errno=-16)

Jun 23 11:52:06 Tower kernel: ata2: hard resetting link

Jun 23 11:52:08 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Jun 23 11:52:08 Tower kernel: ata2.00: configured for UDMA/33

Jun 23 11:52:08 Tower kernel: ata2: EH complete

Jun 23 11:52:08 Tower kernel: mdcmd (148591): spindown 1

Jun 23 11:54:07 Tower kernel: ata2: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen

Jun 23 11:54:07 Tower kernel: ata2: irq_stat 0x00400040, connection status changed

Jun 23 11:54:07 Tower kernel: ata2: SError: { PHYRdyChg DevExch }

Jun 23 11:54:07 Tower kernel: ata2: hard resetting link

Jun 23 11:54:12 Tower kernel: ata2: link is slow to respond, please be patient (ready=0)

Jun 23 11:54:17 Tower kernel: ata2: COMRESET failed (errno=-16)

Jun 23 11:54:17 Tower kernel: ata2: hard resetting link

Jun 23 11:54:19 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Jun 23 11:54:19 Tower kernel: ata2.00: configured for UDMA/33

Jun 23 11:54:19 Tower kernel: ata2: EH complete

Jun 23 11:54:19 Tower kernel: mdcmd (148604): spindown 1

 

Yes something is wrong.  But it does no good to see a partial syslog.  Is this a really old drive?

Sorry about that here is the full syslog attached.  All 3 of my 2TB disks are brand new I do have a single older 1TB drive in there too.  Another bit of information I just ran a full parity check and it all passed with 0 errors.  Could this be a bios setting that is restricting something with unraid?

syslog-2010-06-23.zip

Does the syslog attachment I provided give you enough information to help me?  Is there any other information I can provide? 

No because the syslog file has grown so big that it has overflowed & what is now in syslog is the 'continuation'.

But it appears that the drive is producing an error everytime it's given a spin down command, which is why I asked if it was an old drive.  If you look in /var/log there should be something like 'syslog.1', that's the one I need.  Alternately you can reboot and let it run a while (until you see errors in syslog), then post that syslog.  Anyway something is wrong with disk1, maybe check cabling and/or move to a different controller to see if problem follows drive or controller.  If drive, probably should consider replacing.

I'm getting the same errors on brand new drives connected to the SATA ports on my MB..

 

Anyone have any suggestions ? Checked cables, all good...