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

Forum Discussion

doccy's avatar
doccy
Aspirant
May 02, 2018
Solved

ReadyNASRND2000 bricked.

Hi guys.

 

My ReadyNASRND2000 is not powering on.  Totally dead.  Had a few powercuts recently - no idea if they were related.

 

What is my best next move - my last external back up was over a month ago.

 

Am happy to buy an updated readynas - but need to be clear how I am going to mirror the data on the drives into my new enclosure.  

 

Any advice re best product for me? Safest way to proceed?  I am assuming (I hope not wrongly) that the two internal mirrored drives will still have my data. 

 

Thanks for any help!

  • doccy's avatar
    doccy
    May 03, 2018

    OK - thanks for the help guys.

     

    Pretty sure i have a V1 readynasduo.

     

    Looking a bit closer - my power supply light was not on!  Now confirmed it is blown.  


    I have orderd a replacement power supply and will try that in first instance... if there are issues then at least I know about using the linux setup to try and get data off.  

     

    Cheers for the help! 

15 Replies

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

    doccy wrote:

    I am assuming (I hope not wrongly) that the two internal mirrored drives will still have my data. 

     

    Hopefully you are correct, but there is a chance that the data volume is corrupted.  Power surges can damage the disks, and lost (cached) writes can compromise the RAID array (or the file system).

     

    "Bricked" could use some more clarification.  Are you seeing LEDs lit but a failure to boot?  If so, try installing RAIDar on a PC, and tell us it's status. ( https://kb.netgear.com/20684/ReadyNAS-Downloads#raidar )

     

     

    Do you know what firmware the NAS was running (whether it was 4.1.x or 5.3.x)?  That might make a difference.

     

    Usually the next step is to try to offload the storage using a Windows PC.  For instance, install r-linux for windows on the PC ( https://www.r-studio.com/free-linux-recovery/ ) and then connect disk 1 of the NAS using SATA or a USB/SATA dock or adapter.

     

    If the system looks alive but is not booting, you could also power down, remove disk 1, and then try powering up again.  Use the boot menu option to skip the file system checks (as you don't want the system to attempt to repair file system damage at this point).  The boot menu works differently on 4.1.x systems and 5.3.x systems - that's one reason we need to confirm exactly what model you own.

     

    • doccy's avatar
      doccy
      Aspirant

      Thanks man.

       

      By bricked i mean it won't turn on.  No lights coming on - nothing.

       

      The disks are just 2 mirrors of each other so i was hoping a simple RAID set up like that would be robust (fingers crossed). 

       

      No experience of linux - but that might be the way to go?  Thanks for the tip. 

      • StephenB's avatar
        StephenB
        Guru - Experienced User

        doccy wrote:

         

        No experience of linux - but that might be the way to go?  Thanks for the tip. 


        R-Linux for Windows will be easier for you than booting up the PC under linux and learning how to mount the disks, etc.  If you weren't using RAID-1 the answer would be different.

         

        If that fails, then the next options are 

        1. RAID recovery software.  ReclaiMe is one package that folks have used here.  Cost is about $200, but you pay after you confirm that it sees your data.
        2. Netgear Support offers a data recovery service, and they can do that on your new ReadyNAS ( https://kb.netgear.com/29876/ReadyNAS-Migrating-disks-from-RAIDiator-4-1-or-RAIDiator-5-3-to-ReadyNAS-OS-6 ).  They charge by the hour, and there is a minimum that is approximately $200
        3. Some other RAID recovery service available in your area.

        Though if there was no damage, R-Linux for Windows should be able to read the data (and costs you nothing to try).

         

         

        Can we get an answer on the NAS model you have?  It could be either a v1 or a v2 (introduced in Nov 2011).  They are quite different internally, and this really does matter when you are dealing with recovery of data.

         

        A v2

        • says v2 on the front panel
        • runs 5.3.x firmware
        • has -200XXX in the part number on the rear panel (XXX is either NAS or a country-specific code)

        A v1 

        • runs 4.1.x firmware
        • has -100XXX in the part number
        • often says v2 on a label on the back panel (which misleads people).

        If your NAS runs 4.2.x or 6.x firmware, then it's not a Duo at all (but a different 2-bay NAS).  There often is a label on the back that tells what firmware the NAS shipped with.

         

         

  • Marc_V's avatar
    Marc_V
    NETGEAR Employee Retired

    Hi doccy

     

    Welcome to the Community!

     

    Upgrading to an OS 6 ReadyNAS model would be the best move here,  but you need to make sure that your disks are in healthy condition and the RAID is in working condition so the migration would be successful.


    Migrating to an OS 6 unit is not that simple as booting but following the steps provided on the guide then contacting Support will help you migrate your data to the OS 6 device.

     

    Migrating to OS 6 Units (Duo and Duo V2 share the same steps on migrating data)

     

    Here are a list of models available, I would suggest getting a RN400 series model ReadyNAS OS 6 models

     

    Hope this helps!

     

    Regards

     

     

     

  • Hi Doccy,

    I would recommend you to try recovering the data by installing a copy of linux like mint cinnamon through live usb, you may follow this blog https://www.lifewire.com/create-uefi-bootable-linux-mint-usb-2202084 to create a live bootable usb. Once you boot into mint, you shall be able to view your RAID partitions. After you’ve done this, attach your external HDD which must be equivalent or larger than the size of the array.

    However if you are not able to recover using this method, you could also use recovery tools like Stellar Raid Recovery or R-Studio Network Edition. They have a pretty straightforward recovery process IMO.

    • StephenB's avatar
      StephenB
      Guru - Experienced User

      Crazyraider wrote:

      I would recommend you to try recovering the data by installing a copy of linux like mint cinnamon through live usb, you may follow this blog https://www.lifewire.com/create-uefi-bootable-linux-mint-usb-2202084 to create a live bootable usb.


      While this is an option, R-Linux for Windows is much simpler, since it requires no knowledge of linux.  The sparc-based NAS require installing some older tools to access the RAID array, so it's not as simple as creating a live USB and booting it up.

       

      So I recommend trying the windows tool first - we can circle back to this if the Windows tools fail.

      • alcofribas's avatar
        alcofribas
        Aspirant
        Amazingly enough, the very same thing happened to mine too, at the same time as Doccy, after exactly five years of use in a RAID1 configuration. The thing simply won't turn on when I press the On button. It's not a power supply failure, and I'd be extremely surprised if this was due to a power surge, because it was on a battery backup/surge protector and no other gear has suffered. I think it's likely that there is no disk damage (the failure happened when the NAS wasn't in use) and I'd like to check if I can reuse my 3TB units in an empty frame before starting all over again and spending a lot more money. Underneath the box there's a sticker that says FW:V4.2.21 and I've faithfully updated the firmware whenever I was asked to. I usually work on a Mac, but I do have a Linux laptop and I've just read a bit about RAID1 on Linux https://raid.wiki.kernel.org/index.php/Linux_Raid

        The sparc-based NAS require installing some older tools to access the RAID array, so it's not as simple as creating a live USB and booting it up.
        Does this mean that the RAID metadata is in a weird format, or at a weird location? I'm surprised that the use of a SPARC MPU (if that's what I have on mine) would make a difference in the configuration file format. Can you give a bit more information about this StephenB? Thanks

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