NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ATA error count increasing- Bad disk or bad chassis?
Hello assembled community, I have a Ready NAS 214 diskless purchased in May 2020. I initially populated it with 3 x Toshiba N300 4TB discs and all was well. In November I purchased a 4th Toshib...
als-chups wrote:So, my conclusion is that it is a problem with slot 4 on the chassis, unless you guys can think of an alternative reason. The power supply seems OK.
I have a couple of questions:-
Does it matter? It looks like there are increasing ATA errors on start-up which seem to be sorted within a 5 second timeframe on start-up and then give no further increase during the up-time of the unit. Performance is fine, and it does not look as if the disk involved is failing. The ATA errors are an increase of either 3 or 4 on each boot. If I monitor this for a sudden change, would that give me warning that the disk may be the problem?
The unit is still under hardware warranty, but any interaction with Netgear Support makes me lose the will to live. I could simply return it to the original vendor for a replacement.
How do I re-establish my old volume and data with the other 4 drives I've pulled?
My plan is:-
1.Power down. Remove the drive from slot 4.
2. Boot up with no drives. Factory re-set the device.
3. Re-install configuration files downloaded before first factory reset. Power down.
4. Re-install the 4 drives in their correct order.
5. Re-boot.
Will this work, or is there a chance it will see the 4 drives as new and re-format them?
I agree with your conclusion that it's the chassis. You should check and make sure there isn't just something in the SATA connector that can be blown or picked out before you give up on it completely.
Does it matter? Well, it will likely get worse and will eventually matter. I would do a warraty replacement now, before it gets worse, possibly corrupting the data volume, or your warranty expires.
A factory default without drives does nothing. A factory default re-initializes the drives from the flash; so no drives, no reset. And your problem is not with the firmware, anyway, so no need to do a reset at all.
Hi als-chups
I agree that a factory reset does not seem like it will have any effect on this problem. ATA errors is one of those types of errors that can also be the cause of a fault bay/chassis. It can be the SATA connector as well, in the chassis - or it could be the HDD itself which seems unlikely at this point.
I think you should test the disk with a disk test tool. I am sure Toshiba has one available on their website. That will require that you can connect the HDD to your PC via a USB-to-SATA connector or similar.
If the disk is clean in that disk test, I would then lean toward a chassis issue. My money would be on a problem with the SATA connector in bay 4.
Download the logs from the web admin page. "System" > "Logs" > "Download Logs". Locate the dmesg.log file. Search for "ata4" in that log file. What lines do you see with regards to "ata4"?
Cheers
Many thanks for your helpful reply. I'vee had a look for a Toshiba HDD test utility and they don't seem to supply one, but I'm sure that there are others available which will do the same thing. I'll keep looking.
The Dmesg.log file mentions the ata4 in these lines;-
[Mon Jan 11 20:33:35 2021] ata4.00: exception Emask 0x10 SAct 0x800 SErr 0x400101 action 0x6 frozen
[Mon Jan 11 20:33:35 2021] ata4.00: irq_stat 0x08000000, interface fatal error
[Mon Jan 11 20:33:35 2021] ata4: SError: { RecovData UnrecovData Handshk }
[Mon Jan 11 20:33:35 2021] ata4.00: failed command: WRITE FPDMA QUEUED
[Mon Jan 11 20:33:35 2021] ata4.00: cmd 61/08:58:40:20:00/00:00:00:00:00/40 tag 11 ncq 4096 out
res 40/00:58:40:20:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[Mon Jan 11 20:33:35 2021] ata4.00: status: { DRDY }
[Mon Jan 11 20:33:35 2021] ata4: hard resetting link
[Mon Jan 11 20:33:35 2021] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Mon Jan 11 20:33:36 2021] ata4.00: configured for UDMA/100
[Mon Jan 11 20:33:36 2021] ata4: EH complete
[Mon Jan 11 20:33:36 2021] ata4.00: exception Emask 0x10 SAct 0x40000000 SErr 0x400101 action 0x6 frozen
[Mon Jan 11 20:33:36 2021] ata4.00: irq_stat 0x08000000, interface fatal error
[Mon Jan 11 20:33:36 2021] ata4: SError: { RecovData UnrecovData Handshk }
[Mon Jan 11 20:33:36 2021] ata4.00: failed command: WRITE FPDMA QUEUED
[Mon Jan 11 20:33:36 2021] ata4.00: cmd 61/08:f0:40:20:00/00:00:00:00:00/40 tag 30 ncq 4096 out
res 40/00:f0:40:20:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[Mon Jan 11 20:33:36 2021] ata4.00: status: { DRDY }
[Mon Jan 11 20:33:36 2021] ata4: hard resetting link
[Mon Jan 11 20:33:36 2021] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Mon Jan 11 20:33:36 2021] ata4.00: configured for UDMA/100
[Mon Jan 11 20:33:36 2021] ata4: EH complete
[Mon Jan 11 20:33:36 2021] ata4.00: exception Emask 0x10 SAct 0x2 SErr 0x400101 action 0x6 frozen
[Mon Jan 11 20:33:36 2021] ata4.00: irq_stat 0x08000000, interface fatal error
[Mon Jan 11 20:33:36 2021] ata4: SError: { RecovData UnrecovData Handshk }
[Mon Jan 11 20:33:36 2021] ata4.00: failed command: WRITE FPDMA QUEUED
[Mon Jan 11 20:33:36 2021] ata4.00: cmd 61/08:08:40:20:00/00:00:00:00:00/40 tag 1 ncq 4096 out
res 40/00:08:40:20:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[Mon Jan 11 20:33:36 2021] ata4.00: status: { DRDY }
[Mon Jan 11 20:33:36 2021] ata4: hard resetting link
[Mon Jan 11 20:33:37 2021] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Mon Jan 11 20:33:37 2021] ata4.00: configured for UDMA/100
[Mon Jan 11 20:33:37 2021] ata4: EH complete
[Mon Jan 11 20:33:37 2021] ata4: limiting SATA link speed to 3.0 Gbps
[Mon Jan 11 20:33:37 2021] ata4.00: exception Emask 0x10 SAct 0x1000 SErr 0x400101 action 0x6 frozen
[Mon Jan 11 20:33:37 2021] ata4.00: irq_stat 0x08000000, interface fatal error
[Mon Jan 11 20:33:37 2021] ata4: SError: { RecovData UnrecovData Handshk }
[Mon Jan 11 20:33:37 2021] ata4.00: failed command: WRITE FPDMA QUEUED
[Mon Jan 11 20:33:37 2021] ata4.00: cmd 61/08:60:40:20:00/00:00:00:00:00/40 tag 12 ncq 4096 out
res 40/00:60:40:20:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[Mon Jan 11 20:33:37 2021] ata4.00: status: { DRDY }
[Mon Jan 11 20:33:37 2021] ata4: hard resetting link
[Mon Jan 11 20:33:37 2021] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[Mon Jan 11 20:33:38 2021] ata4.00: configured for UDMA/100
[Mon Jan 11 20:33:38 2021] ata4: EH completeDoes this help in deciding if it's a problem with the SATA connector?
Unfortunately, all the software logs can tell you is that there was an ATA error. There's no way to tell if the problem is in the chassis, or the drive.
One thing you could try is to power down and remove all the drives (labeling them by slot). Then do a fresh factory install on the original disk (putting it in slot 1). After that completes, see if you get any ATA errors when you copy data. If you do, then then drive is likely the problem. If you don't, then move the drive to slot 4, and try again.
If you do see ATA errors only in slot 4, then you have a good case that it is the chassis. But if you don't see them, then the test is inconclusive.
There is definitely issues with reading this disk, as seen in the dmesg logs. Could be the chassis, could be disk but two new disks with the same issue... Just seems unlikely to me. Trying what StephenB suggested would help narrow it down, yes.
rn_enthusiast wrote:
but two new disks with the same issue... Just seems unlikely to me.
True. One complication here - when I've had one failing disk, I've sometimes seen ATA errors show up on other disks in the array as a side effect.
I'm also wondering about power - if the power adapter is failing (or the power circuitry in the NAS is misbehaving), then it's conceivable that the fourth drive isn't getting enough power.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
