[PROBLEM] NAS unmount

[anburg]

hi all
with the 7.2.1 every time i reboot or power off, the NAS unmount and if play the last song i have this error:

Failed to decode /var/lib/mpd/music/NAS/NAS/Hip Hop Rap/Marracash - Marracash (2008)/03 - Dritto Al Punto.mp3; Failed to open '/var/lib/mpd/music/NAS/NAS/Hip Hop Rap/Marracash - Marracash (2008)/03 - Dritto Al Punto.mp3': No such file or directory

I must re Mount the nas and update Library for work. 
thanks and sorry for my English


bye

[Tim Curtis]

Reboot and then post the Moode startup log and the output from the mount command.

Code:

moodeutl -l

mount

[anburg]

Reboot and then post the Moode startup log and the output from the mount command.

Code:

moodeutl -l

mount

hi thanks for the reply

Code:

pi@moode:~ $ moodeutl -l
20210620 165214 worker: -- Start
20210620 165214 worker: Successfully daemonized
20210620 165214 worker: Integrity check (passed)
20210620 165215 worker: File check (OK)
20210620 165215 worker: Session vacuumed
20210620 165216 worker: Session loaded
20210620 165216 worker: Debug logging (OFF)
20210620 165216 worker: -- Audio debug
20210620 165216 worker: ALSA cards: (0:sndrpihifiberry | 1:empty | 2:empty | 3:empty
20210620 165216 worker: MPD config: (0:HiFiBerry Digi+ Pro | mixer:(none) | card:0)
20210620 165216 worker: ALSA mixer actual (none)
20210620 165216 worker: ALSA volume (none)
20210620 165216 worker: -- System
20210620 165217 worker: Host     (moode)
20210620 165217 worker: moOde    (7.2.1 2021-05-06)
20210620 165217 worker: RaspiOS  (10.6)
20210620 165217 worker: Kernel   (5.4.77-v7l+ #1371)
20210620 165217 worker: Platform (Pi-4B 1.1 4GB)
20210620 165217 worker: ARM arch (armv7l, 32-bit kernel)
20210620 165217 worker: MPD ver  (0.22.6_p0x3)
20210620 165217 worker: CPU gov  (ondemand)
20210620 165217 worker: USB boot not available
20210620 165217 worker: File system not expanded yet
20210620 165217 worker: HDMI port off
20210620 165217 worker: -- Network
20210620 165217 worker: eth0 exists
20210620 165217 worker: IP addr (192.168.1.15)
20210620 165217 worker: Netmask (255.255.255.0)
20210620 165217 worker: Gateway (192.168.1.1)
20210620 165217 worker: Pri DNS (8.8.8.8)
20210620 165217 worker: Domain  (192.168.1.27)
20210620 165217 worker: wlan0 exists
20210620 165217 worker: wifi country (US)
20210620 165217 worker: wlan0 SSID is blank
20210620 165217 worker: eth0 addr exists, AP mode not started
20210620 165217 worker: wlan0 address not assigned
20210620 165217 worker: Pi integrated wlan0 power save disabled
20210620 165217 worker: -- Audio config
20210620 165218 worker: MPD conf updated
20210620 165218 worker: ALSA card number (0)
20210620 165218 worker: MPD audio output (HiFiBerry Digi+ Pro)
20210620 165218 worker: Audio formats (S16_LE, S24_LE)
20210620 165218 worker: ALSA mixer name (none)
20210620 165218 worker: MPD volume control (software)
20210620 165218 worker: Hdwr volume controller not detected
20210620 165218 worker: ALSA loopback (On)
20210620 165218 worker: Reset renderer active flags
20210620 165218 worker: CamillaDSP (off)
20210620 165218 worker: -- MPD startup
20210620 165218 worker: MPD started
20210620 165219 worker: MPD accepting connections
20210620 165219 worker: MPD output 1 ALSA Default (on)
20210620 165219 worker: MPD output 2 ALSA Bluetooth (off)
20210620 165219 worker: MPD output 3 HTTP Server (off)
20210620 165219 worker: MPD crossfade (off)
20210620 165219 worker: MPD ignore CUE files (no)
20210620 165219 worker: -- Feature availability
20210620 165219 worker: Source select (available)
20210620 165219 worker: Source select (source: MPD)
20210620 165219 worker: Source select (output: HiFiBerry Digi+ Pro)
20210620 165219 worker: Bluetooth (available)
20210620 165219 worker: Airplay renderer (available)
20210620 165219 worker: Spotify renderer (available)
20210620 165219 worker: Squeezelite (available)
20210620 165219 worker: RoonBridge renderer (not installed)
20210620 165219 worker: UPnP renderer (available)
20210620 165219 worker: DLNA server (available)
20210620 165219 worker: UPnP browser (available)
20210620 165219 worker: GPIO button handler (available)
20210620 165219 worker: Stream recorder (n/a)
20210620 165219 worker: -- Music sources
20210620 165219 worker: USB sources (none attached)
20210620 165227 sourceMount(): Mount error: (mount error(2): No such file or directory
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs))
20210620 165227 worker: NAS and UPnP sources (mountall initiated)
20210620 165227 worker: -- Other
20210620 165227 worker: USB volume knob (Off)
20210620 165227 worker: USB auto-mounter (udisks-glue)
20210620 165227 worker: LED0 (On)
20210620 165227 worker: LED1 (On)
20210620 165227 worker: Saved MPD vol level (0)
20210620 165227 worker: Preamp volume level (0)
20210620 165227 worker: MPD volume level (97) restored
20210620 165227 worker: ALSA volume level (None)
20210620 165227 worker: Auto-play (Off)
20210620 165227 worker: Maintenance interval (3 hours)
20210620 165227 worker: Screen saver activation (Never)
20210620 165227 worker: Session permissions (OK)
20210620 165227 worker: Watchdog started
20210620 165227 worker: Ready

and

Code:

pi@moode:~ $ mount
/dev/mmcblk0p2 on / type ext4 (rw,noatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=1926296k,nr_inodes=147021,mode=755)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,relatime)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=29,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
/dev/mmcblk0p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=392016k,mode=700,uid=1000,gid=1000)

thanks bye

[Tim Curtis]

The log entry below shows an unusual Primary DNS address of 8.8.8.8. Normally a residential Router will act as a DNS proxy and thus will assign its LAN (Gateway) address as the Primary DNS address. This allows all local hosts within 192.168.1.x address space to be resolved.

Code:

20210620 165217 worker: Gateway (192.168.1.1)
20210620 165217 worker: Pri DNS (8.8.8.8)

In your case I would have expected Primary DNS to be 192.168.1.1

[vinnn]

8.8.8.8 is a Google DNS server address.
Shouldn't be set on a host sat on a LAN though, would be normally used for setting a router's WAN DNS to avoid the ISP's often slower DNS services.
Either OP's manually configured this in Moode's settings or has set this in their router's DHCP settings. Either way OP's probably misunderstood what DNS is for and how an external dns server is used.

[anburg]

i tried as you suggest DNS primary 192.168.1.1 but it doesn't work. i also tried DHCP instead of static ip but that doesn't work either.
in my LAN there is a pihole ad blocker DNS 192.168.1.27 i tried to disable it but it doesn't work too
I remember with an old version 6.x it worked fine
bye

[Miss Sissy Princess]

8.8.8.8 is a Google DNS server address.
Shouldn't be set on a host sat on a LAN though, would be normally used for setting a router's WAN DNS to avoid the ISP's often slower DNS services.
Either OP's manually configured this in Moode's settings or has set this in their router's DHCP settings. Either way OP's probably misunderstood what DNS is for and how an external dns server is used.

There is nothing wrong with using 8.8.8.8 (or 1.1.1.1) as the DNS server on a host unless you are relying on DNS resolution to "find" local systems by name.  If someone mounts their NAS using its static IP (or pseudo-static IP if their local DHCP server is configured to supply a fixed IP address based on the MAC address of the NAS), DNS does not come into the equation.  That the OP is able to mount the NAS at all would suggest that the problem isn't a DNS issue.

[vinnn]

8.8.8.8 is a Google DNS server address.
Shouldn't be set on a host sat on a LAN though, would be normally used for setting a router's WAN DNS to avoid the ISP's often slower DNS services.
Either OP's manually configured this in Moode's settings or has set this in their router's DHCP settings. Either way OP's probably misunderstood what DNS is for and how an external dns server is used.

There is nothing wrong with using 8.8.8.8 (or 1.1.1.1) as the DNS server on a host unless you are relying on DNS resolution to "find" local systems by name.  If someone mounts their NAS using its static IP (or pseudo-static IP if their local DHCP server is configured to supply a fixed IP address based on the MAC address of the NAS), DNS does not come into the equation.  That the OP is able to mount the NAS at all would suggest that the problem isn't a DNS issue.

Not entirely, many services including ssh, nfs and samba will perform reverse name lookups on incoming clients whether the client is connecting to a hostname or ip, causing delays and timeouts if the name can't be resolved.

[Miss Sissy Princess]

8.8.8.8 is a Google DNS server address.
Shouldn't be set on a host sat on a LAN though, would be normally used for setting a router's WAN DNS to avoid the ISP's often slower DNS services.
Either OP's manually configured this in Moode's settings or has set this in their router's DHCP settings. Either way OP's probably misunderstood what DNS is for and how an external dns server is used.

There is nothing wrong with using 8.8.8.8 (or 1.1.1.1) as the DNS server on a host unless you are relying on DNS resolution to "find" local systems by name.  If someone mounts their NAS using its static IP (or pseudo-static IP if their local DHCP server is configured to supply a fixed IP address based on the MAC address of the NAS), DNS does not come into the equation.  That the OP is able to mount the NAS at all would suggest that the problem isn't a DNS issue.

Not entirely, many services including ssh, nfs and samba will perform reverse name lookups on incoming clients whether the client is connecting to a hostname or ip, causing delays and timeouts if the name can't be resolved.

Most home and SOHO routers don't resolve DNS requests of any type; they forward them to Internet DNS servers (or fulfill them from cache).  My EdgeRouter 4 is a darned good router and its documentation states that it "includes a DNS forwarding service based on dnsmasq that is consulted when clients use the EdgeRouter as a DNS server. The dnsmasq service runs in the background and will forward all client DNS queries to the specified DNS server(s)."  

In any case, if you're seeing delays and timeouts related to DNS when using 8.8.8.8 on any local host, then something is wrong.  Try "nslookup 192.168.150 8.8.8.8" at the command line and I bet that the 'not found' response will be instantaneous (from a human standpoint).  If you substitute your router's IP as the DNS server, the result should be the same.  And I would be surprised if either returned a hostname for a reverse DNS (PTR) query for a local IP address (e.g., 192.168.x.x).