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

Forum Discussion

PeteC2017's avatar
PeteC2017
Aspirant
Jan 30, 2023
Solved

Volumes now showing inactive after reboot

on one of our ReadyNAS 4312 after a reboot all the disk in the Raid 5 are showing as inactive.  nothing has been written to the NAS.  Isa there a way to bring the drives on line and recover the data ?


  • PeteC2017 wrote:

    it looks like some sort of OS issue, I cannot add SHH servicers.


    Have you been able to download the log zip file?

12 Replies

Replies have been turned off for this discussion
  • StephenB's avatar
    StephenB
    Guru - Experienced User

    PeteC2017 wrote:

    on one of our ReadyNAS 4312 after a reboot all the disk in the Raid 5 are showing as inactive.  nothing has been written to the NAS.  Isa there a way to bring the drives on line and recover the data ?


    There might be, it depends on what went wrong.

     

    Do you know what happened (powerfail, disk failure, etc)?

  • NiveditaP's avatar
    NiveditaP
    NETGEAR Employee Retired

    Hello PeteC2017 

     

    Could you please look into the disk logs , if ATA Error count is greater than 0 then it seems your drive have gone faulty.

    Also, if you are using Raid 5 then the NAS should work with 3 drives.

     

    Have a lovely day, 
    Nivedita Pa
    Netgear Team 

    • Sandshark's avatar
      Sandshark
      Sensei - Experienced User

      ATA errors are not always due to the drive.  SMART can't determine if it's the hardware on the drive side, the NAS (PC, etc.) side, or even another drive on a companion SATA bus.  I had an EDA500 on which the eSATA cable became loose, and the result was dozens of ATA errors before the volume was corrupted and went read-only.

      • StephenB's avatar
        StephenB
        Guru - Experienced User

        Sandshark wrote:

        ATA errors are not always due to the drive.  


        Agreed. And a non-zero ATA count doesn't necessarily mean the drive needs to be replaced.  I've seen cases where drive X has failed to respond to a command, and an ATA error was then reported on Drive Y.  I'm thinking that the SATA bus ended up hung, and that the OS couldn't figure out what drive was at fault.

         

        In this case PeteC2017 says there was one failed drive though, so I do agree that looking at the smart stats (and the other logs) was the right next step. I said that earlier in the thread.

         

        In any event, the posts are quite stale (2 months old), so I don't why the mod decided to reply now.

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