having an issue adding network share on latest 4.0
Very same share use to work flawlessly on previous versions.
Not much to find in log apart from
But share works perfectly fine on network and can be accessed from another linux machine
Any idea what is going on here?
Thanks in advance
Very same share use to work flawlessly on previous versions.
Not much to find in log apart from
Code:
20180205 173648 wrk_sourcemount(): Mount error: (mount error(11): Resource temporarily unavailable
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs))But share works perfectly fine on network and can be accessed from another linux machine
Any idea what is going on here?
Thanks in advance
Last edited:
Do you mean the 1.FM-Blues Radio entry in the MoOde 4.0 Radio list?
Try:
http://strm112.1.fm/blues_mobile_aac
🙂
Bit of a UK tv reference thing, camp presenter who came to fame with
Dale's Supermarket Sweep - Wikipedia
but yes I do own that, along with a couple of other cheesy disco compilations.
having an issue adding network share on latest 4.0
Very same share use to work flawlessly on previous versions.
Not much to find in log apart from
Code:20180205 173648 wrk_sourcemount(): Mount error: (mount error(11): Resource temporarily unavailable Refer to the mount.cifs(8) manual page (e.g. man mount.cifs))
But share works perfectly fine on network and can be accessed from another linux machine
Any idea what is going on here?
Thanks in advance
Hi,
Open the (i) help for Remote directory and you will have the fix.
-Tim
I had it like that before so I have tried all sorts of things 🙂
All same results unfortunately
having an issue adding network share on latest 4.0
Very same share use to work flawlessly on previous versions.
Not much to find in log apart from
Code:20180205 173648 wrk_sourcemount(): Mount error: (mount error(11): Resource temporarily unavailable Refer to the mount.cifs(8) manual page (e.g. man mount.cifs))
But share works perfectly fine on network and can be accessed from another linux machine
Any idea what is going on here?
Thanks in advance
With my QNAP NAS device, I had similar issues that were resolved by removing the '/' from the beginning of the Remote Directory (e.g. /media/SSD -> media/SSD/). I don't remember if I used a '/' at the end, but you may want to try it both ways if it still isn't working...
-Sharkus
did not work either way I have tried.
But it seems to be sorted where I have done it different way than I was doing it before.
On old version of Moode the path which I used and worked was
Code:
media/SSD
Code:
media/usb0
Code:
xbian@xbian /media $ ls -all
total 8
drwxr-xr-x 1 root root 14 Jan 22 09:17 .
drwxr-xr-x 1 root root 158 Jan 2 13:03 ..
drwxrwxrwx 1 xbian xbian 4096 Nov 26 10:26 SSD
lrwxrwxrwx 1 root root 10 Jan 22 09:17 usb0 -> /media/SSDNot sure what is happening here but I am happy as its working so dont care much 🙂
Thanks for replies guys 😉
Because I had to move my 2TB music library over to a new NAS box (took a good while lol) I have only today got around to adding my new NAS to sources on Moode 4. I've been listening to Radio Paradise and Naim Radio to this point.
I could not get it to work at all - I know it was a new NAS box, but the source info all seemed okay... I made sure I was using the NAS IP address as opposed to its hostname and no leading or trailing slashes to the remote directory of Library (this is from previous experiences with WD NAS boxes and earlier versions of Moode)
However, I kept being told it could not be mounted and was being asked to check moode.log for the reason why there was a mount.error. The log file was telling me something similar to cannot change to directory /mnt/NAS/mymusic/Library
When I SSH'd into moode and did a listing of the /mnt directory there was only two mount points listed SDCARD & UPNP
So I took a punt, and typed sudo mkdir /mnt/NAS and restarted. Hey Presto with no further source config changes Moode is now updating the MPD database as the NAS source has mounted successfully.
Is this something that needs to be corrected in the build script? The creation of the /mnt/NAS folder?
I could not get it to work at all - I know it was a new NAS box, but the source info all seemed okay... I made sure I was using the NAS IP address as opposed to its hostname and no leading or trailing slashes to the remote directory of Library (this is from previous experiences with WD NAS boxes and earlier versions of Moode)
However, I kept being told it could not be mounted and was being asked to check moode.log for the reason why there was a mount.error. The log file was telling me something similar to cannot change to directory /mnt/NAS/mymusic/Library
When I SSH'd into moode and did a listing of the /mnt directory there was only two mount points listed SDCARD & UPNP
So I took a punt, and typed sudo mkdir /mnt/NAS and restarted. Hey Presto with no further source config changes Moode is now updating the MPD database as the NAS source has mounted successfully.
Is this something that needs to be corrected in the build script? The creation of the /mnt/NAS folder?
Last edited:
Hi,
I checked both the manual Build Recipe and the Image Builder and both contain the line below:
mkdir /mnt/NAS
Not sure how it may have been deleted but I'll have a look at the code behind the NAS config screen and see if there is a bug.
-Tim
Morias' fix also works for me, thanks Morias! I modified mosbuild_worker.sh to skip the rpi-update in the build and all works ok now
From what I read, as long as we do apt-get upgrade and dist-upgrade, we are safe: software comes from the repository, where everything is tested together. rpi-update is more aggressive. The tool itself warns that it can cause problems with drivers, which is most probably what was happening in our case.
From raspberry.org:
Updating the kernel - Raspberry Pi Documentation
The kernel and the firmware are included in the distribution as packages too, rpi-update overwrites them. So, if an updated kernel or firmware makes it to the distribution, apt-get upgrade will eventually upgrade them, without the need for rpi-update. I tried to reinstall the kernel and bootloader packages again, and that fixed the problem as well. Instructions can be found in the same page.
Are there any good reasons for the rpi-update? If not, I would leave it out. Or at least leave the option in the build script.
Jonners,
Do you recommend raspotify or something different?
I wished I could implement Spotify connect that could pause mpd, as you can with AirPlay. I can’t get this functionality with raspotify/librespot.
Regards
Morias' fix also works for me, thanks Morias! I modified mosbuild_worker.sh to skip the rpi-update in the build and all works ok now
From what I read, as long as we do apt-get upgrade and dist-upgrade, we are safe: software comes from the repository, where everything is tested together. rpi-update is more aggressive. The tool itself warns that it can cause problems with drivers, which is most probably what was happening in our case.
From raspberry.org:
Updating the kernel - Raspberry Pi Documentation
The kernel and the firmware are included in the distribution as packages too, rpi-update overwrites them. So, if an updated kernel or firmware makes it to the distribution, apt-get upgrade will eventually upgrade them, without the need for rpi-update. I tried to reinstall the kernel and bootloader packages again, and that fixed the problem as well. Instructions can be found in the same page.
Are there any good reasons for the rpi-update? If not, I would leave it out. Or at least leave the option in the build script.
Hi,
The latest kernel via rpi-update is perfectly fine and has many benefits including all the bug fixes, improvements and latest device drivers. As I mentioned earlier its rare, at least in my experience, that issue occurs.
On the other hand, I definitely won't support any builds that apply "dist-upgrade" because this operation installs new packages that are not part of the Build Recipe and I would have no way of knowing whether any of the new packages and configs cause problems.
My recommendation if you have isolated a particular issue to a kernel version is to simply install an earlier version via rpi-update using the procedure described in the post below.
http://www.diyaudio.com/forums/pc-based/271811-moode-audio-player-raspberry-pi-1346.html#post5331482
-Tim
Yes I use raspotify, as I said in my PM. I don't really see what your problem is. Why not stream Spotify to Moode via Airplay?
Last edited:
Looking at your screenshot your remote directory has a leading / if you click the i to the right of the field it will tell you leading slashes are not allowed.having an issue adding network share on latest 4.0
Very same share use to work flawlessly on previous versions.
Not much to find in log apart from
Code:20180205 173648 wrk_sourcemount(): Mount error: (mount error(11): Resource temporarily unavailable Refer to the mount.cifs(8) manual page (e.g. man mount.cifs))
But share works perfectly fine on network and can be accessed from another linux machine
Any idea what is going on here?
Thanks in advance
I think @kaspersone is referring the feature in moOde's Airplay (shairport-sync) implementation that can resume MPD playback when the Airplay session stops. This is controlled by aa setting in Airplay config screen.
The MPD resume feature is made possible by a session start/stop event API thats unique to shairport-sync. AFAIK none of the other audio renderers including SpotifyConnect, Bluetooth, Squeezelite and UPnP have such an API.
-Tim