NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

superjuventino's avatar
Aug 31, 2018

RN214 Drive Degraded After Restart

Hi all,

 

We had a breif power failure last night and luckily my UPS kept my NAS running long enough so that I could perform a proper shutdown. However after restarting it this morning, one of the drives changed to degraded after 3 hours. I started a re-sync hoping it will fix the problem. Is this an issue someone else has experienced or is it a faulty drive? If it is a faulty drive, it will be the 2nd one to fail in the 15 months I've owned the ReadyNAS.

 

Model: RN 214

FW: 6.9.3

 

Here are the last few entries of the log showing the failure:

 

Thu Aug 30 2018 14:24:46 Volume: Volume Client-Data health changed from Redundant to Degraded.

Thu Aug 30 2018 14:24:39 Disk: Disk Model:TOSHIBA DT01ACA300 Serial:XXX was removed from Channel 2 of the head unit.

Thu Aug 30 2018 11:14:22 System: ReadyNASOS background service started.

Wed Aug 29 2018 20:54:39 System: The system is shutting down.

 

Thanks in advance!

5 Replies

Replies have been turned off for this discussion
  • mdgm-ntgr's avatar
    mdgm-ntgr
    NETGEAR Employee Retired

    Disks can and do fail at any time.

     

    What do you see for the disk that was considered bad in the logs e.g. in smart_history.log. disk_info.log should indicate the disk letter (though that might have changed when adding the disk back) and you may see entries for the disk in dmesg.log, kernel.log and/or systemd-journal.log that may also give an indication as to why the disk was considered bad.

    • superjuventino's avatar
      superjuventino
      Tutor

      I went through the logs you suggested, didn't see anything bad in the logs ofr that drive. The only thing that stood out was in the kernel.log at the time the NAS weas being shut down:

       

      Aug 29 20:55:03 ABC-Inc kernel: al_eth 0000:00:03.0 eth1: al_eth_down
      Aug 29 20:55:03 ABC-Inc kernel: [eth rx] warn: dma state didn't change to Disable
      Aug 29 20:55:03 ABC-Inc kernel: [eth rx] warn: failed to change state, error -110
      Aug 29 20:55:03 ABC-Inc kernel: al_eth 0000:00:01.0 eth0: al_eth_down
      Aug 29 20:55:03 ABC-Inc kernel: [eth rx] warn: dma state didn't change to Disable
      Aug 29 20:55:03 ABC-Inc kernel: [eth rx] warn: failed to change state, error -110
      Aug 29 20:55:05 ABC-Inc systemd-shutdown[1]: Sending SIGTERM to remaining processes...

      • StephenB's avatar
        StephenB
        Guru - Experienced User

        What stats did you see in disk_info.log?

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More