May 23, 201214 yr I am in the process replacing a bad drive in my array. Unfortunately, another disk is now acting up, and throwing up disk read errors. The current count is up to 27,910. It has slowed the rebuild process to a crawl. It's now reading 46 KB/s, and shows 90% complete, but 73,209 minutes to completion. Should I just let this finish on its own? The webUI has also slowed to a crawl, and takes about a minute to refresh. I'm not sure whether these errors are indicative of a true hardware problem or something I did when I replaced the drive. What is the best smartctl command string to use in this sort of case? I don't think I can attach the complete syslog, as it's about 6MB, but here's a portion: May 22 17:47:11 MediaServer kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 May 22 17:47:11 MediaServer kernel: ata1.00: irq_stat 0x40000001 May 22 17:47:11 MediaServer kernel: ata1.00: failed command: READ DMA EXT May 22 17:47:11 MediaServer kernel: ata1.00: cmd 25/00:00:b0:dd:b6/00:04:d0:00:00/e0 tag 0 dma 524288 in May 22 17:47:11 MediaServer kernel: res 51/40:ef:b8:dd:b6/00:03:d0:00:00/e0 Emask 0x9 (media error) May 22 17:47:11 MediaServer kernel: ata1.00: status: { DRDY ERR } May 22 17:47:11 MediaServer kernel: ata1.00: error: { UNC } May 22 17:47:11 MediaServer kernel: ata1.00: configured for UDMA/133 May 22 17:47:11 MediaServer kernel: ata1: EH complete May 22 17:47:15 MediaServer kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 May 22 17:47:15 MediaServer kernel: ata1.00: irq_stat 0x40000001 May 22 17:47:15 MediaServer kernel: ata1.00: failed command: READ DMA EXT May 22 17:47:15 MediaServer kernel: ata1.00: cmd 25/00:00:b0:e1:b6/00:04:d0:00:00/e0 tag 0 dma 524288 in May 22 17:47:15 MediaServer kernel: res 51/40:5f:40:e3:b6/00:02:d0:00:00/e0 Emask 0x9 (media error) May 22 17:47:15 MediaServer kernel: ata1.00: status: { DRDY ERR } May 22 17:47:15 MediaServer kernel: ata1.00: error: { UNC } May 22 17:47:15 MediaServer kernel: ata1.00: configured for UDMA/133 May 22 17:47:15 MediaServer kernel: ata1: EH complete May 22 17:47:18 MediaServer kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 May 22 17:47:18 MediaServer kernel: ata1.00: irq_stat 0x40000001 May 22 17:47:18 MediaServer kernel: ata1.00: failed command: READ DMA EXT May 22 17:47:18 MediaServer kernel: ata1.00: cmd 25/00:00:b0:e1:b6/00:04:d0:00:00/e0 tag 0 dma 524288 in May 22 17:47:18 MediaServer kernel: res 51/40:5f:40:e3:b6/00:02:d0:00:00/e0 Emask 0x9 (media error) May 22 17:47:18 MediaServer kernel: ata1.00: status: { DRDY ERR } May 22 17:47:18 MediaServer kernel: ata1.00: error: { UNC } May 22 17:47:18 MediaServer kernel: ata1.00: configured for UDMA/133 May 22 17:47:18 MediaServer kernel: ata1: EH complete May 22 17:47:21 MediaServer kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 May 22 17:47:21 MediaServer kernel: ata1.00: irq_stat 0x40000001 May 22 17:47:21 MediaServer kernel: ata1.00: failed command: READ DMA EXT May 22 17:47:21 MediaServer kernel: ata1.00: cmd 25/00:00:b0:e1:b6/00:04:d0:00:00/e0 tag 0 dma 524288 in May 22 17:47:21 MediaServer kernel: res 51/40:5f:40:e3:b6/00:02:d0:00:00/e0 Emask 0x9 (media error) May 22 17:47:21 MediaServer kernel: ata1.00: status: { DRDY ERR } May 22 17:47:21 MediaServer kernel: ata1.00: error: { UNC } May 22 17:47:21 MediaServer kernel: ata1.00: configured for UDMA/133 May 22 17:47:21 MediaServer kernel: ata1: EH complete May 22 17:47:24 MediaServer kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 May 22 17:47:24 MediaServer kernel: ata1.00: irq_stat 0x40000001 May 22 17:47:24 MediaServer kernel: ata1.00: failed command: READ DMA EXT May 22 17:47:24 MediaServer kernel: ata1.00: cmd 25/00:00:b0:e1:b6/00:04:d0:00:00/e0 tag 0 dma 524288 in May 22 17:47:24 MediaServer kernel: res 51/40:2f:70:e3:b6/00:02:d0:00:00/e0 Emask 0x9 (media error) May 22 17:47:24 MediaServer kernel: ata1.00: status: { DRDY ERR } May 22 17:47:24 MediaServer kernel: ata1.00: error: { UNC } May 22 17:47:24 MediaServer kernel: ata1.00: configured for UDMA/133 May 22 17:47:24 MediaServer kernel: ata1: EH complete May 22 17:47:28 MediaServer kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 May 22 17:47:28 MediaServer kernel: ata1.00: irq_stat 0x40000001 May 22 17:47:28 MediaServer kernel: ata1.00: failed command: READ DMA EXT May 22 17:47:28 MediaServer kernel: ata1.00: cmd 25/00:00:b0:e1:b6/00:04:d0:00:00/e0 tag 0 dma 524288 in May 22 17:47:28 MediaServer kernel: res 51/40:5f:40:e3:b6/00:02:d0:00:00/e0 Emask 0x9 (media error) May 22 17:47:28 MediaServer kernel: ata1.00: status: { DRDY ERR } May 22 17:47:28 MediaServer kernel: ata1.00: error: { UNC } May 22 17:47:28 MediaServer kernel: ata1.00: configured for UDMA/133 May 22 17:47:28 MediaServer kernel: ata1: EH complete May 22 17:47:31 MediaServer kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 May 22 17:47:31 MediaServer kernel: ata1.00: irq_stat 0x40000001 May 22 17:47:31 MediaServer kernel: ata1.00: failed command: READ DMA EXT May 22 17:47:31 MediaServer kernel: ata1.00: cmd 25/00:00:b0:e1:b6/00:04:d0:00:00/e0 tag 0 dma 524288 in May 22 17:47:31 MediaServer kernel: res 51/40:5f:40:e3:b6/00:02:d0:00:00/e0 Emask 0x9 (media error) May 22 17:47:31 MediaServer kernel: ata1.00: status: { DRDY ERR } May 22 17:47:31 MediaServer kernel: ata1.00: error: { UNC } May 22 17:47:31 MediaServer kernel: ata1.00: configured for UDMA/133 May 22 17:47:31 MediaServer kernel: sd 1:0:0:0: [sdb] Unhandled sense code May 22 17:47:31 MediaServer kernel: sd 1:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08 May 22 17:47:31 MediaServer kernel: sd 1:0:0:0: [sdb] Sense Key : 0x3 [current] [descriptor] May 22 17:47:31 MediaServer kernel: Descriptor sense data with sense descriptors (in hex): May 22 17:47:31 MediaServer kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 May 22 17:47:31 MediaServer kernel: d0 b6 e3 40 May 22 17:47:31 MediaServer kernel: sd 1:0:0:0: [sdb] ASC=0x11 ASCQ=0x4 May 22 17:47:31 MediaServer kernel: sd 1:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 d0 b6 e1 b0 00 04 00 00 May 22 17:47:31 MediaServer kernel: end_request: I/O error, dev sdb, sector 3501646656 May 22 17:47:31 MediaServer kernel: ata1: EH complete May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646592/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646600/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646608/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646616/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646624/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646632/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646640/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646648/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646656/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646664/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646672/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646680/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646688/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646696/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646704/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646712/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646720/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646728/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646736/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646744/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646752/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646760/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646768/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646776/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646784/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646792/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646800/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646808/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646816/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646824/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646832/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646840/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646848/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646856/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646864/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646872/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646880/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646888/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646896/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646904/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646912/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646920/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646928/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646936/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646944/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646952/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646960/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646968/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646976/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646984/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501646992/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647000/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647008/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647016/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647024/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647032/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647040/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647048/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647056/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647064/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647072/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647080/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647088/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647096/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647104/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647112/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647120/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647128/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647136/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647144/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647152/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647160/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647168/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647176/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647184/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647192/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647200/1, count: 1 May 22 17:47:31 MediaServer kernel: md: disk1 read error May 22 17:47:31 MediaServer kernel: handle_stripe read error: 3501647208/1, count: 1
May 23, 201214 yr Author Update: The rebuild seems to be back up to a reasonable speed (32 MB/s). The webUI is refreshing at normal speed as well. Rebuild is at 93% with an estimated 40 minutes remaining. I'll keep my fingers crossed that there aren't any more errors, and then start some serious troubleshooting on the suspect drive tomorrow.
May 23, 201214 yr Author Update: Rebuild finished with 34,788 errors from the affected disk. Smart report attached. I'm not sure how to interpret it. There are three categories showing as "Pre-fail", including the reallocated sector count, which is at a raw value of 855. I tried to run a SMART short test, and left it for 15 minutes, but it never finished. I aborted it. I'm almost set on doing an RMA for this drive, but I'd appreciate a second opinion. smart.txt
May 23, 201214 yr I'm almost set on doing an RMA for this drive, but I'd appreciate a second opinion. You also have 429 sectors pending re-allocation. 197 Current_Pending_Sector 0x0032 199 001 000 Old_age Always - 429 RMA the disk. Joe L.
Archived
This topic is now archived and is closed to further replies.