NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
bluewomble
Mar 13, 2011Aspirant
Disk Failure Detected...
I've recently purchased a ReadyNAS Ultra 6 along with 6 2 Tb Seagate ST2000DL003 disks (which are on the HCL). I've set up the NAS in a dual redundancy X-RAID2 configuration and have starting copyi...
raykj
Dec 15, 2011Aspirant
Had a drive "failure" last night and contacted Netgear for RMA of hard drive (before noticing this thread). This is a RNDU2220 unit which came preloaded with two of the Seagate 2G ST2000DL003 drives. I'm now guessing that replacing the drive will not really correct the problem.
Interestingy, the failure occurred when nothing was really happening (the unit should have been idling). It dropped the erroring drive out of the RAID.
The drive sent me an email at 6:25 in the morning. Interestingly, the kernel log shows some issue at 23:36 pm the night before:
The unit has been running fine for weeks with non-intensive use. Have a few shares, copied lots-o-data and an iSCSI connection (which, I'm guessing had a little background activity from Win2008 R2 access).
Interestingy, the failure occurred when nothing was really happening (the unit should have been idling). It dropped the erroring drive out of the RAID.
The drive sent me an email at 6:25 in the morning. Interestingly, the kernel log shows some issue at 23:36 pm the night before:
Dec 14 23:36:46 nas-u2 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Dec 14 23:36:46 nas-u2 kernel: ata1.00: failed command: CHECK POWER MODE
Dec 14 23:36:46 nas-u2 kernel: ata1.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0
Dec 14 23:36:46 nas-u2 kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
Dec 14 23:36:46 nas-u2 kernel: ata1.00: status: { DRDY }
Dec 14 23:36:46 nas-u2 kernel: ata1: hard resetting link
Dec 14 23:36:46 nas-u2 kernel: ata1: link is slow to respond, please be patient (ready=0)
Dec 14 23:36:46 nas-u2 kernel: ata1: COMRESET failed (errno=-16)
Dec 14 23:36:46 nas-u2 kernel: ata1: hard resetting link
Dec 14 23:36:46 nas-u2 kernel: ata1: link is slow to respond, please be patient (ready=0)
Dec 14 23:36:46 nas-u2 kernel: ata1: COMRESET failed (errno=-16)
Dec 14 23:36:46 nas-u2 kernel: ata1: hard resetting link
Dec 14 23:36:46 nas-u2 kernel: ata1: link is slow to respond, please be patient (ready=0)
Dec 14 23:36:46 nas-u2 kernel: ata1: COMRESET failed (errno=-16)
Dec 14 23:36:46 nas-u2 kernel: ata1: limiting SATA link speed to 1.5 Gbps
Dec 14 23:36:46 nas-u2 kernel: ata1: hard resetting link
Dec 14 23:36:46 nas-u2 kernel: ata1: COMRESET failed (errno=-16)
Dec 14 23:36:46 nas-u2 kernel: ata1: reset failed, giving up
Dec 14 23:36:46 nas-u2 kernel: ata1.00: disabled
Dec 14 23:36:46 nas-u2 kernel: ata1: EH complete
Dec 14 23:36:46 nas-u2 kernel: sd 0:0:0:0: [sda] Unhandled error code
Dec 14 23:36:46 nas-u2 kernel: sd 0:0:0:0: [sda] Unhandled error code
Dec 14 23:36:46 nas-u2 kernel: sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec 14 23:36:46 nas-u2 kernel: sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec 14 23:36:46 nas-u2 kernel: sd 0:0:0:0: [sda] CDB:
Dec 14 23:36:46 nas-u2 kernel: sd 0:0:0:0: [sda] CDB: Read(10): 28Write(10): 2a 00 00 00 00 48 00 00 02 00
Dec 14 23:36:46 nas-u2 kernel: end_request: I/O error, dev sda, sector 72
Dec 14 23:36:46 nas-u2 kernel: 00 00 6d d5 f0 00 00 30 00
Dec 14 23:36:46 nas-u2 kernel: end_request: I/O error, dev sda, sector 7198192
Dec 14 23:36:46 nas-u2 kernel: md/raid1:md0: sda1: rescheduling sector 7196080
Dec 14 23:36:46 nas-u2 kernel: end_request: I/O error, dev sda, sector 72
Dec 14 23:36:46 nas-u2 kernel: md: super_written gets error=-5, uptodate=0
Dec 14 23:36:46 nas-u2 kernel: md/raid1:md0: Disk failure on sda1, disabling device.
Dec 14 23:36:46 nas-u2 kernel: <1>md/raid1:md0: Operation continuing on 1 devices.
Dec 14 23:36:46 nas-u2 kernel: RAID1 conf printout:
Dec 14 23:36:46 nas-u2 kernel: --- wd:1 rd:2
Dec 14 23:36:46 nas-u2 kernel: disk 0, wo:1, o:0, dev:sda1
Dec 14 23:36:46 nas-u2 kernel: disk 1, wo:0, o:1, dev:sdb1
Dec 14 23:36:46 nas-u2 kernel: RAID1 conf printout:
Dec 14 23:36:46 nas-u2 kernel: --- wd:1 rd:2
Dec 14 23:36:46 nas-u2 kernel: disk 1, wo:0, o:1, dev:sdb1
Dec 14 23:36:46 nas-u2 kernel: md/raid1:md0: redirecting sector 7196080 to other mirror: sdb1
Dec 15 04:00:01 nas-u2 kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Dec 15 06:25:01 nas-u2 kernel: sd 0:0:0:0: [sda] Unhandled error code
Dec 15 06:25:01 nas-u2 kernel: sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec 15 06:25:01 nas-u2 kernel: sd 0:0:0:0: [sda] CDB: Read(10): 28 00 00 90 08 40 00 00 08 00
Dec 15 06:25:01 nas-u2 kernel: end_request: I/O error, dev sda, sector 9439296
Dec 15 06:25:01 nas-u2 kernel: sd 0:0:0:0: [sda] Unhandled error code
Dec 15 06:25:01 nas-u2 kernel: sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec 15 06:25:01 nas-u2 kernel: sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 00 90 08 40 00 00 08 00
Dec 15 06:25:01 nas-u2 kernel: end_request: I/O error, dev sda, sector 9439296
Dec 15 06:25:01 nas-u2 kernel: md/raid:md2: Disk failure on sda3, disabling device.
Dec 15 06:25:01 nas-u2 kernel: <1>md/raid:md2: Operation continuing on 1 devices.
Dec 15 06:25:01 nas-u2 kernel: sd 0:0:0:0: [sda] Unhandled error code
Dec 15 06:25:01 nas-u2 kernel: sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec 15 06:25:01 nas-u2 kernel: sd 0:0:0:0: [sda] CDB: Read(10): 28 00 00 90 08 48 00 00 08 00
Dec 15 06:25:01 nas-u2 kernel: end_request: I/O error, dev sda, sector 9439304
Dec 15 06:25:01 nas-u2 kernel: RAID conf printout:
Dec 15 06:25:01 nas-u2 kernel: --- level:5 rd:2 wd:1
Dec 15 06:25:01 nas-u2 kernel: disk 0, o:0, dev:sda3
Dec 15 06:25:01 nas-u2 kernel: disk 1, o:1, dev:sdb3
Dec 15 06:25:01 nas-u2 kernel: RAID conf printout:
Dec 15 06:25:01 nas-u2 kernel: --- level:5 rd:2 wd:1
Dec 15 06:25:01 nas-u2 kernel: disk 1, o:1, dev:sdb3
The unit has been running fine for weeks with non-intensive use. Have a few shares, copied lots-o-data and an iSCSI connection (which, I'm guessing had a little background activity from Win2008 R2 access).
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!