Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Manul]

I noticed today that my powered down DNS-320L started up when I reset my router. I also remember once before finding the device powered on without my intervention and I think I reset my router around the same time. Has anybody else experienced this behaviour?

[JavaLawyer]

Was your DNS-320L powered-down (completely off) or was the device on with the HDDs in hibernation mode? Any network activity that pings the DNS-320L may cause the HDDs to come out of hibernation.

[Manul]

According to my understanding, it was powered down completely (system was shut down from web interface).

[JavaLawyer]

If the DNS-320L is fully powered down, I don't think rebooting the router would impact the unit. You can perform a test by manually rebooting your router.

As far as I know, the only two instances where the DNS-320L should spontaneously power-up on it's own include: recovery from a power failure and scheduled power on/off (Web UI = System Management > Power Management).

[Manul]

Thanks for your reply. I just tried it again and observed the same behaviour:

• Shut down the DNS-320L from the web interface via System Management->System Settings->Shutdown
    -> result: device is powered down, no LEDs, no ping...
  
• rebooted my router (TP-Link TL-WR1043ND, DNS-320L connected directly to router)
    -> result: DNS-320L powers up and is fully accessible
  

Could somebody else please try this and report whether they can reproduce my findings? It's actually not a problem for me, but it could possibly be used as a kind of poor man's wake on lan.

[JavaLawyer]

    

[JavaLawyer]

Did you reboot the router by flipping a power strip containing the router + ShareCenter or did you perform a soft reboot from the router settings? I'm assuming you performed a soft reboot, but am exploring all possibilities.    

[Manul]

Sorry, I should have mentioned this: Yes, I did a soft reboot from the router's web interface.

[JavaLawyer]

Here's a test to make sure the DNS-320L is truly off:  After you power down the DNS-320L, did you try revisiting the web UI? If the unit is off, the web UI clearly shouldn't open.  Does anything come up?

After the unit is powered down. Remove the DNS-320L power cord for 15 seconds and then plug back in.  Next reboot the router and see what happens.

[Manul]

Yes, I did try the web UI. I also tried pinging the DNS-320L and ssh'ing into it. I believe the device was truly off. I will try disconnecting the power cord when I find the time, currently the DNS-320L is in use.

Thanks very much for trying to help figure out what happened. Have you tried reproducing my findings with your unit?

[JavaLawyer]

Yes, I did try the web UI. I also tried pinging the DNS-320L and ssh'ing into it. I believe the device was truly off. I will try disconnecting the power cord when I find the time, currently the DNS-320L is in use.

Thanks very much for trying to help figure out what happened. Have you tried reproducing my findings with your unit?

I don't personally own a DNS-320L, but have a couple of DNS-343s and DNS-345s.

[Manul]

Just tried it again:

• shut down DNS-320L from web UI
    -> no LEDs, device doesn't ping, no ssh access, web UI not responding
• unplug power cord, wait a little, replug it
    -> device does not power on; still no LEDs, ping, ssh, web UI
• reboot router from router's web UI
    -> DNS-320L starts up; ping, ssh access, web UI all work; files are accessible

[FurryNutz]

Any chance you can test this with a different router? Borrow one if possible?

[Manul]

Probably not anytime soon, sorry. Wouldn't know where to borrow one and, as I said, it's not really a problem, so no pressure to get to the bottom of this on my side.

Still, I'm curious: Has anybody else tried this and can confirm it doesn't happen with their device+router?