E02 Won't Boot From USB [Solved]

[srw]

I had installed arch linux to my E02 PogoPlug and had it running nicely. A few days back, I had a power outage and upon reboot, the pogoplug would not boot. I did an fsck on the USB drive and it reported some errors so I thought that this was the problem. After repairing, it still would not boot from USB.

I then went through the steps of reinstalling the OS to the USB drive per the instructions on this site ( viewtopic.php?f=18&t=3312&p=19207#p19207) . Everything seemed to work fine but again, it would not boot from usb. I've now tried this on four different USB sticks as well as a USB hard drive and I still cannot get it to boot from USB.
Thinking I might have a mangled uboot config file from the power outage, I did a forced update which went fine but still wont boot from usb. To be clear, if I remove all usb devices, the system boots to the pogo OS. If I stick in a usb drive with the archlinux OS, it hangs and never boots. If I insert a usb drive with data / no OS, it boots to Pogo OS.

Does anyone have suggestions for next steps?

thanks in advance!

[moonman]

Did you create ext2 or ext3 partition on the flash drive? also did you change any u-boot environment variables?

[srw]

ext2 partition and no changes to the uboot environment variables other than trying to add netconsole support.

thanks for any suggestions and help

[moonman]

Alright. What is the output of fw_printenv

[xenoxaos]

fw_printenv results are below.

thanks for taking a look

$this->bbcode_second_pass_code('', 'Pogoplug:/usr/sbin$ /usr/sbin/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_installed=0
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_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:04:48:28
arcNumber=2097
usb_init=usb stop; usb start; run usb_scan
serverip=192.168.2.17
ipaddr=192.168.2.28
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
Pogoplug:/usr/sbin$')

[xenoxaos]

I built a serial cable and hooked it up this morning. It appears to me that it starts the boot process into ALARM but then hangs up in the process. Any ideas as to next steps?

$this->bbcode_second_pass_code('', 'U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02

SoC: Kirkwood 88F6281_A0
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot: 0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt

** Unable to read "/rescueme.txt" from usb 0:1 **
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: attached mtd1 to ubi0
UBI: MTD device name: "mtd=3"
UBI: MTD device size: 91 MiB
UBI: number of good PEBs: 728
UBI: number of bad PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 0
UBI: available PEBs: 717
UBI: total number of reserved PEBs: 11
UBI: number of PEBs reserved for bad PEB handling: 7
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
stopping USB..
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
2856016 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
** File not found /boot/uInitrd
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.1.10-13-ARCH
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2855952 Bytes = 2.7 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[ 4.781565] rtc-mv rtc-mv: internal RTC not ticking
[ 4.789955] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)

Welcome to Arch Linux ARM!

Expecting device dev-ttyS0.device...
[ OK ] Reached target Remote File Systems.
[ OK ] Listening on Syslog Socket.
[ OK ] Listening on Delayed Shutdown Socket.
[ OK ] Listening on /dev/initctl Compatibility Named Pipe.
[ OK ] Set up automount Arbitrary Executable File Formats F...utomount Point.
[ OK ] Reached target Encrypted Volumes.
[ OK ] Listening on udev Kernel Socket.
[ OK ] Listening on udev Control Socket.
[ OK ] Reached target Swap.
[ OK ] Listening on Journal Socket.
Starting Remount Root and Kernel File Systems...
Starting Apply Kernel Variables...
Starting udev Kernel Device Manager...
Starting udev Coldplug all Devices...
Mounting POSIX Message Queue File System...
Starting Setup Virtual Console...
Mounting Debug File System...
Starting Journal Service...
[ OK ] Started Journal Service.
[ OK ] Reached target Syslog.
[ OK ] Started udev Kernel Device Manager.
[ OK ] Started Remount Root and Kernel File Systems.
[ OK ] Started Apply Kernel Variables.
[ OK ] Mounted POSIX Message Queue File System.
[ OK ] Mounted Debug File System.
[ OK ] Reached target Local File Systems (Pre).
Mounting /tmp...
Starting Load Random Seed...
[ OK ] Mounted /tmp.
[ OK ] Reached target Local File Systems.
Starting Recreate Volatile Files and Directories...
Starting Trigger Flushing of Journal to Persistent Storage...
[ OK ] Started Setup Virtual Console.
[ OK ] Started udev Coldplug all Devices.
[ OK ] Started Load Random Seed.
[ OK ] Started Recreate Volatile Files and Directories.
[ OK ] Reached target System Initialization.
[ OK ] Listening on D-Bus System Message Bus Socket.
[ OK ] Reached target Sockets.
[ OK ] Reached target Basic System.
Starting Periodic Command Scheduler...
[ OK ] Started Periodic Command Scheduler.
Starting OpenSSH Daemon...
[ OK ] Started OpenSSH Daemon.
Starting Netcfg multi-profile daemon...
Starting Login Service...
Starting D-Bus System Message Bus...
[ OK ] Started D-Bus System Message Bus.
Starting System Logger Daemon...
[ OK ] Started System Logger Daemon.
[ OK ] Found device /dev/ttyS0.
[ OK ] Started Login Service.
[ OK ] Started Trigger Flushing of Journal to Persistent Storage.
Starting Permit User Sessions...
[ OK ] Started Permit User Sessions.
Starting Getty on tty1...
[ OK ] Started Getty on tty1.
Starting Serial Getty on ttyS0...
[ OK ] Started Serial Getty on ttyS0.
[ OK ] Reached target Login Prompts.

Arch Linux 3.1.10-13-ARCH (ttyS0)

alarm login: [FAILED] Failed to start Netcfg multi-profile daemon.
See 'systemctl status netcfg.service' for details.
[ OK ] Reached target Network.
Starting OpenNTP Daemon...
[ OK ] Started OpenNTP Daemon.
[ OK ] Reached target Multi-User.
[ OK ] Reached target Graphical Interface.')

[xenoxaos]

I would log in using the serial console and do what it says...run
$this->bbcode_second_pass_code('', 'systemctl status netcfg.service')
It IS booting, network just isn't coming up.

[srw]

Here are the results:

[root@alarm ~]# systemctl status netcfg.service
netcfg.service - Netcfg multi-profile daemon
Loaded: loaded (/usr/lib/systemd/system/netcfg.service; enabled)
Active: failed (Result: exit-code) since Wed, 1969-12-31 18:00:21 CST; 1min 36s ago
Process: 99 ExecStart=/usr/bin/netcfg-daemon start (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/netcfg.service

I found that if I enter the command netcfg wired-eth0 it reports [BUSY] and eventually fails. If I try the command several times, it eventually connects. What is strange is that my other E02 does not have this problem and the boot USB for this problem Pogo worked fine on the other.

thanks for any suggestions.

[agillis]

Had exactly the same thing happen to me today. Can not get my PogoPlug E02 past the network start up. Funny it boots to the uBoot prompt with no problems. Network comes right up.

Did you ever solve this?

[moonman]

viewtopic.php?f=18&t=4675