NAS is qnap ts-210 all up to date
NAS IP address on lan = 192.168.1.68
Music is in /music folder on NAS
pi user is set up on NAS with password pi
To check this is OK on NAS, have mounted on windows PC using the IP addess and the pi/pi user/pass and it is fully accessible; I can read and write (\\192.168.1.68\music)
On the Raspyfi, NAS information has been added to /etc/auto.nas
[email protected]:~$ more /etc/auto.nas
# /etc/auto.server
# list all the shares to automount, here are some examples
# you need one credential file per different username/password combination
#Nas -fstype=cifs,file_mode=0777,dir_mode=0777,iocharset=utf8,rsize=130048,wsize=4096,cache=strict,username=pi,p
assword= ://192.168.x.x/x
music -fstype=cifs,file_mode=0777,dir_mode=0777,iocharset=utf8,rsize=130048,wsize=4096,cache=strict,username=pi,
password=pi ://192.168.1.68/music
On the Raspyfi, my attempts to mount in /etc/fstab have been commented out
[email protected]:~$ more /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
# / was on /dev/mmcblk0p3 during installation
/dev/mmcblk0p3 / ext3 noatime,errors=remount-ro 0 1
# /boot was on /dev/mmcblk0p1 during installation
/dev/mmcblk0p1 /boot vfat utf8 0 0
# swap was on /dev/mmcblk0p2 during installation
#UUID=a415139e-91c5-49a6-8cc3-192b4cd409f9 none swap sw 0 0
none /run/shm tmpfs defaults,size=256M,noexec,nodev,nosuid 0 0
#
#access to music on nas
#//192.168.1.68/music /mnt/nas cifs username=pi,password=pi
#
#//192.168.1.68/music /mnt/nas cifs username=pi,password=pi,uid=mpd,file_mode=0644,dir_mode=0755,iocharset=utf8,rs
ize=130048,wsize=4096 0 0
Raspyfi then rebooted; no mention of cifs in dmesg & checking the /mnt directories,
[email protected]:~$ dmesg | grep cifs
[email protected]:~$ ls /mnt
music nas Nas
[email protected]:~$ ls /mnt/music
[email protected]:~$ ls /mnt/nas
[email protected]:~$ ls /mnt/Nas
music
[email protected]:~$ ls /mnt/Nas/music
ls: cannot open directory /mnt/Nas/music: No such file or directory
[email protected]:~$ dmesg | grep cifs
[ 156.481998] CIFS VFS: cifs_mount failed w/return code = -22
[email protected]:~$
It appears to be creating the music directory on the Raspyfi in /mnt/Nas/music, though I'd expect it to be in /mnt/music, but when an attempt to access /mnt/Nas/music is made, cifs_mount fails with the code of -22
GPMC connects fine to Raspyfi, click update mpd database but no files appear. The same happens with mpad, but this is no surprise!
Am I doing something stupid with getting the Raspyfi to mount the NAS drive? Have I left out an important step?
Try with this:
Nas -fstype=cifs,file_mode=0777,dir_mode=0777,iocharset=utf8,sec=ntlm,rsize=2048,wsize=4096,cache=strict,username=pi,password= ://192.168.1.68/music
Remove previous lines. I suspect this wasn't working cause you used a password, and because you changed the folder to music. Mind also that the share is mounted only when needed.
So, having this edited. Type:
sudo ls /mnt/Nas/Nas
and your files should appear! Then update the db. I'm sure it will work!
Unfortunately not
When I try it, dmesg shows the following:-
[ 263.987205] CIFS: Unknown mount option "password="
Long shot, this, but, in RC2, I could not get my NAS (Synology DS211j) to mount in /etc/fstab unless I used the NAS domain name in front of the username.
Try adding it in auto.nas first then, if that doesn't work, try in /etc/fstab. So, your file should have something like (from memory) username=nasname/pi, password=pi etc. Obviously 'nasname' is whatever your Qnap (nice NAS, by the way) is called.
Thought just occurred – is 'pi' the administrator username on the Qnap? Might be worth trying the admin username and password in auto.nas.
Hi Derek – I tried putting the NAS' domain in a couple of days ago but no success (noting the domain set on the NAS, but also that the NAS was set to ignore it)
I might try the Qnap admin username password, but I'm not keen to do that as a) I'd rather keep that for administration and not have it in the clear on the pi and b) I didn't need to do that on RC2 which (more or less) worked fine
Regards the Qnap itself, it's "OK" but let down in a couple of ways, the main thing for me being that with it being the low-powered version (bought as it would be on 24/7) isn't powerful enough to run Plex. So if I want to share my video content seemlessly across my LAN to my media centre Pi and Roku boxes then I need to have my PC humming away to transcode which sort of defeats the object of having a NAS…
Got a few minutes to play.
Decided to rewrite the 8GB sd card, grab the release 2 Pi and start from stratch.
Ethernet came up straight away.
ran wicd-curses and set the wifi. That worked straight away.
edited /etc/auto.nas exactly as Michelangelo suggested up there
Wifi works, Nas mounts, database updates as does the cache.
All brilliant
Until I try and play anything…
I'm going to try and investigate the other pi as soon as my next 8GB card turns up
Well, that's progress of sorts. Keep going. Guess all this is what you'll one day call 'experience'. What happens when you try and play?
If you're ever in the market for a different NAS have a look at Synology – very satisfied with mine, especially the remote apps/capabilities.
I'm feeling rather guilty that I only come here with problems, not solutions however, i just want to say
I AM PLAYING MUSIC THROUGH MY RASPYFI AGAIN!
No jokes, it's working.
Not quite as I'd like, but it's working.
So… having restarted with a fresh build and the other Pi, the wireless was fine and the NAS came up as per my other post up there.
Initially I had problems with the Hiface 2:
[ 449.940865] ERROR::handle_hc_chhltd_intr_dma:2537: handle_hc_chhltd_intr_dma: Channel 6, DMA Mode -- ChHltd set, but reason for halting is unknown, hcint 0x00000002, intsts 0x04400001
[ 449.940865]
[ 464.159560] 5:1:1: usb_set_interface failed (-71)
[ 473.873505] 5:1:1: usb_set_interface failed (-71)
[ 498.800513] 5:1:1: usb_set_interface failed (-71)
[ 500.052033] 5:1:1: usb_set_interface failed (-71)
[ 505.681630] 5:1:1: usb_set_interface failed (-71)
[ 546.062554] 5:1:1: usb_set_interface failed (-71)
[ 549.957857] 5:1:1: usb_set_interface failed (-71)
[ 558.482076] 5:1:1: usb_set_interface failed (-71)
[ 4706.164185] 5:1:1: usb_set_interface failed (-71)
[ 4706.920166] 5:1:1: usb_set_interface failed (-71)
[ 4712.441692] 5:1:1: usb_set_interface failed (-71)
[ 4780.949853] 5:1:1: usb_set_interface failed (-71)
[ 4782.000623] 5:1:1: usb_set_interface failed (-71)
[ 4795.711126] usb 1-1.3: USB disconnect, device number 5
[ 4802.344158] usb 1-1.3: new high-speed USB device number 6 using dwc_otg
[ 4802.466193] usb 1-1.3: New USB device found, idVendor=249c, idProduct=930b
[ 4802.474914] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4802.483988] usb 1-1.3: Product: M2Tech USB Audio 2.0
[ 4802.490615] usb 1-1.3: Manufacturer: M2Tech
[ 4802.496486] usb 1-1.3: SerialNumber: 0000
[ 4802.507554] ERROR::handle_hc_chhltd_intr_dma:2537: handle_hc_chhltd_intr_dma: Channel 7, DMA Mode -- ChHltd set, but reason for halting is unknown, hcint 0x00000002, intsts 0x04600001
[ 4802.507554]
[ 4812.508735] parse_audio_format_rates_v2(): unable to find clock source (clock -71)
[ 4812.525223] cannot get ctl value: req = 0x83, wValue = 0x201, wIndex = 0xa00, type = 4
[ 4812.544485] cannot get ctl value: req = 0x83, wValue = 0x200, wIndex = 0xa00, type = 4
[email protected]:~$
And every time I pressed play it went straight back to paused.
I moved all the USB (both wifi and hiface 2) to an external Belkin powered hub (http://www.belkin.com/uk/p/P-F4U039). I no longer did I get the errors, and the music now seems to "play" on mPad. However there's no audio from the amp. The DAC shows sync lock, which indicates that it's connected and the hiface 2 is powered. dmesg has no mention of the hiface 2 so it appears that the pi is simply not noticing it when it's on the hub. Odd.
I disconnected the hiface 2 and went back to the USB connection on the DAC (from the Belkin hub, rebooted and could then play just as it should. I get a constant stream of messages like this in the log; not sure if that's normal or not.
[ 9762.132763] delay: estimated 0, actual 132
[ 9762.140764] delay: estimated 0, actual 132
[ 9762.148769] delay: estimated 0, actual 133
[ 9762.156776] delay: estimated 0, actual 133
[ 9762.164767] delay: estimated 0, actual 133
[ 9762.172769] delay: estimated 0, actual 132
[ 9762.180770] delay: estimated 0, actual 132
[ 9762.188770] delay: estimated 0, actual 133
[ 9762.196818] delay: estimated 0, actual 133
[email protected]:~$
Breaking news…
for a further experiment, I disconnected the hiface 2 from the hub and reconnected it directly to the pi (so now wifi on powered hub, but hiface 2 on pi USB)
And it now plays properly.
Hurrah!
So it appears that…
1. The new pi isn't happy with both wifi and hiface 2 on the on-board usb (power limitations??)
2. The pi isn't happy with the hiface 2 on an hub, but it is on the on-board USB
3. The pi *is* happy with the USB cable to the DAC on the hub
Right now, everything appears to be working as it should.
Whilst waiting for my new 8GB SD cards, I'm rebuilding a RC2 Raspyfi to start trying to diagnose the problems I've been having, as I'd like to know why I had problems with wifi and the NAS rather than just being pleased that they've gone away!
Thanks for all the help getting this far.
That's right, wi-fi and hiface need too much current for the pi… And maybe connecting to the USB hub somehow polluted the usb signal so the Hiface cannot play. The best solution then is to have wi-fi on the hub and the hiface on the Pi.
Glad you did!
Though it was working fine with hiface and wifi on RC2 on mk1 pi.
And the mk1 had the current limited polyfuses, so I'd expect the mk2 to perform better than the mk1 with USB current draw.
After going beck down stairs, I've since noticed that I my higher bit-rate audio isn't starting and I'm getting occasional breaks in the audio on 44.1KHz playback, so I'm tempted to run a wired ethernet to see if that helps.
An inability to log in during playback suggests that the wifi's a bit busy
[ 8258.054488] ERROR::handle_hc_chhltd_intr_dma:2537: handle_hc_chhltd_intr_dma: Channel 6, DMA Mode -- ChHltd set, but reason for halting is unknown, hcint 0x00000002, intsts 0x04600001
… and the Raspyfi is down
Time to switch it off and back on again
This one:-
http://uk.rs-online.com/web/p/…..y/7263069/
I used that power supply quite happily with RC2 with a release 1 pi with the wifi and hiface2 both plugged in to the pi.
The latest problem was with the beta with the hiface2 plugged in to the release 2 pi and the wifi plugged in to an active belkin USB hub.
I've since swapped the release 2 out for the original release 1 and that's holding up. Probably should have left if alone and playing for a few days rather than changing things but i wanted the release 2 pi for another experiment (that might get mentioned in the RC2 checking thread…)
Most Users Ever Online: 200
Currently Online:
6 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Gyp: 82
yoghurtlidlicker: 37
PaulM: 36
icai: 35
Derek: 29
Karsten: 27
tc-fi: 22
Ronaldo: 21
ENSen: 21
chriz: 20
Member Stats:
Guest Posters: 3619
Members: 569
Moderators: 0
Admins: 1
Forum Stats:
Groups: 4
Forums: 10
Topics: 469
Posts: 13163
Newest Members: polo2016, dongdong8, wlpwlp, Sager, ninestab123, lmx66, lmx, jlgg, chenyan, guoyanying
Administrators: admin (401)