netgear readynas login for older units, ssh access

netgear  

ssh -oKexAlgorithms=+diffie-hellman-group1-sha1,diffie-hellman-group14-sha1 -oHostKeyAlgorithms=+ssh-rsa root@<ip>

admin login rejects after connect.  Use admin on 6.0 and later units

--30--

readynas tips page netgear

 

Readynas knowledge base on netgear website

 

https://kb.netgear.com/20898/ReadyNAS-ReadyDATA-Boot-Menu

 

--30--

connect to readynas with 4.x firmware which doesn't support TLS 2 or SMB 1.0

 

Readynas older versions

Notes about connecting to older Readynas 4.x isn't available with (or may not be) TLS 2 support.  Windows 10 has killed TLS below that.  admin page won't work even with warning.

The issue is Firefox (maybe other browsers) enforce this.  Not sure when that was also done with the system support, but undoubtedly will be there at some point.

Firefox setting:

bring up about:config, acknowledge warning

security.tls.version.max

security.tls.version.min

Set min to 1, so that will connect to 1.x web pages.  Max doesn't need to be changed in this case.

Windows SMB

 Windows 10 SMB may be set to not support 1.0.  in a home setting this may be used if the network is secured and not visible or available to outside or unauthorized connections.

hit windows button, type in "Turn Windows Features On or Off" or some portion till matching that.

scroll to SMB 1.0/CIFS File Sharing Support and check the box.  Apply.  May take some time but will have progress box.  took 3min on a win10 client on ESXI host.

about:config  security.tls.version.min = 1  leave max = 4 (as of ver 104 firefox)

--30--

set readynas nfs rootsquash off

rootsquash is a feature in NFS that allows one to add a bit of security to nas systems.  Unfortunately if the user id's aren't managed closely across your systems that give a crap, the systems will have inadvertent portions that aren't available.

The readynas backup is a victim of this.  It faithfully copies across things from one system to another and adjusts times and all, and sets the user id.  Then it can no longer get to it after that.

Sad solution is to turn off rootsquash, so that the actual rsyncs from other systems can get to the files and do the job.

Will have to work on the mess sometime.  However there are not any conventions on user id's across all the distributions to make anything simple.

https://kb.netgear.com/000045496/ReadyNAS-OS-6-8-NFS-User-ID-Mapping

ReadyNAS OS 6.8 allows configuring NFS User ID mapping per NFS share. This functionality ensures NFS connections use a predefined UID/GID when necessary, which prevents permission based issues on certain applications.

Configuring User ID Mapping

1. From the Admin Page, click Shares > Shares. 
2. Click the share you would like to edit, then click Settings.
3. Click Network Access > NFS > Advanced.

There are three UID/GID squashing settings:

• No Root Squash: Allows NFS connection using root access to connect as root. (Anonymous UID/GID text boxes are disabled)
• Root Squashing: Forces all NFS root users to use UID/GID configured in the Anonymous UID/GID text boxes.
• All Squash: Forces all NFS users to use UID/GID configured in the Anonymous UID/GID text boxes.
•  

Migrating Readynas Radiator to OS 6 Readynas devices

One challenge in migrating from Sparc architecture products, to Intel or other (Arm), is that the Linux file system on sparc was built with a 4k block size, rather than 512.

On Intel linux, if you set up your disks, you can mount them with some incantations and special procedures.  Not sure how the Readynas Linux handles that problem, but there is a link showing it.

I had a bad disk and some problems with the data recovery firmware on a REadynas NV+ some years ago and got the support group to help me get around it.  In the mean time, I had mounted the 4 drives on an Intel linux system I'd built up and had recovered most of the data.

https://kb.netgear.com/29875/ReadyNAS-Migrating-disks-from-RAIDiator-to-OS-6?cid=wmt_netgear_organic

Copy of article for archival:

This articles outlines the necessary steps to access data on disks from ReadyNAS units running RAIDiator on ReadyNAS OS 6 units.
Due to differences in CPU architecture and operating system between RAIDiator and ReadyNAS OS 6, it may be necessary to take additional steps once the disks are moved to an OS 6 chassis.
If your ReadyNAS running RAIDiator is still functional, and you can access the data, we recommended you first backup the data to another location
http://kb.netgear.com/app/answers/detail/a_id/21344
If you can no longer access the data using your legacy ReadyNAS and you wish to access the data using your ReadyNAS OS 6 device, booting may not be as easy. Depending on which legacy model the disks come from, and which ReadyNAS OS 6 you posses the steps differ to make the data accessible.
After initially moving the disks from the legacy ReadyNAS to the ReadyNAS OS 6 model please be aware of the following items;

• Do not attempt an OS reinstall
• Do not attemp a factory reset
• The RAID must be healthy i.e. if the RAID was broken on the legacy NAS it will not always be possible to access the data on the ReadyNAS OS 6 - an example of this would be 2 failed disks in a 4 disk RAID 5.
• ReadyNAS OS 6 model must have at least the same amount of drive bays as the legacy ReadyNAS
• Logging a ticket with Technical Support may be required
• Purchasing a data recovery contract may be required
• You may require one additional spare blank disk
• You may require an external location to where you can recover your data to i.e. external USB HD, network share, other NAS storage.

To find the steps needed to access the data on your ReadyNAS OS 6 device, find your model below:

• ReadyNAS OS 6
  • ARM
    • ReadyNAS 100 series (RN102, RN104)
    • ReadyNAS 200 series (RN202, RN204)
    • ReadyNAS 210 series (RN212, RN214)
    • ReadyNAS 2120 (RN2120)
  • x86
    • ReadyNAS 300 series (RN312, RN314, RN316)
    • ReadyNAS 500 series (RN516)
    • ReadyNAS 700 series (RN716X)
    • ReadyNAS 3130 (RN3130)
    • ReadyNAS 3138 (RN3138)
    • ReadyNAS 3220 (RN3220)
    • ReadyNAS 4220 (RN4220)

Find the model of your Legacy ReadyNAS running RAIDiator, click on the link and follow the instructions. X represents whether or not your model came with disks.

• RAIDiator
  • RAIDiator 4.1 (sparc)
    • ReadyNAS Duo (RND2XXX)
    • ReadyNAS NV+ (RND4XXX)
    • ReadyNAS 1100 (RNR4XXX)
    • Follow the instructions at ReadyNAS: Migrating disks from RAIDiator 4.1 or RAIDiator 5.3 to ReadyNAS OS 6 
    • http://kb.netgear.com/app/answers/detail/a_id/29876 
• RAIDiator 4.2 (x86)
• • ReadyNAS NVX, NVX Pioneer (RNDX4XXX, RNDX4XXE)
  • ReadyNAS Pro Series, Pro Pioneer, Pro Business (RNDP2000, RNDP4XXX , RNDP6XXX, RNDPXXXXE)
  • ReadyNAS Ultra Series (RNDU2XXX, RNDU4XXX , RNDU6XXX)
  • ReadyNAS Ultra Plus series (RNDP2XXU, RNDP4XXU, RNDP6XXU)
  • ReadyNAS 1500 (RNRX4000)
  • ReadyNAS 2100 (RNRX4000)
  • ReadyNAS 3100 (RNRP4000)
  • ReadyNAS 3200 (RN12PXXXX)
  • ReadyNAS 4200 (RN12TXXXX, RN12GXXXX, RN12SXXXX)
  • Follow the instructions at ReadyNAS: Migrating disks from RAIDiator 4.2 to ReadyNAS OS 6 (x86)
  • http://kb.netgear.com/app/answers/detail/a_id/29957
• RAIDiator 5.3 (ARM)
• • ReadyNAS Duo v2 (RND2XXXv2)
  • ReadyNAS NV+ v2 (RND4XXXv2)
  • Follow the instructions at ReadyNAS: Migrating disks from RAIDiator 4.1 or RAIDiator 5.3 to ReadyNAS OS 6
  • http://kb.netgear.com/app/answers/detail/a_id/29876 
  
  

Readynas Radiator 4.1 firmware problem with SMB CIFS shares

The changes made to SMB protocol from version 1 to version 3, seems to have killed the share mode of access on readynas older systems.

Switching to user share mode and creating a user is a pain as well.

But the share name is entered as a user id in passwd, but not put up as a user in the gui, which is a huge hole when you switch from share to user.

the only method of fixing it is to install EnableSSHAccess and log in as root.  One can then set an SMB passwd on the shares that exist, and each will be accessible with that passwd on system thru so far and including windows 10.

Also other secured user access is then possible once the sharing is turned on if desired.  The users cannot access others storage w/o using group access features.

Of course this has a possibility of voiding any service you have with Netgear (warranty for 4.x devices is long gone).  But if you have any service agreements, don't do this w/o checking since it may impact your agreements for unauthorized user mods to devices.

To install ssh access for 4.x radiator do the following

Download EnableRootSSHAccess for your architecture from here

EnableRootSSHAccess

Original NV+ and 1100 systems are Sparc.  Pro and Ultra systems on 4.x will be Intel.  I'm not sure if Arm has a 4.x version.  All the ones I've seen with Arm are 6.0

then:

1. Get the SSH bin file from the ReadyNAS web site. Click the Add-ons for RAIDiator 4.1.3+ link and scroll to the EnableRootSSH link. Download the bin file and store it on your local computer.


2. Log in as admin on your ReadyNAS using a browser


3. Update your ReadyNAS firmware (optional). This is under System > Update. Just click the Check for Updates button.


4. Click the Local tab and click Choose File to find the EnableRootSSH.bin file that you previously downloaded. Upload this and follow the prompts.

 A restart of the Readynas system is required, if you have other users on the device.  (since some windows systems may work).  I doubt if any samba stacks such as one would have with shares on MacOS would work, but they may be impacted.

Install instructions from here;

http://blog.epdoc.com/2009/11/ssh-on-readynas-nv.html

Readynas blog, with lots of reviews and info

http://www.rnasguide.com/2011/03/26/migrating-your-disks-from-one-readynas-to-another-readynas-on-the-same-platform/

possible workaround to readynas windows 10 share problem. (relevant to developer win 10 installs)

Note on removing credential (If I understand it), as a workaround fix for broken Windows 10 fix. 

Windows 10 upgrades to the developer releases seem to be invalidating stored credentials with each update with some regularity.  if you have a drive share mount with stored credentials, or on another front though not with the readynas nas, stored logins for say remote desktop, you have to reinput them.

That was working up to the latest 9/14 or 9/16 set of updates.  now it seems to retain the credential and not let you easily reinput the login, or share.

And it was not accepting any password on other shares, even valid ones.

A fellow on the Readynas forum (where this became a topic) suggested a workaround worth documenting.

Thanks to Readynas forum user nayadn for this.

nayadn (Aspirant) posted a new reply in R6000 Series AC WiFi Routers on 2016-09-17 07:32 AM :

---

Re: Can no longer access ReadyShare drives on Windows 10

i googled again the error and i came up with a sideway solution
go into user account in control panel
if you're in windows 10 select manage your credentials this will open 2 options
web credentials and windows credentials
head to windows credentials and add a new windows credential
enter the location of the drive \\readyshare on the first line
your windows user name in the second line
your windows password in the third line
and you're done, you should see the drive under network and be able to access it as before
good luck

Removing a Readynas 1100 or NV+ disk tray with bad button

The early Netgear Readynas NV+ (sparc) and 1100 units (4 across) all had a design which must have looked good on paper.

However the buttons that are supposed to push in, and displace a latch upward, allowing the arm to extract the drive typically is frozen.  I don't know if they ever worked early on, but nearly all of the original ifarant units and the first netgears, which all seem to be about the same just don't work.

there is a small spot in one of the holes you can stick a small probe into and actuate the latch thru a small lever action.

This video of my unit, while removed shows the actuation.  I'll share the raw video, a Youtube video of it, and since I'm not the first one to do this, another illustration for reference.

Disk Tray Removal, Youtube

Raw video (google drive)

A longer version of opening the Duo (and probably the NV)

Here is one of the newer units with a reviewer extracting the drive.

Readynas Duo (at about 2:19, has extract)

An annoying old review of the Readynas 1100 (for reference what one looks like)
Almost feel bad calling it annoying since the reviewer is a Jesuit priest.

Readynas 1100 Review