Pogoplug V2 doesn`t boot with USB HDD

[sunspot]

Hi. I`ve came across a rather strange problem: Pogo V2 with ALARM installation carried out according to the manual, 4Gb USB flash inserted to lower back port. Poro boots OK and even mounts my NTFS drive if I plug it after the booting finishes. But when I try to reboot the Pogo with both 4GB bootable USB and 2TB USB drive my Pogo stops halfway and doesn`t get an IP so naturally I can`t SSH to it.
I`ve set up a Netconsole to compare bootup process between the two cases but the output looks identical and bootable USB is correctly detected in both cases. I`m at a loss, from the second log it looks like he system should be working but its not.

Is it the famous issue of not booting from the correct USB I`m facing?


$this->bbcode_second_pass_code('', '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'!
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)
4549504 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-4.4.1-1-ARCH
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4549440 Bytes = 4.3 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Using machid 0xdd6 from environment

Starting kernel ...')

$this->bbcode_second_pass_code('', '[admin@WL-Asus root]$ nc -u -l -p 6666

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... 4 USB Device(s) found
scanning bus for storage devices... 2 Storage Device(s) found
stopping USB..
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 4 USB Device(s) found
scanning bus for storage devices... 2 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'!
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)
4549504 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-4.4.1-1-ARCH
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4549440 Bytes = 4.3 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Using machid 0xdd6 from environment

Starting kernel ...')

[moonman]

This is a known problem with this uboot. Upgrade uboot to the latest version (look in the sticky uboot 2015.10). Before you do that though issue "blkid" and check that your rootfs partition has PARTUUID field. After upgrading uboot but before restarting, check that you have "ethaddr" set in uboot environment by "fw_printenv | grep ethaddr". If either of those 2 are missing come back here and don't reboot.

[sunspot]

Thanks form the reply.
So I`ve followed this guide
http://forum.doozan.com/read.php?3,12381
since I`m a total noob to build uBoot 2015.10 image myself

and now my console reads
$this->bbcode_second_pass_code('', '[root@alarm tmp]# blkid
/dev/sda1: LABEL="ROOTFS" UUID="29180940-aa4d-46da-844f-6f3f29e525c6" TYPE="ext3"
[root@alarm tmp]# fw_printenv | grep ethaddr
ethaddr=00:25:31:04:4B:E8
[root@alarm tmp]# fw_printenv
bootcmd_exec=mw 0x800000 0 1; run load_uimage; if run load_initrd; then if run load_dtb; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 0x1100000; fi; else if run load_dtb; then bootm 0x800000 - 0x1c00000; else bootm 0x800000; fi; fi
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
device=0:1
devices=usb ide mmc
disks=0 1 2 3
ethact=egiga0
if_netconsole=ping $serverip
led_error=orange blinking
led_exit=green off
led_init=green blinking
dtb_file=/boot/dts/kirkwood-pogo_e02.dtb
load_dtb=echo loading DTB $dtb_file ...; ext2load $bootdev $device 0x1c00000 $dtb_file
load_initrd=echo loading uInitrd ...; ext2load $bootdev $device 0x1100000 /boot/uInitrd
load_uimage=echo loading uImage ...; ext2load $bootdev $device 0x800000 /boot/uImage
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start"; setenv scan_ide "ide reset"; setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if ext2load $dev $disknum:1 0x800000 /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_import=echo importing envs ...; env import -t 0x810000
uenv_init_devices=setenv init_usb "usb start"; setenv init_ide "ide reset"; setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices; do for disknum in 0; do run uenv_read_disk; done; done;
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read; fi; else if $devtype part $disknum; then run uenv_read; fi; fi
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 0x810000 /boot/uEnv.txt; then setenv uenv_loaded 1; fi
usb_ready_retry=15
arcNumber=3542
machid=dd6
ethaddr=00:25:31:04:4B:E8
preboot=run preboot_nc
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
ipaddr=10.0.0.103
serverip=10.0.0.1

')
Am I safe to perform a reboot?

As it turns out I am not Figures. So I`m guessing I`ll need a Linux LiveCD and a copy of at least "uInitrd" so i can put it on the USB stick manually.


$this->bbcode_second_pass_code('', '$ nc -lu -p 6666

U-Boot 2015.10-tld-1 (Nov 06 2015 - 15:46:25 -0800)
Pogo E02
gcc (Debian 4.9.2-10) 4.9.2
GNU ld (GNU Binutils for Debian) 2.25
Hit any key to stop autoboot: 0
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices...
Use USB retry period from the environment: 15 second(s)
1 Storage Device(s) found
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'

Partition Map for USB device 0 -- Partition Type: DOS

Part Start Sector Num Sectors UUID Type
1 51 7820901 00000000-01 83
loading envs from usb 0 ...
** File not found /boot/uEnv.txt **
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'
running scan_disk ...
Scan device usb
device usb 0:1
1 bytes read in 135 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
4549504 bytes read in 347 ms (12.5 MiB/s)
loading uInitrd ...
** File not found /boot/uInitrd **
loading DTB /boot/dts/kirkwood-pogo_e02.dtb ...
** File not found /boot/dts/kirkwood-pogo_e02.dtb **
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-4.4.1-1-ARCH
Created: 2016-02-02 14:06:13 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4549440 Bytes = 4.3 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK


Starting kernel ...')

[moonman]

You don't need to build the image yourself. Where did you read that? the images are installed with pacman!

[sunspot]

Yeah, somehow while reading this thread I've missed that since it wasn't explicitly mentioned.
viewtopic.php?p=46831

Any ideas about what might went wrong? Should I prepare myself a serial connection cable?
I have a full log of my actions between my current state and a guide on qynology blog.

[wobble]

From what I understand the problem was that while your pogoplug boots from the usb stick it doesn't when the hd is plugged in while it's booting. You tried to solve that by compiling your own uboot which apparently didn't solve your problem.

What I don't understand is if your current situation is actually worse than before (that is, doesn't boot at all) or if it still boots with only the usb stick plugged in.

[sunspot]

Firstly I`ve installed Jeff`s uboot and at that moment my Pogo was booting up only with Arch USB stick attached and all of my HDD disconnected. Then I`ve installed new 2015.10 uboot, but not the moonman`s version from pacman but the bodhi`s version by manually flashing nvram. Backed up my original environment to txt, flashed bodhi environment, corrected MAC, arcNumber, machid, ip for netconsole and finally rebooted the whole thing. I could see the the logs from netconsole from uBoot but after that nothing, Pogo doesn't pick up an IP and may be don`t boot.
I`ve attached the whole log of what I did in the txt.

[wobble]

You didn't really answer my question if it still boots with only the usb stick plugged in, but I guess it doesn't.

Did you really follow this guide to set up netconsole and listen on both ip addresses? The boot log you posted looks like only the u-boot part which could mean either that you really get no kernel output or you just don't capture it...

[sunspot]

Sorry, I thought I`ve mentioned that I cannot get anywhere past netconsole uBoot output with only USB stick inserted

I`ve flashed this uBoot uboot.2015.10-tld-1.pogo_e02.bodhi.tar so no idea where kernel netconsole output routed

[wobble]

But both of the logs in the post that started this thread also only show the uboot output even though you say that at that time it did start with only the usb stick inserted, so at least the log belonging to that boot (the first one?) should have some kernel logs, but it has not. So I suspect your netconsole capture setup (on your desktop, not the pogoplug) is to blame...