Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Unable to connect to samba share
#1
Hi All

New user here and some help would be much appreciated please.
Im unable to set up my source which is on a Samba share, this is on a Odroid HC1 with Openmediavault as the OS.  I can connect to this share from my other PC’s and phone but its not having any of it from MoOde.
Ive tried scanning through the forum for any answers and have tried several things from other threads with similar problems but to no avail.
I have tried changing the mount flags to all of these but that hasnt helped

vers=1.0,sec=ntlm,ro,dir_mode=0777,file_mode=0777
vers=1.0,sec=none,ro,dir_mode=0777,file_mode=0777
vers=2.0,sec=ntlm,ro,dir_mode=0777,file_mode=0777
vers=3.0,sec=ntlm,ro,dir_mode=0777,file_mode=0777
vers=2.0,sec=none,ro,dir_mode=0777,file_mode=0777
vers=3.0,sec=none,ro,dir_mode=0777,file_mode=0777
ro,dir_mode=0777,file_mode=0777

My share will show up If i scan for servers and i have also added it manually with no joy
Would somebody be able to give me a bit of advise.

Thanks in advance

Jason

Moode Log

Code:
20181129 092254 worker: - Start
20181129 092254 worker: Successfully daemonized
20181129 092254 worker: Session loaded
20181129 092254 worker: Debug logging (off)
20181129 092254 worker: - Platform
20181129 092255 worker: Host (moode)
20181129 092255 worker: Hdwr (Pi-3B 1GB v1.2)
20181129 092255 worker: Arch (armv7l)
20181129 092255 worker: Rasp (9.4)
20181129 092255 worker: Kver (4.14.72-v7+)
20181129 092255 worker: Ktyp (Standard)
20181129 092255 worker: Gov  (ondemand)
20181129 092255 worker: Rel  (Moode 4.3 2018-09-27)
20181129 092255 worker: Upd  (None)
20181129 092255 worker: MPD  (0.20.20)
20181129 092255 worker: USB boot not enabled yet
20181129 092255 worker: File system not expanded yet
20181129 092256 worker: HDMI port on
20181129 092256 worker: File check ok
20181129 092256 worker: - Network
20181129 092256 worker: eth0 exists
20181129 092256 worker: eth0 address not assigned
20181129 092256 worker: wlan0 exists
20181129 092256 worker: wifi country (GB)
20181129 092256 worker: wlan0 trying SSID (POPTELECOM)
20181129 092256 worker: wlan0 (192.168.1.8)
20181129 092256 worker: - Audio
20181129 092257 worker: ALSA outputs unmuted
20181129 092257 worker: ALSA card number (0)
20181129 092257 worker: Audio out (I2S audio device)
20181129 092257 worker: Audio dev (Allo Boss DAC)
20181129 092257 worker: ALSA mixer name (Digital)
20181129 092257 worker: MPD volume control (software)
20181129 092257 worker: Hdwr volume controller exists
20181129 092257 worker: Chip options (Burr Brown PCM5122)
20181129 092257 worker: - Services
20181129 092257 worker: Reset renderer active
20181129 092259 worker: MPD started
20181129 092259 worker: MPD scheduler policy (time-share)
20181129 092259 worker: Configure MPD outputs
20181129 092259 worker: MPD output 1 ALSA default (on)
20181129 092259 worker: MPD output 2 ALSA crossfeed (off)
20181129 092259 worker: MPD output 3 ALSA parametric eq (off)
20181129 092259 worker: MPD output 4 ALSA graphic eq (off)
20181129 092259 worker: MPD output 5 ALSA bluetooth (off)
20181129 092259 worker: MPD crossfade (off)
20181129 092259 worker: - Music sources
20181129 092259 worker: USB sources (none attached)
20181129 092259 worker: NAS sources (none configured)
20181129 092259 worker: - Miscellaneous
20181129 092259 worker: Volume level (0) restored
20181129 092259 worker: Maintenance interval (21600)
20181129 092259 worker: Screen saver activation (Never)
20181129 092259 worker: Watchdog started
20181129 092259 worker: Ready
20181129 092305 worker: Job i2sdevice
20181129 092833 worker: Job sourcecfg
20181129 092833 wrk_sourcemount(): Mount error: (mount error: could not resolve address for ODROIDXU4: Unknown error)
20181129 092833 src-config(): Job: updmpddb
20181129 092836 worker: Job updmpddb
20181129 094325 worker: Job sourcecfg
20181129 094325 wrk_sourcemount(): Mount error: (mount error: could not resolve address for ODROIDXU4: Unknown error)
20181129 094326 src-config(): Job: updmpddb
20181129 094328 worker: Job updmpddb
20181129 094333 wrk_sourcemount(): Mount error: (mount error: could not resolve address for ODROIDXU4: Unknown error)
20181129 094333 src-config: remount: (unmountall initiated, mountall initiated)
20181129 094429 worker: Job sourcecfg
20181129 094429 src-config(): Job: updmpddb
20181129 094432 worker: Job updmpddb
20181129 094535 worker: Job sourcecfg
20181129 094536 wrk_sourcemount(): Mount error: (mount error: could not resolve address for ODROIDXU4: Unknown error)
20181129 094536 src-config(): Job: updmpddb
20181129 094539 worker: Job updmpddb
20181129 094642 worker: Job sourcecfg
20181129 094642 wrk_sourcemount(): Mount error: (mount error: could not resolve address for ODROIDXU4: Unknown error)
20181129 094643 src-config(): Job: updmpddb
20181129 094645 worker: Job updmpddb
20181129 094743 worker: Job sourcecfg
20181129 094743 src-config(): Job: updmpddb
20181129 094746 worker: Job updmpddb
20181129 095011 worker: Job sourcecfg
20181129 095011 wrk_sourcemount(): Mount error: (Retrying with upper case share name
mount error(6): No such device or address
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs))
20181129 095012 src-config(): Job: updmpddb
20181129 095014 worker: Job updmpddb
20181129 095427 worker: Job sourcecfg
20181129 095428 wrk_sourcemount(): Mount error: (mount error(2): No such file or directory
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs))
20181129 095428 src-config(): Job: updmpddb
20181129 095431 worker: Job updmpddb
20181129 095552 worker: Job installupd
20181129 095552 updater: Downloading update package r43
20181129 095603 updater: Start 2018-10-19 update for moOde 4.3
20181129 095603 updater: ** Version check
20181129 095603 updater: ** Step 1-7: SQL updates
20181129 095604 updater: ** Step 2-7: Binary updates
20181129 095604 updater: ** Step 3-7: Code and Config updates
20181129 095604 updater: ** Step 4-7: Package updates...
20181129 095604 updater: ** Pkg 1 of 1: ethtool
20181129 095740 updater: ** Step 5-7: Kernel update to 4.14.76...
20181129 095828 updater: ** Step 6-7: Reset accent color to Alizarin
20181129 095828 updater: ** Step 7-7: Cached disk writes flushed
20181129 095828 updater: Update installed, REBOOT required
20181129 100721 worker: Job sourcecfg
20181129 100722 src-config(): Job: updmpddb
20181129 100725 worker: Job updmpddb
20181129 100755 worker: Job sourcecfg
20181129 100755 wrk_sourcemount(): Mount error: (mount error: could not resolve address for ODROIDXU4: Unknown error)
20181129 100755 src-config(): Job: updmpddb
20181129 100758 worker: Job updmpddb


Attached Files Thumbnail(s)
       
Reply
#2
Hi,

Try userid=Guest and a blank password.

Btw, i placed your log output in a code box for readability :-) the code box button is 3rd one from the right on the toolbar.

-Tim
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#3
Hi, @Riddik

As it happens, I've been running the same NAS (OMV on an HC1) for many months. I did nothing special with the OMV settings and the connection "just works" for me with the default moOde settings.

I'm away from my system at the moment so can comment only generally.

You show two screen captures, the first with the symbolic server name (ODROIDXU4) and the second with the numeric IP address for it (192....). You also show a moOde log which first shows a number of lines like

Code:
20181129 094325 worker: Job sourcecfg
20181129 094325 wrk_sourcemount(): Mount error: (mount error: could not resolve address for ODROIDXU4: Unknown error)


I assume these correspond to failed attempts to use the symbolic name. A quick test is to ssh into your moOde player and try to "ping ODROIDXU4" from it. If you get no response then your DNS system isn't resolving the name for moOde.

Then some minutes later I see

Code:
20181129 095011 worker: Job sourcecfg
20181129 095011 wrk_sourcemount(): Mount error: (Retrying with upper case share name
mount error(6): No such device or address

I assume this corresponds to a failed attempt to use the numeric IP address. The address has succeeded but the share name (Music) has failed.

I'm confused by your statement "My share will show up If i scan for servers". Does this mean using the moOde scan function? This should have automagically determined the server/share name to use. Did it return "ODROIDXU4/Music"?

Regards,
Kent
Reply
#4
(11-29-2018, 12:19 PM)Tim Curtis Wrote: Hi,

Try userid=Guest and a blank password.

Btw, i placed your log output in a code box for readability :-) the code box button is 3rd one from the right on the toolbar.

-Tim

Hi, Tim.

Latency means your answer slipped in while I was typing mine.

Credentials are of course another issue but I would have expected an error message in the log along the lines of "permission denied" if the rest of the NAS entries were correct but the userid and password were incorrect.

Regards,
Kent
Reply
#5
I would have expected same but there are several different errors in the log at various points so I just thought I'd start from scratch with userid Guest and a blank password. I think most Samba servers are configured to accept Guest logons and proxy them as root, something like that.

Code:
Mount error: (mount error: could not resolve address for ODROIDXU4: Unknown error)
Mount error: (Retrying with upper case share name mount error(6): No such device or address
Mount error: (mount error(2): No such file or directory
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#6
Thanks for your replies Tim & Kent.
Thanks for educating me on the code box Tim Smile
I will try userid=Guest and a blank password do i need to create a guest account on my Samba share?

Kent you asked
I'm confused by your statement "My share will show up If i scan for servers". Does this mean using the moOde scan function? This should have automagically determined the server/share name to use. Did it return "ODROIDXU4/Music"?

The answer to this is yes "ODROIDXU4/Music" was the name given once i had scanned for servers.
I will try and ssh into my moOde player and "ping ODROIDXU4" and see if i get a response.  I did indeed try using "ODROIDXU4/Music" firstly which was what Moode picked up when i scanned for servers and secondly i tried entering the server details manually "192.168.1.8/Music".

I will try the guest login and try and ping the ODROID from the Moode player as suggested is there anything else i can do or provide which may help me find out what the problem is?...thanks for your help

Jason
Reply
#7
Don't create a userid named Guest on your server. The smb.conf on your server most likely has something similar to the settings below. 

Code:
map to guest = Bad User
guest account = root

-Tim
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#8
@Riddik

I assume you are configuring OpenMediaVault (OMV) through its Web-based interface. This automagically fills in the smb.conf values Tim is talking about.

In this interface, OMV offers three choices for a shared folder:
  • Public - No
    requires username/password entry; these must be valid OMV credentials [NOTE: this is the mode I'm using]. This mode successfully mounts for me in moOde.
  • Public - Guests allowed
    requires username/password entry OR username Guest. This mode successfully mounts for me in moOde as username Guest with no password. (It also mounted when I tried username Guest with password Guest.) Of course, it mounts using a legitimate username/password.
  • Public - Guests only
    hmmm - I thought this meant only Guests could access, but I just created a test share with this choice and then successfully mounted it in moOde using a legitimate username/password...must reread docs.
I thought since you had entered a username/password, you were using credentials known to OMV. If they were wrong, you should have seen an error message in moode.log like

Code:
20181129 122343 worker: Job sourcecfg
20181129 122343 wrk_sourcemount(): Mount error: (mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs))
20181129 122343 src-config(): Job: updmpddb


As for the server/share name issue, the default setting for OMV is to return the hostname of the SMB server. The reason I suggested the ping test is that your LAN's DNS may not be resolving an address for the bare hostname. That could explain your first moode.log error. If the default setting has been changed (netbios names don't have to be the same as the hostname) then for sure there'd be a problem.


However, I'm flummoxed by your second error which suggests that you reached the NAS (via its IP address) but it rejected the share name "Music" which you say the scan returned.

Regards,
Kent
Reply
#9
Hi
OK i have tried to log into the MOode source screen with userID Guest and no password and this didn't work.
I have used Putty to SSH into the MOode Player and tried to ping my ODROIDXU4 (IP address 192.168.1.8 which i made static on my router) and this had replied fine.

This is the MOode log from this morning after trying the Guest login
Code:
20181129 101501 worker: - Start
20181129 101501 worker: Successfully daemonized
20181129 101501 worker: Integrity check ok
20181129 101501 worker: Session loaded
20181129 101501 worker: Debug logging (off)
20181129 101501 worker: - Platform
20181129 101503 worker: Host (moode)
20181129 101503 worker: Hdwr (Pi-3B 1GB v1.2)
20181129 101503 worker: Arch (armv7l)
20181129 101503 worker: Rasp (9.4)
20181129 101503 worker: Kver (4.14.76-v7+)
20181129 101503 worker: Ktyp (Standard)
20181129 101503 worker: Gov  (ondemand)
20181129 101503 worker: Rel  (Moode 4.3 2018-09-27)
20181129 101503 worker: Upd  (2018-10-19)
20181129 101503 worker: MPD  (0.20.20)
20181129 101503 worker: USB boot not enabled yet
20181129 101503 worker: File system not expanded yet
20181129 101503 worker: HDMI port on
20181129 101503 worker: File check ok
20181129 101503 worker: - Network
20181129 101503 worker: eth0 exists
20181129 101503 worker: eth0 address not assigned
20181129 101503 worker: wlan0 exists
20181129 101503 worker: wifi country (GB)
20181129 101503 worker: wlan0 trying SSID (POPTELECOM)
20181129 101503 worker: wlan0 (192.168.1.8)
20181129 101504 worker: - Audio
20181129 101504 worker: ALSA outputs unmuted
20181129 101504 worker: ALSA card number (0)
20181129 101504 worker: Audio out (I2S audio device)
20181129 101504 worker: Audio dev (Allo Boss DAC)
20181129 101504 worker: ALSA mixer name (Digital)
20181129 101504 worker: MPD volume control (software)
20181129 101504 worker: Hdwr volume controller exists
20181129 101504 worker: Chip options (Burr Brown PCM5122)
20181129 101504 worker: - Services
20181129 101504 worker: Reset renderer active
20181129 101506 worker: MPD started
20181129 101506 worker: MPD scheduler policy (time-share)
20181129 101506 worker: Configure MPD outputs
20181129 101506 worker: MPD output 1 ALSA default (on)
20181129 101506 worker: MPD output 2 ALSA crossfeed (off)
20181129 101506 worker: MPD output 3 ALSA parametric eq (off)
20181129 101506 worker: MPD output 4 ALSA graphic eq (off)
20181129 101506 worker: MPD output 5 ALSA bluetooth (off)
20181129 101506 worker: MPD crossfade (off)
20181129 101506 worker: - Music sources
20181129 101506 worker: USB sources (none attached)
20181129 101507 wrk_sourcemount(): Mount error: (mount error: could not resolve address for ODROIDXU4: Unknown error)
20181129 101507 worker: NAS sources (mountall initiated)
20181129 101507 worker: - Miscellaneous
20181129 101507 worker: Volume level (0) restored
20181129 101507 worker: Maintenance interval (21600)
20181129 101507 worker: Screen saver activation (Never)
20181129 101507 worker: Watchdog started
20181129 101507 worker: Ready
20181130 092916 worker: Job sourcecfg
20181130 092917 src-config(): Job: updmpddb
20181130 092919 worker: Job updmpddb
20181130 093041 worker: Job sourcecfg
20181130 093041 wrk_sourcemount(): Mount error: (mount error: could not resolve address for ODROIDXU4: Unknown error)
20181130 093041 src-config(): Job: updmpddb
20181130 093044 worker: Job updmpddb

I can move data between all PC's Windows & Linux to this share using User jason & Password jason

I have indeed been using (OMV) through its Web-based interface, Perhaps i need to change the settings of the share within OMV to "Public - No" as Kent has suggested?


Attached Files Thumbnail(s)
       
Reply
#10
(11-30-2018, 09:54 AM)Riddik Wrote: Hi
OK i have tried to log into the MOode source screen with userID Guest and no password and this didn't work.
I have used Putty to SSH into the MOode Player and tried to ping my ODROIDXU4 (IP address 192.168.1.8 which i made static on my router) and this had replied fine.

This is the MOode log from this morning after trying the Guest login
Code:
20181129 101501 worker: - Start
20181129 101501 worker: Successfully daemonized
20181129 101501 worker: Integrity check ok
20181129 101501 worker: Session loaded
20181129 101501 worker: Debug logging (off)
20181129 101501 worker: - Platform
20181129 101503 worker: Host (moode)
20181129 101503 worker: Hdwr (Pi-3B 1GB v1.2)
20181129 101503 worker: Arch (armv7l)
20181129 101503 worker: Rasp (9.4)
20181129 101503 worker: Kver (4.14.76-v7+)
20181129 101503 worker: Ktyp (Standard)
20181129 101503 worker: Gov  (ondemand)
20181129 101503 worker: Rel  (Moode 4.3 2018-09-27)
20181129 101503 worker: Upd  (2018-10-19)
20181129 101503 worker: MPD  (0.20.20)
20181129 101503 worker: USB boot not enabled yet
20181129 101503 worker: File system not expanded yet
20181129 101503 worker: HDMI port on
20181129 101503 worker: File check ok
20181129 101503 worker: - Network
20181129 101503 worker: eth0 exists
20181129 101503 worker: eth0 address not assigned
20181129 101503 worker: wlan0 exists
20181129 101503 worker: wifi country (GB)
20181129 101503 worker: wlan0 trying SSID (POPTELECOM)
20181129 101503 worker: wlan0 (192.168.1.8)
20181129 101504 worker: - Audio
20181129 101504 worker: ALSA outputs unmuted
20181129 101504 worker: ALSA card number (0)
20181129 101504 worker: Audio out (I2S audio device)
20181129 101504 worker: Audio dev (Allo Boss DAC)
20181129 101504 worker: ALSA mixer name (Digital)
20181129 101504 worker: MPD volume control (software)
20181129 101504 worker: Hdwr volume controller exists
20181129 101504 worker: Chip options (Burr Brown PCM5122)
20181129 101504 worker: - Services
20181129 101504 worker: Reset renderer active
20181129 101506 worker: MPD started
20181129 101506 worker: MPD scheduler policy (time-share)
20181129 101506 worker: Configure MPD outputs
20181129 101506 worker: MPD output 1 ALSA default (on)
20181129 101506 worker: MPD output 2 ALSA crossfeed (off)
20181129 101506 worker: MPD output 3 ALSA parametric eq (off)
20181129 101506 worker: MPD output 4 ALSA graphic eq (off)
20181129 101506 worker: MPD output 5 ALSA bluetooth (off)
20181129 101506 worker: MPD crossfade (off)
20181129 101506 worker: - Music sources
20181129 101506 worker: USB sources (none attached)
20181129 101507 wrk_sourcemount(): Mount error: (mount error: could not resolve address for ODROIDXU4: Unknown error)
20181129 101507 worker: NAS sources (mountall initiated)
20181129 101507 worker: - Miscellaneous
20181129 101507 worker: Volume level (0) restored
20181129 101507 worker: Maintenance interval (21600)
20181129 101507 worker: Screen saver activation (Never)
20181129 101507 worker: Watchdog started
20181129 101507 worker: Ready
20181130 092916 worker: Job sourcecfg
20181130 092917 src-config(): Job: updmpddb
20181130 092919 worker: Job updmpddb
20181130 093041 worker: Job sourcecfg
20181130 093041 wrk_sourcemount(): Mount error: (mount error: could not resolve address for ODROIDXU4: Unknown error)
20181130 093041 src-config(): Job: updmpddb
20181130 093044 worker: Job updmpddb

I can move data between all PC's Windows & Linux to this share using User jason & Password jason

I have indeed been using (OMV) through its Web-based interface, Perhaps i need to change the settings of the share within OMV to "Public - No" as Kent has suggested?

IMHO : This looks like a DNS error. Even if ping is working, doesn't mean that other could resolve the name. Also try the full qualified name e.g. ODROIDXU4.home.org - whatever your domain is. Or you try ODROIDXU4.local when you also use Zeroconfig in your environmenmt , the SMB might use this a s advertizing.
Reply


Forum Jump: