Getting my Joggler to see my NAS

[stepoon]

Hi,

I've got a NAS with all of my music on (Linkstation Pro v2 with a 320gb HDD) - i'm trying to get my joggler to see it but i'm totally stuck. I launch the squeezebox server in my web browser but when I add music sources all I see is the folders on the Joggler? Can someone enlighten me on how to get it working at all?

I did manage to get squeezebox server installed on the linkstation but it says that I need to upgrade it for the squeezeplay on the joggler to see it and I'm stuck!

Cheers in advance

[ARJunior]

You probably have to update to Logitech Media Server 7.7 or above...
Verify the version you've installed on your linkstation...

[multiplex]

This thread my help you; http://www.jogglerwiki.com/forum/viewto ... ?f=2&t=275 get the share on your NAS visible. Shout if there are any gaps.

I don't know about the Versions of SQP and server - I've not changed anything since I got it all working

[stepoon]

I think it was 7.33 or something? Found a guide and followed that

[stepoon]

Hi,

I'm totally at loggerheads with this... can someone help me with a step by step guide ?

I've been trying for a week now and am just not getting anywhere.

I've downloaded the cifs kernel module, but then i'm puzzled about where to ssh it into the joggler. I open up tenet etc and i'm bamboozled by the code.

My Linkstation has a folder called share then a folder inside called music so is the path /mnt/disk1/share/music?

Surely it shouldn't be this difficult?

HELP!!

[multiplex]

Hi

Which O/S are you doing this on? - I got it working on Ubuntu in the thread I linked to above (with a little hassle with the fstab file) - I've not tried on the Native O/S - I imagine it would be similar but I have no idea about where you'd get a suitable samba module from.

[stepoon]

Hi,

I'm using the PnP MK II OS...

I can telnet into my linkstation & the joggler. the commands to put the cifs kernel etc in is where i'm stuck, I can't see where to put this , im also not sure about fstab files?

I'm quite happy to tinker around with bits and bobs but this has really baffeled me!

Is there an idiots guide anywhere>?

[multiplex]

Hang on... I think I've got completely the wrong end of the stick here!

you said you've installed Squeesebox server on your linkstation, but PNP puts one on the Joggler - which one are you connecting to with your browser?

For the cifs kernel files I guess you're talking about the jogger - how did you find out where to get the right files from? THat shoudl have had instructions on installing them...

[stepoon]

Yeah - I have squeezebox server installed on my Linkstation but it's only version 7.33 or something. Squeezeplay on the joggler won't see the Linkstation as it says it needs a newer version on the NAS to connect.

So I've decided to use the Squeezeplay server on the joggler to connect to the Linkstation.

I download the cifs kernel from the instructions, but i'm puzzled as to where it goes etc.

[multiplex]

I download the cifs kernel from the instructions, but i'm puzzled as to where it goes etc.

What instructions?

[stepoon]

This link

http://webdiary.com/2010/11/05/squeezeb ... -a-budget/

I've a feeling i've got totally mixed up with how I should be doing this?!

[multiplex]

I've a feeling i've got totally mixed up with how I should be doing this?!

I wouldn't say that (yet)

I'm guessing that you are naturally a Windows user so I'm going to suggest that you use WinSCP - that needs SSH, did you enable that or just Telnet?

[stepoon]

Yeah i've got Winscp open and can connect to the Joggler and see all the file structure in it.

This correct?

[Wilberforce]

Id start off entering the commands manually and see what is output. How far have you got? Have you loaded the kernel module?

Edit: looking at your above posts I'm going to guess you havent transfered the kernel module to your joggler.

Probably easiest to put it on a usb stick then do something like the following:

make a working dir. ( mkdir /cifs)
plug in your usb
check your dmesg:
dmesg > /cifs/dmesg
tail /cifs/dmesg
look for device id in form sd*, where star is a letter.
make a mnt point:
mkdir /mnt2
mount the usb stick using device id from earlier:
mount /dev/sda /mnt2
copy the cifs module onto the joggler:
cp /mnt2/cifs.ko /cifs
load kernel module:
insmod /cifs/cifs.ko
try mount your share (if you dont use a username and pass try -o guest instead):
mkdir /mnt3
mount -t cifs //192.168.1.2/share/music /mnt3 -o user=music,password=secret
remember to replace ip with the one you use for your nas!

[stepoon]

How do I load it? Thats where i'm stuck

[Wilberforce]

New message in case you miss the edit:

make a working dir. ( mkdir /cifs)
plug in your usb
check your dmesg:
dmesg > /cifs/dmesg
tail /cifs/dmesg
look for device id in form sd*, where star is a letter.
make a mnt point:
mkdir /mnt2
mount the usb stick using device id from earlier:
mount /dev/sda /mnt2
copy the cifs module onto the joggler:
cp /mnt2/cifs.ko /cifs
load kernel module:
insmod /cifs/cifs.ko
try mount your share (if you dont use a username and pass try -o guest instead):
mkdir /mnt3
mount -t cifs //192.168.1.2/share/music /mnt3 -o user=music,password=secret
remember to replace ip with the one you use for your nas!

Edit: Missed the fact you got WinSCP working... If thats the case, its probbaly easier to use that to transfer the kernel module to the joggler, then pickup from loading the kernel module (use telnet or ssh if it's set up).

[stepoon]

Tried to mount the share and it says something about busy box etc then a long list of code.... When i go into the file structure the mnt3 folder is now there but no mounted drive. Think I may have to give up!

[Wilberforce]

can you copy and paste the output? Also, I made a mistake in my instructions from mounting a usb stick - you need to specifiy the partition number:
e.g mount /dev/sda1 /mnt2,
but im guessing you managed to copy the kernel module over ok. Did it load without errors? What is the result of lsmod | grep cifs after you have loaded the module with insmod?

[stepoon]

Hi,

This is what I get

/$ mount -t cifs //192.168.0.10/share/music /mnt3 -o
mount: option requires an argument -- o
BusyBox v1.10.4 (2010-06-25 14:21:21 EDT) multi-call binary

Usage: mount [flags] DEVICE NODE [-o options,more-options]

Mount a filesystem. Filesystem autodetection requires /proc be mounted.

Options:
-a Mount all filesystems in fstab
-f don't mount
-r Read-only mount
-t fs-type Filesystem type
-w Read-write mount (default)
-o option:
[a]sync Writes are asynchronous / synchronous
[no]atime Disable / enable updates to inode access times
[no]diratime Disable / enable atime updates to directories
[no]dev Allow use of special device files / disallow them
[no]exec Allow use of executable files / disallow them
[no]suid Allow set-user-id-root programs / disallow them
[r]shared Convert [recursively] to a shared subtree
[r]slave Convert [recursively] to a slave subtree
[r]private Convert [recursively] to a private subtree
[un]bindable Make mount point [un]able to be bind mounted
bind Bind a directory to an additional location
move Relocate an existing mount point
remount Remount a mounted filesystem, changing its flags
ro/rw Mount for read-only / read-write

There are EVEN MORE flags that are specific to each filesystem
You'll have to see the written documentation for those filesystems

??

[Wilberforce]

I think the command you want is:
mount -t cifs //192.168.0.10/share/music /mnt3 -o guest