ATA errors at 42, should I return hard drive?

What brand and model hard drives?

What version of RAIDiator?

When did the ATA error count increase on the drives and by how much?

mdgm wrote:
What brand and model hard drives? What version of RAIDiator? When did the ATA error count increase on the drives and by how much?

1. The hard drives in question are Western digital 2TB green drives. Model WD20EARS-00MVWB0

2. The Raidiator is 4.1.8. version.

3. The ATA Errors increased from 0 to 42 on one of my drives which I learned about in the Raidiator alert system with logs. The other 2 drives seem to show 42 to start out with so I assume they had 42 to begin with. So I have 3 out of 4 Drives with some type of ATA error.

I also pulled out every drive and tested them individually on my computer using a long drive test and they were all said to have passed.

What do you think?

So is the count 42 or 46?

If you download the logs (Status > Logs > Download all logs) and extract the zip contents what does partition.log look like?

NETGEAR recommends replacing disks at 50 reallocated sectors and 1 ATA error. This also applies to NETGEAR's accessory hard drive warranty if you purchased the disks with the unit.

readysecure1985 I'm trying to establish whether the ATA errors were due to the compatibility issue on old firmware or not. Remember how there was a compatibility issue where the count would increase by 6 each reboot?

mdgm wrote:
readysecure1985 I'm trying to establish whether the ATA errors were due to the compatibility issue on old firmware or not. Remember how there was a compatibility issue where the count would increase by 6 each reboot?

I am not familiar with the 6 ATA errors after each reboot... usually something that causes that on all disks isnt' a disk issue but a chassis issue. This is what we have in regards to more information on the WD20EARS drives: http://www.readynas.com/?p=3690

That disk is only compatible with a ReadyNAS Duo v1 for Sparc units (the NV, NV+ do not support the Caviar Green disks).

For Sparc, the issue was fixed in 4.1.7 (released November 12, 2010). If the drives were installed when the NAS was running firmware prior to 4.1.7 then the issue would be encountered. That was what I was trying to establish.

http://www.readynas.com/RAIDiator_4_1_7_Notes

NetGear wrote:
8. Added support for WD drives that don’t support TLER.

mdgm wrote:
So is the count 42 or 46? If you download the logs (Status > Logs > Download all logs) and extract the zip contents what does partition.log look like?

I originally thought it was 46 but as I looked at at the S.M.A.R.T report, it did say 42 not 46.


I did experience a power outage during the expansion/syncing of one of the expansion hard drives.

Here are the log files you asked for from Partition.log:

Disk /dev/hde doesn't contain a valid partition table

Disk /dev/hda: 1020 MB, 1020837888 bytes
16 heads, 63 sectors/track, 1978 cylinders, total 1993824 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1              32     1993823      996896    6  FAT16

Disk /dev/hdc: 2000.3 GB, 2000388448256 bytes
255 heads, 63 sectors/track, 243200 cylinders, total 3907008688 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/hdc1               2     4096001     2048000   83  Linux
Partition 1 does not end on cylinder boundary.
/dev/hdc2         4096002     4608001      256000   82  Linux swap / Solaris
Partition 2 does not end on cylinder boundary.
/dev/hdc3         4608002  3907008687  1951200343    5  Extended
/dev/hdc5         4608003  1465112305   730252151+  8e  Linux LVM
/dev/hdc6      1465112312  3906992303  1220939996   8e  Linux LVM

Disk /dev/hde: 2000.3 GB, 2000388448256 bytes
255 heads, 63 sectors/track, 243200 cylinders, total 3907008688 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000


Disk /dev/hdg: 2000.3 GB, 2000388448256 bytes
255 heads, 63 sectors/track, 243200 cylinders, total 3907008688 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/hdg1               2     4096001     2048000   83  Linux
Partition 1 does not end on cylinder boundary.
/dev/hdg2         4096002     4608001      256000   82  Linux swap / Solaris
Partition 2 does not end on cylinder boundary.
/dev/hdg3         4608002  3907008687  1951200343    5  Extended
/dev/hdg5         4608003  3906992297  1951192147+  8e  Linux LVM

Disk /dev/hdi: 2000.3 GB, 2000388448256 bytes
255 heads, 63 sectors/track, 243200 cylinders, total 3907008688 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/hdi1               2     4096001     2048000   83  Linux
Partition 1 does not end on cylinder boundary.
/dev/hdi2         4096002     4608001      256000   82  Linux swap / Solaris
Partition 2 does not end on cylinder boundary.
/dev/hdi3         4608002  3907008687  1951200343    5  Extended
/dev/hdi5         4608003  3906992297  1951192147+  8e  Linux LVM

Most likely the ATA errors were caused by the compatibility issue.

What model ReadyNAS is this?

How long ago did you buy these drives?

mdgm wrote:
Most likely the ATA errors were caused by the compatibility issue. What model ReadyNAS is this? How long ago did you buy these drives?

When I log into frontview web admin screen, it said that its a " ReadyNAS X6" however in the RAIDiator software, it comes up as "readynas 600"

May I ask what exactly do you see in the log files to indicate there is a compatible issue with the hard drives? I know that one of the drives shows 0 ATA errors and the rest show 42. If there is a compatiable issue, would it effect all the drives. I think they are all the 2TB WD green drive.

I purchased the entire system used so I can't say for certain how old the drives are but I did check one of them out and it has about 8 months left on its warranty.

When I did purchase the system, I noticed that it was not working properly. When I signed into the system, it said something like " 0MB available on 0MB drive" which was really strange. I did a factory reset and the entire thing broke.

The only way I could get it working was to load a very old version of the firmware 2.00c1-p5 into the compact flash card then update to 4.1.6 then do a factory reset( it worked here) then I would update to version 4.1.8.

If I ever updated the firmware to 4.1.8 or 4.1.10 and did a factory reset, it would break and I would have to eventually load the older version of the firmware( 2.00c1-p5)

Please tell me what you are thinking?

Thanks.