I still need someone’s help.
I cannot use my hpfs HDD from moode audio player 3.1 still.
It seems USB HDD could not mount.
So mpd does not see my USB HDD.
I sshed to my mood.local and found was as follows.
It seems moodeOS recognize my USB Disk as /dev/sda and my music partition can see as /dev/sda2.
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 8192 131071 122880 60M c W95 FAT32 (LBA)
/dev/mmcblk0p2 131072 62945279 62814208 30G 83 Linux
Disk /dev/sda: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 2DE3740C-2E5C-4DA1-BB9E-82934DE0B0CD
Device Start End Sectors Size Type
/dev/sda1 34 262177 262144 128M Microsoft reserved
/dev/sda2 264192 5860532223 5860268032 2.7T Microsoft basic data
And I could not find my USB Disk on fstab.
fstab
proc /proc proc defaults 0 0
/dev/mmcblk0p1 /boot vfat defaults 0 2
/dev/mmcblk0p2 / ext4 defaults,noatime 0 1
# a swapfile is not a swap partition, no line here
# use dphys-swapfile swap[on|off] for that
What should I do?
Thank you for your advice in advance.
Hiroyoshi Satoh
Hi Hiroyoshi,
Moode uses udisks-glue for auto mounting USB storage devices. Its config file is /etc/udisks-glue.conf
What file system is being used on your disk? Run cmd below to display the file system type.
sudo blkid /dev/sda
-Tim
My Audiophonics board is a different model than the one in the photograph from that link.
Just for fun, I updated and older RPi I have had for some time, it is a PiFi DAC+ v2.0 (from what is printed on the board) which gets configured as a HiFiBerry DAC+. When I play the Stereo Test from the SD card the Left and Right are correct. YMMV.
Hi,
Pi-Zero W working nicely with Moode 3.5 Standard kernel 4.4.50 🙂 Got a bit of soldering to do this coming weekend then will be verifying I2S audio function using an IQaudIO Pi-DACZero.
The W was provided compliments of @Zootalaws. Thanks Mike!
-Tim
Pi-Zero W working nicely with Moode 3.5 Standard kernel 4.4.50 🙂 Got a bit of soldering to do this coming weekend then will be verifying I2S audio function using an IQaudIO Pi-DACZero.
The W was provided compliments of @Zootalaws. Thanks Mike!
-Tim
Attachments
Tim,
I'm loving Moode, it just works and sounds great!
A couple of questions:
1) I am struggling a bit with access to the web based UI. I am only able to access it from one device at a time, is that per design? (I'd seen one of your 2015 posts on computeraudiophile website which said that you could access from more than one device at a time.)
2) Additionally, what is the best way to recover if i can't access via the web based UI? Pulling the power results in SD card corruption issues. (any special network settings needed?)
3) Moode works great for me when i leave it alone and let it play music but occasionally when creating playlists or other tasks it appears to lock up or I lose access to the web UI but music keeps playing. Any precautions that I need to follow to prevent these issues?
Thanks & Keep up the great work!!!!!!!
Greg
I'm loving Moode, it just works and sounds great!
A couple of questions:
1) I am struggling a bit with access to the web based UI. I am only able to access it from one device at a time, is that per design? (I'd seen one of your 2015 posts on computeraudiophile website which said that you could access from more than one device at a time.)
2) Additionally, what is the best way to recover if i can't access via the web based UI? Pulling the power results in SD card corruption issues. (any special network settings needed?)
3) Moode works great for me when i leave it alone and let it play music but occasionally when creating playlists or other tasks it appears to lock up or I lose access to the web UI but music keeps playing. Any precautions that I need to follow to prevent these issues?
Thanks & Keep up the great work!!!!!!!
Greg
Tim,
I'm loving Moode, it just works and sounds great!
A couple of questions:
1) I am struggling a bit with access to the web based UI. I am only able to access it from one device at a time, is that per design? (I'd seen one of your 2015 posts on computeraudiophile website which said that you could access from more than one device at a time.)
2) Additionally, what is the best way to recover if i can't access via the web based UI? Pulling the power results in SD card corruption issues. (any special network settings needed?)
3) Moode works great for me when i leave it alone and let it play music but occasionally when creating playlists or other tasks it appears to lock up or I lose access to the web UI but music keeps playing. Any precautions that I need to follow to prevent these issues?
Thanks & Keep up the great work!!!!!!!
Greg
Hi Greg,
In my environment:
- I often have multiple clients connected a single Pi and no issues.
- I frequently just pull the plug and no sd card corruption.
- I've only had one sd card go bad in over 3 years and my systems really get heavy r/w I-O and are running 7/24/365. I use Sandisk Ultra Class 10 cards 🙂
The symptoms that you describe suggest issues external to Moode software for example network issues, bad SD card, bad power supply.
1) "I am only able to access it from one device at a time"
2) "occasionally when creating playlists or other tasks it appears to lock up or I lose access to the web UI but music keeps playing"
3) "Pulling the power results in SD card corruption issues"
-Tim
Thanks. I'm using an IQ Audio Pi-DAC+ with TI chip.
Tim,
I'm loving Moode, it just works and sounds great!
A couple of questions:
1) I am struggling a bit with access to the web based UI. I am only able to access it from one device at a time, is that per design? (I'd seen one of your 2015 posts on computeraudiophile website which said that you could access from more than one device at a time.)
2) Additionally, what is the best way to recover if i can't access via the web based UI? Pulling the power results in SD card corruption issues. (any special network settings needed?)
3) Moode works great for me when i leave it alone and let it play music but occasionally when creating playlists or other tasks it appears to lock up or I lose access to the web UI but music keeps playing. Any precautions that I need to follow to prevent these issues?
Thanks & Keep up the great work!!!!!!!
Greg
When I have had those symptoms, rewriting my SD has fixed it. Not that the SD has gone bad, but that there was some sort of error in the first place. When you write the image, make sure all your checksums from the moodeaudio link match up. (As I have found recently!)
Ok, i've discovered that I can access the pi on both my android phone and tablet simultaneously if I access via its IP address but access via diyAudio server HTTPS page doesn't work with the Chrome app. I can access my pi with my macbook pro via diyAudio server HTTPS page or its IP address.
Does this make any sense?
Thanks
Greg
Does this make any sense?
Thanks
Greg
Ok, i've discovered that I can access the pi on both my android phone and tablet simultaneously if I access via its IP address but access via diyAudio server HTTPS page doesn't work with the Chrome app. I can access my pi with my macbook pro via diyAudio server HTTPS page or its IP address.
Does this make any sense?
Thanks
Greg
Hi Greg,
Android OS does not support multicast DNS (mDNS, Zeroconf, Avahi, etc.) which means that it does not support the .local domain so http:// moode.local will not work. Android is only OS that I know of that does not support mDNS.
Furthermore if your Router does not support dynamic DNS whereby when the client receives its ip address from DHCP the DHCP server also updates DNS with the clients host name, then http: //moode will not work.
That leaves http: //IP_ADDRESS as the only option.
-Tim
Yes, and it bites me on the *** all the time. I have to remember to check the polarity with the sound check file on the SD card.
It is Moode at fault - all my interlinks and speaker cables are the right polarity for other sources. To remedy I switch the rca plugs at the Pi.
Maybe Tim can tell us why Moode is ***-backwards, if he has power and hasn't lost the tips of his fingers to frostbite 🙂
Hi Mike,
I ran quick test using a DAC PRO with both headphones and speakers and no issues. L/R channels are as they should be. Same for my other DAC's.
-Tim
I use 2 RPis, a Pi3, Moode v3.2 with HiFiBerry Digi+ Pro, WiFi turned off, Samsung Evo 540 SSD to USB for most of my music and WD Duo NAS. All works flawlessly, superb sound, Many Thanks.
My second system uses an earlier Pi B+, PiHut USB WiFi adaptor, Moode V2.7 with HiFiBerry Amp+ which has worked well until recently when I started losing some of the higher bit rate BBC radio streams. I tried unsuccesfully to update to Moode V3.2, but seem to recall that it won't work with the Pi B+. Searched the forum but can't find a specific warning V3.2 won't work with the PI B+. Should it work or does it need some amendments?
My second system uses an earlier Pi B+, PiHut USB WiFi adaptor, Moode V2.7 with HiFiBerry Amp+ which has worked well until recently when I started losing some of the higher bit rate BBC radio streams. I tried unsuccesfully to update to Moode V3.2, but seem to recall that it won't work with the Pi B+. Searched the forum but can't find a specific warning V3.2 won't work with the PI B+. Should it work or does it need some amendments?
Yes, and it bites me on the *** all the time. I have to remember to check the polarity with the sound check file on the SD card.
It is Moode at fault - all my interlinks and speaker cables are the right polarity for other sources. To remedy I switch the rca plugs at the Pi.
Maybe Tim can tell us why Moode is ***-backwards, if he has power and hasn't lost the tips of his fingers to frostbite 🙂
Hi Mike,
I too used to suffer from 'Mr Potato-Head syndrome' but found that by painting an 'R' and an 'L' on each of my ears I was able to place them correctly when waking each day. 😀😛
Seriously though, never had a problem with channels being reversed in any of my Pi's and Moode .
Seems strange as I am sure you have your wiring sorted given what you do for a crust. Presumably it happens on all your Pi's ? and not just one aberrant unit...
Last edited:
Problem writing to auto mounted usb disk
Hi,
First, thank you for the great player. It really sound superb.
I have a usb disk connected to my rpi. it has NTFS file system on it (don't ask me why) and all my music is stored on it. it is auto mounted as:
It works well as music source but when I try to add new music to it (with sudo cp), the cp never finish writing. It worked well with runeaudio but i don't think it was automounted. If anyone has any idea why this is happening, I would be grateful. Failing that, i will rebood the rune, and see how it was mounted there....
Best regards,
Moshe
Hi,
First, thank you for the great player. It really sound superb.
I have a usb disk connected to my rpi. it has NTFS file system on it (don't ask me why) and all my music is stored on it. it is auto mounted as:
Code:
/dev/sda1 /media/Seagate\040Expansion\040Drive fuseblk rw,sync,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0
It works well as music source but when I try to add new music to it (with sudo cp), the cp never finish writing. It worked well with runeaudio but i don't think it was automounted. If anyone has any idea why this is happening, I would be grateful. Failing that, i will rebood the rune, and see how it was mounted there....
Best regards,
Moshe
It might be the "sync" option in conjunction with recent kernel "enhancements".
AIUI it now updates the FAT/whatever, every time it performs a write. In conjunction with "sync", that means it's asking the disk (slow) an awful lot of questions.
AIUI it now updates the FAT/whatever, every time it performs a write. In conjunction with "sync", that means it's asking the disk (slow) an awful lot of questions.
mmmm that might be the case, as touch worked and i stopped the cp (of 7mb file!) after a min or so. Is there a script or anything that makes the automount that i can change?
Hi Mike,
I ran quick test using a DAC PRO with both headphones and speakers and no issues. L/R channels are as they should be. Same for my other DAC's.
-Tim
I've got a Pi-DAC+
I tried turning the amp around, performing an and/or on my MP3 files - nada. Red is white and white is red.
Maybe Gordon got a mismatched set of connectors?
This is what mine looks like.
https://flic.kr/p/RJetgN
Headphones sound normal too - it's not Moode, as far as I am aware. Looks like manufacturing. I'll open one up and check the traces.
mmmm that might be the case, as touch worked and i stopped the cp (of 7mb file!) after a min or so. Is there a script or anything that makes the automount that i can change?
/etc/udisks-glue.conf
-Tim
Tim, I would love to be a beta tester!!! Have zero W and Pi3..
I can also participate in beta testing of 3.5.
I have now a shiny new Pi3 and the Allo BOSS DAC.
I can also participate in beta testing of 3.5.
I have now a shiny new Pi3 and the Allo BOSS DAC.
+1 !
Just bought a Raspberry PI ZERO W. I'll would like to test moode 3.5 image on my Pi-ZeroW.
Is it possible ?
Thanks in advance.
Giorgino
- Home
- Source & Line
- PC Based
- Moode Audio Player for Raspberry Pi