[mdlug] Mounting NAS volume / Wake-On-Lan problem

[Carl T. Miller]

My guess is that the "Host is down" means that it can't
connect using SMB3.  I would check the configuration
of samba on the pi to see if it's possible to enable SMB2.
Most likely the option is there, but it contains a warning
that SMB2 is not safe on untrusted networks.

Incidentally, the wake-on-lan feature provides a way
to turn on a device remotely.  My understanding is that
it cannot wake a device which is in sleep mode.  I've
never heard of a NAS going into sleep mode.  Is it
possible to disable that?

c


On 1/22/20 10:16 AM, email5000 at usa.com wrote:
> Perhaps someone can shed some light on a problem mounting my NAS volume
> on the Pi.
>
> I've had it working before on the Pi, but am having trouble with it now.
> The command I'm using is:
>     mount -t cifs //192.168.0.1/Volume_1    /media/Drive_Z .... (The
> folder Drive_Z DOES exist on the Pi; and the NAS volume is an NTFS file
> system)
>
> The error message is:
>     mount error (112): Host is down
>
> At first I thought it was because it was asleep (the main power-up light
> was not on, but the other physical drive lights were on dim - consistent
> with sleep mode), so I figured I'd try to wake it up.  I've done some
> research and found a couple of utilities that SHOULD wake the device,
> and I've tried both (wakeonlan, etherwake), and, yes I followed the
> instructions (I believe), correctly, and each utility's response to
> invocation states that the message has been sent; but it doesn't appear
> to awakem. Now, the obvious prelude to all this is that the device has
> the ability to wake up when accessed (and of course being a NAS, it
> SHOULD), and which it MUST have, since it works just fine in Windows
> (XP, 10) and even an old version of OSX (from years ago).
>
> I did power up the windows machine and accessed the volume using Win 10
> again - the NAS main power light is now on, and I can do directory
> listings (in Windows), but RPi still says it's down - even when being
> accesses by Windows.
>
> What am I missing?
>
> One thought that just occurred to me is the issue with Samba - I've had
> problems in the past between various Linux distros and the NAS. My
> understanding is the NAS will handle up to SMB2 (correct terminology ?).
> Apparently there is no further updated OE OS to make it SMB3 compliant.
> The Pi has been updated/upgraded since I've accessed the NAS with it,
> which I understand is upgraded to SMB3 and is not 'down-gradable' to (or
> compliant with) SMB2. So would that difference cause Raspbian to think
> that the host (NAS) is asleep?
>
> Thanks for your help,
> -Rich Hall
>