ReadyNAS 102 NIC Not Activating on Isolated Private LAN

Question

Workhorse RN102 was recently moved to a new network with a new subnet. RN102 had been previously configured with static IP b/c, at the time, the (antique) router fw wasn't supporting assigning IPs to MAC addresses.

Recovery plan was to create a private lan using a spare linksys router using the old RN subnet: 192.168.1.0/24 and reconfigure the NAS back to DHCP.

The new LAN subnet is 192.168.2.0/24.

I plugged five other NAS devices, previous to this one, over e-net to private lan and reconfigured to DHCP, converting them to the new network. (In other words, hardware configuration is valid.) However, when I get to RN102, I cannot get NIC to activate - indicator lights on backplane are out. No light on router port.

I switch-out LAN cable s.t. RN102 now on new subnet. Get activation light on NAS nic backplane and on router port indicator but cannot see (nmap -sn 192.168.2.0/24) RN102 on LAN, of course, b/c static IP config on device.

Question is: what's preventing the RN102 nic from activating when attached to the isolated private lan? Is it b/c there's no internet connection to that LAN and RN NAS OS won't activate the nic until it calls home?

Would a system reset (OS Reinstall option) restore the network setting back to DHCP? (Doc just says "resets some settings on your storage system, such as Internet protocol settings".) How "safe" is this in terms of guaranteed to work? I'm getting no warning lights at all on boot... this was a perfectly working NAS before I had my subnet changed...

Thank you, in advance, for any help!

--mike

StephenB · Answer

You could of course change the subnet on the new router to match the old one - either temporarily or permanently.
&nbsp;
emopausal&nbsp;wrote:
Would a system reset (OS Reinstall option) restore the network setting back to DHCP?&nbsp; (Doc just says "resets some settings on your storage system, such as Internet protocol settings".)&nbsp; How "safe" is this in terms of guaranteed to work?&nbsp;

The OS-reinstall will

reset the network back to default - which is DHCP.
reset the NAS admin password back to password
disable volume quota (on the volume settings wheel).

Other settings are not changed, and it is generally safe (meaning non-destructive).&nbsp;
&nbsp;
I have no idea why the NIC wasn't lit on the other linksys router.&nbsp;&nbsp;

Sandshark · Answer

If the LinkSys is a "green" router (which adjusts signal strength according to perceived cable length and interference), that may be the issue. BUT, it typically indicates that the NIC in the NAS has also been damaged in some way, just not completely dead yet.

The file format on the ReadyNAS is not proprietary, but it is atypical. It uses the BTRFS file system on top of MDADM RAID. These can be added to any Linux system. There are also experimental drivers available for Windows.

emopausal · Answer

Yes, I can't change the subnet of the router to match the RN b/c the ISP router grabbed that subnet and has but a single port and no wifi.

I'll try the reset - I figured that would probably be the outcome - but I was hesitant to try the reset and risk the data.

Side question - preparing for a worse-case scenario, does the RN write to disk using a proprietary format?

Thanks!

--mike

emopausal · Answer

Thank you for the info - which proc'd one more question:&nbsp;Assuming the nic is going out - which is entirely possible given the age of the device and the number of physical moves it's been subjected to in it's lifetime (seriously, this thing is just a tank!), and I'm looking to replace it via the easiest possible way by just plugging the drives into a new host device, what device would that be that would recognize the format of the 102?&nbsp;I'll try a different cable - but the cable hooked to the 192.168.1&nbsp; subnet is a 6' cat 5e and the 192.168.2 net uses a 100' cat 6 - and the RN was lighting up on the latter.&nbsp; Also noticed that the nic appears to be a 10/100 mbps card and not gigabit.&nbsp; &nbsp;(Not that that should matter.)Again, thank you for the help!&nbsp;--mike

StephenB · Answer

emopausal&nbsp;wrote:
Also noticed that the nic appears to be a 10/100 mbps card and not gigabit.&nbsp; &nbsp;(Not that that should matter.)

The NIC is gigabit, so if you aren't seeing it negotiate gigabit there is a problem.&nbsp; That could be the cable or the socket (gigabit uses all 8 pairs in the cable, and if some aren't connecting you can end up with 100 mbps - which only uses 4 pairs).
&nbsp;
emopausal&nbsp;wrote:
I'm looking to replace it via the easiest possible way by just plugging the drives into a new host device, what device would that be that would recognize the format of the 102?
&nbsp;

You can migrate directly to another OS-6 ReadyNAS.&nbsp; If you have apps installed, they probably won't work if you switch to an x86 model (RN300 or above).&nbsp; Going with an RN212 or RN214 would eliminate that problem, as it is also an arm platform.&nbsp; But inventory is scarce, and some models are either hard to find or very expensive.
&nbsp;
The file system is btrfs running on software (mdadm) raid.&nbsp; You can mount the volume manually on pretty much any linux system, and there are also beta-level software available that would let you mount it on Windows.&nbsp; If you are using XRAID/RAID-1 or have two jbod volumes, you'd only need to connect one disk to mount the volume.

Forum Discussion

ReadyNAS 102 NIC Not Activating on Isolated Private LAN

6 Replies

Related Content

guest WLAN isolation

ReadyNAS Ultra 6 Review (RNDU6000) no network activity???

Disable AP isolation

Activate Insight Premium Subscription

Orbi Pro 6 - IOT Client Isolation

NETGEAR Academy

ProSupport for Business