O2 Joggler Forum

Yup your mount command doesn't show the USB stick mounted.

If you do an FDISK -L you will see the following. See if you see the USB stick.

root@ICS-MythTV:~# fdisk -l

Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders, total 234441648 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
Disk identifier: 0x00040a95

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 226260991 113129472 83 Linux
/dev/sda2 226263038 234440703 4088833 5 Extended
/dev/sda5 226263040 234440703 4088832 82 Linux swap / Solaris
root@ICS-MythTV:~#

@ilovemyjoggler,

Thanks for the reply, i did check for remove for reinstall file in the root of the usb, but did not find anything, also i did try 6 usb drives as mentioned above. Also i did use joggler as a password, in order to insert the commants shown above.

@pete_c this is what i get if i write FDISK -L:

atom login: joggler
Password:

OpenPeak Atom BSP ("Frame")
Copyright(C) 2008 OpenPeak, Inc.
All rights reserved.
# FDISK -L
-sh: FDISK: not found

So i suppose it will not find the usb drive. The funny thing is that when i use reflash tool to install openpeak image or squeezeplay,usb is recognized, when i use the same usb drive to install pnpii it is not recognized...WHY?????any suggestions?

Commands are case sensitive on linux so try fdisk - l not FDISK - L

JimbobVFR400 wrote:Commands are case sensitive on linux so try fdisk - l not FDISK - L

I did try both,I can get the above message only with FDISK -L

The message above means it's not a valid command. Type wibblewobble at the command line and you'll get the same message. What actually happens with the correct syntax.

See if fdisk is there by looking at the directory:

root@ICS-MythTV:/# cd sbin
root@ICS-MythTV:/sbin# ls fd*
fdisk
root@ICS-MythTV:/sbin#

I'm guessing that fdisk might be there but FDISK won't be.

Probably the first lesson for anyone using the forums is that linux is case-sensitive and that fdisk isn't the same as FDISK or even Fdisk. It's an easy mistake to make if you use Windows most of the time and I remember making similar errors when using linux myself for the first time, way back in the late 20th century.

Commands should always be duplicated exactly as they appear in this forum. At least then if they don't work it's due to a genuine scripting error rather than spelling and syntax mistakes when copying . If a script fails when executed properly, you will probably get a more meaningful error message than a command not being found.

@ttherapo - Since you say that you've tried fdisk -l what was the output when you ran that command?

Just got a brand new in the box OpenPeak branded Joggler. That said the OS looks to be like your PnP3 dave.

Ah you should license it such that you get the royalties from it. (even better if you do a graduated by the widget royalties charge)

First thing with first boot; it doesn't do that weird white screen thing. Thinking so far all of the OpenPeak Jogglers do not do this (must be an odd hardware thing).

I ssh'd into this "virginal" OpenPeak box (thinking the count is now at 16-17 of these boxes) and can do all and see all just fine. OK I will quit now collecting Jogglers. I don't know why I keep doing this.

@ttherapo - I agree with gegs/JimbobVFR400 on the upper and lower case thingy.

Just tried it again. With no USB stick I see nothing after doing an fdisk -l

login as: joggler
joggler@192.168.244.253's password:
# fdisk -l

With a USB stick inserted I see the following with typing an fdisk -l

# fdisk -l

Disk /dev/sda: 7944 MB, 7944011776 bytes
4 heads, 32 sectors/track, 121216 cylinders
Units = cylinders of 128 * 512 = 65536 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 17 992 62464 e Win95 FAT16 (LBA)
/dev/sda2 993 4896 249856 82 Linux swap
/dev/sda3 4897 60944 3587072 83 Linux

EDIT 4th MAY 16:32: STILL TINKERING BUT ALMOST THERE!

To install cifs (if not already installed) telnet/putty in and enter To install easy access to Network Share mounting via the Webserver, telnet/putty in and enter: There should then be an additional option at the top of the Webserver page (accessed by typing the Joggler's IP into a browser on a networked computer) to mount a Network Share. This should then appear in /media/media in Logitech Media Server. You can point LMS at it by going to Settings->Basic Settings->Media Folders

Thanks to gforums (original author of the first PnP) for creating this feature which I've simply resurrected and tweaked. I'll get it included by default on the next version on PnP III when I get a chance.

Hmm. Now I get cannot insert cifs.ko Invalid module format. Will investigate later.

Right, just about got mounting of shared folder sorted. Now to investigate cifs.ko module issue.

EDIT: Ah-ha - I think I was just having an issue with the router firewall/filtering/parental controls blocking the proper download of stuff from Dropbox to the kids Jogglers. Just tried it with a 'grown-up' Joggler and seems like we might be onto a winner with the above script. Scanning now. Will test more tomorrow.

Hmm. Scans first time OK 14000+ files and folders. Then an automatic overnight rescan seems to lock it up on file 67 or 68 out of 958 new or changed files. If I abort the scan we're back in business. More work needed.

OK, have built PnP III v3.31 and and now testing...

Great

Interestingly, when I abort a LMS scan it is still able to access all files on my Network Drive, which is only a 1 TB portable drive running as a NAS thanks to a Linksys x3000 router. Awesome router by the way (apart from no geeky stats at all). Up to 25 days solid connection where the Netgear before would go for 5-10 before dropping the session and picking it up again.

PnP III v3.31 update: 22:34

Now that I feel I am getting somewhere, here's what I've been working on:



The various commands and files I've finished up with have the interesting effect on one of the Jogglers of scanning some of the files (reporting 75 albums with 964 songs by 36 artists) , but still being able to access all of them (which my sqpOS Joggler actually reports as 930 albums with 13285 songs by 399 artists). Another Joggler seems to be going for the lot!

I am now going to leave my test machines overnight to see if LMS crashes or not on the 2 Jogglers I have running PnP III v3.31 and the OpenFrame2 running a custom build of PnP III with the Network Storage Access cobbled on.

Fingers crossed. If not I'll have to have another fiddle next weekend!

OK, the results of last night's testing:

The OpenFrame2 unit:
No issues. LMS is still running and it boasts 874 albums with 12374 songs by 376 artists. Remember this is a 2Gb unit as opposed to the Joggler 1Gb

PnP III v3.31 Joggler 1
LMS crashed overnight. It works following a 'LMS restart' via SWF Manager. It now boasts 874 albums with 12660 songs by 376 artists.

PnP III v3.31 Joggler 2
LMS appeared to keep running overnight. However, when loaded up, LMS reported that after 9 hours it was still Rescanning Media Library... Scanning new music files (4299 of 13322). I've now aborted that scan and restarted it.

I suspect issues are due to lack of space for caching on the unit itself. Indeed I think I've seen posts about incorporating a usb stick to cope with this. Will investigate further another day.

In the meantime I'll continue to monitor and test v3.31 this week. Everything else on v3.31 in the changelog seems to work though.

After further lock-ups on one of the Jogglers, I've been fiddling with LMS settings. I have no idea whatsoever if it'll make any difference, but in LMS->Settings->Advanced->Performance I've set the settings to

Database Memory Config: Normal

Library Statistics: Disable Library Statistics (Default: Enabled)

Artwork Pre-caching: Do not pre- cache artwork (Default: Pre-cache Artwork)

Server Priority: 15 Low (Default: Current Server Priority)

Scanner Priority: 15 Low (Default: 0 Normal)

Maximum Playlist Length: 500

I've also messed around with the insmod cifs command that gets run at Joggler startup to see if that makes a difference. Both Jogglers have been running fine for the past 10 hours so I'll see what happens over the next few days and hopefully get v3.31 uploaded!

Everything seems stable on the three machines at the moment so I'm now going to flash another 2 Jogglers to see what happens. If all goes well I'll make v3.31 available this week. Updated screenshots are show in the opening post.

Yay! I've just noticed that PnP III is 1 year old tomorrow!