Hi Bodhi, The USB controller is from a Seagate 1.5 tb USB harddrive. I don't know how to find the make and model of it. No brand on it, really just a small green pcb. As a side note, I still sometimes get the "EHCI timed out on TD" when cold booting the pogoplug E02 after its been sitting for awhile disconnected from power source. Once it's on, I just power off and thenby hachigo - Debian
Bodhi, I have finalized the setup with the steps outlined in your guides. New ssh-keygen and everything. Followed the instructions to a T. All steps were followed exactly all the way to the end using your guides on the uBoot and Debian rootfs harddrive. I have even reproduced the problem. The only difference that I saw that resulted in a working harddrive Debian rootfs was in the connectiby hachigo - Debian
Tried what you just suggested. cd /media/sdb1/boot cp -a uImage uImage.pogo_e02 cp -a uImage.orig uImage sync This is what I see now. I am not sure if it is normal. There is no login for a user/root. It just gives me a (initramfs). This is the serial connection output. U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:13:18 -0700) Pogo E02 SoC: Kirkwood 88F6281_A0 DRAM: 256 MiB WARNIby hachigo - Debian
Good call. This is the printenv output. arcNumber=3542 bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr;by hachigo - Debian
I recently updated my uBoot on my pogoplug E02 to the 2017 version. I saved my current env settings before flashing over uboot.2016.05-tld-1.environment.img, I followed the instructions and changed my ethaddr, machID and arcNumber to pogo E02. I used a new hard drive and extracted the Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 and followed the directions as stated. Plugged in the harddrivby hachigo - Debian
bodhi, Ok I will go through my uBoot envs again. I just realized I didn't copy my working env settings before I formatted my USB drive. I hope Chessplayer's env settings will work for me too. Thanks again for your help. -hachigoby hachigo - Rescue System
bodhi, Oh ok. Before I was able to ssh into it and also use the netconsole, but now I can't. I guess now I can only get into the stock OS with serial cable? I was also wondering if installing debian to the nand is still viable option. I came across this https://github.com/ingmar-k/Pogoplug_V3_Emdebian_Debian while browsing other threads on this site and google. I'd like to be aby hachigo - Rescue System
hi bodhi, Success!!! thank you so much! This almost makes up for the exam I bombed this past Friday... How did you learn how to do all this stuff? lol. I gotta a lot of learning to do. If you don't mind, I have another question that got me into this mess of trying to boot from sata in the first place. I was wondering if there was a Rescue System like Rescue v.2.8.2 for the pro. Mby hachigo - Rescue System
Hi bodhi, Hmm. What you suggested is what I did the the very first time, but it never booted. I just tried again what you suggested and still nothing. Just to be sure I'm not screwing anything up here's what I did. On my ubuntu machine, I erased and reformatted my sata harddrive with fdisk. Created one 4GB primary partition. Then formatted to ext3 with the label "rootfs&quby hachigo - Rescue System
Hi bodhi, Thanks for the help. I wasn't sure if you wanted the boot messages with the sata attached. It all looks like the matrix to me so I wasn't sure what's important. As a side note, I bought a second pogoplug hoping to get an e02 but got a pro instead. Arch has stopped support for pro model, so that is why I want to use debian. I want to use Debian rootfs. Since Iby hachigo - Rescue System
Hi bodhi, Ok I broke apart and pulled the builtin cable for pink pogoplug that I made for easy access to serial console. It boots and then gives brings me to a command line. Serial console output with no drives attached: U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12) Boot device: NAND Attempting to set PLLA to 850 MHz ... plla_ctrl0 : 0000020a plla_ctrl1 : 00330000 plby hachigo - Rescue System
Hi bodhi, I tried your suggestion. The commands seem to work. But it is still not booting up. I will just outline what I did exactly for clarity, just in case I did something wrong. Step 1: Used WarheadSE's disk_create script. (It worked and was able to boot Arch linux with the Arch rootfs tarball) Step 2: Extracted Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2 to /dev/sdx2 on my sby hachigo - Rescue System
Hi bodhi, I was successfully able to boot with sata drive, but it had a deprecated version of arch linux and I was not able to install u-boot-tools package or mtd-utils. I was hoping that those tools would have been on there already. Before I give up and hook up a serial cable (I'm trying to avoid this because I don't have a JST header or soldering iron right now), is there anyway Iby hachigo - Rescue System
Hi bodhi. I have just tried your suggestion, but it still does not boot. I cannot get the netconsole to work either now. Before it was reporting through netconsole and I was able to manipulate it. I am not sure if it is even booting and grabbing an IP address now, I cannot detect it on my openwrt router. I really hope that it is just uBoot environment settings that can be fixed with a serial cby hachigo - Rescue System
Hello. I've just tried to do this for my Pogoplug Pro Oxnas. Now I can no longer boot. I was able to update uBoot to latest version prior to trying this out. I noticed after updating uBoot I was not able to change ethaddr. It kept saying cannot overwrite ethaddr. I thought maybe I could set the ethaddr with this Rescue system like on my other pogoplug E02. But now I can no longer boot. I mayby hachigo - Rescue System
Hi Bodhi. I wasn't able to make the booting multiple drives to work with just Bodhi's instructions alone. But after messing with it and pulling out my hair I finally got it to work. I read from archlinux forums that you can use ramdisk to help the pogoplug search for the correct boot USB device. I don't fully understand this but it appears to work. I will leave how I did it hereby hachigo - uBoot
Thank you all. I had no idea. I am really just starting to delve into this computer stuff coming from a bioscience background, it's a bit of a learning curve.by hachigo - uBoot
Hi again. I just bought a second pogo e02. I am trying to install the newest update uboot again and wanted to make sure my bad eraseblock is not within the first 1M of my NAND. Here is my output from dmesg. # dmesg | grep -i 'bad' [ 3.137387] Scanning device for bad blocks [ 3.157177] Bad eraseblock 206 at 0x0000019c0000 [ 3.169361] Bad eraseblock 306 at 0x0000026400by hachigo - uBoot
2. set the booting environment variable (note that usb_root variable is part of the bootargs): fw_setenv setenv usb_root 'LABEL=rootfs' Is this command correct? Should it be? : fw_setenv usb_root 'LABEL=rootfs' Also will this work with Pogoplug v2?by hachigo - uBoot
Oh ok makes sense now. Thanks.by hachigo - uBoot
Is it necessary to flash the default u-boot env when you update the U-Boot? All it seems to do for my Pogoplug v2 is brick it. I've done it in the past before and it bricked my pogo, and I did it again this time because I saw there was an updated U-Boot. SIde note- The reason I was updating again because I read in this thread about multi-drive configuration and maybe the new U-boot wouby hachigo - uBoot
Oh lol. Sorry I misunderstood. I am using linux. I can't seem to get it to work for mac or windows. As a side note, my usb doesn't boot anymore after installing the default environment image. Hopefully I can fix the env parameters with netconsole when I get some free time. I saw another thread where the user had the same problem, so hopefully I can fix it using information there befoby hachigo - uBoot
I thought it was necessary in case I break something as per the instructions. 10. Set up netconsole. It's important to set up neconsole if you don't already have serial console connected. I'm trying to learn as much Linux as I can with this pogoplug and I'm more than likely going to breaking somethings as I go. As for the netconsole, it turns out I skipped installingby hachigo - uBoot
Here is the screen output (I'm not sure where the logs are kept). # flash_erase /dev/mtd0 0 4 Erasing 128 Kibyte @ 60000 -- 100 % complete # nandwrite /dev/mtd0 uboot.2014.07-tld-1.pogo_e02.mtd0.kwb Writing data to block 0 at offset 0x0 Writing data to block 1 at offset 0x20000 Writing data to block 2 at offset 0x40000 Writing data to block 3 at offset 0x60000 Here is my fw_enby hachigo - uBoot
I've made it all the way through the guide. I think It has installed, I'm not entirely sure. Netconsole setup isn't working, I followed the directions on Jeff's guide. I'm booting directly into the Archlinux usb. The pogoplug just blinks orange without the USB plugged in, is this normal behavior? The pogoplug would boot before without a USB plugged in and I could ssh iby hachigo - uBoot
Hi, I was reading the guide on how to update the uBoot for Pogoplug E02. And I've detected bad block. 1. What should I do? 2. Also is it safe to upgrade the uBoot from Archlinux on usb or do I need to unplug all usbs? # dmesg | grep -i 'bad' [ 7.269250] Scanning device for bad blocks [ 7.301153] Bad eraseblock 366 at 0x000002dc0000by hachigo - uBoot