September 13, 201213 yr This morning I woke up and my media server had crashed. I rebooted it to find one of the drives red balled. I replaced it with a new precleared drive and rebuilt parity without problems. I plugged the old drive back in and checked its smart report, everything seems fine. Seconds later I noticed I could no longer access the drive and noticed the below errors in my syslog: Sep 12 20:08:23 Tower ntpd[3409]: synchronized to 192.75.12.10, stratum 2 Sep 12 20:27:49 Tower kernel: ata7: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen (Errors) Sep 12 20:27:49 Tower kernel: ata7: edma_err_cause=00000020 pp_flags=00000000, SError=00180000 (Errors) Sep 12 20:27:49 Tower kernel: ata7: SError: { 10B8B Dispar } (Errors) Sep 12 20:27:49 Tower kernel: ata7: hard resetting link (Minor Issues) Sep 12 20:27:49 Tower kernel: ata7: SATA link down (SStatus 0 SControl 300) (Drive related) Sep 12 20:27:54 Tower kernel: ata7: hard resetting link (Minor Issues) Sep 12 20:27:55 Tower kernel: ata7: SATA link down (SStatus 0 SControl 300) (Drive related) Sep 12 20:27:55 Tower kernel: ata7: limiting SATA link speed to 1.5 Gbps (Drive related) Sep 12 20:28:00 Tower kernel: ata7: hard resetting link (Minor Issues) Sep 12 20:28:00 Tower kernel: ata7: SATA link down (SStatus 0 SControl 310) (Drive related) Sep 12 20:28:00 Tower kernel: ata7.00: disabled (Errors) Sep 12 20:28:00 Tower kernel: ata7: EH complete (Drive related) Sep 12 20:28:00 Tower kernel: ata7.00: detaching (SCSI 6:0:0:0) (Drive related) Sep 12 20:28:00 Tower kernel: sd 6:0:0:0: [sda] Synchronizing SCSI cache (Drive related) Sep 12 20:28:00 Tower kernel: sd 6:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00 (System) Sep 12 20:28:00 Tower kernel: sd 6:0:0:0: [sda] Stopping disk (Drive related) Sep 12 20:28:00 Tower kernel: sd 6:0:0:0: [sda] START_STOP FAILED (Drive related) Sep 12 20:28:00 Tower kernel: sd 6:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00 (System) Sep 12 20:28:00 Tower unmenu[1635]: /dev/sda: No such file or directory (Drive related) Sep 12 20:28:11 Tower unmenu[1635]: sh: line 0: cd: /boot/smarthistory: No such file or directory Sep 12 20:28:11 Tower unmenu[1635]: sh: ./smarthistory: No such file or directory Sep 12 20:29:03 Tower kernel: NTFS driver 2.1.29 [Flags: R/O MODULE]. (System) I can now no longer access the drive at all. Anyone have ideas? I also noticed my automated status emails had not been sending out for the past 10 days or so. (Could be randomly related)
September 13, 201213 yr Or, re-seat BOTH the power and SATA cables (both ends of both cables) Although the disk itself could have failed, it could just as likely be a loose cable.
September 13, 201213 yr Author I should have mentioned in the original post that the new drive went into the same slot as the old one and works fine (same sata and power cable) the old drive has been tested in 2 completely different slots with no luck. Ive never had a drive just fail like this where it won't do anything, unraid doesnt see it at all. New experience for me
September 13, 201213 yr I should have mentioned in the original post that the new drive went into the same slot as the old one and works fine (same sata and power cable) the old drive has been tested in 2 completely different slots with no luck. Ive never had a drive just fail like this where it won't do anything, unraid doesnt see it at all. New experience for me Sounds like the old drive just died... Remember... There are only two kinds of hard disks... Those that have already failed... Those that have not yet failed..... but will... they just need a bit more time. Joe L.
Archived
This topic is now archived and is closed to further replies.