Problem installing U-Boot and kernel for Pogoplug V3 (OXNAS OX820)

I'm pretty sure it's a normal HDD. How do I modify the uBoot environment to only use USB for boot? I assume it's just some text file in the USB?

-_- oops, the first post said it hadn't been posted because I wrote like a bot. I guess it did actually post after all, hahaha. Can someone delete one pls?

Ancient Abysswalker Wrote:
-------------------------------------------------------
> I'm pretty sure it's a normal HDD. How do I modify
> the uBoot environment to only use USB for boot? I
> assume it's just some text file in the USB?

There a few different ways to adjust u-boot envs to boot the correct drive that has the rootfs.

- In serial console, this is safe if you take precaution not to save the envs until you know it works.
- In Debian, this must be vcarefully done, because a wrong setting could lock you out of the box.
- Using uEnv.txt, this is very safe, in that the envs are only executed during boot, and never got saved.

The u-boot installation thread describes how to use uEnv.txt:

Quote

A. How to use the uEnv.txt script

If you are not sure after reading that, then post your current u-boot envs listing and I'll help to adjust them.

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

Sorry for the delayed response, I'm working away from home on weekly stints but I'm back for a bit now. I think i did something wrong... I made the uEnv.txt file in the correct directory, and added the singular line "devices=usb" (I'm guessing that's where my mistake is). When I boot with just a USB everything's fine, but when I have the USB and the SATA - instead of getting a login prompt at the end of booting I get to (initramfs) at which point it looks like i can send commands. What should I be writing to the uEnv to get it to always boot USB? Instead of writing "devices=USB" am I supposed to give the USB MAC address or something?

Here is the general explanation:
http://forum.doozan.com/read.php?3,19093

And read section 11 in the installation procedure for this uboot:
http://forum.doozan.com/read.php?3,16017

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

Sorry. Just to clarify, am I copying the scanning code bits from section A and the mounting bits from B into the uEnv.txt file? Or is this a different method of approaching the boot order problem? I'm just not sure what bits I'm actually using here :) hahaha

Ancient Abysswalker Wrote:
-------------------------------------------------------
> Sorry. Just to clarify, am I copying the scanning
> code bits from section A and the mounting bits
> from B into the uEnv.txt file? Or is this a
> different method of approaching the boot order
> problem? I'm just not sure what bits I'm actually
> using here :) hahaha

The default envs already have the scanning logic. What you need to ensure is the rootfs on the USB drive satisfies all the setup requirements as stated in the rootfs installation procedure. And the HDD drive has only data.

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

Afar as I can tell I already satisfy all four... I have only one disk with a kernel, the disk has one partition - rootfs - with is ext3...? I only have issues when I boot initially with a second device installed :/ And the HDD i have has been wiped

Boot with USB rootfs only. And get these outputs:

fw_printenv
cat /proc/cmdline
fdisk -l
ls -l /dev/disk/by-label
mount

Plug the Sata drive in, mount it. Assuming it is mounted at /media/sdb1. Get these outputs:

fdisk -l 
ls -l /dev/disk/by-label
ls -l /media/sdb1/

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



Edited 1 time(s). Last edit at 10/13/2016 10:35PM by bodhi.

Here's the data I pulled:

fw_printenv -> http://imgur.com/wKyvLf5
cat /proc/cmdline -> console=ttyS0,115200 root=/dev/sda1 rootdelay=10
fdisk -l -> http://imgur.com/U4xerhh
ls -l /dev/disk/by-label and mount -> http://imgur.com/gHUooEW

Plug the Sata drive in, mount it. Assuming it is mounted at /media/sdb1. Get these outputs:
fdisk -l -> http://imgur.com/DIjlJVt
ls -l /dev/disk/by-label and ls -l /mnt/sdb1 -> http://imgur.com/UBeENb6

Ancient Abysswalker,

Advise: never post captured images for troubleshooting. If it is a simple problem, then a small screen capture is OK, but text log is always the best way (we can not search for a string in images). Please post text log only.

---------

Your problem is because the u-boot envs are old, not uboot.2013.10-tld-5.ox820.environment version. Did you install the new u-boot ?

Quote

Updated 22 Nov 2015

I've uploaded the uboot.2015.10-tld-1 u-Boot image for Pogoplug V3 Oxnas.

There is no scanning script in your u-boot envs, and bootargs does not have the root label. That's why u-boot could not figure out which drive is the rootfs.

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

Odd. I am using the files from uboot.2015.10-tld-1.ox820.bodhi.tar so yes I think I'm using new uBoot. I'm also using the files from Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2 and I'm guessing that's where the issue is arising from? In this case, do I just need to redo the boot USB, or is the issue with the uBoot I flashed to the pogoplug?

Ancient Abysswalker Wrote:
-------------------------------------------------------
> Odd. I am using the files from
> uboot.2015.10-tld-1.ox820.bodhi.tar so yes I think
> I'm using new uBoot. I'm also using the files from
> Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2 and
> I'm guessing that's where the issue is arising
> from? In this case, do I just need to redo the
> boot USB, or is the issue with the uBoot I flashed
> to the pogoplug?

Only need to do step 10 and the rest in the uboot installation instruction. Everything else is OK.

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

I only need to redo step 10 then (and ensure step 11 is upheld - which I believe it is)? - which version of the uboot environment image do I need? I used the 2013.10-tld-5 that was included in the tar for the 2015 update...

You have not done these steps when you installed new u-boot:

Flashing Instruction: 

.....


9. Erase 1 block starting 0x00100000 
/usr/sbin/flash_erase /dev/mtd0 0x00100000 1
Expected output 
Erasing 128 Kibyte @ 100000 -- 100 % complete

10. Flash uboot environment to 0x00100000 
/usr/sbin/nandwrite -s 1048576 /dev/mtd0 uboot.2013.10-tld-5.ox820.environment.img
Expected output 
Writing data to block 8 at offset 0x100000

......

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

Huh, odd. I thought I did those, but maybe I typo'd them the first time. I won't have any time to check for two weeks due to work but I'll redo those steps when I get back and check...

And that was it, I just missed those two lines