March 10, 201313 yr Syslog attached but zipped due to size. Recently swapped out two older controllers, an adaptec 4 port and a Promise 4 port PCI for a new Supermicro 8 port SAS/SATA pci express. (AOC-SASLP-MV8) Everything seemed fine until disk9 dropped off the controller on may 5th with stripe errors exactly like those in the current attached log. I swapped out that disk for a brand new one and tested the suspect disk in another system and it seems to be ok. Rebuild went fine and the system has been chugging along until today. Once again, today, while streaming video, I got a stutter and freeze. Went to the unraid and indeed the disk9 has red balled yet again. Could this be a bad cable? I am using 3ware min sas to sata. If so why would it only happen once in a while? Any analysis would be helpful. Thanks. syslog-2013-03-10.zip
March 11, 201313 yr Author Here are the relevant entries in the log - Mar 10 16:49:42 Tower2 kernel: sd 11:0:4:0: [sdr] command f76fe600 timed out (Drive related) Mar 10 16:49:42 Tower2 kernel: sd 11:0:4:0: [sdr] command f76fe6c0 timed out (Drive related) Mar 10 16:49:42 Tower2 kernel: sd 11:0:4:0: [sdr] command f76fea80 timed out (Drive related) Mar 10 16:49:42 Tower2 kernel: sas: Enter sas_scsi_recover_host busy: 3 failed: 3 (Drive related) Mar 10 16:49:42 Tower2 kernel: sas: trying to find task 0xc4916280 (Drive related) Mar 10 16:49:42 Tower2 kernel: sas: sas_scsi_find_task: aborting task 0xc4916280 (Drive related) Mar 10 16:49:42 Tower2 kernel: sas: sas_scsi_find_task: task 0xc4916280 is aborted (Drive related) Mar 10 16:49:42 Tower2 kernel: sas: sas_eh_handle_sas_errors: task 0xc4916280 is aborted (Errors) Mar 10 16:49:42 Tower2 kernel: sas: trying to find task 0xc4917180 (Drive related) Mar 10 16:49:42 Tower2 kernel: sas: sas_scsi_find_task: aborting task 0xc4917180 (Drive related) Mar 10 16:49:42 Tower2 kernel: sas: sas_scsi_find_task: task 0xc4917180 is aborted (Drive related) Mar 10 16:49:42 Tower2 kernel: sas: sas_eh_handle_sas_errors: task 0xc4917180 is aborted (Errors) Mar 10 16:49:42 Tower2 kernel: sas: trying to find task 0xc4916140 (Drive related) Mar 10 16:49:42 Tower2 kernel: sas: sas_scsi_find_task: aborting task 0xc4916140 (Drive related) Mar 10 16:49:42 Tower2 kernel: sas: sas_scsi_find_task: task 0xc4916140 is aborted (Drive related) Mar 10 16:49:42 Tower2 kernel: sas: sas_eh_handle_sas_errors: task 0xc4916140 is aborted (Errors) Mar 10 16:49:42 Tower2 kernel: sas: ata15: end_device-11:4: cmd error handler (Errors) Mar 10 16:49:42 Tower2 kernel: sas: ata11: end_device-11:0: dev error handler (Errors) Mar 10 16:49:42 Tower2 kernel: sas: ata12: end_device-11:1: dev error handler (Errors) Mar 10 16:49:42 Tower2 kernel: sas: ata13: end_device-11:2: dev error handler (Errors) Mar 10 16:49:42 Tower2 kernel: sas: ata14: end_device-11:3: dev error handler (Errors) Mar 10 16:49:42 Tower2 kernel: sas: ata15: end_device-11:4: dev error handler (Errors) Mar 10 16:49:42 Tower2 kernel: ata15.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x6 frozen (Errors) Mar 10 16:49:42 Tower2 kernel: sas: ata16: end_device-11:5: dev error handler (Errors) Mar 10 16:49:42 Tower2 kernel: ata15.00: failed command: READ FPDMA QUEUED (Minor Issues) Mar 10 16:49:42 Tower2 kernel: ata15.00: cmd 60/00:00:90:b8:a8/02:00:04:00:00/40 tag 0 ncq 262144 in (Drive related) Mar 10 16:49:42 Tower2 kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) (Errors) Mar 10 16:49:42 Tower2 kernel: sas: ata17: end_device-11:6: dev error handler (Errors) Mar 10 16:49:42 Tower2 kernel: ata15.00: status: { DRDY } (Drive related) Mar 10 16:49:42 Tower2 kernel: sas: ata18: end_device-11:7: dev error handler (Errors) Mar 10 16:49:42 Tower2 kernel: ata15.00: failed command: READ FPDMA QUEUED (Minor Issues) Mar 10 16:49:42 Tower2 kernel: ata15.00: cmd 60/00:00:90:b6:a8/02:00:04:00:00/40 tag 1 ncq 262144 in (Drive related) Mar 10 16:49:42 Tower2 kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Mar 10 16:49:42 Tower2 kernel: ata15.00: status: { DRDY } (Drive related) Mar 10 16:49:42 Tower2 kernel: ata15.00: failed command: READ FPDMA QUEUED (Minor Issues) Mar 10 16:49:42 Tower2 kernel: ata15.00: cmd 60/00:00:90:ba:a8/02:00:04:00:00/40 tag 2 ncq 262144 in (Drive related) Mar 10 16:49:42 Tower2 kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Mar 10 16:49:42 Tower2 kernel: ata15.00: status: { DRDY } (Drive related) Mar 10 16:49:42 Tower2 kernel: ata15: hard resetting link (Minor Issues) Mar 10 16:49:44 Tower2 kernel: mvsas 0000:01:00.0: Phy4 : No sig fis (Drive related) Mar 10 16:49:44 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 1521:mvs_I_T_nexus_reset for device[4]:rc= 0 (System) Mar 10 16:49:44 Tower2 kernel: sas: sas_form_port: phy4 belongs to port4 already(1)! (Drive related) Mar 10 16:49:50 Tower2 kernel: ata15.00: qc timeout (cmd 0x27) (Drive related) Mar 10 16:49:50 Tower2 kernel: ata15.00: failed to read native max address (err_mask=0x4) (Minor Issues) Mar 10 16:49:50 Tower2 kernel: ata15.00: HPA support seems broken, skipping HPA handling (Minor Issues) Mar 10 16:49:50 Tower2 kernel: ata15.00: revalidation failed (errno=-5) (Minor Issues) Mar 10 16:49:50 Tower2 kernel: ata15: hard resetting link (Minor Issues) Mar 10 16:49:52 Tower2 kernel: mvsas 0000:01:00.0: Phy4 : No sig fis (Drive related) Mar 10 16:49:52 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 1521:mvs_I_T_nexus_reset for device[4]:rc= 0 (System) Mar 10 16:49:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 1951:Release slot [0] tag[0], task [c4916140]: (System) Mar 10 16:49:56 Tower2 kernel: sas: sas_ata_task_done: SAS error 8a (Errors) Mar 10 16:49:56 Tower2 kernel: ata15.00: failed to set xfermode (err_mask=0x11) (Minor Issues) Mar 10 16:49:56 Tower2 kernel: ata15.00: limiting speed to UDMA/133:PIO3 (Minor Issues) Mar 10 16:49:56 Tower2 kernel: sas: sas_form_port: phy4 belongs to port4 already(1)! (Drive related) Mar 10 16:49:58 Tower2 kernel: ata15: hard resetting link (Minor Issues) Mar 10 16:50:03 Tower2 kernel: ata15.00: qc timeout (cmd 0xec) (Drive related) Mar 10 16:50:03 Tower2 kernel: ata15.00: failed to IDENTIFY (I/O error, err_mask=0x5) (Errors) Mar 10 16:50:03 Tower2 kernel: ata15.00: revalidation failed (errno=-5) (Minor Issues) Mar 10 16:50:03 Tower2 kernel: ata15.00: disabled (Errors) Mar 10 16:50:03 Tower2 kernel: ata15.00: device reported invalid CHS sector 0 (Drive related) Mar 10 16:50:03 Tower2 last message repeated 2 times Mar 10 16:50:03 Tower2 kernel: ata15: hard resetting link (Minor Issues) Mar 10 16:50:06 Tower2 kernel: mvsas 0000:01:00.0: Phy4 : No sig fis (Drive related) Mar 10 16:50:06 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 1521:mvs_I_T_nexus_reset for device[4]:rc= 0 (System) Mar 10 16:50:06 Tower2 kernel: ata15: EH complete (Drive related) Mar 10 16:50:06 Tower2 kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 (Drive related) Mar 10 16:50:06 Tower2 kernel: sd 11:0:4:0: [sdr] Unhandled error code (Errors) Mar 10 16:50:06 Tower2 kernel: sd 11:0:4:0: [sdr] Result: hostbyte=0x04 driverbyte=0x00 (System) Mar 10 16:50:06 Tower2 kernel: sd 11:0:4:0: [sdr] CDB: cdb[0]=0x28: 28 00 04 a8 ba 90 00 02 00 00 (Drive related) Mar 10 16:50:06 Tower2 kernel: end_request: I/O error, dev sdr, sector 78166672 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166608/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: sd 11:0:4:0: [sdr] Unhandled error code (Errors) Mar 10 16:50:06 Tower2 kernel: sd 11:0:4:0: [sdr] md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166616/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: Result: hostbyte=0x04 driverbyte=0x00 (System) Mar 10 16:50:06 Tower2 kernel: sd 11:0:4:0: [sdr] CDB: cdb[0]=0x28: 28 00 04 a8 b6 90 00 02 00 00 (Drive related) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: end_request: I/O error, dev sdr, sector 78165648 (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166624/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166632/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166640/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166648/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: sd 11:0:4:0: [sdr] Unhandled error code (Errors) Mar 10 16:50:06 Tower2 kernel: sd 11:0:4:0: [sdr] Result: hostbyte=0x04 driverbyte=0x00 (System) Mar 10 16:50:06 Tower2 kernel: sd 11:0:4:0: [sdr] CDB: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166656/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: cdb[0]=0x28: 28 00 04 a8 b8 90 00 02 00 00 Mar 10 16:50:06 Tower2 kernel: end_request: I/O error, dev sdr, sector 78166160 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166664/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166672/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166680/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166688/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166696/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166704/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: sd 11:0:4:0: [sdr] READ CAPACITY(16) failed (Drive related) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166712/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: sd 11:0:4:0: [sdr] Result: hostbyte=0x04 driverbyte=0x00 (System) Mar 10 16:50:06 Tower2 kernel: sd 11:0:4:0: [sdr] Sense not available. (Drive related) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166720/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166728/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: sd 11:0:4:0: [sdr] READ CAPACITY failed (Drive related) Mar 10 16:50:06 Tower2 kernel: sd 11:0:4:0: [sdr] Result: hostbyte=0x04 driverbyte=0x00 (System) Mar 10 16:50:06 Tower2 kernel: sd 11:0:4:0: [sdr] Sense not available. (Drive related) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166736/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166744/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166752/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: sd 11:0:4:0: [sdr] Truncating mode parameter data from 8226 to 512 bytes (Drive related) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166760/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: sd 11:0:4:0: [sdr] Got wrong page (Drive related) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166768/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: sd 11:0:4:0: [sdr] Assuming drive cache: write through (Drive related) Mar 10 16:50:06 Tower2 kernel: sdr: detected capacity change from 3000592982016 to 0 (Drive related) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166776/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166784/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166792/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166800/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166808/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166816/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166824/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166832/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166840/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166848/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166856/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166864/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166872/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166880/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166888/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166896/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166904/9, count: 1 (Errors) Mar 10 16:50:06 Tower2 kernel: md: disk9 read error (Errors) Mar 10 16:50:06 Tower2 kernel: handle_stripe read error: 78166912/9, count: 1 (Errors)
March 11, 201313 yr Author I found the old syslog which I'd saved as well: Mar 5 22:02:33 Tower2 kernel: sd 1:0:4:0: [sdr] command f276e840 timed out Mar 5 22:02:33 Tower2 kernel: sd 1:0:4:0: [sdr] command f276e000 timed out Mar 5 22:02:39 Tower2 kernel: sd 1:0:4:0: [sdr] command f76d2480 timed out Mar 5 22:02:39 Tower2 kernel: sas: Enter sas_scsi_recover_host busy: 3 failed: 3 Mar 5 22:02:39 Tower2 kernel: sas: trying to find task 0xc4b1a140 Mar 5 22:02:39 Tower2 kernel: sas: sas_scsi_find_task: aborting task 0xc4b1a140 Mar 5 22:02:39 Tower2 kernel: sas: sas_scsi_find_task: task 0xc4b1a140 is aborted Mar 5 22:02:39 Tower2 kernel: sas: sas_eh_handle_sas_errors: task 0xc4b1a140 is aborted Mar 5 22:02:39 Tower2 kernel: sas: ata15: end_device-1:4: cmd error handler Mar 5 22:02:39 Tower2 kernel: sas: ata11: end_device-1:0: dev error handler Mar 5 22:02:39 Tower2 kernel: sas: ata12: end_device-1:1: dev error handler Mar 5 22:02:39 Tower2 kernel: sas: ata13: end_device-1:2: dev error handler Mar 5 22:02:39 Tower2 kernel: sas: ata14: end_device-1:3: dev error handler Mar 5 22:02:39 Tower2 kernel: sas: ata15: end_device-1:4: dev error handler Mar 5 22:02:39 Tower2 kernel: sas: ata16: end_device-1:5: dev error handler Mar 5 22:02:39 Tower2 kernel: sas: ata17: end_device-1:6: dev error handler Mar 5 22:02:39 Tower2 kernel: ata15.00: exception Emask 0x1 SAct 0x7 SErr 0x0 action 0x6 frozen Mar 5 22:02:39 Tower2 kernel: ata15.00: failed command: READ FPDMA QUEUED Mar 5 22:02:39 Tower2 kernel: sas: ata18: end_device-1:7: dev error handler Mar 5 22:02:39 Tower2 kernel: ata15.00: cmd 60/00:00:37:5b:d6/02:00:28:00:00/40 tag 0 ncq 262144 in Mar 5 22:02:39 Tower2 kernel: res 41/04:af:88:5a:d6/00:00:28:00:00/40 Emask 0x1 (device error) Mar 5 22:02:39 Tower2 kernel: ata15.00: status: { DRDY ERR } Mar 5 22:02:39 Tower2 kernel: ata15.00: error: { ABRT } Mar 5 22:02:39 Tower2 kernel: ata15.00: failed command: READ FPDMA QUEUED Mar 5 22:02:39 Tower2 kernel: ata15.00: cmd 60/00:00:37:59:d6/02:00:28:00:00/40 tag 1 ncq 262144 in Mar 5 22:02:39 Tower2 kernel: res 41/04:af:88:5a:d6/00:00:28:00:00/40 Emask 0x5 (timeout) Mar 5 22:02:39 Tower2 kernel: ata15.00: status: { DRDY ERR } Mar 5 22:02:39 Tower2 kernel: ata15.00: error: { ABRT } Mar 5 22:02:39 Tower2 kernel: ata15.00: failed command: READ FPDMA QUEUED Mar 5 22:02:39 Tower2 kernel: ata15.00: cmd 60/00:00:37:5d:d6/02:00:28:00:00/40 tag 2 ncq 262144 in Mar 5 22:02:39 Tower2 kernel: res 41/04:af:88:5a:d6/00:00:28:00:00/40 Emask 0x1 (device error) Mar 5 22:02:39 Tower2 kernel: ata15.00: status: { DRDY ERR } Mar 5 22:02:39 Tower2 kernel: ata15.00: error: { ABRT } Mar 5 22:02:39 Tower2 kernel: ata15: hard resetting link Mar 5 22:02:42 Tower2 kernel: mvsas 0000:01:00.0: Phy4 : No sig fis Mar 5 22:02:42 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 1521:mvs_I_T_nexus_reset for device[4]:rc= 0 Mar 5 22:02:45 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 1951:Release slot [0] tag[0], task [c4b1b900]: Mar 5 22:02:45 Tower2 kernel: sas: sas_ata_task_done: SAS error 8a Mar 5 22:02:45 Tower2 kernel: ata15.00: failed to IDENTIFY (I/O error, err_mask=0x11) Mar 5 22:02:45 Tower2 kernel: sas: sas_form_port: phy4 belongs to port4 already(1)! Mar 5 22:02:45 Tower2 kernel: ata15.00: revalidation failed (errno=-5) Mar 5 22:02:48 Tower2 kernel: ata15: hard resetting link Mar 5 22:02:53 Tower2 kernel: ata15.00: qc timeout (cmd 0xec) Mar 5 22:02:53 Tower2 kernel: ata15.00: failed to IDENTIFY (I/O error, err_mask=0x5) Mar 5 22:02:53 Tower2 kernel: ata15.00: revalidation failed (errno=-5) Mar 5 22:02:53 Tower2 kernel: ata15: hard resetting link Mar 5 22:02:56 Tower2 kernel: mvsas 0000:01:00.0: Phy4 : No sig fis Mar 5 22:02:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 1521:mvs_I_T_nexus_reset for device[4]:rc= 0 Mar 5 22:02:59 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 1951:Release slot [0] tag[0], task [c4b1b900]: Mar 5 22:02:59 Tower2 kernel: sas: sas_ata_task_done: SAS error 8a Mar 5 22:02:59 Tower2 kernel: ata15.00: failed to IDENTIFY (I/O error, err_mask=0x11) Mar 5 22:02:59 Tower2 kernel: ata15.00: revalidation failed (errno=-5) Mar 5 22:02:59 Tower2 kernel: ata15.00: disabled Mar 5 22:02:59 Tower2 kernel: ata15: EH complete Mar 5 22:02:59 Tower2 kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 Mar 5 22:02:59 Tower2 kernel: sd 1:0:4:0: [sdr] Unhandled error code Mar 5 22:02:59 Tower2 kernel: sd 1:0:4:0: [sdr] Result: hostbyte=0x04 driverbyte=0x00 Mar 5 22:02:59 Tower2 kernel: sd 1:0:4:0: [sdr] CDB: cdb[0]=0x28: 28 00 28 d6 5d 37 00 02 00 00 Mar 5 22:02:59 Tower2 kernel: end_request: I/O error, dev sdr, sector 685137207 Mar 5 22:02:59 Tower2 kernel: sd 1:0:4:0: [sdr] Unhandled error code Mar 5 22:02:59 Tower2 kernel: sd 1:0:4:0: [sdr] Result: hostbyte=0x04 driverbyte=0x00 Mar 5 22:02:59 Tower2 kernel: sd 1:0:4:0: [sdr] CDB: cdb[0]=0x28: 28 00 28 d6 59 37 00 02 00 00 Mar 5 22:02:59 Tower2 kernel: end_request: I/O error, dev sdr, sector 685136183 Mar 5 22:02:59 Tower2 kernel: sd 1:0:4:0: [sdr] Unhandled error code Mar 5 22:02:59 Tower2 kernel: sd 1:0:4:0: [sdr] Result: hostbyte=0x04 driverbyte=0x00 Mar 5 22:02:59 Tower2 kernel: sd 1:0:4:0: [sdr] CDB: cdb[0]=0x28: 28 00 28 d6 5b 37 00 02 00 00 Mar 5 22:02:59 Tower2 kernel: end_request: I/O error, dev sdr, sector 685136695 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137144/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137152/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137160/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137168/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137176/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137184/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137192/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137200/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137208/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137216/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137224/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137232/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137240/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137248/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137256/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137264/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137272/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137280/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137288/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137296/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137304/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137312/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137320/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137328/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137336/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137344/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error Mar 5 22:02:59 Tower2 kernel: handle_stripe read error: 685137352/9, count: 1 Mar 5 22:02:59 Tower2 kernel: md: disk9 read error
March 11, 201313 yr No evidence of a cable issue, appears to be a controller issue. You have identified how it begins, the same way in each case, and it ends about 50 or 60 lines further when the drive is disabled (Mar 5 22:02:59 Tower2 kernel: ata15.00: disabled) and (Mar 10 16:50:03 Tower2 kernel: ata15.00: disabled). All subsequent drive errors can be ignored. You can determine if the problem stays with the fifth port or stays with the drive, by swapping Disk 9 with another drive on the same card. Communications between the drive and the controller seem to just stop all of a sudden. That usually means there is nothing wrong with the drive, even though you see lots of errors. The errors come from the drive appearing to be removed. It is usually fine once you reboot, except that UnRAID will record that the drive was missing (marked with a red ball), and you have to deal with that. There were reports elsewhere that a firmware upgrade (P11 to P15?) seemed to take care of issues just like this. Perhaps you could research that, or perhaps someone more knowledgeable about it will respond.
March 11, 201313 yr Author Thanks. That was the kind of help I was hoping for. I am also pretty sure it's not a drive issue since the drive it happened to before was replaced. The part that gets me is that it's the same port. If it had happened to a different port I would be sure it was the controller card or cable. I have a backup of the superblock.dat from after the March 5th rebuild where it was once again stable. Since I am 95% certain the current disk9 drive is OK I could restore that and get back to a protected state asap. The other idea I had was to shutdown, move my cache drive to the disk9 slot, put a replacement spare in the old cache drive spot and rebuild. That way if the same port fails again it won't break parity. I will research the firmware issue. Currently it's on 3.1.0.15N which is what it shipped with. I still welcome any additional notes or analysis.
March 11, 201313 yr Author This seems to describe the problem I am having but they are in a windows environment. - http://hardforum.com/showthread.php?t=1584144 Here is a thread in this forum that seems to be the same issue - http://lime-technology.com/forum/index.php?topic=25779.msg225810 This thread suggests there is some strange underlying incompatibility between certain mobos and the Supermicro card. - http://lime-technology.com/forum/index.php?topic=26391.msg231144 (funny since my mobo is a Supermicro) Should I return this card for the SAS2LP? Maybe an IBM M1015?
March 12, 201313 yr I've had a similar issue with my array also with the AOC-SASLP-MV8 controller (running firmware 3.1.0.21). One day Disk9 of my array had a red ball. I tried to add it back to the array and rebuild. It failed and I ended up with a red ball again. I was getting handle stripe errors. I took the disk out of the array and tested it on a Windows box for bad sectors but it came up clean. I ended up RMAing the drive because I wasn't sure if the drive was bad or not. I placed a different brand new and tested good disk in the same slot that my previous "bad" disk was in. The array rebuilt fine. But sure enough, a few days later, the new good disk had a red ball. I've tried swapping the mini-sas cable for another one and everything seems to be fine now though I don't believe the cable is really the issue. From what I'm reading online, I'm suspecting this is a controller issue and not a cable issue. I actually just ordered a M1015 and flashed it to IT mode last night. I plan on swapping the cards this weekend. I hope this resolves my issues with dropouts.
March 12, 201313 yr Author Interesting! Definitely keep me posted, either via this thread or PM. I ordered a couple of new mini-sas to sata cables from Monoprice with the same intention. If that doesn't fix the issue I'm going to pull the trigger on the IBM controller as well. My plan seems to have work so far. I shutdown the array Upgraded to RC11 Swapped out my super.dat with one before the most recent failure Moved the cache to the disk 9 spot and the red balled, but good, drive to the cache drive slot Powered up and started a parity check - it found about 1100 changes which makes some sense and since the data on the disk9 and the rest of the array is "known good" correcting parity should be the way to go. Data seems intact and the array is stable for now. Not sure if I am going to go ahead and do the cable swap once they are here or wait to see if I have problems again.
March 12, 201313 yr Another thing to note is that I never had an issue with dropouts before I upgraded a bunch of hardware in my server. I previously had a Supermicro X7SLA-H (dual core atom) motherboard along with the AOC-SASLP-MV8. I recently swapped to a Supermicro X9SCM-iiF (with E3-1230v2) motherboard and also added 3x Supermicro CSE-M35T-1B drive cages. I removed a few of the older and slower drives from my array. I also upgraded from unRAID 4.7 to unRAID 5rc11. In addition I upgraded the firmware of my controller from 3.1.0.15 to 3.1.021 with the understanding that this newer firmware supported 3TB+ drives (I seemed to gather now that 3.1.0.15 seems to also work with 3TB+ drives). With the older motherboard (X7SLA-H) I only would get 30-50MB/sec parity checks. With the new motherboard (all 2TB and 3TB drives now) I get 80-100MB/sec parity checks. Another thread mentioned getting dropouts with a high load on the controller. Perhaps this is what is happening to me.
March 13, 201313 yr I have the SAS2LP X 2. Disk 9 was reballing on parity checks. I smart checked the hdds and found nothing. This redballing occurred on rc6 rc8 but I dare not try rc11! Therefore I am on rc5 which is running perfectly. Parity checks on RC5 are about 90MB/s and the other two RC are about 50MB/s. Something is definitely wrong somewhere! http://lime-technology.com/forum/index.php?topic=22789.0
March 13, 201313 yr Author I'd like to have RC5 as a fallback. Anyone know where I can get a copy? I've dug through the forums but can't find any links.
March 13, 201313 yr Author Thanks for the link. I setup a dual boot with it on my flash drive. The next time I have to reboot or have issues I think I will give RC5 a shot. I'm also very interested to see if my parity check and rebuild speeds go up, like so many have reported. Currently, I am stable. Last night I copied a bunch of stuff to the array, via the cache drive, and the mover ran without issue later that evening.
March 13, 201313 yr I had my parity drive redballed a couple a days ago. It was attached to my Supermicro AOC-SASLP-MV8(Firmware 3.1.021) card. It happened when I tried to get the smart report. I powered down and made sure the parity drive is on the motherboard sata instead. I rebuild the parity and made a parity check and right now everything seems ok. Mar 9 19:34:14 Tower kernel: sd 0:0:1:0: command f364d300 timed out Mar 9 19:34:14 Tower kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Mar 9 19:34:14 Tower kernel: sas: trying to find task 0xd0b4b900 Mar 9 19:34:14 Tower kernel: sas: sas_scsi_find_task: aborting task 0xd0b4b900 Mar 9 19:34:14 Tower kernel: sas: sas_scsi_find_task: task 0xd0b4b900 is aborted Mar 9 19:34:14 Tower kernel: sas: sas_eh_handle_sas_errors: task 0xd0b4b900 is aborted Mar 9 19:34:14 Tower kernel: sas: ata10: end_device-0:1: cmd error handler Mar 9 19:34:14 Tower kernel: sas: ata9: end_device-0:0: dev error handler Mar 9 19:34:14 Tower kernel: sas: ata10: end_device-0:1: dev error handler Mar 9 19:34:14 Tower kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Mar 9 19:34:14 Tower kernel: ata10.00: failed command: SMART Mar 9 19:34:14 Tower kernel: ata10.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Mar 9 19:34:14 Tower kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Mar 9 19:34:14 Tower kernel: sas: ata11: end_device-0:2: dev error handler Mar 9 19:34:14 Tower kernel: ata10.00: status: { DRDY } Mar 9 19:34:14 Tower kernel: sas: ata12: end_device-0:3: dev error handler Mar 9 19:34:14 Tower kernel: ata10: hard resetting link Mar 9 19:34:15 Tower kernel: sas: sas_form_port: phy1 belongs to port1 already(1)! Mar 9 19:34:15 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1521:mvs_I_T_nexus_reset for device[1]:rc= 0 Mar 9 19:34:21 Tower kernel: ata10.00: qc timeout (cmd 0x27) Mar 9 19:34:21 Tower kernel: ata10.00: failed to read native max address (err_mask=0x4) Mar 9 19:34:21 Tower kernel: ata10.00: HPA support seems broken, skipping HPA handling Mar 9 19:34:21 Tower kernel: ata10.00: revalidation failed (errno=-5) Mar 9 19:34:21 Tower kernel: ata10: hard resetting link Mar 9 19:34:23 Tower kernel: mvsas 0000:0a:00.0: Phy1 : No sig fis Mar 9 19:34:23 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1521:mvs_I_T_nexus_reset for device[1]:rc= 0 Mar 9 19:34:27 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1951:Release slot [0] tag[0], task [d0b4b900]: Mar 9 19:34:27 Tower kernel: sas: sas_ata_task_done: SAS error 8a Mar 9 19:34:27 Tower kernel: ata10.00: failed to set xfermode (err_mask=0x11) Mar 9 19:34:27 Tower kernel: ata10.00: limiting speed to UDMA/133:PIO3 Mar 9 19:34:27 Tower kernel: sas: sas_form_port: phy1 belongs to port1 already(1)! Mar 9 19:34:29 Tower kernel: ata10: hard resetting link Mar 9 19:34:35 Tower kernel: ata10.00: qc timeout (cmd 0xec) Mar 9 19:34:35 Tower kernel: ata10.00: failed to IDENTIFY (I/O error, err_mask=0x5) Mar 9 19:34:35 Tower kernel: ata10.00: revalidation failed (errno=-5) Mar 9 19:34:35 Tower kernel: ata10.00: disabled Mar 9 19:34:35 Tower kernel: ata10: hard resetting link Mar 9 19:34:37 Tower kernel: mvsas 0000:0a:00.0: Phy1 : No sig fis Mar 9 19:34:37 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1521:mvs_I_T_nexus_reset for device[1]:rc= 0 Mar 9 19:34:37 Tower kernel: ata10: EH complete Mar 9 19:34:37 Tower kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 Mar 9 19:34:37 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 9 19:34:37 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 9 19:34:37 Tower kernel: sd 0:0:1:0: [sdk] READ CAPACITY(16) failed Mar 9 19:34:37 Tower kernel: sd 0:0:1:0: [sdk] Result: hostbyte=0x04 driverbyte=0x00 Mar 9 19:34:37 Tower kernel: sd 0:0:1:0: [sdk] Sense not available. Mar 9 19:34:37 Tower kernel: sd 0:0:1:0: [sdk] READ CAPACITY failed Mar 9 19:34:37 Tower kernel: sd 0:0:1:0: [sdk] Result: hostbyte=0x04 driverbyte=0x00 Mar 9 19:34:37 Tower kernel: sd 0:0:1:0: [sdk] Sense not available. Mar 9 19:34:37 Tower kernel: sd 0:0:1:0: [sdk] Asking for cache data failed Mar 9 19:34:37 Tower kernel: sd 0:0:1:0: [sdk] Assuming drive cache: write through Mar 9 19:34:37 Tower kernel: sdk: detected capacity change from 4000787030016 to 0 Mar 9 19:34:41 Tower kernel: sas: sas_form_port: phy1 belongs to port1 already(1)! Mar 9 19:34:59 Tower unmenu[12425]: which: no bwm-ng in (/usr/local/sbin:/usr/sbin:/sbin:./:/usr/local/bin:/usr/bin:/bin:/usr/lib/java/bin:/usr/kerberos/bin:/usr/kerberos/sbin) Mar 9 19:35:16 Tower unmenu[12425]: HDIO_DRIVE_CMD(identify) failed: Input/output error Mar 9 19:35:36 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 9 19:36:10 Tower last message repeated 12 times Mar 9 19:36:12 Tower last message repeated 7 times Mar 9 19:36:21 Tower kernel: mdcmd (322): spinup 0 Mar 9 19:36:21 Tower kernel: Mar 9 19:36:21 Tower kernel: md: disk0: ATA_OP e3 ioctl error: -5 Mar 9 19:36:26 Tower kernel: mdcmd (323): spinup 0 Mar 9 19:36:26 Tower kernel: Mar 9 19:36:26 Tower kernel: md: disk0: ATA_OP e3 ioctl error: -5 Mar 9 19:36:34 Tower kernel: mdcmd (324): spinup 0 Mar 9 19:36:34 Tower kernel: Mar 9 19:36:34 Tower kernel: md: disk0: ATA_OP e3 ioctl error: -5 Mar 9 19:42:24 Tower kernel: mdcmd (325): spinup 0 Mar 9 19:42:24 Tower kernel: Mar 9 19:42:24 Tower kernel: md: disk0: ATA_OP e3 ioctl error: -5 Mar 9 19:42:32 Tower kernel: mdcmd (326): spinup 1 Mar 9 19:42:32 Tower kernel: Mar 9 19:42:53 Tower kernel: mdcmd (327): spinup 0 Mar 9 19:42:53 Tower kernel: Mar 9 19:42:53 Tower kernel: md: disk0: ATA_OP e3 ioctl error: -5 Mar 9 20:42:33 Tower kernel: mdcmd (328): spindown 1 Mar 9 20:42:54 Tower emhttp: mdcmd: write: Input/output error Mar 9 20:42:54 Tower kernel: mdcmd (329): spindown 0 Mar 9 20:42:54 Tower kernel: md: disk0: ATA_OP e0 ioctl error: -5 Mar 9 20:47:55 Tower kernel: mdcmd (330): spindown 3 Mar 9 20:59:16 Tower cache_dirs: ============================================== Mar 9 20:59:16 Tower cache_dirs: command-args=process ID 22772 started, To terminate it, type: cache_dirs -q Mar 9 20:59:16 Tower cache_dirs: vfs_cache_pressure=10 Mar 9 20:59:16 Tower cache_dirs: max_seconds=10, min_seconds=1 Mar 9 20:59:16 Tower cache_dirs: max_depth=9999 Mar 9 20:59:16 Tower cache_dirs: command=find -noleaf Mar 9 20:59:16 Tower cache_dirs: version=1.6.7 Mar 9 20:59:16 Tower cache_dirs: ---------- caching directories --------------- Mar 9 20:59:16 Tower cache_dirs: Anime Mar 9 20:59:16 Tower cache_dirs: Audiobooks Mar 9 20:59:16 Tower cache_dirs: Backup Mar 9 20:59:16 Tower cache_dirs: Movies Mar 9 20:59:16 Tower cache_dirs: Music Mar 9 20:59:16 Tower cache_dirs: Pictures Mar 9 20:59:16 Tower cache_dirs: TV Series Mar 9 20:59:16 Tower cache_dirs: Videos Mar 9 20:59:16 Tower cache_dirs: ---------------------------------------------- Mar 9 20:59:16 Tower cache_dirs: cache_dirs process ID 21369 started, To terminate it, type: cache_dirs -q Mar 9 21:57:03 Tower kernel: md: disk0 read error Mar 9 21:57:03 Tower kernel: handle_stripe read error: 44376/0, count: 1 Mar 9 21:57:03 Tower kernel: md: disk0 read error Mar 9 21:57:03 Tower kernel: handle_stripe read error: 44384/0, count: 1 Mar 9 21:57:03 Tower kernel: md: disk0 read error Mar 9 21:57:03 Tower kernel: handle_stripe read error: 44392/0, count: 1 Mar 9 21:57:03 Tower kernel: md: disk0 read error Mar 9 21:57:03 Tower kernel: handle_stripe read error: 44400/0, count: 1 Mar 9 21:57:03 Tower kernel: md: disk0 read error Mar 9 21:57:03 Tower kernel: handle_stripe read error: 44408/0, count: 1 Mar 9 21:57:03 Tower kernel: md: disk0 read error Mar 9 21:57:03 Tower kernel: handle_stripe read error: 44416/0, count: 1 Mar 9 21:57:03 Tower kernel: md: disk0 read error Mar 9 21:57:03 Tower kernel: handle_stripe read error: 44424/0, count: 1 Mar 9 21:57:03 Tower kernel: md: disk0 read error Mar 9 21:57:03 Tower kernel: handle_stripe read error: 44432/0, count: 1 Mar 9 21:57:03 Tower kernel: md: disk0 read error Mar 9 21:57:03 Tower kernel: handle_stripe read error: 44440/0, count: 1 Mar 9 21:57:17 Tower kernel: md: disk0 read error Mar 9 21:57:17 Tower kernel: handle_stripe read error: 2452635656/0, count: 1 Mar 9 21:57:17 Tower kernel: md: disk0 read error Mar 9 21:57:17 Tower kernel: handle_stripe read error: 2452635664/0, count: 1 Mar 9 21:57:17 Tower kernel: md: disk0 read error Mar 9 21:57:17 Tower kernel: handle_stripe read error: 2452635672/0, count: 1 Mar 9 21:57:17 Tower kernel: md: disk0 read error Mar 9 21:57:17 Tower kernel: handle_stripe read error: 2452635680/0, count: 1 Mar 9 21:57:17 Tower kernel: md: disk0 read error Mar 9 21:57:17 Tower kernel: handle_stripe read error: 2452635688/0, count: 1 Mar 9 21:57:17 Tower kernel: md: disk0 read error Syslog attached. [EDIT] I'm using unRAID 5 rc11. syslog-2013-03-10.zip
March 13, 201313 yr I noticed that if i try to get a smart report whilst the hdd is spun down then that drive will red ball.
March 13, 201313 yr I noticed that if i try to get a smart report whilst the hdd is spun down then that drive will red ball. I just tried that and I didn't get any redball.
March 13, 201313 yr Author I noticed that if i try to get a smart report whilst the hdd is spun down then that drive will red ball. I just tried that and I didn't get any redball. Yeah, me neither, I run smart reports on a schedule, daily, at night, and never had a drive redball like that. Both times mine dropped, I was streaming video.
Archived
This topic is now archived and is closed to further replies.