Bad mp3 directory on mt-daapd startup – stumped

[Anonymous]

mt-daapd/Firefly Version: 2.4.2
Server Operating System: Linus – Slackware 12.2
Server Hardware: Pentium PC, 2 MHz
Client Device: Roku Soundbridge, ITunes
Connection of clients: Wifi

When I try to start mt-dappd from root, I get:

Bad mp3 directory (/mnt/mp3/iTunes/music ): No such file or directory

I am mounting a USB Hard Drive as my music file storage. I am able to to cd, write to, and read from the /mnt/mp3/iTunes/music directory as both the “root” and “nobody” users.

As you can see, This USB hard drive used to be what I used under Windows XP Itunes. It has not been re-formatted. However, as I said I am able to mount it and read / write from it.

I have chmod the /mnt/mp3/iTunes/music directory recursively….no help.

This is the startup log when Linux finds the USB HD:

scsi 2:0:0:0: Direct-Access ST340063 3A 3.AA PQ: 0 ANSI: 0
sd 2:0:0:0: [sda] 781422768 512-byte hardware sectors (400088 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 10 00 00 00
sd 2:0:0:0: [sda] Assuming drive cache: write through
sd 2:0:0:0: [sda] 781422768 512-byte hardware sectors (400088 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 10 00 00 00
sd 2:0:0:0: [sda] Assuming drive cache: write through
sda: sda1

Here is how it shows up in fdisk:

oot@workhorse:~# fdisk -l /dev/sd?

Disk /dev/sda: 400.0 GB, 400088457216 bytes
255 heads, 63 sectors/track, 48641 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xc7883ced

Device Boot Start End Blocks Id System
/dev/sda1 * 1 48641 390708801 c W95 FAT32 (LBA)

root@workhorse:~# fdisk -l /dev/sd?

Disk /dev/sda: 400.0 GB, 400088457216 bytes
255 heads, 63 sectors/track, 48641 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xc7883ced

Device Boot Start End Blocks Id System
/dev/sda1 * 1 48641 390708801 c W95 FAT32 (LBA)

root@workhorse:~# mount /dev/sda1 /mnt/mp3

root@workhorse:~# df -k

Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 33641476 4934100 26998464 16% /
tmpfs 254848 0 254848 0% /dev/shm
/dev/sda1 390613408 212956192 177657216 55% /mnt/mp3

Try to star mt-daapd:

root@workhorse:~# mt-daapd -d9
Read web_root: /usr/local/share/mt-daapd/admin-root
Read port: 3689
Read admin_pw: mt-daapd
Read db_dir: /var/cache/mt-daapd
Read mp3_dir: /mnt/mp3/iTunes/music
Read servername: mt-daapd
Read runas: root
Read playlist: /etc/mt-daapd.playlist
Read extensions: .mp3,.m4a,.m4p
Checking existence of /mnt/mp3/iTunes/music
Bad mp3 directory (/mnt/mp3/iTunes/music ): No such file or directory
Error reading config file (/etc/mt-daapd.conf)

However, I can:

root@workhorse:~# cd /mnt/mp3/iTunes/music

root@workhorse:/mnt/mp3/iTunes/music# cd ..

root@workhorse:/mnt/mp3/iTunes# ls

Album Artwork iT 1.tmp iT 2.tmp iT.tmp iTunes Library.itl iTunes Music Library.xml music

root@workhorse:/mnt/mp3/iTunes# cp iT.tmp /tmp

root@workhorse:/mnt/mp3/iTunes# ls -l /tmp/iT.tmp
-rwxr-xr-x 1 root root 69809644 2008-12-15 15:55 /tmp/iT.tmp

I can also access the mount from “nobody”, even though it should not matter because i have switched mt-daapd to “runas” root:

root@workhorse:/mnt/mp3/iTunes# su – nobody

nobody@workhorse:/$ cd /mnt/mp3/iTunes
nobody@workhorse:/mnt/mp3/iTunes$ ls
Album Artwork iT 1.tmp iT 2.tmp iT.tmp iTunes Library.itl iTunes Music Library.xml music

I have googled my brains out and tried everything I could find, no help. Does anyone have any suggestions? I am realtively new to Linux, but know enough to followup suggestions.

My hunch is that I am not mounting it with the right parameters, just dont understand why I can read/write to the mount in that case.

Any help or suggestion would be greatly appreciated, I would really like to get mt-daapd on Slackware working withthe Roku ASAP. My Xmas CDs are on there!! 🙂

Thanks,

Curt

[EVILRipper]

Don’t really know if this will help, but I had a similar problem.
I mounted my usb hard disk using /etc/fstab .
My guess is that that harddisk is formatted in FAT as windows and linux both have no trouble using it.
(FAT in linux is sometimes known as vfat)
When mounting a FAT harddisk, you can determine the permissions in /etc/fstab.

If you run ‘man mount’ you get the manpage for the mount option.
These static mount options are determined in the /etc/fstab when booting.
When you scroll down the manpage, near line 412, there are specific “Mount options for fat”.
The umask determines the permissions for the mounted drive.

Not sure whether this would be useful for your situation, but at least I tried. 🙂

[fizze]

The umask for the fat is most likely the culprit. Set it to be umask=0000 in the fstab entry, then every user has full access to every folder.
Everything else is extremly troublesome in linux with multiple users and groups.

[Author]

Posts