Welcome! Log In Create A New Profile

Advanced

Pogoplug E02 boot issue

Posted by Jörg 
Jörg
Pogoplug E02 boot issue
December 21, 2014 02:49PM
Hi everyone,

I have tried several tutorials to install Debian and ArchLinux on my Pogoplug. The installs are running without a problem. After booting from the usb key, the LED blinks and light than permanent. It looks like everything is ok, but the pogo gets no IP from the network. In the meantime I have tested three different usb keys. How can I fix this problem? Keep in mind, I am a bloody newbie ;-).

Cheers
Jörg
Re: Pogoplug E02 boot issue
December 21, 2014 05:12PM
Jörg,

When asking for solution, it's best to state the problem first. Your post does not have much information that enable others to see what the problem is. Gree LED ligth blinking and and then stay solid usually means the rootfs can not be mounted. But it is just an educated guess. Here are the information you will need to provide:

1. Pogoplug model
2. How many drives are plugged in? single USB is recommended installation.
3. Which procedure was you using to install? (the last one you tried)
4. Do you have a log of the installation that you can post?
5. The behavior of LED light (you already provided)
5. Can you connect a serial console? (have parts ready to do that).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Jörg
Re: Pogoplug E02 boot issue
December 22, 2014 02:10AM
Hi bodhi,

following the answers...
1. Pogoplug model
It is a POGO-E02 Arm5
2. How many drives are plugged in? single USB is recommended installation.
Always a single USB key
3. Which procedure was you using to install? (the last one you tried)
the last one: ArchLinux
following I also tried:
Debian
Debian
4. Do you have a log of the installation that you can post?
No, but I can do an installation once more if it is helpful.
5. The behavior of LED light (you already provided)
The LED is blinking orange and than stay solid green.
5. Can you connect a serial console? (have parts ready to do that).
No, I have not a cable.

Without an USB key the Pogo OS starts normal and I can SSH.

Thanks!

Jörg
Re: Pogoplug E02 boot issue
December 22, 2014 02:42AM
Jörg,

> The LED is blinking orange and than stay solid green.

> Without an USB key the Pogo OS starts normal and I
> can SSH.

Then it is easy.

1. Download the basic Debian rootfs 3.16 or 3.17. Following the instruction, put it on the USB thumb drive and see if you can boot with it.

2. If you can't boot into Debian, then boot to Pogo OS, ssh in and get the env listing and post it content here.
blparam > /tmp/u-boot-envs.txt

If blparam is not available in the path, then find it in /usr/local/bin or somewhere
find /usr -name '*blparam*'

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Jörg
Re: Pogoplug E02 boot issue
December 22, 2014 05:49AM
Hi bodhi,

can I do "basic Debian rootfs 3.16 or 3.17 instruction" direct on Pogo OS? The problem is that I have only windows PCs available.
Thanks for your support :-)

Jörg
Jörg
Re: Pogoplug E02 boot issue
December 22, 2014 03:37PM
Hi bodhi,

actually I try to install Linux on an old Notebook for installation of kirkwood.
The last uBoot was this one
wget http://jeff.doozan.com/debian/uboot/install_uboot_mtd0.sh
and
#format and label partition
./mke2fs -L ROOTFS -j /dev/sda1
and
#Update uboot env varibles
#Have uboot mount partition as ext3
/usr/sbin/fw_setenv usb_rootfstype ext3

How can I check usb_rootfstype?
Should I now use Ext3 or Ext2 on the new kirkwood USB drive?

Cheers
Jörg
Re: Pogoplug E02 boot issue
December 22, 2014 03:49PM
Jörg,

This install_uboot_mtd0.sh can not be run on the laptop. This u-boot installation script must be run on the pogoplug itself.

My recommendation:

1. Make rootfs on another Linux box, use a single Ext3 partition (following instruction in the kernel thread I posted above).

2. SSH into the Pogo OS and run:
cd /tmp
wget http://jeff.doozan.com/debian/uboot/install_uboot_mtd0.sh 
chmod +x install_uboot_mtd0.sh
./install_uboot_mtd0.sh


3. Plug in the USB rootfs, sync, reboot:

sync
shutdown -r now

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 12/22/2014 03:50PM by bodhi.
Jörg
Re: Pogoplug E02 boot issue
December 23, 2014 10:47AM
Hi bodhi,

I did all steps you posted one thread above. The Pogo didn't boot into Debian, then I boot to Pogo OS and want to get the env listing. Sadly the blparam command also do not work :-(. I don't know why, but this little peace of hardware is not a friend of me.

Pogoplug:/bin$ find /usr -name '*blparam*'
/usr/sbin/blparam
/usr/local/cloudengines/bin/blparam
Pogoplug:/$ cd /usr/sbin/
Pogoplug:/usr/sbin$ blparam > /tmp/u-boot-envs.txt
-bash: blparam: command not found
Pogoplug:/$ cd /usr/local/cloudengines/bin/
Pogoplug:/usr/local/cloudengines/bin$ blparam > /tmp/u-boot-envs.txt
-bash: blparam: command not found

Do you have any ideas?

Jörg
Re: Pogoplug E02 boot issue
December 23, 2014 02:24PM
Jörg,

Execute with full path:

/usr/local/cloudengines/bin/blparam > /tmp/u-boot-envs.txt

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Jörg
Re: Pogoplug E02 boot issue
December 23, 2014 02:59PM
Hi bodhi,

first thank you very much for your support!
This time the LED is not blinking and no solid light.

Here we are:
Pogoplug:~$ /usr/local/cloudengines/bin/blparam
baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
netmask=255.255.0.0
run_diag=yes
console=console=ttyS0,115200
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/mtdblock2 ro
ethmtu=1500
usb0Mode=host
nandEcc=1bit
ethact=egiga0
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
bootargs=console=ttyS0,115200 root=/dev/mtdblock2 ro
serverip=169.254.254.252
ipaddr=169.254.254.253
ethaddr=00:25:31:04:9A:5F
cesvcid=95EQTQ9A354ZF95XDLX43RDMFN
ceboardver=PPV2
bootcmd=nand read.e 0x800000 0x100000 0x200000; setenv bootargs $(console) $(bootargs_root); bootm 0x800000
Pogoplug:~$

Cheers
Jörg
Re: Pogoplug E02 boot issue
December 23, 2014 08:13PM
OK,

You can SSH in to the pogo again and do this:
http://forum.doozan.com/read.php?3,18917,18935#msg-18935

Remember to keep the log of everything.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Jörg
Re: Pogoplug E02 boot issue
December 24, 2014 05:52AM
Hi bodhi,

after reboot the pogo, the LED on USB rootfs is not blinking.
following the log:

login as: root
root@192.168.2.23's password:
Pogoplug:~$ cd /tmp
Pogoplug:/tmp$ wget http://jeff.doozan.com/debian/uboot/install_uboot_mtd0.sh
Connecting to jeff.doozan.com (50.116.34.13:80)
install_uboot_mtd0.s 100% |**************************************************************| 18406  00:00:00 ETA
Pogoplug:/tmp$ chmod +x install_uboot_mtd0.sh
Pogoplug:/tmp$ ./install_uboot_mtd0.sh


!!!!!!  DANGER DANGER DANGER DANGER DANGER DANGER  !!!!!!

If you lose power to your device while running this script,
it could be left in an unusable state.

This script will replace the bootloader on /dev/mtd0.

This installer will only work on the following devices:
 Seagate Dockstar
 Seagate GoFlex Net
 Seagate GoFlex Home
 Pogoplug v1
 Pogoplug Pink (v2)
Do not run this installer on any other device.

By typing ok, you agree to assume all liabilities and risks
associated with running this installer.

If you agree, type 'ok' and press ENTER to continue: ok
# checking for /usr/sbin/nandwrite...
# checking for /usr/sbin/nanddump...
# checking for /usr/sbin/flash_erase...
# checking for /usr/sbin/fw_printenv...
# checking for /etc/fw_env.config...

# Validating existing uBoot...
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
Connecting to jeff.doozan.com (50.116.34.13:80)
valid-uboot.md5      100% |**************************************************************|  1133  --:--:-- ETA
## Valid uBoot detected: [pinkpogo davygravy-2012-02-20-current]
## The newest uBoot is already installed on mtd0.


You are already running the latest uBoot.
Your current uBoot environment should be reasonable.  However, if you're having
any probems booting, you can reset the environment variables to know good values.
Would you like to reset the uBoot environment? [N/y] y

# Installing uBoot environment
Connecting to download.doozan.com (50.116.34.13:80)
uboot.environment.md 100% |**************************************************************|    32  --:--:-- ETA
Connecting to download.doozan.com (50.116.34.13:80)
uboot.environment    100% |**************************************************************|   128k 00:00:00 ETA
Erase Total 1 Units
Performing Flash Erase of length 131072 at offset 0xc0000 done
Writing data to block 6 at offset 0xc0000

# Verifying uBoot environment
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x000c0000 and ending at 0x000e0000...
Connecting to download.doozan.com (50.116.34.13:80)
uboot.environment.md 100% |**************************************************************|    32  --:--:-- ETA

# uBoot installation has completed successfully.
Pogoplug:/tmp$ sync
Pogoplug:/tmp$ reboot

Jörg
Re: Pogoplug E02 boot issue
December 24, 2014 03:17PM
Jörg,

Everything looks good. You are running davygravy 2012 u-boot and the envs were flashed successfully. davygravy's Pogo E02 u-boot does not flash LED during booting. Look for the Pogo in your network (it's dynamic IP) router. Or if you have smartphone, use Fing to scan all the nodes in the network.

Next step If you can't find it:

Do you have a log of how you created the rootfs on USB? if you post the entire log, then perhaps I could spot something mis-step somwhere. If you did not save the log, then please redo it:

- Create a fresh Ext2 single partition on a USB drive (everything old is wiped out)
- Following the instruction in the kernel & rootfs thread, untar the downloaded rootfs to it.
- Plug in the rootfs, and power up

NOTE: you might want to use the rootfs 3.16 in the above thread, to make it easier to create it on a Windows box with Live CD or other Linux box where you can't install software.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 12/24/2014 03:25PM by bodhi.
Jörg
Re: Pogoplug E02 boot issue
December 25, 2014 10:26AM
Hi bodhi,

with the blinking Led I didn't mean the Led on the Pogo but on the USB key itself. Normaly it flashes also if the key is in use.
In the meantime I have a working ubuntu PC. So it is no problem to install the rootfs 3.17 again (with saving the logs). Format with Ext3, because you wrote above Ext2?

Jörg
Re: Pogoplug E02 boot issue
December 25, 2014 01:41PM
Jörg,

IIRC, your u-boot version set rootfstype to Ext2. Ext3 would work, but just to make it consistent you should use Ext2.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Jörg
Re: Pogoplug E02 boot issue
December 29, 2014 06:31AM
Hi bodhi,

I don't know why, but now it is working :-).

Finally one question... My ubuntu server do I update with following command:
apt-get update && apt-get dist-upgrade && apt-get autoremove
Can I use this also for the rootfs Pogoplug?

Thank you thousand times for your excellent support. I wish you and your family
a happy new year!

Cheers
Jörg
Re: Pogoplug E02 boot issue
December 29, 2014 10:44AM
Jörg,

> Finally one question... My ubuntu server do I
> update with following command:
> apt-get update && apt-get dist-upgrade && apt-get
> autoremove
> Can I use this also for the rootfs Pogoplug?

Yes, the similar commands. However, don't do dist-upgrade. Upgrade is enough to get the latest version of all packages. OTOH, dist-upgrade will replace the customized kernel with mainline version, which is not recommended.

apt-get update && apt-get upgrade && apt-get autoremove

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: