Down at the bottom. Just upgraded from 4.6 to 4.7

syslog-2012-01-30.txt

Does the main screen shown any thing in the Errors column?

I would check power requirements, cables (power and data), etc.

 

Then run some SMART reports on the drives, as the failed command is not a good sign.

My drive started throwing those and failed although made it through a pre-clear, shortly after starting throwing even more errors.  RMA'ed it.

 

I forget how to translate ata1.00 to which "sd" assignment it is... try looking at your "device" page and look at the pci-0000 notation.  I'm sure one of the guru's will help you there if you can't find which drive it is.

 

Either way, won't hurt to run smart on all the drives.

Does the main screen shown any thing in the Errors column?

 

No errors are shown.

I would check power requirements, cables (power and data), etc.

 

Then run some SMART reports on the drives, as the failed command is not a good sign.

My drive started throwing those and failed although made it through a pre-clear, shortly after starting throwing even more errors.  RMA'ed it.

 

I forget how to translate ata1.00 to which "sd" assignment it is... try looking at your "device" page and look at the pci-0000 notation.  I'm sure one of the guru's will help you there if you can't find which drive it is.

 

Either way, won't hurt to run smart on all the drives.

 

Does the smart report have to be run at the console? I'm running headless.

Does the smart report have to be run at the console? I'm running headless.

Yes, but not the physical console. You can use telnet if you stay connected, or screen inside telnet if you want the console session to stay alive while you disconnect telnet.

Does the main screen shown any thing in the Errors column?

 

No errors are shown.

 

One of the disks is giving errors.  A refresh of the Main screen should show errors. Otherwise, post SMART reports for all drives.

I used telnet to get the smart reports. No errors. I'm running a parity check now to see if it will generate some errors. It will be done sometime in the middle of the night I'd imagine. I'll post my findings tomorrow. Thanks for the help so far.

Post the contents of the SMART reports. They may indicate the problem drive.

Syslog after parity check with no errors on main screen

 

Jan 30 20:47:40 Norco login[16732]: ROOT LOGIN  on `pts/0' from `192.168.0.124' (Logins)

Jan 30 21:06:50 Norco emhttp: Spinning up all drives... (Other emhttp)

Jan 30 21:06:50 Norco kernel: mdcmd (19): spinup 0 (Routine)

Jan 30 21:06:50 Norco kernel: mdcmd (20): spinup 1 (Routine)

Jan 30 21:06:50 Norco kernel: mdcmd (21): spinup 2 (Routine)

Jan 30 21:06:50 Norco kernel: mdcmd (22): spinup 3 (Routine)

Jan 30 21:07:05 Norco kernel: mdcmd (23): check CORRECT (unRAID engine)

Jan 30 21:07:05 Norco kernel: md: recovery thread woken up ... (unRAID engine)

Jan 30 21:07:05 Norco kernel: md: recovery thread checking parity... (unRAID engine)

Jan 30 21:07:05 Norco kernel: md: using 1152k window, over a total of 1953514552 blocks. (unRAID engine)

Jan 30 23:21:00 Norco kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

Jan 30 23:21:00 Norco kernel: ata1.00: irq_stat 0x40000001 (Drive related)

Jan 30 23:21:00 Norco kernel: ata1.00: failed command: READ DMA EXT (Minor Issues)

Jan 30 23:21:00 Norco kernel: ata1.00: cmd 25/00:00:27:ad:99/00:04:67:00:00/e0 tag 0 dma 524288 in (Drive related)

Jan 30 23:21:00 Norco kernel:          res 51/40:bf:5f:ad:99/00:03:67:00:00/e0 Emask 0x9 (media error) (Errors)

Jan 30 23:21:00 Norco kernel: ata1.00: status: { DRDY ERR } (Drive related)

Jan 30 23:21:00 Norco kernel: ata1.00: error: { UNC } (Errors)

Jan 30 23:21:00 Norco kernel: ata1.00: configured for UDMA/133 (Drive related)

Jan 30 23:21:00 Norco kernel: ata1: EH complete (Drive related)

Jan 30 23:21:03 Norco kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

Jan 30 23:21:03 Norco kernel: ata1.00: irq_stat 0x40000001 (Drive related)

Jan 30 23:21:03 Norco kernel: ata1.00: failed command: READ DMA EXT (Minor Issues)

Jan 30 23:21:03 Norco kernel: ata1.00: cmd 25/00:00:27:de:99/00:04:67:00:00/e0 tag 0 dma 524288 in (Drive related)

Jan 30 23:21:03 Norco kernel:          res 51/40:4f:d7:df:99/00:02:67:00:00/e0 Emask 0x9 (media error) (Errors)

Jan 30 23:21:03 Norco kernel: ata1.00: status: { DRDY ERR } (Drive related)

Jan 30 23:21:03 Norco kernel: ata1.00: error: { UNC } (Errors)

Jan 30 23:21:03 Norco kernel: ata1.00: configured for UDMA/133 (Drive related)

Jan 30 23:21:03 Norco kernel: ata1: EH complete (Drive related)

Jan 30 23:21:10 Norco kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

Jan 30 23:21:10 Norco kernel: ata1.00: irq_stat 0x40000001 (Drive related)

Jan 30 23:21:10 Norco kernel: ata1.00: failed command: READ DMA EXT (Minor Issues)

Jan 30 23:21:10 Norco kernel: ata1.00: cmd 25/00:00:27:2b:9a/00:04:67:00:00/e0 tag 0 dma 524288 in (Drive related)

Jan 30 23:21:10 Norco kernel:          res 51/40:5f:c7:2d:9a/00:01:67:00:00/e0 Emask 0x9 (media error) (Errors)

Jan 30 23:21:10 Norco kernel: ata1.00: status: { DRDY ERR } (Drive related)

Jan 30 23:21:10 Norco kernel: ata1.00: error: { UNC } (Errors)

Jan 30 23:21:10 Norco kernel: ata1.00: configured for UDMA/133 (Drive related)

Jan 30 23:21:10 Norco kernel: ata1: EH complete (Drive related)

Jan 30 23:21:25 Norco kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

Jan 30 23:21:25 Norco kernel: ata1.00: irq_stat 0x40000001 (Drive related)

Jan 30 23:21:25 Norco kernel: ata1.00: failed command: READ DMA EXT (Minor Issues)

Jan 30 23:21:25 Norco kernel: ata1.00: cmd 25/00:00:47:ed:9b/00:04:67:00:00/e0 tag 0 dma 524288 in (Drive related)

Jan 30 23:21:25 Norco kernel:          res 51/40:bf:87:ef:9b/00:01:67:00:00/e0 Emask 0x9 (media error) (Errors)

Jan 30 23:21:25 Norco kernel: ata1.00: status: { DRDY ERR } (Drive related)

Jan 30 23:21:25 Norco kernel: ata1.00: error: { UNC } (Errors)

Jan 30 23:21:25 Norco kernel: ata1.00: configured for UDMA/133 (Drive related)

Jan 30 23:21:25 Norco kernel: ata1: EH complete (Drive related)

Jan 30 23:21:28 Norco kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

Jan 30 23:21:28 Norco kernel: ata1.00: irq_stat 0x40000001 (Drive related)

Jan 30 23:21:28 Norco kernel: ata1.00: failed command: READ DMA EXT (Minor Issues)

Jan 30 23:21:28 Norco kernel: ata1.00: cmd 25/00:00:47:ed:9b/00:04:67:00:00/e0 tag 0 dma 524288 in (Drive related)

Jan 30 23:21:28 Norco kernel:          res 51/40:bf:87:ef:9b/00:01:67:00:00/e0 Emask 0x9 (media error) (Errors)

Jan 30 23:21:28 Norco kernel: ata1.00: status: { DRDY ERR } (Drive related)

Jan 30 23:21:28 Norco kernel: ata1.00: error: { UNC } (Errors)

Jan 30 23:21:28 Norco kernel: ata1.00: configured for UDMA/133 (Drive related)

Jan 30 23:21:28 Norco kernel: ata1: EH complete (Drive related)

Jan 30 23:30:48 Norco kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

Jan 30 23:30:48 Norco kernel: ata1.00: irq_stat 0x40000001 (Drive related)

Jan 30 23:30:48 Norco kernel: ata1.00: failed command: READ DMA EXT (Minor Issues)

Jan 30 23:30:48 Norco kernel: ata1.00: cmd 25/00:f0:3f:6c:02/00:03:6e:00:00/e0 tag 0 dma 516096 in (Drive related)

Jan 30 23:30:48 Norco kernel:          res 51/40:ef:3f:6e:02/00:01:6e:00:00/e0 Emask 0x9 (media error) (Errors)

Jan 30 23:30:48 Norco kernel: ata1.00: status: { DRDY ERR } (Drive related)

Jan 30 23:30:48 Norco kernel: ata1.00: error: { UNC } (Errors)

Jan 30 23:30:48 Norco kernel: ata1.00: configured for UDMA/133 (Drive related)

Jan 30 23:30:48 Norco kernel: ata1: EH complete (Drive related)

Jan 31 03:22:49 Norco kernel: md: sync done. time=22544sec rate=86653K/sec (unRAID engine)

Jan 31 03:22:49 Norco kernel: md: recovery thread sync completion status: 0 (unRAID engine)

Jan 31 05:22:55 Norco kernel: mdcmd (24): spindown 1 (Routine)

Jan 31 05:22:56 Norco kernel: mdcmd (25): spindown 3 (Routine)

Jan 31 05:59:51 Norco dhcpcd[1343]: sending DHCP_REQUEST for 192.168.0.123 to 192.168.0.1  (Routine)

Jan 31 05:59:51 Norco dhcpcd[1343]: dhcpIPaddrLeaseTime=86400 in DHCP server response.  (Routine)

Jan 31 05:59:51 Norco dhcpcd[1343]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec  (Routine)

Jan 31 05:59:51 Norco dhcpcd[1343]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec  (Routine)

Jan 31 05:59:51 Norco dhcpcd[1343]: DHCP_ACK received from  (192.168.0.1)  (Routine)

Jan 31 06:00:38 Norco kernel: mdcmd (26): spindown 0 (Routine)

Jan 31 06:00:39 Norco kernel: mdcmd (27): spindown 2 (Routine)

UNC = un-correctable-read errors.

 

In other words, un-readable sectors on the disk.  They should show up in the SMART report as either pending re-allocation, or already re-allocated if subsequently written to since the errors had occurred.

find out which drive ata1 is and check the wiring to the drive and/or replace the sata cable if you can.

find out which drive ata1 is and check the wiring to the drive and/or replace the sata cable if you can.

Sorry to disagree, but a cable would cause CRC errors  (checksum errors), but not UNC errors.  You are seeing errors from un-readable sectors on the physical disk, not intermittent communications on a SATA cable.

 

Get smartctl reports from the drives.  You'll probably see the sectors pending re-allocation.