NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS 102 NIC Not Activating on Isolated Private LAN
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 t...
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
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.
Thank you for the info - which proc'd one more question:
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?
I'll try a different cable - but the cable hooked to the 192.168.1 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. Also noticed that the nic appears to be a 10/100 mbps card and not gigabit. (Not that that should matter.)
Again, thank you for the help!--mike
emopausal wrote:
Also noticed that the nic appears to be a 10/100 mbps card and not gigabit. (Not that that should matter.)
The NIC is gigabit, so if you aren't seeing it negotiate gigabit there is a problem. 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).
emopausal 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?
You can migrate directly to another OS-6 ReadyNAS. If you have apps installed, they probably won't work if you switch to an x86 model (RN300 or above). Going with an RN212 or RN214 would eliminate that problem, as it is also an arm platform. But inventory is scarce, and some models are either hard to find or very expensive.
The file system is btrfs running on software (mdadm) raid. 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. If you are using XRAID/RAID-1 or have two jbod volumes, you'd only need to connect one disk to mount the volume.
I purchased for parts a unit that was damaged by a lightning-induced surge and it would not connect at all to a "green" switch and would only negotiate 10/100 on another, so the incorrect speed negotiation can also be due to a damaged Ethernet tranceiver. If it's not a cable issue, then I think you are wise to consider a replacement while it's your choice and you have time to look around for one.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
