Posts: 8
Threads: 0
Joined: Apr 2018
Reputation:
0
(04-30-2018, 01:34 PM)Martin Wrote: (04-29-2018, 08:34 PM)Tim Curtis Wrote: sudo not needed. The log might have been automatically cleared by the maintenance task.
Open Sources screen, click RESCAN then wait a bit, then view the log.
I have clicked RESCAN and had a look at the log. It appears to have scanned the SD card but not the
NAS.
Apr 30 14:28 : update: updating SDCARD/Stereo Tes
t/LRMonoPhase4.flac
Martin
Hi Tim,
I still haven't figured out how to get this to work.
Following your advice, I have configured my NAS source as MYCLOUD-AP41K0.local/Public, which results in a green tick. In the Browse panel I now see a NAS option. When I click on NAS I can see My Cloud, which would suggest that it has mounted properly
THe problem is that when I click to update the NAS folder, I see a message telling me that the Update path is NAS/MyCloud, but it can't find the files. My music files on my My Cloud device are located in Files/Family/Music but I can't see a way to tell Moode the correct path to enable it to find my files when I update the NAS folder.
Martin
Posts: 12,030
Threads: 271
Joined: Mar 2018
Reputation:
458
My MacBook running Sierra only offers SMB or AFP as sharing protocols. There is no NFS option.
In moOde create the NAS source and specify SMB (Samba) as the Type. Try userid=Guest and blank password or specify the userid and password that u use to login to your Mac. One of these should work.
-Tim
Posts: 6
Threads: 0
Joined: Feb 2019
Reputation:
0
I have a very similar problem RPi 3B + Kali + Piano2.1 with Synology DS216se NAS
I have SSHed to the NAS and created a suitable etc/exports file. I have two identical streamers the second one is currently running Volumio and I can connect to the NAS with that one, OK. However all attempts to connect the player running Moode have failed. Attempting to connect using NFS with "192.168.178.59/volume1/music" as connection string and all other params as default, results in the following error msg "20190204 195413 wrk_sourcemount(): Mount error: (mount.nfs: mount point /mnt/NAS/Music1 does not exist)".
Trying with Samba gives the following error "20190204 200111 wrk_sourcemount(): Mount error: (Couldn't chdir to /mnt/NAS/Music1: No such file or directory)"
Posts: 5,547
Threads: 168
Joined: Apr 2018
Reputation:
205
(02-04-2019, 07:04 PM)Paulbj Wrote: I have a very similar problem RPi 3B + Kali + Piano2.1 with Synology DS216se NAS
I have SSHed to the NAS and created a suitable etc/exports file. I have two identical streamers the second one is currently running Volumio and I can connect to the NAS with that one, OK. However all attempts to connect the player running Moode have failed. Attempting to connect using NFS with "192.168.178.59/volume1/music" as connection string and all other params as default, results in the following error msg "20190204 195413 wrk_sourcemount(): Mount error: (mount.nfs: mount point /mnt/NAS/Music1 does not exist)".
Trying with Samba gives the following error "20190204 200111 wrk_sourcemount(): Mount error: (Couldn't chdir to /mnt/NAS/Music1: No such file or directory)"
@ Paulbj
The fact that moOde keeps telling you that /mnt/NAS/Music doesn't exist is suggestive. It's acting on information you gave it, so let's see what you did.
I have no knowledge of Synology NAS software but I would have thought you could configure both Samba and NFS share via some administrative UI. Since you "created a suitable etc/exports file" from the command line, show us the file. Then show us the moOde NAS Config panel with the information you entered into it.
As a point of comparision, I run OpenMediaVault on a server and export both NFS and Samba shares from it. Both kinds mount without incident in moOde.
Regards,
Kent
Posts: 6
Threads: 0
Joined: Feb 2019
Reputation:
0
I assumed that the error log was referring to the directory " /mnt/NAS" not existing on the Moode device rather than on the NAS. That would be the rational conclusion, I think. It's the Moode device that is mounting the NAS rather than the other way round.
Posts: 12,030
Threads: 271
Joined: Mar 2018
Reputation:
458
Run the cmd below and then post the output. Also post a screen shot of the NAS config screen.
Code: /var/www/command/sysinfo.sh
Posts: 5,547
Threads: 168
Joined: Apr 2018
Reputation:
205
(02-05-2019, 01:11 PM)Paulbj Wrote: I assumed that the error log was referring to the directory " /mnt/NAS" not existing on the Moode device rather than on the NAS. That would be the rational conclusion, I think. It's the Moode device that is mounting the NAS rather than the other way round.
@ Paulbj
The directory /mnt/NAS is predefined in moOdeOS as the root of all the NAS mountpoints. The mountpoints themselves are derived from the info you enter into the NAS Source panel (the "friendly" Name)
Example:
My OpenMediaVault (OMV) NAS with the hostname OMV-HC1 has a directory '/export/Music'. In its '/etc/exports' file I* tell NFS to export this directory read-only to my entire subnet.
Code: /export/Music 192.168.1.0/24(fsid=1,ro,subtree_check,insecure)
At this point, the directory is visible to NFS clients on my LAN as 'OMV-HC1:/Music'.
In moOde's NAS Source panel, I enter this into the Host/Share box as 'OMV-HC1/Music' (note we lose the ':'). I give it a friendly Name 'OMV-NFS' (to differentiate it from, you guessed it, 'OMV-SMB' for my Samba share //OMV-HC1/Music from the same host).
When I'm all done and look at moOde's mount list, I see among the many entries
Code: pi@moode:~ $mount
...
//OMV-HC1/Music on /mnt/NAS/OMV-SMB type cifs (ro,relatime,vers=1.0,cache=strict,username=moode,domain=,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.1.12,soft,unix,posixpaths,mapposix,acl,rsize=61440,wsize=65536,echo_interval=60,actimeo=1)
OMV-HC1:/Music on /mnt/NAS/OMV-NFS type nfs4 (ro,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.182,local_lock=none,addr=192.168.1.12)
The first entry is the Samba share and the second is the NFS share from my OpenMediaVault NAS. Here you see explicitly the moOde-named mountpoints such as /mnt/NAS/OMV-NFS.
As an aside, choosing directory names such as 'export' and 'Music' is arbitrary; what's important is that the names be consistently used between the NAS and moOde and not confused with the friendly name you assign in the NAS Source panel.
Regards,
Kent
*more precisely, that's what the OMV Admin UI entered based on what I told it.
Posts: 6
Threads: 0
Joined: Feb 2019
Reputation:
0
(02-05-2019, 03:26 PM)TheOldPresbyope Wrote: (02-05-2019, 01:11 PM)Paulbj Wrote: I assumed that the error log was referring to the directory " /mnt/NAS" not existing on the Moode device rather than on the NAS. That would be the rational conclusion, I think. It's the Moode device that is mounting the NAS rather than the other way round.
@Paulbj
The directory /mnt/NAS is predefined in moOdeOS as the root of all the NAS mountpoints. The mountpoints themselves are derived from the info you enter into the NAS Source panel (the "friendly" Name)
Example:
My OpenMediaVault (OMV) NAS with the hostname OMV-HC1 has a directory '/export/Music'. In its '/etc/exports' file I* tell NFS to export this directory read-only to my entire subnet.
Code: /export/Music 192.168.1.0/24(fsid=1,ro,subtree_check,insecure)
At this point, the directory is visible to NFS clients on my LAN as 'OMV-HC1:/Music'.
In moOde's NAS Source panel, I enter this into the Host/Share box as 'OMV-HC1/Music' (note we lose the ':'). I give it a friendly Name 'OMV-NFS' (to differentiate it from, you guessed it, 'OMV-SMB' for my Samba share //OMV-HC1/Music from the same host).
When I'm all done and look at moOde's mount list, I see among the many entries
Code: pi@moode:~ $mount
...
//OMV-HC1/Music on /mnt/NAS/OMV-SMB type cifs (ro,relatime,vers=1.0,cache=strict,username=moode,domain=,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.1.12,soft,unix,posixpaths,mapposix,acl,rsize=61440,wsize=65536,echo_interval=60,actimeo=1)
OMV-HC1:/Music on /mnt/NAS/OMV-NFS type nfs4 (ro,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.182,local_lock=none,addr=192.168.1.12)
The first entry is the Samba share and the second is the NFS share from my OpenMediaVault NAS. Here you see explicitly the moOde-named mountpoints such as /mnt/NAS/OMV-NFS.
As an aside, choosing directory names such as 'export' and 'Music' is arbitrary; what's important is that the names be consistently used between the NAS and moOde and not confused with the friendly name you assign in the NAS Source panel.
Regards,
Kent
*more precisely, that's what the OMV Admin UI entered based on what I told it. Right by tweaking the etc/exports file a bit on the Synology NAS and manually creating the mnt/NAS folder on the Moode device (the 'NAS' sub-folder was not present!) I have managed to get Moode to connect to the NAS using Samba but not with NFS which I would have thought was the 'native' connection style between two Linux boxes. However, after appearing for a few minutes in the 'music' are of the site but having no music behind it, the NAS has now disappeared altogether and nothing I do seems to want the make it reappear as an option alongside Radio, USB etc
Posts: 5,547
Threads: 168
Joined: Apr 2018
Reputation:
205
@ Paulbj
Ah, you probably mean "NAS" doesn't show up in moOde's Music browse panel. IIRC, it won't appear until you've successfully mounted at least one NAS share (after all, until then there's nothing to browse).
The moOde bootable image file, OTOH, already contains the directories /mnt/NAS and /mnt/SDCARD. If they aren't both present in the file system after you install it then the install has become borked somehow.
Don't overthink the problem. Samba is well supported in Linux and on most-all NAS products. You can use Samba or NFS, whichever you prefer. For casual users, Samba is nearly always easier to use.
At this point, I don't understand where you've gotten to.
My advice is to start over with a fresh install of moOde and a stock Synology configuration with one or more Samba shares and use only their UIs to configure them, but it's your call.
Regards,
Kent
Posts: 6
Threads: 0
Joined: Feb 2019
Reputation:
0
After much further tweaking of lots of things including returning the original the original SD card to the shop as it was, improbably enough, faulty! I now have the NAS mounted correctly. I have created one at a time, a NAS mount using the Samba then one using NFS and both show the sought after green tick! However, if I go into the music browser immediately after mounting the NAS, I can see NAS item listed but there is no music available underneath it, if I click on it. After a few minutes, the NAS item in the music browser disappears and nothing I can think of will bring it back!
I have had a look in the /mnt/NAS folder and the NAS is listed there along all the sub-folders that should be there and the sub-sub-folders etc. I can drill right down through the sub-folders to the music files at the lowest levels BUT none of that shows up on the music browser!
If I run sysinfo.sh, this is the output:
pi@Alistair-moode:~ $ /var/www/command/sysinfo.sh
modprobe: ERROR: could not insert 'configs': Operation not permitted
rmmod: ERROR: Module configs is not currently loaded
S Y S T E M P A R A M E T E R S
Date and time = 2019-02-08 13:04:44
System uptime = up 12 hours, 46 minutes
Timezone = Europe/Luxembourg
moOde = Release 4.4 2018-12-09
Host name = Alistair-moode
ETH0 IP = 192.168.178.60
ETH0 MAC = b8:27:eb:23:d3:05
WLAN0 IP = unassigned
WLAN0 MAC = no adapter
WiFi country = US
HDWR REV = Pi-3B+ 1GB v1.3
SoC = BCM2835
CORES = 4
ARCH = armv7l
RASPBIAN = 9.6
KERNEL = 4.14.84-v7+
KTIMER FREQ = No /proc/config.gz Hz
USB BOOT = enabled
Warranty = OK
ROOT size = 15G
ROOT used = 15%
ROOT avail = 12G
FS expand = expanded
MEM free = 172 MB
MEM used = 65 MB
Temperature = 58.0°C
CPU GOV = performance
MPD SCHDPOL = TS
P3-WIFI = Off
P3-BT = Off
HDMI = Off
ETH0 CHECK = On
MAX USB CUR = Off
UAC2 FIX = Off
ETHPORT FIX = Off
SSH server = Off
LED0 = on
LED1 = on
C O R E S E R V E R S
PHP-FPM = 7.0.30
NGINX = 1.10.3
SQLite = 3.16.2
C P U L O A D
CPU %usr %sys %idle
all 0.50 0.00 99.50
0 0.00 0.00 100.00
1 0.50 0.00 99.50
2 1.52 0.00 98.48
3 0.00 0.00 100.00
P R O C E S S L O A D
PRI RTPRIO COMMAND %MEM PSR %CPU
19 - bash 0.4 2 0.6
19 - sshd 0.6 1 0.3
29 - mpd 2.6 1 0.2
19 - systemd 0.5 0 0.2
19 - sysinfo.sh 0.2 3 0.2
19 - worker.php 1.2 1 0.1
19 - systemd 0.6 2 0.0
19 - kthreadd 0.0 1 0.0
39 - kworker/0:0H 0.0 0 0.0
C L O C K F R E Q U E N C I E S
arm = 1400 MHz pwm = 0 MHz
core = 400 MHz emmc = 200 MHz
h264 = 300 MHz pixel = 0 MHz
isp = 300 MHz vec = 0 MHz
v3d = 300 MHz hdmi = 0 MHz
uart = 48 MHz dpi = 0 MHz
grep: /sys/kernel/debug/mmc0/ios: Permission denied
S Y S T E M V O L T A G E S
core = 1.3500V
sdram controller = 1.2500V
sdram I/O = 1.2500V
sdram chip = 1.2250V
U I C U S T O M I Z A T I O N S
Theme = Standard
Accent color = Emerald
Alpha blend = 1.0
Adaptive background = No
Background image = No
Playback history = No
Extra metadata = Yes
Artist list order = Artist
Compilation rollup = No
Compilation excludes = greatest hits
Cover search pri = Embedded cover
Hi-res covers = Auto
Pixel ratio = 1
Cover backdrop = No
Cover blur = 20px
Cover scale = 1.25
A U D I O P A R A M E T E R S
Audio device = Allo Piano 2.1 Hi-Fi DAC
Interface = I2S
Hdwr volume = Controller detected
Mixer name = Master
Output stream = S32_LE / 44100
ALSA version = 1.1.3-5+rpi3
SoX version = 0.1.2-2
Volume knob = 14
Volume mute = Unmuted
Bluetooth controller = Off
Airplay receiver = Off
Spotify receiver = Off
Squeezelite = Off
UPnP client = Off
DLNA server = Off
Rotary encoder = Off
Encoder params = 100 2 3 4 5
Crossfeed = Off
Parametric EQ = Off
Graphic EQ = Paul
Auto-shuffle = Off
Autoplay = Off
MPD crossfade = Off
M P D S E T T I N G S
Version = 0.20.20
Volume control = software
ALSA device = hw:0
SoX resampling = disabled
SoX quality = very high
SoX multithreading = off
Audio buffer (kb) = 4096
Buffer before play = 10%
Output buffer size (kb) = 81920
Volume normalization = No
DSD over PCM (DoP) = yes
Replay gain = off
B L U E T O O T H S E T T I N G S
Bluetooth ver = 5.49
Bluealsa ver = Turn BT on for version info
Speaker sharing = No
Resume MPD = No
A I R P L A Y S E T T I N G S
Version = 3.2.2
Friendly name = Moode Airplay
ALSA device = hw:0
Volume mixer = auto
Resume MPD = No
Output bit depth = S16
Output sample rate = 44100
Session interruption = no
Session timeout (ms) = 120
Audio buffer (secs) = 0.0
S P O T I F Y S E T T I N G S
Friendly name = Moode Spotify
ALSA device = default:CARD=PianoDACPlus
Resume MPD = No
Bit rate = 160
Initial volume = 0
Volume curve = Logarithmic
Volume normalization = No
Normalization pregain = 0
S Q U E E Z E L I T E S E T T I N G S
Version = 1.8.7-1052 "DSD/SRC enabled"
Friendly name = Moode
ALSA device = hw:0
ALSA params = 80:4::1
Output buffers = 40000:100000
Task priority = 45
Codec list = flac,pcm,mp3,ogg,aac,alac,dsd
Resume MPD = No
Other options = -W -D 500 -R E -S /var/loca
M O O D E L O G
20190208 001814 worker: - Start
20190208 001814 worker: Successfully daemonized
20190208 001814 worker: Integrity check ok
20190208 001815 worker: Session loaded
20190208 001815 worker: Debug logging (off)
20190208 001815 worker: - Platform
20190208 001816 worker: Host (Alistair-moode)
20190208 001816 worker: Hdwr (Pi-3B+ 1GB v1.3)
20190208 001816 worker: Arch (armv7l)
20190208 001816 worker: Rasp (9.6)
20190208 001816 worker: Kver (4.14.84-v7+)
20190208 001816 worker: Ktyp (Standard)
20190208 001816 worker: Gov (performance)
20190208 001817 worker: Rel (Moode 4.4 2018-12-09)
20190208 001817 worker: Upd (None)
20190208 001817 worker: MPD (0.20.20)
20190208 001817 worker: USB boot enabled
20190208 001820 worker: File system expanded
20190208 001820 worker: HDMI port off
20190208 001820 worker: File check ok
20190208 001820 worker: - Network
20190208 001820 worker: eth0 exists
20190208 001820 worker: eth0 (192.168.178.60)
20190208 001820 worker: wlan0 does not exist
20190208 001820 worker: - Audio
20190208 001821 worker: ALSA outputs unmuted
20190208 001821 worker: ALSA card number (0)
20190208 001821 worker: Audio out (I2S audio device)
20190208 001821 worker: Audio dev (Allo Piano 2.1 Hi-Fi DAC)
20190208 001821 worker: ALSA mixer name (Master)
20190208 001821 worker: MPD volume control (software)
20190208 001821 worker: Hdwr volume controller exists
20190208 001821 worker: Chip options (Burr Brown PCM5142)
20190208 001821 worker: Piano output mode (Dual-Stereo)
20190208 001826 worker: Piano 2.1 initialized
20190208 001826 worker: - Services
20190208 001826 worker: Reset renderer active
20190208 001828 worker: MPD started
20190208 001828 worker: MPD scheduler policy (time-share)
20190208 001828 worker: Configure MPD outputs
20190208 001828 worker: MPD output 1 ALSA default (off)
20190208 001828 worker: MPD output 2 ALSA crossfeed (off)
20190208 001828 worker: MPD output 3 ALSA parametric eq (off)
20190208 001828 worker: MPD output 4 ALSA graphic eq (on)
20190208 001828 worker: MPD output 5 ALSA bluetooth (off)
20190208 001828 worker: MPD crossfade (off)
20190208 001828 worker: - Music sources
20190208 001828 worker: USB source (1 ROCK)
20190208 001828 worker: USB source (3 CLASSICAL)
20190208 001828 worker: USB source (4 BFJ)
20190208 001829 worker: NAS sources (mountall initiated)
20190208 001829 worker: - Miscellaneous
20190208 001829 worker: Volume level (14) restored
20190208 001829 worker: Maintenance interval (21600)
20190208 001829 worker: Screen saver activation (Never)
20190208 001829 worker: Watchdog started
20190208 001829 worker: Ready
20190208 061925 worker: Maintenance completed
20190208 122011 worker: Maintenance completed
|
