N40L with three Hitachi HDS723030BLE640 with 5.0.5 running. drives running at 40C as it pretty hot here.

 

Did a reboot and full scan three days ago. 92% full.

 

Copies are starting to fail with this ( parity drive )

 

Dec 26 20:44:27 nas kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 26 20:44:27 nas kernel: ata3.00: failed command: WRITE DMA EXT

Dec 26 20:44:27 nas kernel: ata3.00: cmd 35/00:00:18:7f:a6/00:04:f5:00:00/e0 tag 0 dma 524288 out

Dec 26 20:44:27 nas kernel:          res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)

Dec 26 20:44:27 nas kernel: ata3.00: status: { DRDY }

Dec 26 20:44:27 nas kernel: ata3: hard resetting link

Dec 26 20:44:27 nas kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Dec 26 20:44:27 nas kernel: ata3.00: configured for UDMA/133

Dec 26 20:44:27 nas kernel: ata3: EH complete

Dec 26 20:45:20 nas kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 26 20:45:20 nas kernel: ata3.00: failed command: READ DMA EXT

Dec 26 20:45:20 nas kernel: ata3.00: cmd 25/00:20:58:89:a7/00:01:f5:00:00/e0 tag 0 dma 147456 in

Dec 26 20:45:20 nas kernel:          res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)

Dec 26 20:45:20 nas kernel: ata3.00: status: { DRDY }

Dec 26 20:45:20 nas kernel: ata3: hard resetting link

 

Dec 27 14:06:37 nas kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 27 14:06:37 nas kernel: ata3.00: failed command: READ DMA EXT

Dec 27 14:06:37 nas kernel: ata3.00: cmd 25/00:f8:28:d2:cf/00:03:bb:00:00/e0 tag 0 dma 520192 in

Dec 27 14:06:37 nas kernel:          res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)

Dec 27 14:06:37 nas kernel: ata3.00: status: { DRDY }

Dec 27 14:06:37 nas kernel: ata3: hard resetting link

Dec 27 14:06:38 nas kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Dec 27 14:06:38 nas kernel: ata3.00: configured for UDMA/33

 

Attached to port: sdd

ID# ATTRIBUTE NAME FLAG VALUE WORST THRESH TYPE UPDATED FAILED RAW VALUE

1 Raw Read Error Rate 0x000b 077 077 016 Pre-fail Always Never 15074127

2 Throughput Performance 0x0005 139 139 054 Pre-fail Offline Never 71

3 Spin Up Time 0x0007 143 143 024 Pre-fail Always Never 379 (Average 420)

4 Start Stop Count 0x0012 100 100 000 Old age Always Never 784

5 Reallocated Sector Ct 0x0033 073 073 005 Pre-fail Always Never 672

7 Seek Error Rate 0x000b 100 100 067 Pre-fail Always Never 0

8 Seek Time Performance 0x0005 119 119 020 Pre-fail Offline Never 35

9 Power On Hours 0x0012 097 097 000 Old age Always Never 25754

10 Spin Retry Count 0x0013 100 100 060 Pre-fail Always Never 0

12 Power Cycle Count 0x0032 100 100 000 Old age Always Never 41

192 Power-Off Retract Count 0x0032 100 100 000 Old age Always Never 860

193 Load Cycle Count 0x0012 100 100 000 Old age Always Never 860

194 Temperature Celsius 0x0002 157 157 000 Old age Always Never 38 (Min/Max 18/43)

196 Reallocated Event Count 0x0032 066 066 000 Old age Always Never 794

197 Current Pending Sector 0x0022 100 100 000 Old age Always Never 0

198 Offline Uncorrectable 0x0008 100 100 000 Old age Offline Never 0

199 UDMA CRC Error Count 0x000a 200 200 000 Old age Always Never 0

 

Device Model: Hitachi HDS723030BLE640

Serial Number: MS79215X02SD9A

LU WWN Device Id: 5 000cca 37ec14092

Firmware Version: MX6OAAB0

User Capacity: 3,000,592,982,016 bytes [3.00 TB]

Sector Sizes: 512 bytes logical, 4096 bytes physical

Rotation Rate: 7200 rpm

Device is: Not in smartctl database [for details use: -P showall]

ATA Version is: ATA8-ACS T13/1699-D revision 4

SATA Version is: SATA 3.0, 6.0 Gb/s (current: 1.5 Gb/s)

Local Time is: Sun Dec 27 17:13:14 2015 EST

SMART support is: Available - device has SMART capability.

SMART support is: Enabled

SMART overall-health : PASSED

syslog.zip

Drive data and syslog info does look suspicious, but there's nothing conclusive.  Temps are fine, it's never been hotter than 43, which is OK.  Raw Read Error Rate is 77 which is lower than I'm used to, but I don't know what's normal for that drive model.  You can check that yourself since all 3 of your drives are the same model.  Compare their SMART reports, and you should be able to tell if 77 is normal or low.  If low, it's still much higher than the Threshold of 16, so may not be a serious issue, but may be indicative of small mechanical issues.

 

The syslog shows quite a few of those exceptions, all timeouts while waiting for an I/O to process.  No actual errors are reported, just the fact that the drive is taking way too long to perform the I/O actions, which *may* indicate trouble on the drive, but no indication what the trouble is.  You do have 672 remapped sectors, which is rather high, and not a good sign.  What is weird is that Reallocated Event Count is 794, somewhat higher than the 672 sectors reallocated!  Either you have buggy drive firmware (not a good sign!), or the same sector(s) have been reallocated multiple times.  In other words, spare sectors were found to be bad and had to be replaced with other spares, which means you may have less *good* spares than you think.

 

I cannot say I trust the drive.  Sometimes the first sign of a drive going bad is long unexpected delays trying to read or write to it.  I would consider replacing it.  If you purchase a replacement and rebuild parity onto the new drive, you can take this one and Preclear it 2 or 3 times, then decide from the results (and how long it takes) what to do with it.

Went for the reboot, and the full smart check. Came up no errors, and nothing in the logs since. Perhaps just a moment. Not writing much to the system at the moment to test, but do now have a new drive on standy

upgrade to 6.1.6 .. full parity check was ok , but went from 150mb/s to 200k/s in places.

 

Running another full smart now and it Reallocated sector count of 841 , so I'm guessing the end of disk ( at 92 % ) is not so good, or the disk in on its way out.

 

Guess my planned expansion is now a parity replacement. Time to go read the manuals