So, this has happened: this week the ReadyNAS just “stops working”. I can log into the admin webpage, and everything looks perfectly fine and there are no errors or any other loud warnings.
However, at the same time, neither my Mac Mini, my MacBook, my wife’s Windows laptop, my iPad, my android tablet, nor my iPhone can see the device. It’s “working just fine“ as long as you don’t want to access any data (so what’s the point, really?).
Anyone else seen this type of behavior? This seems to have escalated about two weeks ago.
Model: RN31200|ReadyNAS 300 Series 2- Bay (Diskless)
However, at the same time, neither my Mac Mini, my MacBook, my wife’s Windows laptop, my iPad, my android tablet, nor my iPhone can see the device. It’s “working just fine“ as long as you don’t want to access any data (so what’s the point, really?).
Perhaps download the log zip file, and see if there are any errors related to Samba. You can send the mods ( @JohnCM_S or @Marc_V ) a private message (PM) with a downloadable link the log zip, and ask them to analyze it. Do that using the envelope icon in the upper right of the forum page. Don't post the zip publicly.
Are all these devices accessing with SMB? If not, what protocols are you using? When the problem occurs, does it always affect all devices? Or does it just affect some?
Also, on the Windows laptop - have you tried entering \\NAS-IP-ADDRESS in the file address bar when you can't "see" the NAS? Use the real IP address for the NAS of course (and be careful to use the correct slash direction). It'd be helpful to understand if this is a discovery issue, or an access issue.
Thanks for the reply. We are using SMB (for windows) and AFS (for the Macs). I have looked at the log files and they don't show any errors that I can see, but I will upload them to the devs as you recommended.
As for the access, we are always using the IP address for connections as I haven't set up a DNS for the house that includes the NAS so that you have to know it is there to access it (security by obscurity).
As for the access, we are always using the IP address for connections
Ok. On the Windows system, are you entering the IP address in the file explorer address bar? Or are you looking for an icon in the left pane under "network"?
Access via Windows over the SMB shares with IP address direction (i.e. M: drive is 10.0.0.xxx mapped).
So, the "same thing but different" just happened; RN321 just totally went offline, but stayed up. Couldn't connect to web admin. Shares that were mounted dropped. Couldn't connect new shares. iPhone app couldn't communicate with it. Didn't respond to power button depress. Had to pull the freaking power cord to get the unit to shut down.
Rebooted, NO Errors, NO Warnings, NO messages of any import to review. The unit just "went on holiday" with no record, save the work I lost in trying to save data to this blasted thing.
I will send the logs as directed above, but I have little doubt that there is anything that anyone will ever find since the "admin console" flags no errors.
Access via Windows over the SMB shares with IP address direction (i.e. M: drive is 10.0.0.xxx mapped).
So, the "same thing but different" just happened; RN312 just totally went offline, but stayed up. Couldn't connect to web admin. Shares that were mounted dropped. Couldn't connect new shares.
Obviously more than the web admin interface went down. I'd look for a disk issue first, so maybe look at overall disk health in disk_info.log and look for disk or btrfs errors in system.log and kernel.log.
What apps are you running?
Did you look for a full OS partition in the logs? Do this by looking in volume.log and scrolling down to the === df -h === section.
In volume.log (md0 not full but is a lot fuller than you stated):
/dev/md0 4.0G 3.0G 662M 83% /
Should I look to do some disk cleanup? What would be using the root filesystem that I could purge?
83% is quite full, and could interfere with firmware updates. Though it shouldn't cause a hang in normal operation. Still, it should be looked at.
Likely some of these apps are installed on the OS partition. If that's the case, the usual approach is to copy the folders to the data volume (generally into the existing /data/.apps folder) and replace the original folder with a soft link to the new one.
There are some other possibilities on space, so report back on the usage after you've moved the apps to the data volume.
Do you need all these services on the NAS? You probably should disable ones you aren't using (as they will take some memory resources). From a troubleshooting perspective, it is possible that the apps or maybe the services are causing or triggering the problem.
/apps and /home are mount points to the data volume, so the information there might be misleading.
It's best to do this by remounting to OS partition as /mnt, and then analyze space there. Among other things, that lets you see data hidden under the mount points.
# mount --bind / /mnt
If you connect USB drives to the NAS, then look in /mnt/media, which can sometimes have a lot of files that shouldn't be there.
Also, the OS file system is btrfs, so there are aspects of free space that du and df won't tell you. You should also use the btrfs commands here. For instance, btrfs fi du, and btrfs fi df.
