NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Corruption when reading large files from an RN31400 over SMB
When I copy a large file (example: Ubuntu 24.04.3 ISO, 6.3 GB) from my RN31400 NAS to my local drive on a Windows 10 machine using SMB, the file will almost always contain at least one error (as detected with fc /b). If I copy the same file to the same drive when the machine is booted into Linux and using NFS, the file will contain no errors. Has anyone run into this? I'm using the latest NAS firmware (6.10.10).
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.Cant enable SMB on ReadyNas 316
Hi, I noticed that SMB service on my ReadyNas 316 with version 6.9.3 stopped working 2 days ago and I can't turn it on. At first I didnt see the shares and after reboot, I saw that SMB was turned off. I have tried to search for any solutions but I cant find one. I really don't want to do an factory reset. What I tried so far: OS Reinstall Downgrade from: 6.9.3 -> 6.9.1 -> 6.9.0 -> 6.8.1 and then back to 6.9.3 = None version is working Update pagages with "apt upgrade" When I run "systemctl status -a smb": root@NAS:~# systemctl status -a smb smb.service - Samba SMB Daemon Loaded: loaded (/lib/systemd/system/smb.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2018-04-28 13:18:04 CEST; 49s ago Process: 8988 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=1/FAILURE) Main PID: 8988 (code=exited, status=1/FAILURE) Apr 28 13:18:03 NAS systemd[1]: Starting Samba SMB Daemon... Apr 28 13:18:04 NAS systemd[1]: smb.service: Main process exited, code=exited, status=1/FAILURE Apr 28 13:18:04 NAS systemd[1]: Failed to start Samba SMB Daemon. Apr 28 13:18:04 NAS systemd[1]: smb.service: Unit entered failed state. Apr 28 13:18:04 NAS systemd[1]: smb.service: Failed with result 'exit-code'. When I try to manually start smb.service I get: root@NAS:~# systemctl start smb Job for smb.service failed because the control process exited with error code. See "systemctl status smb.service" and "journalctl -xe" for details. I find following in journalctl -xe: Apr 28 13:14:57 NAS systemd[1]: Starting Samba NMB Daemon... -- Subject: Unit nmb.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit nmb.service has begun starting up. Apr 28 13:14:58 NAS systemd[1]: nmb.service: Main process exited, code=exited, status=1/FAILURE Apr 28 13:14:58 NAS systemd[1]: Failed to start Samba NMB Daemon. -- Subject: Unit nmb.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit nmb.service has failed. -- -- The result is failed. Apr 28 13:14:58 NAS systemd[1]: nmb.service: Unit entered failed state. Apr 28 13:14:58 NAS systemd[1]: nmb.service: Failed with result 'exit-code'. Apr 28 13:15:09 NAS readynasd[3398]: Service 'nmb.service' goto unexpected state 'failed'. Expect to be 'active'('activating'). Apr 28 13:15:09 NAS readynasd[3398]: Protocol 'cifs' is reloaded Apr 28 13:15:09 NAS systemd[1]: Starting Samba NMB Daemon... -- Subject: Unit nmb.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit nmb.service has begun starting up. Apr 28 13:15:09 NAS systemd[1]: Started WSD/LLMNR Discovery/Name Service Daemon. -- Subject: Unit wsdd2.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit wsdd2.service has finished starting up. -- -- The start-up result is done. Apr 28 13:15:09 NAS wsdd2[8270]: starting. Apr 28 13:15:09 NAS systemd[1]: nmb.service: Main process exited, code=exited, status=1/FAILURE Apr 28 13:15:09 NAS systemd[1]: Failed to start Samba NMB Daemon. -- Subject: Unit nmb.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit nmb.service has failed. -- -- The result is failed. Apr 28 13:15:09 NAS systemd[1]: nmb.service: Unit entered failed state. Apr 28 13:15:09 NAS systemd[1]: nmb.service: Failed with result 'exit-code'. Apr 28 13:15:09 NAS systemd[1]: Starting Samba SMB Daemon... -- Subject: Unit smb.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit smb.service has begun starting up. Apr 28 13:15:09 NAS wsdd2[8270]: cannot read workgroup from testparm Apr 28 13:15:09 NAS wsdd2[8270]: cannot read workgroup from testparm Apr 28 13:15:09 NAS wsdd2[8270]: cannot read netbios name from testparm Apr 28 13:15:09 NAS wsdd2[8270]: cannot read netbios name from testparm Apr 28 13:15:09 NAS systemd[1]: smb.service: Main process exited, code=exited, status=1/FAILURE Apr 28 13:15:09 NAS systemd[1]: Failed to start Samba SMB Daemon. -- Subject: Unit smb.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit smb.service has failed. -- -- The result is failed. Apr 28 13:15:09 NAS systemd[1]: smb.service: Unit entered failed state. Apr 28 13:15:09 NAS systemd[1]: smb.service: Failed with result 'exit-code'. Apr 28 13:15:09 NAS wsdd2[8270]: Terminated received. Apr 28 13:15:09 NAS wsdd2[8270]: Terminated received. Apr 28 13:15:09 NAS systemd[1]: Stopping WSD/LLMNR Discovery/Name Service Daemon... -- Subject: Unit wsdd2.service has begun shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel Can someone please help me?
Windows 10 Install: no longer able to access NAS shares
Hi, I upgraded 3 days a go to Windows 10 Enterprise build 16299. It was an installation from scratch I sadly have no longer access to any of my SMB shares. Access was working on Windows 7: see image below - I tried dropping to SMB1 in SMB Application + reboot both PC and NAS: no success - I disabled IPV6 under LAN adapter in Windows 10: no success - I enabled every sharing option under Windows 10 for both Private and Public networks: no success Using cmd in admin console to map the network share: net use * /delete net use t: \\nas-ip-address\data /user:admin nas-admin-password Under the shell cmd, I have access to the shares and their listing through drive T: However, it is wired that Explorer GUI cannot access to the T: drive. So I still cannot see my shares in GUI Under Explorer, I can see the NAS: - under "Media Devices", and brows the DLNA folders - under "Storage", double clicking brings the NAS web admin GUI - under "Computer", named correctly "NAS-01": but if I try to access the shares it gives me a "Network access error" I attach above the image with my error Please help me fix this asap, I am lost and really need the SMB access to manage my backupsReadyNas104 - cannot active SMB
I' ve upgrade the firmware from 6.7.5 to 6.8.0 the other day. After that I installed one app from the website but failed. And the app cannot be started or uninstalled from the website, so I used command dpkg -r to uninstall that through SSH. Then I reboot the nas and found I cannot connect the nas by Network Neighborhood, even use IP address directly. I checked the website that smb button turned grey. Whenever activate it times, SMB still cannot work and the button was grey all the time. So I reinstall os 6.7.5 with img downloaded from office site, but the smb still not work. Then upgade to os 6.8.0 again, the smb service still cannot be actived. After the upgrade, the status is as follows and I'll mail the log. root@z00-nas:~# systemctl status smb.service ● smb.service - Samba SMB Daemon Loaded: loaded (/lib/systemd/system/smb.service; enabled; vendor preset: enab led) Active: failed (Result: exit-code) since Thu 2017-09-14 02:30:22 H KT; 36s ago Process: 6943 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, stat us=1/FAILURE) Main PID: 6943 (code=exited, status=1/FAILURE) Sep 14 02:30:20 z00-nas systemd[1]: Starting Samba SMB Daemon... Sep 14 02:30:22 z00-nas systemd[1]: smb.service: Main process exited, co de=exited, status=1/FAILURE Sep 14 02:30:22 z00-nas systemd[1]: Failed to start Samba SMB Daemon. Sep 14 02:30:22 z00-nas systemd[1]: smb.service: Unit entered failed sta te. Sep 14 02:30:22 z00-nas systemd[1]: smb.service: Failed with result 'exi t-code'. root@z00-nas:~# I checked the questions asked in forums, but cannot found the fix methon except factory reset. But I don't have enough spaces to backup from the NAS, is there any other way to fix it?
