DS218play periodically loses network connection, can't be reached - how to reboot and how to fix?

Currently reading
DS218play periodically loses network connection, can't be reached - how to reboot and how to fix?

2
0
NAS
DS218play
Operating system
Linux, macOS, Windows
Mobile operating system
Android, iOS
My DS218play periodically enters a state where it can't be reached over the network. File share, web browser control panel, the Synology tool, ping from the command line, nothing reaches it. The status lights seem normal. Status, Disk1 and Disk2 are solid green, LAN flickers green, power is solid Blue. When I say "periodically" I mean it'll happen after a month or so with no issues. I don't use the NAS every day so it's hard to pinpoint when it happens. I'm not receiving any emails from it with status alerts. When I hard-reboot it and go back into disk station manager, everything says it's healthy. I turned off the disk hibernation but it still happens.

When I try to reboot it by holding down the power button, the power light flashes green, but I don't hear a beep. The power light continues flashing green. It will stay like this for weeks until I give up and cut power.

So... a couple questions:

1. why is this happening? Is it normal for these to go offline like this?
2. how do I troubleshoot it..? are there more verbose logging/notification options I could try?
3. is there a better way to reboot? I don't need continuous uptime, I use it in my home office to archive large files that I don't use on a regular basis, I just need to be able to turn it on and get the files when I need them :(
 
10
2
NAS
DS411+II, DS412+, DS418Play, DS216+II, DS218+ DS918+
Router
RT1900ac
Operating system
macOS, Windows
Mobile operating system
Android, iOS
Did you create a ticket on this? You should
To take out "wrong software", I suggest to take your data from the NAS, diskpart-clean your NAS disks and start from scratch with installing DSM. Do the minimal to work with it for a while to test. If it re-occurs there is a big change it is failure in hardware.
But again, create a ticket first
 
10
2
NAS
DS411+II, DS412+, DS418Play, DS216+II, DS218+ DS918+
Router
RT1900ac
Operating system
macOS, Windows
Mobile operating system
Android, iOS
- a NAS is build to be on power 24/7.
- there is in my opinion no other way to bring it down when it is stuck like you describe
 

fredbert

Moderator
Supporter
941
387
You've manually configured the LAN IP and other network settings of the NAS?

If you know your NAS's MAC address you can launch the Mac Terminal app and run an arp -na command to see what devices are seen. The '-na' will show the current IP address that corresponds to each MAC address. When the NAS becomes unresponsive again you can run this again.
 

jeyare

Moderator
Supporter
903
338
NAS
1811+, 3x 1813+, 718+, 214play ... multisite Ubiquiti Unifi networks (USG-Pro,PoE,NanoHD)
Operating system
Linux, Windows
Mobile operating system
Android, iOS
You don’t need provide any clean of data at this moment - @GuiMSP pls. be aware that this isn’t a good approach in first level of problem analysis
as @fredbert wrote, we need more inputs:
- what is your LAN setup (NAS, Gateway, switch, devices connected to NAS), dynamic/static IP, protocols,...
- OS of devices connected to the NAS
Maybe a screenshot from your NAS network setup.
It will helps us to better understand your situation.
 
2
0
NAS
DS218play
Operating system
Linux, macOS, Windows
Mobile operating system
Android, iOS
Hi, thanks for the suggestions.

Router: Asus RT-AC68P

NAS is connected by ethernet

PC laptop and Mac laptop are connected by Wifi. Main OS I use to connect to the NAS is Windows 10.

IP is dynamic. I notice the router does consistently assign the NAS the same IP (192.168.1.34) when I cycle the power on it. Would giving it a static IP help? When I have this issue of not being able to connect to the NAS, it doesn't appear in the router's network map client list, so I figured if it was just a problem of the IP changing at least it'd still be listed there..?

NAS settings: default gateway is 192.168.1.1, subnet mask 255.255.255.0, DSM ports are 5000/5001

Protocols: mostly CIFS/SMB, some AFP. (not sure if that's what you're asking?)

Thanks for the tip about arp, I ran that and wrote down the MAC address and I'll try it again next time it becomes unresponsive.

Now here's something interesting. I found the logs, and can see where the events occur where I'm cycling the power:

1581847516699.png


the interesting thing is that this sequence of boot messages appears a number of other places, where I did not manually reboot the NAS. System started to boot up, System booted up from an improper shutdown, failed to send email, service was started. So that suggests first I need to fix the settings for having it email me :) and second that it's rebooting itself (or maybe losing power?) at times that I don't know about.
 

jeyare

Moderator
Supporter
903
338
NAS
1811+, 3x 1813+, 718+, 214play ... multisite Ubiquiti Unifi networks (USG-Pro,PoE,NanoHD)
Operating system
Linux, Windows
Mobile operating system
Android, iOS
Sorry for a delay, now I'm back from winter digital silence break.
Step by step to your problems

First problem group:

My DS218play periodically enters a state where it can't be reached over the network. File share, web browser control panel, the Synology tool, ping from the command line, nothing reaches it. ... When I say "periodically" I mean it'll happen after a month or so with no issues. I don't use the NAS every day so it's hard to pinpoint when it happens. I'm not receiving any emails from it with status alerts. When I hard-reboot it and go back into disk station manager, everything says it's healthy.
then you wrote:
NAS is connected by ethernet
PC laptop and Mac laptop are connected by Wifi. Main OS I use to connect to the NAS is Windows 10.
IP is dynamic. I notice the router does consistently assign the NAS the same IP (192.168.1.34) when I cycle the power on it. Would giving it a static IP help? When I have this issue of not being able to connect to the NAS, it doesn't appear in the router's network map client list, so I figured if it was just a problem of the IP changing at least it'd still be listed there..?

NAS settings: default gateway is 192.168.1.1, subnet mask 255.255.255.0, DSM ports are 5000/5001

Protocols: mostly CIFS/SMB, some AFP. (not sure if that's what you're asking?)
So, follow your description written above I have few recommendations:
- it's better to use fixed IP for the NAS, rater than dynamic, e.g. when you need map the Shared folders as another drive in your W10. Take it as must.

More important:
1. Download Security check list and check your NAS weak setup (e.g. port 5000/5001). This is mandatory setup of your NAS, if you don't need unexpected visitors.

For better understanding of your problem - you have to better describe the situations when you can't access your NAS.
1. Your statement: File share, web browser control panel, the Synology tool, ping from the command line, nothing reaches it.
It does mean:
a) File Share - you can't access your NAS by MS Explorer (Network section)? Did you see the NAS in the Network devices list and you can't connect it (by 2-click)? Pls. explain it.
b) Web Browser - when you aren't sure about the NAS address you can download (free) Advanced IP Scanner. Link Then you need just setup your LAN addresses range for the Scan:
1582393368993.png

it will help you definitely find every device in your LAN. By right click on the device list (found by Scan) you can use Explore feature to direct connection:
1582393542612.png


It will help you to prevent situation, when Synology tool (Synology Assistant) can't find the NAS (sometimes it happens).

When you can't find the NAS in router devices list (especially in your Asus) don't take it seriously. Asus has a golden medal for an accuracy.

Your statement: When I hard-reboot it and go back into disk station manager, everything says it's healthy.
Did you mean that the NAS is discoverable by MS Explorer, browser, ping, ... ? Still in the same address?

Re protocols:
- right setup of the SMB is frequently the reason of connection problems (discovery, speed, ...). But you need fixed the IP address first.
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Latest posts

Top