Alarm in NetGear CP admin (relocated sector)

HI,

  Thanks for your quick reply, as I'm not tech person and 

can't read or understand the log file .. 

but these numbers what I found :

• Health data
  ATA Error Count: 3
  Reallocated Sectors: 2768
  Reallocation Events: 2768
  Spin Retry Count: 0
  Command Timeouts: 1
  Current Pending Sector Count: 0
  Uncorrectable Sector Count: 0
  Temperature: 50
  Start/Stop Count: 26
  Power-On Hours: 43478
  Power Cycle Count: 26
  Load Cycle Count: 1829

there is no way we can tell which one is fault ? as I have two disks 

both raid 0

---

AnishaA wrote:

 

ATA Error Count: 0
Reallocated Sectors: 0
Reallocation Events: 0
Spin Retry Count: 0

 

Check for these four and if this count exceeds more than 0 then we suggest you replace that disk.

 

---

makkistyle:  FWIW, I think 0 is too low a threshold.  Personally if I see steadily increasing counts for reallocated sectors, or if I see it exceed about 25 or so, I'll replace the disk. Another indicator is when I am experiencing poor performance, failed transfers, etc.  There is no definitive answer on this, different folks have different thresholds on when a disk needs replacing.

One thing I would like to point out - Backup is the best way to keep your data safe.  If you don't have a backup plan in place for your data, then you should set one up.  With solid backups, disk errors are a nuisance and not a disaster.  The forum community can help with setting up a good backup plan.  

If you are using RAID-0, then you should back up all your data immediately. Everything on the volume will be lost if the disk fails. And everything will be lost when you replace the disk.

---

makkistyle wrote:

 

• Health data
  Reallocated Sectors: 2768
  Reallocation Events: 2768

---

Though people do have different criteria for replacement, this particular disk should definitely be replaced.

---

makkistyle wrote:

there is no way we can tell which one is fault ? as I have two disks 

 

---

One thing I suggest is regularly running the disk test, from the volume settings wheel.

If you have two volumes, then run the test on both of them.  This test will take a while, but there will be an entry on the log page when it completes.  Note you can schedule these tests (using the volume schedule).  I run one maintenance function per month (so the disk test runs every 4 months).

Once the test is complete, then you can look at the stats again.

As far as identifying the disk - this can sometimes be tricky. While some of the logs identify the first disk as 1, there are some spots where it is identifed as 0.  Look in disk_info.log - the disk in the first bay is listed as "channel 0", the next bay is "channel 1".  You can double-check by noting the serial number.  Then power down the NAS, remove the disk, and check the serial number.  (Put the disk back while the NAS is powered down).

The temperature rise could be linked to the failing disk (probably the only way to tell is to replace it).

I don't see an immediate need to replace the other one. But I am thinking you should consider going with 2x8TB RAID-1 instead of RAID-0.  That of course would require replacing both.  A transistion plan might be to consolidate to 1 disk for now, and add a second larger disk later on.