Max2Play Home › Forums › Max2Play on Raspberry PI › Filesystem mounts, but LMS doesn't see my music!
Tagged: Airport Extreme, filesystem, Mount
- This topic has 8 replies, 2 voices, and was last updated 6 years, 1 month ago by
Heiner premium.
-
Posted in: Max2Play on Raspberry PI
-
22. Februar 2018 at 2:36 #34056
I’d really appreciate some help… Here’s what I know:
My setup: RPI3, Apple Airport Extreme WIFI, WD Passport plugged into the Airport Express. Running current versions of M2P & LMS.
Here’s what I know for sure…
1) The WD Passport is formatted correctly for the Airport Extreme. I have access to the music files via my microsoft laptop via the WIFI server.
2) I’ve had success mounting the file in M2P. It seems to mount fine. I’ve tried numerous versions of the filesystem path, mountpoint, etc. The filesystem seems to mount fine, but LMS doesn’t seem to see the files.
3) I’ve watched the video. I’ve read through the forum. I’ve also replicated the RPI/M2P/LMS system in another house, and it works fine. The only difference between the two installations is that the other one isn’t using an Apple Airport Extreme for WIFI.I’ve tried every combination I can come up with. I’m stuck. I’ve read that I should try to look at permissions (chmod?), but it’s not clear to me how to drop out of M2P into the Linux code… I’m not afraid to try, but the last programming language I had to learn was fortran, and that was about 40 years ago…
I could sure use some help! Thanks.
24. Februar 2018 at 2:47 #34071Nothing? No ideas? No suggestions? Anyone? PLEASE — and THANKS!!!
27. Februar 2018 at 17:04 #34111Hi mnvelocitypilot,
Sorry about the late reply. I was on holiday for the last week and am still going through all the outstanding requests.
Let me first make sure I get the situation correctly:
– You have a share with the files of a USB HDD attached to an Apple NAS
– You used our filesystem mount menu to add the share with HDD’s files on the Apple NAS to your Pi
– You selected the path with the files in the LMS but the files are not found
– The files are found in a different setup with a different NAS (?)
Please clarify if there is anything I got wrong.Ideas:
– Make sure the format of HDD which is correct for the Apple product is also working with RPi
– Try connecting the HDD directly to the Pi and create a SambaShare on the path to share it with the rest of the network
– Make sure your files and folders of music do not have any special rights or formats to rule this out as a source of error1. März 2018 at 1:20 #34152Hi Heiner
First – thank you very much for trying to help! It’s greatly appreciated. Let me respond to your questions directly:
Here’s what your wrote:
Let me first make sure I get the situation correctly:
– You have a share with the files of a USB HDD attached to an Apple NAS (Correct)
– You used our filesystem mount menu to add the share with HDD’s files on the Apple NAS to your Pi (also correct)
– You selected the path with the files in the LMS but the files are not found (correct again, examples below)
– The files are found in a different setup with a different NAS (?) (I’ve got a similar system running just fine at work; and, the system at home that has me pulling out my hair worked just fine prior to an extended absence… when I rebooted upon return, the files could not be found… making this even more frustrating).Ideas:
– Make sure the format of HDD which is correct for the Apple product is also working with RPi (The HDD is formatted explicitly for the Apple Airport Extreme, and the files can be seen on my Windows 10 laptop. Also, as mentioned, it was working fine with the RPI/M2P/Logitec setup).
– Try connecting the HDD directly to the Pi and create a SambaShare on the path to share it with the rest of the network (interesting idea, but I’m not familiar with Linux, and unsure as to how to drop out of the M2P operating system into Linux. Assuming that the RPi has enough horsepower to run the filesystem and M2P at the same time, though, that’s an interesting idea).
– Make sure your files and folders of music do not have any special rights or formats to rule this out as a source of error (I will double check).Here’s the filesystem mount in M2P:
Filesystem – mount network paths (Samba or NFS)
Path: //192.168.0.2/TIMS-AIRPORT-EX/music??????/music/Mountpoint:/mnt/music/
Type: cifs
Options:user=null,password=music,sec=ntlm,iocharset=utf8
And here’s the path in LMS:
Media Library Name: Music
Media Folders
Folder: /mnt/share/musicAgain, Heiner, I’m grateful for any ideas or help. Thank you!
Dave
1. März 2018 at 13:39 #34159Hi Dave,
SambaShare is rather simple with Max2Play, you can find it in the Filesystem/Mount menu and it says exactly what to do there to (both to create one and to access it on a windows device). However, depending on the size of library this might (not necessarily) strain the Pi’s computing powers.
7. März 2018 at 16:28 #34266Heiner, thanks again!
I’ll try SambaShare. One quick question… my library is quite large. If I put SambaShare on a different Pi (not the Pi that’s running LMS), would the other Pis be in the „share“? Would that help keep the processor from overloading?
THANK YOU!
Dave
8. März 2018 at 11:08 #34269Hi Dave,
You could indeed mount the SambaShare from one Pi on another with Filesystem Mount.
But if the load is indeed too high for your Pi’s, you can also try creating a new login for your share on the Apple NAS to use in Max2Play to rule out an error there.8. März 2018 at 23:14 #34289Heiner, you may be interested in this…
For other reasons I wound up replacing my Apple Airport Extreme WIFI with a Linksys EA6350.
The system now works just fine… it immediately found my music… no problem.
I suspect that Apple does good testing with other Apple products, but doesn’t overly worry about testing other products.
Lesson learned! I’m now all set – but very thankful for your help!
Dave
12. März 2018 at 11:36 #34330Hi Dave,
Glad you have everything working now 🙂
Also, thanks for informing us. We might have to investigate this issue to make sure that future Max2Play users with Apple NAS do not run into this issue in the future.
-
You must be logged in to reply to this topic.