Welcome! Log In Create A New Profile

Advanced

Cannot boot any image anymore pogoplug V4

Posted by t3ch42 
Cannot boot any image anymore pogoplug V4
July 08, 2015 05:06PM
I've had some issues since I've updated to the newer uboot on my V4, and I'm not sure if it's a hardware problem or uboot environment variable problem.
I used to be able to boot up since I updated the uboot, but it seems after a power outage that I am locked out.
My netcat still works, and I can change variables, but I cannot communicate after any image supposedly boots.
I have tried multiple usb sticks, rootfs versions(3.18.5-3.14) and rescue fs as well.
Can anybody see any issues in my env that may be causing issues?
Pulling my hair out.
Thanks!


Pogov4> printenv
 p r i n t e n v 
arcNumber=3960
baudrate=115200
bootcmd=run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; reset
bootcmd_mmc=run mmc_init; run set_bootargs_mmc; run mmc_boot
bootcmd_sata=run sata_init; run set_bootargs_sata; run sata_boot;
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=10
console=ttyS0,115200
device=0:1
ethact=egiga0
ethaddr=00:25:re:da:ct:ed
if_netconsole=ping $serverip
ipaddr=192.168.1.128
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=ext2load usb 0:1 0x1c00000 /boot/dts/kirkwood-pogoplug_v4.dtb
load_initrd=ext2load usb 0:1 0x1100000 /boot/uInitrd
load_uimage=ext2load usb 0:1 0x800000 /boot/uImage
machid=f78
mainlineLinux=yes
mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; if run mmc_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
mmc_init=mmc rescan
mmc_load_uimage=ext2load mmc $device 0x800000 /boot/uImage
mmc_load_uinitrd=ext2load mmc $device 0x1100000 /boot/uInitrd
mmc_root=/dev/mmcblk0p1
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
ncip=192.168.1.252
partition=nand0,2
preboot=run preboot_nc
preboot_nc=run if_netconsole start_netconsole
rootdelay=10
rootfstype=ext2
sata_boot=mw 0x800000 0 1; run sata_load_uimage; if run sata_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
sata_init=ide reset
sata_load_uimage=ext2load ide $device 0x800000 /boot/uImage
sata_load_uinitrd=ext2load ide $device 0x1100000 /boot/uInitrd
sata_root=/dev/sda1
serverip=192.168.1.252
set_bootargs_mmc=setenv bootargs console=$console root=$mmc_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_sata=setenv bootargs console=$console root=$sata_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc
usb_boot=mw 0x800000 0 1; run usb_load_uimage; if run usb_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_init=usb start; setenv usb_root LABEL=rootfs
usb_load_uimage=ext2load usb $device 0x800000 /boot/uImage
usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd
usb_root=/dev/sda1

Environment size: 2480/131068 bytes
here is an example of boot
Pogov4> run usb_boot
 r u n   u s b _ b o o t 
2756040 bytes read in 401 ms (6.6 MiB/s)
6032465 bytes read in 520 ms (11.1 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.16.0-kirkwood-tld-2
   Created:      2014-09-01  23:18:31 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2755976 Bytes = 2.6 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-3.16.0-kirkwood-tld-2
   Created:      2014-09-01  23:18:48 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6032401 Bytes = 5.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK


Starting kernel ...



Edited 1 time(s). Last edit at 07/08/2015 05:08PM by t3ch42.
Re: Cannot boot any image anymore pogoplug V4
July 08, 2015 05:35PM
@ t3ch42 ,

Your envs are OK.

It's very likely that the rootfs was corrupted after a power outage because you're using ext2
rootfstype=ext2

Try to recreate the rootfs 3.16 again. This time use a single Ext3 partition on the USB drive, set its label to rootfs. And set u-boot env rootfstype to Ext3. Basically, follow the instruction very closely (and doing all these activity as root user).

In netconsole,
setenv rootfstype ext3
After booted into Debian, set it permanently
fw_setenv rootfstype ext3

Also, note that when you want to test the boot in netconsole, you should run bootcmd_usb (not usb_boot).

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



Edited 1 time(s). Last edit at 07/08/2015 05:36PM by bodhi.
Re: Cannot boot any image anymore pogoplug V4
July 08, 2015 06:53PM
Whew. That's good to know. I looked at everything and removed the reference to booting the external file from the dts folder. I was able to get the plug to boot up on 3.16 again using the setenv rootfstype ext3. I thought I had wandered through that step, but I may have missed it...

Anyhow, I set the variable and everything seemed to work out.

I tested extensively, and that switch either killed the boot or allowed it to continue.

Thanks again!
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: