Thank you for your donation!


Cannot mount to Synology NAS
#1
I have try to mount to my Synology NAS and so far cannot get to mount.

Can anyone please help me?

Thanks


Attached Files Thumbnail(s)
   
Reply
#2
(07-05-2019, 02:13 AM)willytom Wrote: I have try to mount to my Synology NAS and so far cannot get to mount.

Can anyone please help me?

Thanks

@willytom

There's not enough information in your post to be able to help directly. [1] You don't even mention the version of moOde you are running.

Is that IP address correct for your NAS and is the published share named "music"? Do you really have a user named "Music" on your NAS and does that user own the share named "music"? All that's what your attached screenshot says.

Have you been able to access this share from any other computer on your LAN using these credentials---a Mac or a Windows system for example?

I don't own a Synology NAS but for testing purposes, I've spun up the Synology DSM software in a virtual host. Candidly, I thought their configuration instructions were confusing, but once I got it set up I had no difficulty accessing either Samba or NFS shares from moOde.

Regards,
Kent

[1] Yes, the NAS mount error messages are somewhat inscrutable. Nevertheless, you should include the moode.log in your post.
Reply
#3
User id....admin?
Reply
#4
I am using Moode 5.31 version. On the Synology I did create an account name Music and password. 
The NAS IP is 192.168.1.20 and there is a folder name Music where I stored all the music files.
I can login into the NAS with my Mac with the credential Music and password with no problem at all.

Thanks for your help.

log.................

20190705 224434 worker: - Start
20190705 224434 command/moode: Connection to MPD failed
20190705 224437 command/moode: Connection to MPD failed
20190705 224439 worker: Successfully daemonized
20190705 224439 worker: Integrity check (passed)
20190705 224440 worker: ALSA volume set to (0%)
20190705 224440 worker: Session loaded
20190705 224440 worker: Debug logging (off)
20190705 224440 worker: - Platform
20190705 224442 worker: Rel  (Moode 5.3.1 2019-06-12)
20190705 224442 worker: Upd  (None)
20190705 224442 worker: Rasp (9.9)
20190705 224442 worker: Kern (4.19.49-v7+)
20190705 224442 worker: MPD  (0.20.23)
20190705 224442 worker: Host (moode)
20190705 224442 worker: Hdwr (Pi-3B+ 1GB v1.3)
20190705 224442 worker: Arch (armv7l)
20190705 224442 worker: Gov  (performance)
20190705 224442 worker: USB boot enabled
20190705 224442 worker: File system expanded
20190705 224442 worker: HDMI port on
20190705 224442 worker: File check ok
20190705 224442 worker: - Network
20190705 224442 worker: eth0 exists
20190705 224442 worker: eth0 (192.168.1.110)
20190705 224442 worker: wlan0 exists
20190705 224442 worker: wifi country (US)
20190705 224442 worker: wlan0 SSID is blank
20190705 224442 worker: eth0 addr exists, AP mode not started
20190705 224442 worker: wlan0 address not assigned
20190705 224442 command/moode: Connection to MPD failed
20190705 224442 worker: - Audio
20190705 224443 worker: ALSA outputs unmuted
20190705 224443 worker: ALSA card number (0)
20190705 224443 worker: Audio output (I2S audio device)
20190705 224443 worker: Audio device (HiFiBerry DAC+ Pro)
20190705 224443 worker: ALSA mixer name (Digital)
20190705 224443 worker: MPD volume control (software)
20190705 224443 worker: Hdwr volume controller exists
20190705 224443 worker: Chip options (Burr Brown PCM5122)
20190705 224443 worker: - Services
20190705 224443 worker: Reset renderer active state
20190705 224443 worker: MPD conf updated
20190705 224443 worker: MPD started
20190705 224443 worker: MPD accepting connections
20190705 224443 worker: Configure MPD outputs
20190705 224444 worker: MPD output 1 ALSA default (on)
20190705 224444 worker: MPD output 2 ALSA crossfeed (off)
20190705 224444 worker: MPD output 3 ALSA parametric eq (off)
20190705 224444 worker: MPD output 4 ALSA graphic eq (off)
20190705 224444 worker: MPD output 5 ALSA polarity inversion (off)
20190705 224444 worker: MPD output 6 ALSA bluetooth (off)
20190705 224444 worker: MPD output 7 HTTP stream (off)
20190705 224444 worker: MPD crossfade (off)
20190705 224444 worker: Audio source (Local)
20190705 224444 worker: Output device (Local)
20190705 224444 worker: - Music sources
20190705 224444 worker: USB sources (none attached)
20190705 224444 worker: NAS sources (none configured)
20190705 224444 worker: - Miscellaneous
20190705 224444 worker: Saved MPD vol level (0)
20190705 224444 worker: Preamp volume level (0)
20190705 224444 worker: MPD volume level (0) restored
20190705 224444 worker: ALSA volume level (100%)
20190705 224444 worker: Auto-play is off
20190705 224444 worker: LocalUI started
20190705 224444 worker: Maintenance interval (21600)
20190705 224444 worker: Screen saver activation (Never)
20190705 224444 worker: Watchdog started
20190705 224444 worker: Ready
20190705 224557 worker: Job sourcecfg
20190705 224557 sourceMount(): Mount error: (mount error(95): Operation not supported
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs))
20190705 224600 worker: Job updmpddb
Reply
#5
@willytom

It's been a while since I explored the various errors thrown during an SMB mount, but IIRC that opaque message "mount error(95): Operation not supported" means your server is refusing your request to connect using the SMBv1 protocol ("vers=1.0" in your Mount flags string).

As stated under Mount flags, you may need to try vers=2.0 or 3.0 to match with your server. [Google is your friend if you really want the lowdown on Samba/SMB. Bottom line: you have to know your systems.]

This protocol versions issue has been discussed before and various changes proposed to make the process more seamless. I suspect there's an item somewhere in Tim's endless ToDo list about it.

Regards,
Kent
Reply


Forum Jump: