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

Forum Discussion

Sunfox1's avatar
Sunfox1
Tutor
Jul 08, 2023

ReadyNAS Pro 6 - web "connection refused"

I had an email an hour ago from my very old ReadyNAS Pro 6 about a failed drive. Fine, no problem. But when I went to use the web interface to see which drive, I get nothing but "connection refused" and can't access it.

 

My network shares are still functional and data's all there, and the front control panel says "volume C degraded" with an "X" through the #6 drive.

 

However, I'm confused why I can't get to the web interface anymore? Is something corrupted? Is there a fix? Should I no longer trust this thing?

14 Replies

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

    Sunfox1 wrote:

     

    However, I'm confused why I can't get to the web interface anymore? 


    The web interface runs at a lower priority than other processes, so it is likely that the it isn't getting enough resources to run - particularly if the failing disk is generating a lot of errors.

     

    Do you have ssh enabled?

    Also, what firmware are you running?

    • Sunfox1's avatar
      Sunfox1
      Tutor

      Firmware is OS 4.2.31.  I had planned to upgrade the memory and install the newer OS later this summer.

       

      EDIT: oh, I need to login with "root" and not admin. Okay, SSH is working, yes.

      • StephenB's avatar
        StephenB
        Guru - Experienced User

        Sunfox1 wrote:

        Okay, SSH is working, yes.


        Ok.  Then you can see the serial numbers of the disks that are responding with smartctl.

         

        for i in /dev/sd[a-f]; do smartctl -x $i | grep Serial; done

        If you only see 5 serials, then the one that is missing is the failed disks.  Copy off the serials you see for later.

         

        If you see all 6 serial numbers (or if you want to look at the smart info details), you can check each disk using

        smartctl -x /dev/sda
        ...
        smartctl -x /dev/sdf

        Note with these commands, a completely failed disk should give you "no such device".

         

        You could look at what's blocking the web ui with top, etc.  Though I think I'd just assume it's due to the failed disk. 

         

        I suggest remove the bad disk with the NAS powered down (confirming that the serial doesn't match one of the good disks).

         

        Then use the boot menu to skip the file system check. The system should boot ok, and the volume will be degraded (no RAID redundancy).