Have a Netgear ReadyNas 212 with 2 x 3TB disks configured for RAID. The disk models are different (1 is a Seagate 3TB IronWolf and the other a 3TB Toshiba P300) but have worked together fine for over a year. A week ago the ReadyNas reported it had gone into non-redundant mode and the Seagate drive was shown as degraded. I unplugged and reseated the drive and the NAS did a re-sync which took about 5 hours. All worked fine for several days but the same thing has happened again except that now the Toshiba drive is shown as degraded. I initially thought the Seagate drive was failing but now the fault has switched to the other drive I assume something else may be causing the problem.
Any ideas or suggestions would be welcome.
Thanks
Model: RN212D23|ReadyNAS 212 Series 2- Bay (2x 3TB Desktop)
I can poke around in the logs for you. You can get them from System > Logs > Download Logs and that will download a zip file for you. You can upload that zip file to Google Drive, Dropbox or similar and PMme a link to grab them.
Also, please ensure you have an update-to-date backup at this point.
One drive may be the real culprit, but is affecting the whole SATA subsystem. Or, the hardware could be failing.
But, that's one 7200RPM drive and one 5900RPM? I had a similar problem with a legacy NAS and a mix of drive speeds, and it was related to how long it took the drives to spin up from idle. I'd check the logs to see if the problem arises at that point. Turning off drive idle spin-down could be a solution -- it was for me, though that was on a very different OS version.
Thanks for your suggestions. I've had the same disks and spin-down settings since August 2020 when I added the Seagate IronWolf after a previous disk failure. I must admit it didn't occur to me that it had a different RPM spec to the existing Toshiba drive but the configuration has been running fine since then until the recent problem. I will turn off spin down and see if I get any more issues and have shared the log files.
Unless something was unintentionally changed in a recent OS update, the fact that you've been running that configuration without error for that long points more to a hardware issue in a drive or the NAS itself. But the problem in a drive could be just affecting spin-up for now.
Thanks for the logs. Here are events that lead to to the two resyncs. First ("sda" at the time) the Seagate disk drops out.
[21/05/03 11:26:30 WEST] notice:volume:LOGMSG_HEALTH_VOLUME Volume data health changed from Redundant to Degraded.
[21/05/03 11:26:31 WEST] warning:disk:LOGMSG_DELETE_DISK Disk Model:ST3000VN007-2AH16M Serial:ZM413W96 was removed from Channel 1 of the head unit.
[21/05/03 19:47:47 WEST] notice:volume:LOGMSG_RESILVERCOMPLETE_VOLUME Volume data is resynced.
[21/05/03 19:47:47 WEST] notice:volume:LOGMSG_HEALTH_VOLUME Volume data health changed from Degraded to Redundant.
I kernel logs we can see it appears to be SATA connection errors.
May 03 11:26:29 ReadyNas1 kernel: ata1.00: status: { DRDY }
May 03 11:26:29 ReadyNas1 kernel: ata1: hard resetting link
May 03 11:26:29 ReadyNas1 kernel: ata1: link is slow to respond, please be patient (ready=0)
May 03 11:26:29 ReadyNas1 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 03 11:26:29 ReadyNas1 kernel: ata1.00: qc timeout (cmd 0xec)
May 03 11:26:29 ReadyNas1 kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
May 03 11:26:29 ReadyNas1 kernel: ata1.00: revalidation failed (errno=-5)
May 03 11:26:29 ReadyNas1 kernel: ata1: hard resetting link
May 03 11:26:29 ReadyNas1 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 03 11:26:29 ReadyNas1 kernel: ata1.00: qc timeout (cmd 0xec)
May 03 11:26:29 ReadyNas1 kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
May 03 11:26:29 ReadyNas1 kernel: ata1.00: revalidation failed (errno=-5)
May 03 11:26:29 ReadyNas1 kernel: ata1: limiting SATA link speed to 3.0 Gbps
May 03 11:26:29 ReadyNas1 kernel: ata1: hard resetting link
May 03 11:26:29 ReadyNas1 kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
May 03 11:26:29 ReadyNas1 kernel: ata1.00: qc timeout (cmd 0xec)
May 03 11:26:29 ReadyNas1 kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
May 03 11:26:29 ReadyNas1 kernel: ata1.00: revalidation failed (errno=-5)
May 03 11:26:29 ReadyNas1 kernel: ata1.00: disabled
May 03 11:26:29 ReadyNas1 kernel: ata1: hard resetting link
May 03 11:26:29 ReadyNas1 kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
May 03 11:26:29 ReadyNas1 kernel: ata1.00: qc timeout (cmd 0xec)
May 03 11:26:29 ReadyNas1 kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
May 03 11:26:29 ReadyNas1 kernel: ata1: hard resetting link
May 03 11:26:29 ReadyNas1 kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
May 03 11:26:29 ReadyNas1 kernel: ata1.00: qc timeout (cmd 0xec)
May 03 11:26:29 ReadyNas1 kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
May 03 11:26:29 ReadyNas1 kernel: ata1: limiting SATA link speed to 1.5 Gbps
May 03 11:26:29 ReadyNas1 kernel: ata1: hard resetting link
May 03 11:26:29 ReadyNas1 kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 03 11:26:29 ReadyNas1 kernel: ata1.00: qc timeout (cmd 0xec)
May 03 11:26:29 ReadyNas1 kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
May 03 11:26:29 ReadyNas1 kernel: ata1: hard resetting link
May 03 11:26:29 ReadyNas1 kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 03 11:26:29 ReadyNas1 kernel: sd 0:0:0:0: [sda] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
May 03 11:26:29 ReadyNas1 kernel: sd 0:0:0:0: [sda] tag#16 Sense Key : 0x5 [current] [descriptor]
May 03 11:26:29 ReadyNas1 kernel: sd 0:0:0:0: [sda] tag#16 ASC=0x21 ASCQ=0x4
May 03 11:26:29 ReadyNas1 kernel: sd 0:0:0:0: [sda] tag#16 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
May 03 11:26:29 ReadyNas1 kernel: blk_update_request: I/O error, dev sda, sector 72
May 03 11:26:29 ReadyNas1 kernel: md: super_written gets error=-5
May 03 11:26:29 ReadyNas1 kernel: md/raid1:md0: Disk failure on sda1, disabling device.
md/raid1:md0: Operation continuing on 1 devices.
May 03 11:26:29 ReadyNas1 kernel: sd 0:0:0:0: rejecting I/O to offline device
May 03 11:26:29 ReadyNas1 kernel: blk_update_request: I/O error, dev sda, sector 9437256
May 03 11:26:29 ReadyNas1 kernel: md: super_written gets error=-5
And the disk is dropped from the data-raid.
May 03 11:26:29 ReadyNas1 kernel: md/raid1:md127: Disk failure on sda3, disabling device.
md/raid1:md127: Operation continuing on 1 devices.
The following day, the Toshiba disk (also "sda" at the time) drops out. It even looks like it wasn't re-detected for some hours before it gets "added" back in.
[21/05/04 15:36:06 WEST] warning:disk:LOGMSG_DELETE_DISK Disk Model:TOSHIBA DT01ACA300 Serial:95QGT86GS was removed from Channel 1 of the head unit.
[21/05/04 15:36:15 WEST] warning:volume:LOGMSG_HEALTH_VOLUME Volume data health changed from Redundant to Degraded.
[21/05/04 22:48:15 WEST] notice:disk:LOGMSG_ADD_DISK Disk Model:TOSHIBA DT01ACA300 Serial:95QGT86GS was added to Channel 1 of the head unit.
[21/05/05 07:12:39 WEST] notice:volume:LOGMSG_RESILVERCOMPLETE_VOLUME Volume data is resynced.
[21/05/05 07:12:39 WEST] notice:volume:LOGMSG_HEALTH_VOLUME Volume data health changed from Degraded to Redundant.
Kernel logs against show SATA connection issues. This time we see ATA bus errors on both disks...
15:35:43 ReadyNas1 kernel: ata2.00: exception Emask 0x10 SAct 0x0 SErr 0x10200 action 0xe frozen
May 04 15:35:43 ReadyNas1 kernel: ata2.00: irq_stat 0x00400000, PHY RDY changed
May 04 15:35:43 ReadyNas1 kernel: ata2: SError: { Persist PHYRdyChg }
May 04 15:35:43 ReadyNas1 kernel: ata2.00: failed command: FLUSH CACHE EXT
May 04 15:35:43 ReadyNas1 kernel: ata2.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 15
res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA bus error)
May 04 15:35:43 ReadyNas1 kernel: ata2.00: status: { DRDY }
May 04 15:35:43 ReadyNas1 kernel: ata2: hard resetting link
May 04 15:35:47 ReadyNas1 kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x10300 action 0xe frozen
May 04 15:35:47 ReadyNas1 kernel: ata1.00: irq_stat 0x08400002, interface fatal error, PHY RDY changed
May 04 15:35:47 ReadyNas1 kernel: ata1: SError: { UnrecovData Persist PHYRdyChg }
May 04 15:35:47 ReadyNas1 kernel: ata1.00: failed command: FLUSH CACHE EXT
May 04 15:35:47 ReadyNas1 kernel: ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 18
res 50/00:01:48:00:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
May 04 15:35:47 ReadyNas1 kernel: ata1.00: status: { DRDY }
May 04 15:35:47 ReadyNas1 kernel: ata1: hard resetting link
May 04 15:35:48 ReadyNas1 kernel: ata2: link is slow to respond, please be patient (ready=0)
May 04 15:36:06 ReadyNas1 kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 04 15:36:06 ReadyNas1 kernel: ata2.00: configured for UDMA/133
May 04 15:36:06 ReadyNas1 kernel: ata2.00: retrying FLUSH 0xea Emask 0x10
May 04 15:36:06 ReadyNas1 kernel: ata2.00: device reported invalid CHS sector 0
May 04 15:36:06 ReadyNas1 kernel: ata2: EH complete
May 04 15:36:06 ReadyNas1 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 04 15:36:06 ReadyNas1 kernel: ata1.00: both IDENTIFYs aborted, assuming NODEV
May 04 15:36:06 ReadyNas1 kernel: ata1.00: revalidation failed (errno=-2)
May 04 15:36:06 ReadyNas1 kernel: ata1: hard resetting link
May 04 15:36:06 ReadyNas1 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 04 15:36:06 ReadyNas1 kernel: ata1.00: both IDENTIFYs aborted, assuming NODEV
May 04 15:36:06 ReadyNas1 kernel: ata1.00: revalidation failed (errno=-2)
May 04 15:36:06 ReadyNas1 kernel: ata1: hard resetting link
May 04 15:36:06 ReadyNas1 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 04 15:36:06 ReadyNas1 kernel: ata1.00: both IDENTIFYs aborted, assuming NODEV
May 04 15:36:06 ReadyNas1 kernel: ata1.00: revalidation failed (errno=-2)
May 04 15:36:06 ReadyNas1 kernel: ata1.00: disabled
May 04 15:36:06 ReadyNas1 kernel: ata1: hard resetting link
May 04 15:36:06 ReadyNas1 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 04 15:36:06 ReadyNas1 kernel: ata1.00: both IDENTIFYs aborted, assuming NODEV
May 04 15:36:06 ReadyNas1 kernel: sd 0:0:0:0: [sda] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
May 04 15:36:06 ReadyNas1 kernel: sd 0:0:0:0: [sda] tag#18 Sense Key : 0x5 [current] [descriptor]
May 04 15:36:06 ReadyNas1 kernel: sd 0:0:0:0: [sda] tag#18 ASC=0x21 ASCQ=0x4
May 04 15:36:06 ReadyNas1 kernel: sd 0:0:0:0: [sda] tag#18 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
May 04 15:36:06 ReadyNas1 kernel: blk_update_request: I/O error, dev sda, sector 72
May 04 15:36:06 ReadyNas1 kernel: md: super_written gets error=-5
ay 04 15:36:06 ReadyNas1 kernel: ata1.00: detaching (SCSI 0:0:0:0)
May 04 15:36:06 ReadyNas1 kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
May 04 15:36:06 ReadyNas1 kernel: sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=0x00
May 04 15:36:06 ReadyNas1 kernel: sd 0:0:0:0: [sda] Stopping disk
May 04 15:36:06 ReadyNas1 kernel: sd 0:0:0:0: [sda] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=0x00
And the Toshiba disk is kicked out of the data-raid...
May 04 15:36:06 ReadyNas1 kernel: md/raid1:md127: Disk failure on sda3, disabling device.
md/raid1:md127: Operation continuing on 1 devices.
This is definitely not a good situation. I checked the disks and they look healthy after the disk test. Given that it looks like SATA issues and both disks appear OK, I would be suspect of chassis backplane issue or maybe a power supply issue (though I saw no evidence of power issues in the logs). If I were you, I would backup my data asap, and keep daily backups from now on. Then keep an eye on it and if it happens again, it would probably be time to talk to Netgear about a chassis or PSU replacement.
Then keep an eye on it and if it happens again, it would probably be time to talk to Netgear about a chassis or PSU replacement.
FYI, the warranty on the RN212 is three years for the original purchaser. If you are close to the end of the warranty period, then you could try contacting them now.
Replacement power adapters for the RN212 are pretty easy to find, and are inexpensive. You could also do a risk-buy of one, and see if it makes any difference.
The problem has re-occurred and I'm certain now is caused because the device keeps losing power. The AC adapter is OK but the power socket in the ReadyNas is broken and is not making a good connection with the AC adapter connector (I can move the AC Adapter cable where it plugs into the ReadyNas and the ReadyNas powers off). Device is out of warranty so I will try and strip down and see what's causing the bad connection.
The DuoV1 had a recessed power connection, which would have gone a long way to preventing stress on the connector from it being hit. Unfortunately, Netgear didn't stick with that on later units nor did they go to a 90° mating connector that wouldn't stick out so far. That makes damage more prevalent. One of the units I bought "for parts" simply had broken solder joints where the power connector mounts to the system board, so maybe yours is as simple. If the connector itself is damaged, and especially if the board is, you may want to solder on a "pigtail" rather than use a new board-mount connector. Not only is that easier to find, it'll probably last longer.
If it is just the solder joints, adding some epoxy fillets for stress relief could prevent a repeat. The potential downside of that, though, is it will make the connector harder to remove if it does ultimately go bad.
Taken apart and found that the power connector itself is faulty. Solder connections to circuit board are fine but get intermittent connection from the center pin if I move it slightly. Any pointers as to where I might find a replacement for the connector?
It's a standard 5.5 x 2.1mm connector. A search for 5.5mm board mount connector turned up some on eBay, but I don't know if the solder tabs are in the right places. As I mentioned before, a "pigtail" connector -- a short section of wire and an inline connector -- is also an option.
