Welcome! Log In Create A New Profile

Advanced

Rescue system V2 - error messages on boot on pogoplug pink

Posted by rkrug 
Rescue system V2 - error messages on boot on pogoplug pink
December 17, 2013 07:40AM
Hi

I installed the rescue system from

http://forum.doozan.com/read.php?4,3896

and uboot as well as netconsole from

http://forum.doozan.com/read.php?3,14

and I get quite a few error messages when booting the pogoplug without usb attached, and some seem to indicate that the pogoplug thinks that there are USB devices attached:

U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
Hit any key to stop autoboot:  0 
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
** Block device usb 0 not supported

** Invalid boot device **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000008000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI error: ubi_read_volume_table: the layout volume was not found
UBI error: ubi_init: cannot attach mtd1
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error 22
** Block device usb 0 not supported
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..

NAND read: device 0 offset 0x100000, size 0x400000
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.32.18-dockstar
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3236180 Bytes = 3.1 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

My fw_printenv looks as follow:

rescue:~# fw_printenv 
ethact=egiga0
bootdelay=3
baudrate=115200
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_list=1 2 3 4
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_init=run usb_scan
usb_device=0:1
usb_root=/dev/sda1
usb_rootfstype=ext2
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
ethaddr=00:25:31:00:49:4B
rescue_installed=1
arcNumber=3542
serverip=192.168.0.41
ipaddr=192.168.0.102
if_netconsole=ping $serverip
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
preboot=run if_netconsole start_netconsole
rescue:~#

Should I worry? Or is this normal?

Thanks,

Rainer
Re: Rescue system V2 - error messages on boot on pogoplug pink
December 17, 2013 11:44AM
It is normal. The USB device detected was the hub. UBI error is normal too, since it tried to use mtd3. Everything looks OK. Also look in dmesg to see if there is any error.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Rescue system V2 - error messages on boot on pogoplug pink
December 17, 2013 12:14PM
Great - thanks. No I can sleep much better.

Cheers,

Rainer
me too plz
March 16, 2015 09:09PM
'ole Newb here... :D
I believe mine installed correctly, because it's not bricked and more often than not it'll boot into an Arch stick or hard drive. Before, 2/3rds of the time want to boot into the stock Pogoplug instead of Arch. Having said that, i can't reach into the rescue boot with PuTTy or WinSCP. Session attempt times out.
I might have missed a memo here, and i finally DID whack an easily replaceable Arch installation, but what am i looking for here? Do you get into it with https or something?
Re: me too plz
March 16, 2015 10:10PM
@Joey,


No, it meant the the rescue system rootfs has a problem. So it must be fixed, or reinstalled. The best way to fix this is to connect serial console. And watch the boot process. Log in to the rescue system through serial console connection and then fix the problem. Or take the shortcut by reinstalling it.

Btw, serial console is the indispensible tool for embedded Linux device :) get one if you don't have it.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Rescue system V2 - error messages on boot on pogoplug pink
March 17, 2015 11:46PM
Ok on the serial cable, the past month has shown me how indispensable that item is.

Hey while we're at it, is there any merit in making pretty much, just a boot manager out of the stock flash drive? I was about to ask about a minimal arch or something in the neighborhood of the space it takes for router firmware. But then again, since Pogo is headless then nothing is there to tell me the boot choices. Ahh... lol

I've still got a couple good questions left in me, but thanks a million for answering the tough ones, some go back way over a decade.
Just turning my hideous LED from orange to green... anything past that is some kind of textual lottery ...
Re: Rescue system V2 - error messages on boot on pogoplug pink
March 18, 2015 01:46AM
Joey,

> Hey while we're at it, is there any merit in
> making pretty much, just a boot manager out of the
> stock flash drive? I was about to ask about a
> minimal arch or something in the neighborhood of
> the space it takes for router firmware. But then
> again, since Pogo is headless then nothing is
> there to tell me the boot choices. Ahh... lol

Boot menu does work in u-boot, but only good if you connect using serial console. Therefore it's not much help because the pogo is headless. netconsole does not work with bootmenu (real name) , because it is not possible to use termimal protocol (i.e ANSI) over it.

It is possible to work out some poor-man kind of menu over netconsole, but it is too much works for minimal gain.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
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: