[
attachment=528]I have successfully got Volumio and MoOde2.6 to work Ok, but the latest version of MoOde defeats me. Googling is no help. Please can you?
I use an AppleMac/Mojave.
Thanks,
Richard
(02-19-2019, 01:08 PM)Bonky Wrote: [ -> ]I have successfully got Volumio and MoOde2.6 to work Ok, but the latest version of MoOde defeats me. Googling is no help. Please can you?
I use an AppleMac/Mojave.
Thanks,
Richard
@
Bonky
We're just now discussing NAS settings in the Test Team channel. Could you try changing the (Advanced) Mount flags from "vers=1.0" to "vers=default"?
Also, your Mount flags seem to be missing some other moOde-default values like "ro" and several modes, but these should not have prevented the mount.
Regards,
Kent
Thanks Kent for the speedy reply.
Sorry, I tried that and adding: "vers=default,cache=strict,ro,dir_mode=0777,file_mode=0777"
I don't mean to sound ungrateful but one may expect that incremental updates make things easier...
It's probably something very easy but I've tried all I know at present.
Thanks again,
Regards,
Richard
You can try omitting the vers= param
Code:
ro,dir_mode=0777,file_mode=0777
Or try bumping the version number to 2.0 or 3.0
Code:
vers=2.0,ro,dir_mode=0777,file_mode=0777
vers=3.0,ro,dir_mode=0777,file_mode=0777
Thanks Tim,
No joy I'm afraid with any of those options.
BW
Richard
Unfortunately the errors from the mount process are almost totally useless.
The only way to troubleshoot a failed mount is to fiddle with the mount parameters from the cmd line but even this is no guarantee that you will land on the right combination.
In any case here are the cmds for your mount string based on your screen shot.
Code:
mkdir ./tmp
sudo mount -t cifs "//NAS/Hi-Res Music" -o username=guest,password='',rsize=61440,wsize=65536,iocharset=utf8,vers=1.0,ro,dir_mode=0777,file_mode=0777 "./tmp"
After testing remove the mount and temp dir
sudo umount ./tmp
sudo rmdir ./tmp
(02-19-2019, 01:55 PM)Bonky Wrote: [ -> ]Thanks Kent for the speedy reply.
Sorry, I tried that and adding: "vers=default,cache=strict,ro,dir_mode=0777,file_mode=0777"
I don't mean to sound ungrateful but one may expect that incremental updates make things easier...
It's probably something very easy but I've tried all I know at present.
Thanks again,
Regards,
Richard
Understandable reaction. We all want software which "just works ".
You can help us get there if you're willing. Tim and I are coming from slightly different directions so bear with us.
Log into your moOde player's command line (using ssh on your Mac or using moOde's Web SSH Terminal which you enable from the System conf panel).
First, execute the following line just to scan your LAN for available servers. Please post your results. (Shown is partial output from a scan of my LAN. OMV-HC1 is my OpenMediaVault Server and MOODELR is a copy of moOde r4.4 running in my living room.):
Code:
pi@MoodeLR:~ $ smbtree -N -b
WORKGROUP
\\OMV-HC1 omv-hc1 server
\\OMV-HC1\IPC$ IPC Service (omv-hc1 server)
\\OMV-HC1\Music
\\OMV-HC1\Test a test directory
\\MOODELR moOde SMB Server
\\MOODELR\IPC$ IPC Service (moOde SMB Server)
\\MOODELR\SDCard SDCARD Storage
\\MOODELR\Radio RADIO Stations
\\MOODELR\Playlists Playlist Directory
\\MOODELR\NAS NAS Shares
I assume you will see a branch for \\NAS since that is the name you used in the NAS Source panel.
Second, to ferret out the SMB protocol version level your server will accept, try a sequence of commands against your server name (here, I assumed NAS) and, again, post your results:
Code:
pi@moode:~ $ smbclient -N -L NAS
pi@moode:~ $ smbclient -N -L NAS -m SMB2
pi@moode:~ $ smbclient -N -L NAS -m SMB3
The first will succeed and list the server's shares if SMB1 (vers=1.0) is acceptable. Otherwise it will fail with a protocol negotiation failed message.
Similarly, the second will succeed if SMB2 (vers=2.0) is acceptable and the third will succeed if SMB3 (vers=3.0) is acceptable.
Sorry that this works seems to retrace steps you've already taken.
Regards,
Kent
Hi,
Numptie here...please spell out what I need to do in order to:"Log into your moOde player's command line (using ssh on your Mac or using moOde's Web SSH Terminal which you enable from the System conf panel).
I can login to the Moode system config panel but cannot paste in the top line of your command...and I can't type it as I can't find the wavy symbol after ":"
The Mac terminal doesn't seem to understand 'SSH'; presumably I need to type something else?
Thanks again,
Richard
Apologies
(02-19-2019, 03:23 PM)Bonky Wrote: [ -> ]Hi,
Numptie here...please spell out what I need to do in order to:"Log into your moOde player's command line (using ssh on your Mac or using moOde's Web SSH Terminal which you enable from the System conf panel).
I can login to the Moode system config panel but cannot paste in the top line of your command...and I can't type it as I can't find the wavy symbol after ":"
The Mac terminal doesn't seem to understand 'SSH'; presumably I need to type something else?
Thanks again,
Richard
Apologies
Oops, sorry, I went a bridge too far!
I'm not a Mac owner. I assumed from other peoples' posts that you could invoke ssh from the Terminal application in OS X.
It sound like you already accomplished the alternatve. [Just in case, here it is in more detail. From moOde's System config panel under "Local Services", you can enable the SSH term server (select "ON" and then "SET"). Once moOde has finished digesting that command and control returns to the UI, you can click on "OPEN" in the line "OPEN Web SSH terminal" just below the setting.]
"pi@moode:~ $ " is the prompt you'll see when you're at the command line after you log in. You type what comes after, such as smbtree... or smbclient..., then <return>.
Regards,
Kent