× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

Re: NAS RN212 SSD Detected increasing ATA error count error code

RichardB56
Guide

NAS RN212 SSD Detected increasing ATA error count error code

NAS RN212 SSD Detected increasing ATA error count error code

I do not see any testing while in the Admin page.  I want to test the SSD concerning these errors.  This is a new SSD.  Is the only testing in the Boot menu?

Message 1 of 8
StephenB
Guru

Re: NAS RN212 SSD Detected increasing ATA error count error code


@RichardB56 wrote:

NAS RN212 SSD Detected increasing ATA error count error code

I do not see any testing while in the Admin page.  I want to test the SSD concerning these errors.  This is a new SSD.  Is the only testing in the Boot menu?


I'd start by download the log zip file, and looking in there for other disk-related errors.  dmesg.log, systemd-journal.log, system.log, and kernel.log are all good places to look.  There is a lot in there, but you should be able to tell what messages are disk-related.  If you have trouble doing that, let us know - I'd be willing to take a look at the logs.

 

But to answer your question - go to the volume page, and then choose the setting wheel for the volume that uses the disk.  You'll find a disk test option there.  It runs the long test built into smartctl for all drives in the volume.  When completed, it will give you a pop-up message (and it will show as completed on the logs page).

 

You can also run this same test from ssh if you prefer.

 

One thing to keep in mind is that ATA errors are on the SATA interface.  The cause can be the disk itself, but it can also be the SATA interface hardware in the NAS.

Message 2 of 8
RichardB56
Guide

Re: NAS RN212 SSD Detected increasing ATA error count error code

I found the issue, it is an incompatible SSD.  I'm not sure why it worked fine for months then started to fail.  I'm replacing the SSD to resolve the issue.  The existing SSD is still good but will not work on the NAS.

Message 3 of 8
StephenB
Guru

Re: NAS RN212 SSD Detected increasing ATA error count error code


@RichardB56 wrote:

I found the issue, it is an incompatible SSD.  


What model is it?

Message 4 of 8
RichardB56
Guide

Re: NAS RN212 SSD Detected increasing ATA error count error code

Team Group QX 4tb SSD was the rejected SSD

 

The SSD in the NAS now shows as a 4.1 TB.  I added a 4tb SSD and it will not update the current volume because it is smaller.  Is there a way around this?  Transfer all data from 4.1 tb to 4tb, boot up on 4tb then add the 4.1tb?

Message 5 of 8
StephenB
Guru

Re: NAS RN212 SSD Detected increasing ATA error count error code


@RichardB56 wrote:

 

The SSD in the NAS now shows as a 4.1 TB.  I added a 4tb SSD and it will not update the current volume because it is smaller.  Is there a way around this?  Transfer all data from 4.1 tb to 4tb, boot up on 4tb then add the 4.1tb?


That is the simplest way.  Destroy the 4.1 TB volume after you transfer the data and then remove the disk.  After that, reboot and hot-insert the 4.1 TB disk.

 


@RichardB56 wrote:

Team Group QX 4tb SSD was the rejected SSD

 


Interesting.  We haven't seen any reports on incompatible SSDs here (at least not in a long time).

 

Note the Netgear HCL is not a useful guide, it hasn't been updated in a long time.

Message 6 of 8
RichardB56
Guide

Re: NAS RN212 SSD Detected increasing ATA error count error code

I am unable to find how to copy the volume to the new drive.  Would this be done outside the NAS?

I installed the new drive but since it is smaller it will not expand the volume.  I tried to crest a separate volume but the option is not available.

Message 7 of 8
StephenB
Guru

Re: NAS RN212 SSD Detected increasing ATA error count error code


@RichardB56 wrote:

I am unable to find how to copy the volume to the new drive. 


  1. Create a jbod volume on the new disk.
  2. Create temporary shares that correspond to the shares on the existing disk  These need to have different names
  3. create and run backup jobs to copy the files to the temporary shares.
  4. destroy the original volume and rename the shares on the new one

This process will NOT

  • copy the home folder
  • preserve the hidden .apps folder that apps use

So if you use the home shares, you should copy those manually before you destroy the original volume.  If you run apps, then uninstall them before destroying the volume, and reinstall them afterwards.

Message 8 of 8
Top Contributors
Discussion stats
  • 7 replies
  • 675 views
  • 0 kudos
  • 2 in conversation
Announcements