NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Character encoding, Codepages, SMB/CIFS and NFS
We've got 4 ReadyNAS in operation. The 2 oldest units run RAIDiator: v4.1.16 with Samba v.3.6.25 and cannot be upgraded anymore. Microsoft finally decided to dump SMBv1 and all machines on our network got upgraded to a life without SMBv1 hence the 2 old NAS were no longer available to the network. To resolve this issue we decided to enable NSF and disable SMB/CIFS. Microsoft was nice enough to include the NSF-Client and server in their updates. This way we can keep them units on the Network and in production as redundant backups of backups - we first thought. We we're able to map the shares to Windows 10, read and write data for testing, etc. all is operational. So far so good and almost too nice to be true. But there is a problem! Folder- & file-names that use special characters changed their appearance. For instance all Umlaut like äöü became double characters. eg. the letter "ü" displays as double character "ü" in NSF-client. Yep it's an issue directly related to varying codepages. Apparently the NAS OS (RAIDiator) uses varying codepages for SMB/CIFS and NSF. The option for language selection in Frontview is missleading. To be on the safe side one would have to select english ASCII. By selecting any Unicode option incompatibility between SMB/CIFS and NFS filesystems/protocols gets in effect without any mention. This is not documented by Neatgear (at least we could not find anyting). We assume we're not the first and only customers experiencing this senselessness and would like to learn wether there is a solution that we might have missed. Looking forward to receiving responses.
How long to reinstall OS on RN102
I have an RN102 that has been giving me headaches as of late under heavy NFS load. It's providing NFS shares for a ProxMox Virtualization (Hypervisor) system. Lately, when under heavy load, particularly when migrating qcow2 disk files from one NFS Share on one disk in the NAS to another NFS share on another disk in the NAS, the system locks up and becomes unresponsive to anything but pings. Web UI is non-responsive and the NFS shares drop off the network (Proxmox no longer sees them). To try and solve this, I did an OS Reinstall per the documentation. Started the reinstall around 8pm one evening and at 7:30am the following morning, the power LED on the NAS was still flashing as if the OS reinstall was still in progress. Not sure what to do next with this. Do I leave it and hope it finally completes? I'm not in front of the NAS now, so I don't recall the specific model, just that it's a 100 series RN102. It is on the latest production firmware available from Netgear. Thanks in advance for any info or suggestions.