OUR NETWORK:TiVoCommunity TechLore MyOpenRouter Dijit Community MediaSmart Home See all... About UsAdvertiseContact Us

 
Learn about scoring Forum's Raw Score: 620915.0
December 31, 2009 11:35 PM

Categories: PogoPlug Development

Rating (0 votes)
  • 1
  • 2
  • 3
  • 4
  • 5
Rate This!

Member Avatar

crimsonredmk

Member
Joined: 05/17/2009

Title says it all. Reply if you use OpenPogo. If you want to, you can include what apps you run and if there are any other comments.

Just want to know how many Pogoplugged readers also run OpenPogo. :)

Discussion:    Add a Comment | Comments 1-25 of 26 | Latest Comment | 1 2 Next »

January 1, 2010 12:18 PM

I do.
I have installed the samba server and am using one drive partition for backups, while use use the others for regular pogo stuff.

January 1, 2010 7:05 PM

I use it.

January 2, 2010 2:50 PM

Are you using OpenPogo with the newer v.2 of PogoPlug? I read that it may not work with v.2 and may even brick it. I just got the v.2 Pogoplug and would love to try to use OpenPogo to install use samba, bittorrent, Firefly, etc on it. Is it safe to do this on the new v.2 PogoPlug or not?

January 3, 2010 4:00 AM

I have OpenPogo installed on the new V2 PogoPlug and it seems to be running fine. I have LightTPD with PHP and FCGI running. LightTPD has been running for about a week now and serving up basic web pages. I haven't done anything with PHP yet because of Crimsonred's advisory. I look forward to the day that we can install OpenPogo on the V2 and not have to worry about doing damage.

Thanks
Jim

January 3, 2010 2:25 PM

Hey Jim, in that case, can you SSH in and paste the output of "cat /etc/init.d/rcS.original" here, or on Pastebin? I just want to see if maybe the boot scripts are different than the v1 Pogoplug. The thing is that some Pogoplug v2's bricked while some didn't and until I know whether it's OpenPogo's fault, I'd use caution. CloudEngines has no extra Pogoplugs to send us to test with for support so OpenPogo can, you know, continue to exist. But that's another matter. ;)

January 3, 2010 3:42 PM

It looks like openpogo on the v2 plug has been discontinued. I think I will return my pogoplug v2 and get the sheeva.

January 4, 2010 4:49 AM

CrimsonRed,

Here is the info you requested.

#! /bin/sh

mount -t proc none /proc
mount -t sysfs none /sys
mount -t devpts none /dev/pts
mount -t tmpfs none /tmp
mkdir /tmp/var

echo "/tmp/core_%e_%t" > /proc/sys/kernel/core_pattern

hostname Pogoplug

ifconfig lo 127.0.0.1
ifconfig eth0 169.254.37.133
udhcpc -b `hostname`

telnetd
/etc/init.d/db

/etc/init.d/hbmgr.sh start

Thanks
Jim

January 4, 2010 6:00 AM

CrimsonRed,

Here's some more insight. While trying to copy and paste the init script actually ran. After installing OpenPogo I never rebooted I only ran the init script for LightTPD. Well it appears that after a reboot and the original script runs is when the problem shows up. I have nothing at this point it won't even detect that the USB drive exists. I can still log in OK just no drives available. Hope this helps.

Thanks
Jim

January 4, 2010 7:21 AM

CrimsonRed,

Here is the feedback I get when the rcS script is run.

-bash-3.2# #! /bin/sh
-bash-3.2#
-bash-3.2# mount -t proc none /proc
mount: mounting none on /proc failed: Device or resource busy
-bash-3.2# mount -t sysfs none /sys
mount: mounting none on /sys failed: Device or resource busy
-bash-3.2# mount -t devpts none /dev/pts
mount: mounting none on /dev/pts failed: Device or resource busy
-bash-3.2# mount -t tmpfs none /tmp
-bash-3.2# mkdir /tmp/var
-bash-3.2#
-bash-3.2# echo "/tmp/core_%e_%t" > /proc/sys/kernel/core_pattern
-bash-3.2#
-bash-3.2# mount /dev/mtdblock3 /opt
mount: mounting /dev/mtdblock3 on /opt failed: Invalid argument

hostname Pogoplug
-bash-3.2#
-bash-3.2# hostname Pogoplug
-bash-3.2#
-bash-3.2# ifconfig lo 127.0.0.1
-bash-3.2# ifconfig eth0 169.254.37.133

telnetd
/etc/init.d/db
ntpd -g

/etc/init.d/hbmgr.sh start

#/bin/mount -a

-bash-3.2# udhcpc -b -h `hostname`
udhcpc (v1.7.0) started
HWADDR 00 0x25 0x31 0x00 0x1a 0x40
PIP0 26
PIP1 64
ifconfig: SIOCSIFADDR: File exists
Sending discover...
Sending select for 192.168.1.5...
Lease of 192.168.1.5 obtained, lease time 86400
HWADDR 00 0x25 0x31 0x00 0x1a 0x40
PIP0 26
PIP1 64
route: SIOCADDRT: File exists
eth0 Link encap:Ethernet HWaddr 00:25:31:00:1A:40
inet addr:192.168.1.5 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1956 errors:0 dropped:0 overruns:0 frame:0
TX packets:658 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:532
RX bytes:528437 (516.0 KiB) TX bytes:202643 (197.8 KiB)
Interrupt:11

eth0:0 Link encap:Ethernet HWaddr 00:25:31:00:1A:40
inet addr:169.254.26.64 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:11

-bash-3.2#
-bash-3.2# telnetd
-bash: telnetd: command not found
-bash-3.2# /etc/init.d/db
-bash-3.2# ntpd -g
-bash: ntpd: command not found
-bash-3.2#
-bash-3.2# /etc/init.d/hbmgr.sh start
Loading fs modules: insmod: cannot insert '/usr/local/cloudengines/bin/fat.ko': File exists (-1): File exists
insmod: cannot insert '/usr/local/cloudengines/bin/vfat.ko': File exists (-1): File exists
insmod: cannot insert '/usr/local/cloudengines/bin/hfs.ko': File exists (-1): File exists
insmod: cannot insert '/usr/local/cloudengines/bin/hfsplus.ko': File exists (-1): File exists
insmod: cannot insert '/usr/local/cloudengines/bin/fuse.ko': File exists (-1): File exists
Success
insmod: cannot insert '/usr/local/cloudengines/bin/ufsd.ko': File exists (-1): File exists
Loading tun.ko: insmod: cannot insert '/usr/local/cloudengines/bin/tun.ko': File exists (-1): File exists
Success
Loading xce.ko: insmod: cannot insert '/usr/local/cloudengines/bin/xce.ko': File exists (-1): File exists
Success
Starting hbplug: Success
-bash-3.2#
-bash-3.2# #/bin/mount -a

Thanks
Jim

January 4, 2010 9:43 AM updated: January 4, 2010 9:45 AM

How about running an "ls /dev/mtd*". Either mtdblock3 is missing or something...When you run that command, does mtdblock3 show up at all? How about running "mkdir -p /opt" and then trying to run "mount /dev/mtdblock3 /opt"?

Also, are you khai from OpenPgo forums by any chance? Same issue...

January 4, 2010 11:15 AM

CrimsonRed,

Here is the output from what you suggested.

-bash-3.2# ls /dev/mtd*
/dev/mtd0 /dev/mtd14 /dev/mtd6 /dev/mtdblock2
/dev/mtd1 /dev/mtd15 /dev/mtd7 /dev/mtdblock3
/dev/mtd10 /dev/mtd2 /dev/mtd8 /dev/mtdblock4
/dev/mtd11 /dev/mtd3 /dev/mtd9 /dev/mtdblock5
/dev/mtd12 /dev/mtd4 /dev/mtdblock0 /dev/mtdblock6
/dev/mtd13 /dev/mtd5 /dev/mtdblock1 /dev/mtdblock7
-bash-3.2# mkdir -p /opt
-bash-3.2# mount /dev/mtdblock3 /opt
mount: mounting /dev/mtdblock3 on /opt failed: Invalid argument

Thanks
Jim

January 4, 2010 11:30 AM

Was /opt created? "ls -al /" as the file system is read only after a reboot.

January 4, 2010 12:17 PM

/opt exists already and I can get to it and use files in /opt/bin

Thanks
Jim

January 4, 2010 2:08 PM

We just sent OpenPogo a bunch of v2's for testing, so they should add it back to their list of supported devices soon. Everything we are hearing is that OpenPogo works fine with v2.

January 4, 2010 5:30 PM updated: January 4, 2010 5:31 PM

I have no idea why your mtdblock3 won't mount to /opt in that case. Are you sure it isn't already mounted? Run a "df -h". Sorry for asking you to run all of this and not giving you an answer, but it's the 2nd report of this same problem. And yes, CloudEngines sent me testing Pogoplugs, so hopefully we'll get all of the issues people were having sorted out so we can officially support it without worrying about the warranty or bricked plugs.

January 4, 2010 7:01 PM

CrimsonRed,

Here is the output from df -h, so it appears that it is mounted but i don't see anything when I log into my PogoPlug through PogoPlug Web Site. It also does not see the drive.

-bash-3.2# df -h
Filesystem Size Used Available Use% Mounted on
/dev/mtdblock2 32.0M 11.5M 20.5M 36% /
none 125.0M 8.0k 125.0M 0% /tmp
/dev/mtdblock3 91.0M 13.5M 77.5M 15% /opt
/tmp/.cemnt/sda1 931.3G 1.1G 930.1G 0% /tmp/.cemnt/mnt_sda1
-bash-3.2#

Thanks
Jim

January 4, 2010 10:19 PM

Everything I've heard about the Pogoplug v2 and OpenPogo is bad so far, and that's another addition to my list ^^^. I'll be looking at a fix for you, but how about a "cp /etc/init.d/rcS.original /etc/init.d/rcS". That'll restore your Pogoplug's bootup to normal. Afterwards, just unplug the Pogoplug and plug it back in to power to restart it. If your drive still doesn't work, contact Pogoplug support and mention that you didn't modify boot files.

January 5, 2010 5:26 AM updated: January 5, 2010 5:31 AM

jim_richards said:
...
/dev/mtdblock3 91.0M 13.5M 77.5M 15% /opt
... 

This says mtdblock3 is 91MB - on the original pogoplug it is about 450 MB. How big is the nand on the pogoplug v2?

January 5, 2010 5:52 AM

CrimsonRed,

I tried the copy as you suggested and it comes back and says that it is a read only file system.

cp: cannot remove 'rcS': Read-Only file System

Thanks
Jim

January 5, 2010 6:14 AM

To mount the file system as read/write

mount -o rw,remount /

then
cp /etc/init.d/rcS.original /etc/init.d/rcS

January 5, 2010 7:04 AM

Thanks ianjb,

System is back to normal.

CrimsonRed if you should need help with testing I'm fine with that I have nothing critical on my V2 PogoPlug.

Thanks
Jim

January 6, 2010 8:57 AM

ianjb said:
jim_richards said: ... /dev/mtdblock3 91.0M 13.5M 77.5M 15% /opt ... 
This says mtdblock3 is 91MB - on the original pogoplug it is about 450 MB. How big is the nand on the pogoplug v2?

 The NAND flash is 128MB in size. Doing 'dmesg' will show you that.

January 6, 2010 9:24 AM

jim_richards said: I have OpenPogo installed on the new V2 PogoPlug and it seems to be running fine. I have LightTPD with PHP and FCGI running. LightTPD has been running for about a week now and serving up basic web pages. I haven't done anything with PHP yet because of Crimsonred's advisory. I look forward to the day that we can install OpenPogo on the V2 and not have to worry about doing damage.

 So, what is the advisory on the OpenPogo page about it not running on the V2? And define "bricking". If I have serial console access, I should be able to un-brick it.

January 6, 2010 9:26 AM

I got my parts from DigiKey, so I'll have a serial console built soon.

January 6, 2010 10:27 AM

A serial cable will allow access to the boot process and the uBoot environment. As long as there is not a real hardware failure and uBoot is intact, the serial cable along with an ethernet connection to a tftp server will enable you to un-brick a system with: a corrupted uBoot environment, corrupted kernel and/or corrupted file system. If uBoot is not intact then a jtag connection is required. The other open (8 pin?) connector provides the jtag functionality but I'm not aware of anyone that has tried/succeeded in using the jtag connection.

DO you you have access to the crimp tool for the hirose connector?

Discussion:    Add a Comment | Back to Top | Comments 1-25 of 26 | Latest Comment | 1 2 Next »

Add Your Reply

(will not be displayed)

Email me when comments are added to this thread

 
 

Please log in or register to participate in this community!

Log In

Remember

Not a member? Sign up!

Did you forget your password?

You can also log in using OpenID.

close this window
close this window