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

Forum Discussion

aldawson's avatar
aldawson
Aspirant
Apr 13, 2018

ReadyNAS 2120 v2 Missing Volume after reboot

Recently upgraded to 6.9.3.

2120 with 4x4TB drives

Now after a reboot - NAS advises that no volume exists when I navigate to view the iscsi LUNS, which is all we really use.

 

we did have a \data volume with 2GB free!

 

all other configuration is present and correct - even the LUNS are listed

NAS is only used as vmware datastore location, backups were made to faclilitate file level recovery using veamm - to another iscsi lun on same NAS (which is also inaccessible)

 

any guidance would be appreciated

5 Replies

Replies have been turned off for this discussion
  • JohnCM_S's avatar
    JohnCM_S
    NETGEAR Employee Retired

    Hi aldawson,

     

    Welcome to the Community!

     

    Can you download the NAS system logs? If you can, you may provide it to us. You may check this link for the procedure on how you can send it.

     

    Regards,

    • aldawson's avatar
      aldawson
      Aspirant

      Hi JohnCM_S

       

      logs have been emailed over to nsbu_logs

       

      Regards

      Al

      • JohnCM_S's avatar
        JohnCM_S
        NETGEAR Employee Retired

        Hi aldawson,

         

        Thank you for providing the logs. The logs are actually flooded with messages about iSCSI. It could be that there is a file system issue but we are not yet sure what it is. Can you boot the NAS into Volume Read-only mode and then download the logs ASAP after it comes up?

         

        Regards,

  • mdgm-ntgr's avatar
    mdgm-ntgr
    NETGEAR Employee Retired

    aldawson wrote:

    NAS is only used as vmware datastore location, backups were made to faclilitate file level recovery using veamm - to another iscsi lun on same NAS (which is also inaccessible)


    Some would say that backups stored on the same device are not much of a backup as there's a single point of failure.

     

    The logs suggest that it failed to recover balance.

    Apr 18 09:42:40 NAS kernel: BTRFS error (device md127): bad tree block start 13045144509306137155 19182968307712
    Apr 18 09:42:40 NAS kernel: BTRFS error (device md127): bad tree block start 13045144509306137155 19182968307712
    Apr 18 09:42:40 NAS kernel: BTRFS error (device md127): failed to recover balance: -5
    Apr 18 09:42:40 NAS kernel: BTRFS error (device md127): open_ctree failed

    Were you running a balance on this when the problem happened? How did you run that balance?

  • Hi

    "Were you running a balance on this when the problem happened? How did you run that balance?"

     

    No - balance wasn't being run, wouldn't know how to do that.

     

    issue was identified after users were not able to connect to shared files located via a windows server iscsi connection on the NAS.

     

    The NAS was ultimately rebooted via the web gui, i did notice that the \data volume was present before the reboot but missing after

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