Moode Forum
[PROBLEM] Can't connect to NAS - Printable Version

+- Moode Forum (https://moodeaudio.org/forum)
+-- Forum: moOde audio player (https://moodeaudio.org/forum/forumdisplay.php?fid=3)
+--- Forum: Support (https://moodeaudio.org/forum/forumdisplay.php?fid=7)
+--- Thread: [PROBLEM] Can't connect to NAS (/showthread.php?tid=696)

Pages: 1 2 3 4

RE: Can't connect to NAS - julessilver - 12-16-2018

(12-13-2018, 04:49 PM)Tim Curtis Wrote: 1. Remove the NAS config
2. Verify via SSH that there is no subdirectories under /mnt/NAS and if there is then remove it
3. UPGRADE to moOde 4.4
4. Recreate the NAS config and specify Vers=3.0 (or whatever ver matches whats running on the NAS) in the mount flags

Thanks for the pointers Tim.
I tried to upgrade to 4.4 but it seemed to be having probs so I downloaded the 4.4 iso and cut it to a different SD.
Rebooted from scratch and now have permission denied (see pic). 
Which is again really strange as there is only one user with admin rights on everything.
And Volumio works fine (see pic).
I am obviously doing something really basically wrong but I cant see it. 
Essentially with the same hardware I can see the NAS with Volumio and not with Moode. 
I prefer the moode interface and I want to get this running instead of Volumio.

Let me know if you have any other ideas?

RE: Can't connect to NAS - Tim Curtis - 12-16-2018

Post a screen shot of NAS Config

RE: Can't connect to NAS - TheOldPresbyope - 12-16-2018

@julessilver

Are you comfortable using SSH to work from the command line of your moOde player? (moOde's builtin Web SSH Terminal works great.) Then, let's bypass moOde's NAS configuration panel.

From the command line, can you successfully ping the hostname SynNAS? Does the ping response include the IP address you expect (apparently 192.168.1.73)? 

Example: here's what I get pinging my server OMV-HC1 (note u/l-case doesn't matter in the hostname):

Code:
pi@moode:~ $ ping omv-hc1 -c 1
PING omv-hc1.fios-router.home (192.168.1.12) 56(84) bytes of data.
64 bytes from omv-hc1.fios-router.home (192.168.1.12): icmp_seq=1 ttl=64 time=3.50 ms

--- omv-hc1.fios-router.home ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 3.508/3.508/3.508/0.000 ms


From the command line you can test-mount your username/password-protected SMB share (note that u/l-case doesn't matter in hostname/share but it very much does matter in username and password):

Code:
mkdir /tmp/test
sudo mount -t cifs //<hostname or ip>/<sharename> /tmp/test -o username=xxx,password=yyy

# examples assuming the hostname is SynNAS, the IP address is 192.168.1.73,
# the username is jules, and the password is yyy
# sudo mount -t cifs //SynNAS/Music /tmp/test -o username=jules,password=yyy
# or
# sudo mount -t cifs //192.168.1.73/Music -o username=jules,password=yyy

NOTE ADDED IN EDIT: the mount command is a single line; reading my completed post in my browser it is folded at "-o" into two lines)

(If you leave off the password option, you'll be prompted for it; if you leave off the username option, interesting things happen if the share is protected).

If you can successfully mount it, then un-mount it with (note the odd spelling of the command)

Code:
sudo umount /tmp/test

If the username and/or password is wrong in the mount command, you should see---wait for it---"mount error (13), permission denied". This is what I see repeatedly in your log.

As for NFS, I don't use it but you can test in a similar way:

Code:
sudo mount -t nfs <hostname or ip>:/<sharename> /tmp/test <nfs-options>

Note that there's no nfs option for a username/password. you'll have to dig into NFS documentation to sort out how to deal with the raft of options (both on the server end and the client end).

Hope this helps.

Regards,
Kent

RE: Can't connect to NAS - Paul1 - 12-16-2018

hi Tim,

i updated to 4.4. from 3.2 moode

i have the same problem connecting my Synology NAS mounted. Either using IP or hostname, and either using vers=1 or vers=3.

SSH is working OK to the NAS en to pi 2B+.

I had no problem mounting in 3.2, but in 4.3 and 4.4. I cannot mount.

Paul

RE: Can't connect to NAS - Tim Curtis - 12-16-2018

Try turning on debug logging in System config, reboot and then examine moode.log for the mount string and any error messages that follow it. Post the mount string and errors and I'll have a look.

Code:
moodelog

Also post the output from the cmd below

Code:
sudo systemctl status smbd


-Tim

RE: Can't connect to NAS - Paul1 - 12-17-2018

(12-16-2018, 10:08 PM)Tim Curtis Wrote: Try turning on debug logging in System config, reboot and then examine moode.log for the mount string and any error messages that follow it. Post the mount string and errors and I'll have a look.

Code:
moodelog

Also post the output from the cmd below

Code:
sudo systemctl status smbd


-Tim

hi Tim,

Code:
20181217 213704 engine-mpd: Open socket
  20181217 213704 readMpdResponse(): reading response
  20181217 213704 readMpdResponse(): success $str=(OK MPD 0.20.0)
  20181217 213704 readMpdResponse(): success $resp[0]=(OK MPD 0.20.0)
  20181217 213704 engine-mpd: Get initial status
  20181217 213704 readMpdResponse(): reading response
  20181217 213704 readMpdResponse(): success $str=(OK)
  20181217 213704 readMpdResponse(): success $resp[0]=(volume: -1)
  20181217 213704 engine-mpd: UI state=(play), MPD state=(play)
  20181217 213704 engine-mpd: Idle
  20181217 213704 engine-mpd: Wait for idle timeout
  20181217 213704 readMpdResponse(): reading response
  20181217 213952 waitWorker(): Start (src-config, w_active=1)
  20181217 213953 waitWorker(): Wait  (1)
  20181217 213954 worker: Job sourcecfg
  20181217 213954 wrk_sourcemount(): mountstr=(mount -t cifs "//192.168.1.11/Share" -o username=admin,password='sy123456',rsize=61440,wsize=65536,iocharset=utf8,vers=3.0,ro,dir_mode=0777,file_mode=0777 "/mnt/NAS/moodeaudio")
  20181217 213954 wrk_sourcemount(): sysoutput=(mount error(95): Operation not supported
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs))
  20181217 213954 wrk_sourcemount(): Mount error: (mount error(95): Operation not supported
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs))
  20181217 213954 waitWorker(): Wait  (2)
  20181217 213954 waitWorker(): End   (src-config, w_active=0)
  20181217 213955 engine-mpd: Connect
  20181217 213955 engine-mpd: Session loaded
  20181217 213955 engine-mpd: Open socket
  20181217 213955 readMpdResponse(): reading response
  20181217 213955 readMpdResponse(): success $str=(OK MPD 0.20.0)
  20181217 213955 readMpdResponse(): success $resp[0]=(OK MPD 0.20.0)
  20181217 213955 engine-mpd: Get initial status
  20181217 213955 readMpdResponse(): reading response
  20181217 213955 readMpdResponse(): success $str=(OK)
  20181217 213955 readMpdResponse(): success $resp[0]=(volume: -1)
  20181217 213955 engine-mpd: UI state=(undefined), MPD state=(play)
  20181217 213955 engine-mpd: Generating enhanced metadata
  20181217 213955 readMpdResponse(): reading response
  20181217 213955 readMpdResponse(): success $str=(OK)
  20181217 213955 readMpdResponse(): success $resp[0]=(file: http://89.16.185.174:8000/stream)
  20181217 213955 enhanceMetadata(): Radio station
  20181217 213955 engine-mpd: Metadata returned to client: Size=(29)
  20181217 213955 engine-mpd: Connect
  20181217 213955 engine-mpd: Session loaded
  20181217 213955 engine-mpd: Open socket
  20181217 213955 readMpdResponse(): reading response
  20181217 213955 readMpdResponse(): success $str=(OK MPD 0.20.0)
  20181217 213955 readMpdResponse(): success $resp[0]=(OK MPD 0.20.0)
  20181217 213955 engine-mpd: Get initial status
  20181217 213955 readMpdResponse(): reading response
  20181217 213955 readMpdResponse(): success $str=(OK)
  20181217 213955 readMpdResponse(): success $resp[0]=(volume: -1)
  20181217 213955 engine-mpd: UI state=(play), MPD state=(play)
  20181217 213955 engine-mpd: Idle
  20181217 213955 engine-mpd: Wait for idle timeout
  20181217 213955 readMpdResponse(): reading response
  20181217 213957 worker: Job updmpddb
  20181217 213957 readMpdResponse(): reading response
  20181217 213957 readMpdResponse(): success $str=(OK MPD 0.20.0)
  20181217 213957 readMpdResponse(): success $resp[0]=(OK MPD 0.20.0)
  20181217 213957 readMpdResponse(): reading response
  20181217 213957 readMpdResponse(): success $str=(OK)
  20181217 213957 readMpdResponse(): success $str=(OK)
  20181217 213957 readMpdResponse(): success $resp[0]=(changed: update)
  20181217 213957 readMpdResponse(): success $resp[0]=(changed: update)
  20181217 213957 engine-mpd: resp[0]=(changed: update)
  20181217 213957 engine-mpd: resp[0]=(changed: update)
  20181217 213957 engine-mpd: Get new status
  20181217 213957 engine-mpd: Get new status
  20181217 213957 readMpdResponse(): reading response
  20181217 213957 readMpdResponse(): reading response
  20181217 213957 readMpdResponse(): success $str=(OK)
  20181217 213957 readMpdResponse(): success $str=(OK)
  20181217 213957 readMpdResponse(): success $str=(OK)
  20181217 213957 readMpdResponse(): success $resp[0]=(volume: -1)
  20181217 213957 readMpdResponse(): success $resp[0]=(volume: -1)
  20181217 213957 readMpdResponse(): success $resp[0]=(updating_db: 19)
  20181217 213957 engine-mpd: Idle timeout event=(changed: update)
  20181217 213957 engine-mpd: Idle timeout event=(changed: update)
  20181217 213957 engine-mpd: Generating enhanced metadata
  20181217 213957 engine-mpd: Generating enhanced metadata
  20181217 213957 readMpdResponse(): reading response
  20181217 213957 readMpdResponse(): reading response
  20181217 213957 readMpdResponse(): success $str=(OK)
  20181217 213957 readMpdResponse(): success $str=(OK)
  20181217 213957 readMpdResponse(): success $resp[0]=(file: http://89.16.185.174:8000/stream)
  20181217 213957 readMpdResponse(): success $resp[0]=(file: http://89.16.185.174:8000/stream)
  20181217 213957 enhanceMetadata(): Radio station
  20181217 213957 enhanceMetadata(): Radio station
  20181217 213957 engine-mpd: Metadata returned to client: Size=(31)
  20181217 213957 engine-mpd: Metadata returned to client: Size=(31)
  20181217 213957 engine-mpd: Connect
  20181217 213957 engine-mpd: Session loaded
  20181217 213957 engine-mpd: Open socket
  20181217 213957 readMpdResponse(): reading response
  20181217 213957 readMpdResponse(): success $str=(OK MPD 0.20.0)
  20181217 213957 readMpdResponse(): success $resp[0]=(OK MPD 0.20.0)
  20181217 213957 engine-mpd: Get initial status
  20181217 213957 readMpdResponse(): reading response
  20181217 213957 readMpdResponse(): success $str=(OK)
  20181217 213957 readMpdResponse(): success $resp[0]=(volume: -1)
  20181217 213957 engine-mpd: UI state=(play), MPD state=(play)
  20181217 213957 engine-mpd: Idle
  20181217 213957 engine-mpd: Wait for idle timeout
  20181217 213957 readMpdResponse(): reading response
  20181217 214015 readMpdResponse(): success $str=(OK)
  20181217 214015 readMpdResponse(): success $resp[0]=(changed: update)
  20181217 214015 engine-mpd: resp[0]=(changed: update)
  20181217 214015 engine-mpd: Get new status
  20181217 214015 readMpdResponse(): reading response
  20181217 214015 readMpdResponse(): success $str=(OK)
  20181217 214015 readMpdResponse(): success $resp[0]=(volume: -1)
  20181217 214015 engine-mpd: Idle timeout event=(changed: update)
  20181217 214015 engine-mpd: Generating enhanced metadata
  20181217 214015 readMpdResponse(): reading response
  20181217 214015 readMpdResponse(): success $str=(OK)
  20181217 214015 readMpdResponse(): success $resp[0]=(file: http://89.16.185.174:8000/stream)
  20181217 214015 enhanceMetadata(): Radio station
  20181217 214015 engine-mpd: Metadata returned to client: Size=(30)
  20181217 214015 engine-mpd: Connect
  20181217 214015 engine-mpd: Session loaded
  20181217 214015 engine-mpd: Open socket
  20181217 214015 readMpdResponse(): reading response
  20181217 214015 readMpdResponse(): success $str=(OK MPD 0.20.0)
  20181217 214015 readMpdResponse(): success $resp[0]=(OK MPD 0.20.0)
  20181217 214015 engine-mpd: Get initial status
  20181217 214015 readMpdResponse(): reading response
  20181217 214015 readMpdResponse(): success $str=(OK)
  20181217 214015 readMpdResponse(): success $resp[0]=(volume: -1)
  20181217 214015 engine-mpd: UI state=(play), MPD state=(play)
  20181217 214015 engine-mpd: Idle
  20181217 214015 engine-mpd: Wait for idle timeout
  20181217 214015 readMpdResponse(): reading response

and

Code:
Last login: Mon Dec 17 21:22:18 2018 from 192.168.1.13
pi@moode:~ $ sudo systemctl status smbd
● smbd.service - Samba SMB Daemon
  Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor preset: enabled)
  Active: active (running) since Sun 2018-12-16 17:10:45 CET; 1 day 4h ago
    Docs: man:smbd(8)
          man:samba(7)
          man:smb.conf(5)
Main PID: 537 (smbd)
  Status: "smbd: ready to serve connections..."
  CGroup: /system.slice/smbd.service
          ├─537 /usr/sbin/smbd
          ├─538 /usr/sbin/smbd
          └─539 /usr/sbin/smbd

Dec 16 17:10:44 moode systemd[1]: Starting Samba SMB Daemon...
Dec 16 17:10:45 moode systemd[1]: smbd.service: Supervising process 537 which is not our child. We'll most likely not notice when it ex
Dec 16 17:10:45 moode systemd[1]: Started Samba SMB Daemon.
Dec 16 17:10:45 moode smbd[537]: [2018/12/16 17:10:45.657391,  0] ../lib/util/become_daemon.c:124(daemon_ready)
Dec 16 17:10:45 moode smbd[537]:   STATUS=daemon 'smbd' finished starting up and ready to serve connections
(last message is in Red letter type)


Paul

RE: Can't connect to NAS - Tim Curtis - 12-17-2018

Hi Paul,

I don't see anything suspicious in the logs.

From googling "linux cifs operation not permitted", the error seems to arise when the vers= setting is not compatible with what the Samba server on the NAS accepts.

Beginning in Linux kernel 4.13.y all cifs mounts default to vers=3.0 unless its overridden in the mount command. moOde defaults to vers=1.0 for maximum compatibility but this can be changed in the mount flags on the NAS config screen.

-Tim

RE: Can't connect to NAS - TheOldPresbyope - 12-17-2018

@Paul1

Notice these lines in your log?

Code:
 20181217 213954 wrk_sourcemount(): sysoutput=(mount error(95): Operation not supported
 Refer to the mount.cifs(8) manual page (e.g. man mount.cifs))
 20181217 213954 wrk_sourcemount(): Mount error: (mount error(95): Operation not supported
 Refer to the mount.cifs(8) manual page (e.g. man mount.cifs))

They suggest a mismatch in protocol levels between your NAS and your moOde player. 

Here's a piece I extracted from a stackexchange post (https://unix.stackexchange.com/questions/144522/mounting-cifs-operation-not-supported

Quote:There are several different mount error messages which can be traced back to mismatched protocol level. A non-exhaustive list (feel free to edit answer and add more):

mount error(13): Permission denied
mount error(95): Operation not supported
mount error(121): Remote I/O error


You may have to experiment with the protocol level you specify in the NAS Config panel. Possible values include


Code:
vers=1.0
vers=2.0
vers=2.1
vers=3.0
vers=3.0.2
vers=3.1.1


(Apparently, the latest version 3.1.1 was introduced with Windows 10.)

I have no idea what values the Synology DSM O/S accepts. Their documentation is lacking in technical details.

Regards,
Kent

RE: Can't connect to NAS - Onionhead - 12-17-2018

No problems connecting NAS with moOde from 3.8 forward. I use a Synology DS415 Play and ORBI router. I have a mesh wi-fi network and never been able to get SAMBA scan to find my NAS so I use NFS only. Here are some suggestions for anyone interested in NFS config that works for me.

1. make sure the shared folder permission includes the pi running moOde
2. if possible setup an IP reservation for the pi running moOde
3. Edit server manually for example 10.0.0.39/volume1/Music  - Pay attention to upper lower case naming conventions
4. Clear browser cache
5. shutdown moOde and turn off pi. 
6. reboot router
7. powerup pi

RE: Can't connect to NAS - Paul1 - 12-18-2018

(12-17-2018, 09:36 PM)TheOldPresbyope Wrote: @Paul1

Notice these lines in your log?

Code:
 20181217 213954 wrk_sourcemount(): sysoutput=(mount error(95): Operation not supported
 Refer to the mount.cifs(8) manual page (e.g. man mount.cifs))
 20181217 213954 wrk_sourcemount(): Mount error: (mount error(95): Operation not supported
 Refer to the mount.cifs(8) manual page (e.g. man mount.cifs))

They suggest a mismatch in protocol levels between your NAS and your moOde player. 

Here's a piece I extracted from a stackexchange post (https://unix.stackexchange.com/questions/144522/mounting-cifs-operation-not-supported

Quote:There are several different mount error messages which can be traced back to mismatched protocol level. A non-exhaustive list (feel free to edit answer and add more):

mount error(13): Permission denied
mount error(95): Operation not supported
mount error(121): Remote I/O error


You may have to experiment with the protocol level you specify in the NAS Config panel. Possible values include


Code:
vers=1.0
vers=2.0
vers=2.1
vers=3.0
vers=3.0.2
vers=3.1.1


(Apparently, the latest version 3.1.1 was introduced with Windows 10.)

I have no idea what values the Synology DSM O/S accepts. Their documentation is lacking in technical details.

Regards,
Kent

Hi Kent,

Thanks for the information. I tried all these numbers of vers but did not succeed.

regards,
Paul