Cannot mount NAS

foxint

Hi Guys,

Thanks for all the help. I am temporarily having a break from the HiFiBerry Dac + Pro XLR as nothing works.. I did email HiFiBerry, but they sent me back here....so rock and a hard place??? Perhaps I should sell it and get another with XLR

I have been able to hear the radio on my other pi the Pi2Media 502 DAC (not that keen on this one as it does not have XLR).

I have never heard any of my flac files as I have never been able to mount the NAS. It is all about the music...ha-ha

Can anyone lend a hand???

I have mount error(112): host is down. Refer to the mount.cifs(8) manual page. I searched this on the site and got nothing. I pushed all the buttons "Update MPD Library" Rebuild MPD Library" "remount all Sources". Nothing

The flac files are on a PC win 10 via a router on another PC on a separate HDD.

Any suggestions?

eea123

It doesn't sound like you have the drive pathed to Rune under "Sources". I have my "Network Mount" mounted via its IP address, //10.0.0.XX/multimedia/music. I'll offer that I gave the Rune app admin rights instead of fighting to setup an individual account.

If you are using WiFi, make sure both are connected via the same router or use physical ethernet connections. I have an old NetGear router that I use to cover the outside deck and for some reason it assigns 192.168.0.XX even though the primary XFinity's DCHP is assigning 10.0.0.XX. If I use the Rune app on my tablet connected to the 192 subnet I am out of luck connecting to the player which is hardwired to the Comcast router in the 10 subnet.

foxint

Hi Mate

Thanks for the reply.

I am using ethernet - wire. I have the IP address - 192.168.X.X/W/Music. Everything has a static IP Address including the Pi.

MediaMonkey can find the music at this IP Address - so I am very confused that the Pi cannot find it????

I am using PC Win 10. No tablets or phones or anything like that

???

cmh714

So on my Western Digital NAS, The Volume Name is Public with the "Shared Music" folder under it. On the WD interface it says my nfs mount point is: 192.168.1.111/nfs/Public

notice I did not put in the nfs before the Public but its there and thats what works for me when I mount.....without the nfs/ before Public it fails.

You may have something similar like that.....GL!

foxint

Hi Mate

Thank you.

My "NAS" is a PC that has 6 HDD that I use to backup my other 6 HDD. Since my main PC is not shared (I have kids and would not like them to make changes by accident), I have shared ALL the drives on the other PC. As I said the MediaMonkey can play music from anywhere in the network

I added each and both suggestions - Nothing

Sorry for having such a strange arrangement. Perhaps something somewhere else. Perhaps this is future upgrade???

foxint

Mate - I hope it is helpful...ha-ha

eea123

Here are my Source settings for Rune regarding my NAS:

Source Name: your-NAS-name-here
Fileshare protocol: SMB/CIFS
IP address: 10.0.0.XX
Remote directory: Multimedia/Music (again this will change for your NAS)
Guest access: OFF
Username: admin (I should probably change this someday)
Password: XXXXXX
Advanced options: left these as default

I'd say at this point you should check the multimedia settings on the NAS. For mine I think I had to make sure I added SMB protocol enabled for the sharing. My QNAP media streaming app is showing my RuneAudio's IP as connected, but I think it has more to do with this showing up under mapping. I also have it mapped under Windows as Y: drive for \\10.0.0.XX\Multimedia\Music.

englishtim

Hi Everyone,

eea123's comment about SMB reminded me of some mount-related struggles I had a while back with the "official" build on my first-gen Pi Model B...

It seems that RuneAudio can in some circumstances be quite sensitive to the version of SMB that's used to communicate with the NAS - if the SMB version on the NAS is "too new" it borks the communication to the Pi. When I first hit this problem on the official v0.3 build my Pi needed to use SMB 1 - my NAS at the time was set to use SMB 3. Downgrading the SMB version on the NAS fixed the problem. Later builds (for instance Gearhead & Janui's excellent v0.5 beta) are less fussy, and in my experience can tolerate at least SMB 2.

As the OP mentioned that their NAS is PC-based there's a possibility that SMB 1 is disabled - I vaguely recall that Windows does this by default.

Hope this helps,

Peace and friendship,
englishtim

foxint

Guys – thank you.

I do have some questions, things I do not understand:

Eea123:
Make sure I added SMB protocol enabled for the sharing
• I have no idea what this means or how to do this?
• The NAS is an old PC and using it in the windows environment is easy.

Englishtim: Good point. But I have not knowledge of SMB as it relates to windows.

Source Name: your-IP Address
File share protocol: SMB/CIFS
IP address: IP Address – as above
Remote directory: W/Music
Guest access: ON
Username: Greyed out
Password: Greyed out
Advanced options: left these as default

Question: “Log in with guest account NO use/password required”

But when I make the Guest Access OFF – it asks me for a username and password

How do I find out my username and password – I do not use this and no one uses this on the network. Yes, it is not “safe” but if I cannot trust the family who can I trust.

I still get - mount error(112): Host is down Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

eea123

I personally haven't done a PC based NAS, but:

https://www.windowscentral.com/how-access-files-network-devices-using-smbv1-windows-10

The article states Windows 10 no longer supports SMBv1, but has a work around.

janui

Hi Everyone,

Rune 0.5b, when upgraded to the latest patch level, supports all CIFS versions (1.0 to 3.1.1). This includes the standard version on Windows 10. The latest patch level is 7, you should see this in the RuneAudio Debug UI:

Build version: janui-20180903-7

Upgrade to the latest version if this is not the case, instructions are here: #65321

The error message in the first post in this thread

...mount error(112): host is down. Refer to the mount.cifs(8) manual page...

Means that Rune cannot see a valid CIFS or SMB share at the specified IP address.

You should first try pinging the PC from via SSH from Rune, this will verify the network connection:

ping <ip address>

Please post the results.

If that is OK then try this command from SSH to see if shares are being broadcast by Windows:

avahi-browse -atrlkp | grep -Ei 'smb|cifs|nfs' | grep -w '='

You should be able to see the IP address in the response. Again post the results.

janui

foxint

eea123

Thank you.

No still not working. It was a good shot, but I am still not not connecting with the network.

I also just tried the USB. I can see the music, but cannot hear it.

Looks like, as nice as the HiFiBerry DAC+ Pro XLR is....as one bloke on a forum said: "I just could not get it to work". So I am stuck between the hardware people saying it works and the software people saying it works.

Looks like my only option is to throw in the bin.

Then you can get rid of my annoying questions and say yippie....

Ha-ha....I still have the Pi2 Media 502 Dac that still is not configured property...perhaps this one will work???

eea123

That's too bad. Honestly I fought with my setup for a couple of initial go arounds. First being a solder it in yourself DAC card and then getting a pinned connection unit. Still had to do some tweaks, but it is there now. Please also look at the writeup about version 0.5. I'm running version 0.4, but it sounds like it should also help with the PC based NAS issue you are having. I am not sure if a MIME server on the PC side might help?

foxint

Thanks mate

I have updated to 0.5....

Not sure what to do. I have tried Moode. Also not working. But the guys here are fair nicer. I have totally given up on Moode.

I will re-think, but probably throw the HiFiBerry Dac + XLR in the bin and go back to Pi2Media.

Thank you

rastus

foxint wrote...probably throw the HiFiBerry Dac + XLR in the bin and go back to Pi2Media.

If your going to "throw the HiFiBerry Dac + XLR in the bin", I'll have it.... will even drive on up your way to get it. Let me know.....

eea123

Bummer, I should have called dibs first

eea123

foxint wroteeea123
I also just tried the USB. I can see the music, but cannot hear it.

With that being said about your USB, this sounds like it might be the Audio Output Interface under the MPD. I had to change mine since I'm using an eBAY sourced I^2S card. While I'm running v0.4 which says you can change on the fly, I had to coldboot (power cord pull) the PI after I changed it. Now that I think back to it, I actually had to edit the Rune config file remotely from my PC on the PI. That was a 1 year ago and once I got it changed, it took right off. Here's that help discussion: #6335

It looks like I edited the config file to "HiFiBerry DAC", but the current Rune interface says "HiFiBerry DAC+" with no choice for the other when I checked it this morning. My generic I^2S DAC board has RCA line level outs, not XLR.

foxint

eea123

Appreciate your comments.

I have the latest software, and it says I do not need to do any tinkering (Fred).

I not sure what you are suggesting?

(If ti all remains bad, I think I will sell it on eBay - I want some money back for the pain).

rastus

foxint wrote ...throw the HiFiBerry Dac + XLR in the bin...

(If ti all remains bad, I think I will sell it on eBay - I want some money back for the pain).

If you're throwing it "...in the bin...", I'll have it.

If you're going to "...sell it on eBay...", then how much do you want for it?

If you're going to continue to tinker with it, then do it, and stop teasing, some of us take you seriously.

Regards,

Rastus

foxint

Mate

All I am saying is: if there is some light at the end of the tunnel, it is worth continuing. But if no one has any solutions, I may as well give up.

There are a lot of good people who have lots of experience. If I had given up on day 1 I would not have enjoyed the journey or met some nice people.

So if there is no solution there is no solution. But HiFiBerry tell me it works, the RunePeople tells me it works. So I have to give it my best shot.

No hard feeling if it does not work. All I can say is I gave it my best shot.

Do not be so quick to pick the meat of the carcus.