NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Chris_S's avatar
Chris_S
Aspirant
Mar 29, 2012

Dead Disk.. but not really

Does anybody have the same problem? So far this has happened twice to me:

brand new Ultra6. I get the message that Disk1 (also brand new, no SMART errors etc) is dead (out of 4 disks with dual redundancy Xraid2). I put in a replacement disk, nothing happens. No re-synching, on the webinterface, Disk1 still shows up as dead. I put back the original disk1 and reboot, everything is fine again. This has happened twice. My question: apart from why does a good disk show up as dead when it isn't, isn't the unit supposed to integrate the new (replacement) disk on the fly?

I am wondering if something is wrong the my chassis. Because:

about a week after I bought the unit and after running it on 3 disks, I put in a 4th one and then it crashed while re-synching. The unit would then not go properly into tech-support mode, only after several OS-reinstalls (basically, when in tech support mode it picked up an IP address outside my network!?). Netgear tech support eventually managed to get some of my data back (they too could not figure out what had happened in the first palce and/or why my unit would not go into tech support mode), but that took several weeks. In the meantime I tried to return the unit but the shop would not take it back because it's past the 2 week return period..

Thanks a lot!

22 Replies

Replies have been turned off for this discussion
  • Looks like i have the same problem.

    I have a ReadyNAS Ultra 6 with 6 Seagate ST2000DL003 9VT166 2TB drives. This morning, after several months of no problems, my disk 1 is reported as "dead". I replace it with a brand new drive (same Seagate model), but the new drive is still not detected and the NAS continues to report disk 1 as "dead". Tried pulling it out and re-seating it, but nothing changes. I have not tried replacing the previous "dead" drive yet, but will try that now.

    The log files don't show any problems with disk 1.
  • evan2's avatar
    evan2
    NETGEAR Expert
    You had batter not use ST2000DL003, Seagate drive has "FLUSH CACHE EXT" hang problem, the symptom would be exactly same as described:
    Entire disk(all partitions) not responding, only power cycle can bring it back.
    Seagate recently admitted this issue, they have a test firmware to address this hang issue.
    Please check kernel.log and find if it has "FLUSH CACHE EXT", please see below information,

    Apr 15 16:36:59 Orac kernel: TCP: Possible SYN flooding on port 36130. Sending cookies.
    Apr 17 00:52:35 Orac kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    Apr 17 00:53:36 Orac kernel: ata2.00: failed command: FLUSH CACHE EXT
    Apr 17 00:53:36 Orac kernel: ata2.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
    Apr 17 00:53:36 Orac kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    Apr 17 00:53:36 Orac kernel: ata2.00: status: { DRDY }
    Apr 17 00:53:36 Orac kernel: ata2: hard resetting link
    Apr 17 00:53:36 Orac kernel: ata2: link is slow to respond, please be patient (ready=0)
    Apr 17 00:53:36 Orac kernel: ata2: COMRESET failed (errno=-16)
    Apr 17 00:53:36 Orac kernel: ata2: hard resetting link
    Apr 17 00:53:36 Orac kernel: ata2: link is slow to respond, please be patient (ready=0)
    Apr 17 00:53:36 Orac kernel: ata2: COMRESET failed (errno=-16)
    Apr 17 00:53:36 Orac kernel: ata2: hard resetting link
    Apr 17 00:53:36 Orac kernel: ata2: link is slow to respond, please be patient (ready=0)
    Apr 17 00:53:36 Orac kernel: ata2: COMRESET failed (errno=-16)
    Apr 17 00:53:36 Orac kernel: ata2: limiting SATA link speed to 1.5 Gbps
    Apr 17 00:53:36 Orac kernel: ata2: hard resetting link
    Apr 17 00:53:36 Orac kernel: ata2: COMRESET failed (errno=-16)
    Apr 17 00:53:36 Orac kernel: ata2: reset failed, giving up
    Apr 17 00:53:36 Orac kernel: ata2.00: disabled
    Apr 17 00:53:36 Orac kernel: ata2.00: device reported invalid CHS sector 0
    Apr 17 00:53:36 Orac kernel: ata2: EH complete
    Apr 17 00:53:36 Orac kernel: sd 1:0:0:0: [sdb] Unhandled error code
    Apr 17 00:53:36 Orac kernel: sd 1:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
    Apr 17 00:53:36 Orac kernel: sd 1:0:0:0: [sdb] CDB: Read(10): 28 00 00 30 c2 e0 00 00 08 00
    Apr 17 00:53:36 Orac kernel: end_request: I/O error, dev sdb, sector 3195616
    Apr 17 00:53:36 Orac kernel: md/raid1:md0: sdb1: rescheduling sector 3195528
    Apr 17 00:53:36 Orac kernel: sd 1:0:0:0: [sdb] Unhandled error code
    Apr 17 00:53:36 Orac kernel: sd 1:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
    Apr 17 00:53:36 Orac kernel: sd 1:0:0:0: [sdb] CDB: Read(10): 28 00 00 32 42 50 00 00 08 00
    Apr 17 00:53:36 Orac kernel: end_request: I/O error, dev sdb, sector 3293776
    Apr 17 00:53:36 Orac kernel: md/raid1:md0: sdb1: rescheduling sector 3293688

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More