2015.10 U-Boot for Pogoplug V3 (OXNAS OX820)

Bodhi,

That would be awesome!
If i understand things right i will be able to boot from the external hdd attached to the sata connection.
I also would be able to flash a uboot in the nand so the hdd does not have to be attached to the sata connection in order to boot right?

I found multiple sounds that when you change the nand you will not be able to run the pogoplug service. There is one blog that says we should be able to do:http://blog.qnology.com/2013/03/tutorial-pogoplug-e02-with-arch-linux.html
Is that true?

In the mean time i am prepairing a 500gig hdd for the boot. Have a ubuntu usb stick for the terminal to execute all the commands. The only thing i need are the files.
If i am correct i need one file more it's the Oxnas rootfs found here(well not found anymore): http://archlinuxarm.org/os/ArchLinuxARM-oxnas-latest.tar.gz
Is there a replacement for that file?

Lithium,

> If i understand things right i will be able to
> boot from the external hdd attached to the sata
> connection.
> I also would be able to flash a uboot in the nand
> so the hdd does not have to be attached to the
> sata connection in order to boot right?

Yes, correct.

>
> I found multiple sounds that when you change the
> nand you will not be able to run the pogoplug
> service. There is one blog that says we should be
> able to
> do:http://blog.qnology.com/2013/03/tutorial-pogopl
> ug-e02-with-arch-linux.html
> Is that true?

No, it is not true. That's for a different device: Pogo E02 (Kirkwood). Once you've flashed the new u-boot (OXNAS) from this thread, Pogoplug service will not be usable anymore.

> In the mean time i am prepairing a 500gig hdd for
> the boot. Have a ubuntu usb stick for the terminal
> to execute all the commands. The only thing i need
> are the files.
> If i am correct i need one file more it's the
> Oxnas rootfs found here(well not found anymore):
> http://archlinuxarm.org/os/ArchLinuxARM-oxnas-late
> st.tar.gz
> Is there a replacement for that file?

That is Arch rootfs. So it does not apply. The tarballs that people have been offerred in the past was a tarball containing Debian rootfs. But regardless which one, all that matters is you can boot back to Linux and then flash new u-boot.

So when you said you are preparing the HDD, please describe all the steps you did here so we can see what is your remaining missing file, or steps yet need to be done.

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

The 500 gig hdd was almost full so i needed to copy everything else. Put the hdd in another laptop so i can boot ubuntu. I deleted all partitions on it as mentioned in step one. Now we need to wait for a tarball so i can make it boot.

Copying 500gig takes a little time haha

Here you go, our Leggo knows where to find it:
http://forum.doozan.com/read.php?2,27011,27015#msg-27015

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

Hi Bodhi,

I saw the post, awesome! I managed to download the disk create files from: https://groenholdt.net/Computers/Gentoo/medion-0x820-based-nas/onax-sata_boot.tar.gz

I got a connection time-out at rapidshare :(

Lithium Wrote:
-------------------------------------------------------
> Hi Bodhi,
>
> I saw the post, awesome! I managed to download the
> disk create files from:
> https://groenholdt.net/Computers/Gentoo/medion-0x8
> 20-based-nas/onax-sata_boot.tar.gz
>
> I got a connection time-out at rapidshare :(

Please register to the forum so either Leggo or I can send the tarball to you to try.

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

I made an account :)

What i have so far and what i did so far:

I found a file on the net: http://www.filedropper.com/onax-sataboottar hope the file is the right one.

After that i made a bootable ubuntu usb so i can boot my laptop on ubuntu. Deleted all the partitions on the hdd.
Found my hdd on /dev/sdb
Edited disk_create file and changed the line to: disk=/dev/sdb

I didn't change the symlinks in it, i am not sure if the classic has a pci bus, and i don't know what to do with the symlinks.

The commands till now are:

ubuntu@ubuntu:~/Desktop/tmp$ tar -xvzf onax-sata_boot.tar.gz 
./
./disk_create
./uImage
./stage1/
./stage1/stage1.wrapped750
./stage1/stage1.wrapped850
./stage1/stage1.wrapped700
./stage1/stage1.wrapped800
./u-boot/
./u-boot/u-boot.wrapped
./u-boot.wrapped
./stage1.wrapped
./uImages/
./uImages/uImage.nopci
./uImages/uImage.pci

sudo ./disk_create
0+1 records in
0+1 records out
444 bytes (444 B) copied, 2.89768 s, 0.2 kB/s
Writing stage 1
14+1 records in
14+1 records out
7576 bytes (7.6 kB) copied, 0.0194048 s, 390 kB/s
Writing uboot
253+1 records in
253+1 records out
129852 bytes (130 kB) copied, 0.187917 s, 691 kB/s
Writing kernel to 
4164+1 records in
4164+1 records out
2132324 bytes (2.1 MB) copied, 0.00910292 s, 234 MB/s

ubuntu@ubuntu:~/Desktop/tmp$ sudo fdisk /dev/sdb

Welcome to fdisk (util-linux 2.26.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): p
Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00008000

Command (m for help): n
Partition type
   p   primary (0 primary, 0 extended, 4 free)
   e   extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1): 1
First sector (2048-976773167, default 2048): 2048
Last sector, +sectors or +size{K,M,G,T,P} (2048-976773167, default 976773167): +10M

Created a new partition 1 of type 'Linux' and of size 10 MiB.

Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

ubuntu@ubuntu:~/Desktop/tmp$ sudo fdisk /dev/sdb

Welcome to fdisk (util-linux 2.26.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): n
Partition type
   p   primary (1 primary, 0 extended, 3 free)
   e   extended (container for logical partitions)
Select (default p): p
Partition number (2-4, default 2): 2
First sector (22528-976773167, default 22528): 
Last sector, +sectors or +size{K,M,G,T,P} (22528-976773167, default 976773167): +100M

Created a new partition 2 of type 'Linux' and of size 100 MiB.

Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

ubuntu@ubuntu:~/Desktop/tmp$ sudo mkfs.ext3 /dev/sdb2
mke2fs 1.42.12 (29-Aug-2014)
Creating filesystem with 102400 1k blocks and 25688 inodes
Filesystem UUID: 5336a9d1-e862-4cad-b8c8-26180c716868
Superblock backups stored on blocks: 
	8193, 24577, 40961, 57345, 73729

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done 

ubuntu@ubuntu:~/Desktop/tmp$ sudo e2label /dev/sdb2 rootfs

ubuntu@ubuntu:~/Desktop/tmp$ sudo ./disk_create
0+1 records in
0+1 records out
444 bytes (444 B) copied, 0.000132105 s, 3.4 MB/s
Writing stage 1
14+1 records in
14+1 records out
7576 bytes (7.6 kB) copied, 0.0444857 s, 170 kB/s
Writing uboot
253+1 records in
253+1 records out
129852 bytes (130 kB) copied, 0.443836 s, 293 kB/s
Writing kernel to 
4164+1 records in
4164+1 records out
2132324 bytes (2.1 MB) copied, 0.00784558 s, 272 MB/s

And from here i am stuck, i need a oxnas rootfs, the download link on this page is down: www.arclinus.org/os/ArchLinuxARM-oxnas-latest.tar.gz

Edit: I was looking trhough my download history from yesterday and somehow i have downloaded oxnas-rootfs-2013-06.tar from: https://dl.dropboxusercontent.com/u/15043728/ArchLinuxArm/oxnas/oxnas-rootfs-2013-06.tar.gz
Should this be the right one?

Edit2: i neede to change the symlink from uImage to nopci. After that i plugged the power in the pogo and after a few seconds i saw the green leg flashing rapidly a few times and it went off again. Not able to connect through ssh.

Edit3: Serial information attached in the txt file.

Edit4: Serial printenv output:

$ printenv
bootcmd=run dload1 boot || run dload2 boot || lightled
bootdelay=2
baudrate=115200
ethaddr=00:30:e0:00:00:01
ipaddr=172.31.0.128
serverip=172.31.0.100
autoload=n
netmask=255.255.0.0
bootfile="uImage"
lightled=ledfail 1
extinguishled=ledfail 0
boot=bootm 60500000
dload1=diskboot 60500000 0:1
dload2=diskboot 60500000 0:2
root_dev1=/dev/sda2
root_dev2=/dev/sda1
root_dev=/dev/sda2
stdin=serial
stdout=serial
stderr=serial
bootargs=root=/dev/sda2 console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 rootwait ubi.mtd=2,512 mem=128M poweroutage=yes

Environment size: 565/8188 bytes

Edited 4 time(s). Last edit at 03/26/2016 09:36AM by Lithium.

Okay, by searching a half day i finally found the problem.
It had something to do with the network adapter.
This post: https://archlinuxarm.org/forum/viewtopic.php?f=55&t=2146&start=340#p29888
Subscribed what i did.
I wrote the uImage.nopci again and it works now.

The serial commands says alarm login and ssh works fine :)
I suppose i can now begin with flashing the nand?

I have a bad block in the first 2M:

[root@alarm tmp]# dmesg | grep -i 'bad'
[    2.300000] Scanning device for bad blocks
[    2.300000] Bad eraseblock 5 at 0x0000000a0000
[    2.300000] Bad eraseblock 116 at 0x000000e80000
[    2.310000] Bad eraseblock 268 at 0x000002180000
[    2.340000] Bad eraseblock 590 at 0x0000049c0000
[    2.350000] Bad eraseblock 789 at 0x0000062a0000
[    2.860000] UBI: number of bad PEBs:         4
[    2.890000] UBI: number of PEBs reserved for bad PEB handling: 9

Step 4 says there is a workaround. I was not able to find that workaround. Would you mind to provide that to me?
The next steps are also a little unclear. With the steps i am flashing the nand. What should i do after that? I suppose i need a Debian to install on a usb so the pogoplug can run it?



Edited 2 time(s). Last edit at 03/26/2016 02:09PM by Lithium.

Congrat! so it's alive and well!

Let me look at your serial log and then suggest how to proceed.

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

Lithium,

Please repost the latest serial boot log. You can post it here in code tag.


Next step is preparing a USB Debian rootfs: http://forum.doozan.com/read.php?2,16044

After flashing u-boot, you will be able to unplug the HDD, and boot with USB.

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



Edited 1 time(s). Last edit at 03/26/2016 03:44PM by bodhi.

Lithium,

Looking at your situation, it is OK to proceed with flashing u-boot to NAND. You already have a recovery system which is booting SATA. So no fear :)

Proceed with the u-boot instruction. With the following special attention:

At step 1, make sure you see this:

dev:    size   erasesize  name
mtd0: 00e00000 00020000 "boot"
mtd1: 07200000 00020000 "data"

At step 8

Quote

8. Flash u-boot to 0x40000
/usr/sbin/nandwrite -s 262144 /dev/mtd0 uboot.2015.10-tld-1.ox820.mtd0.img
Expected output
Writing data to block 2 at offset 0x40000
Writing data to block 3 at offset 0x60000
Writing data to block 4 at offset 0x80000
Writing data to block 5 at offset 0xa0000

Stop here and post the entire flashing session log. The step 8 output will show error but I expect it to be OK. I want to see and confirm this before you can go to step 9.

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

Hi Bodhi,
In the attachment the serial log.

What to do first?
How do i get this output at step 1?

dev:    size   erasesize  name
mtd0: 00e00000 00020000 "boot"
mtd1: 07200000 00020000 "data"

I now have:

[root@alarm boot]# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 08000000 00020000 "NAND 128MiB 3,3V 8-bit"
mtd1: 00e00000 00020000 "boot"
mtd2: 07200000 00020000 "rootfs"

I dont know how to modify this.

Lithium,

Interrupt u-boot serial console and

printenv

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



Edited 1 time(s). Last edit at 03/26/2016 06:41PM by bodhi.

I am not able to use apt-get. Command not found. What now?

Lithium Wrote:
-------------------------------------------------------
> I am not able to use apt-get. Command not found.
> What now?

Did you put the Debian rootfs in the HDD? or you are still running Arch?

Slow down :) tell us what you have done so far, and pls get the envs in serial console as I've requested above.

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



Edited 1 time(s). Last edit at 03/26/2016 06:53PM by bodhi.

$ printenv
bootcmd=run dload1 boot || run dload2 boot || lightled
bootdelay=2
baudrate=115200
ethaddr=00:30:e0:00:00:01
ipaddr=172.31.0.128
serverip=172.31.0.100
autoload=n
netmask=255.255.0.0
bootfile="uImage"
lightled=ledfail 1
extinguishled=ledfail 0
boot=bootm 60500000
dload1=diskboot 60500000 0:1
dload2=diskboot 60500000 0:2
root_dev1=/dev/sda2
root_dev2=/dev/sda1
root_dev=/dev/sda2
stdin=serial
stdout=serial
stderr=serial
bootargs=root=/dev/sda2 console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 ipv6.disable=1 rootwait ubi.mtd=2,512 mem=128M poweroutage=yes

Environment size: 580/8188 bytes


I am still running arch from the hdd.
I dont know how to put the Debian rootfs in the HDD.
Managed to run archlinux on the hdd so i can boot. Thats all. The steps i made can be found in this thread.



Edited 5 time(s). Last edit at 03/26/2016 08:32PM by Lithium.

Lithium,

> I now have:
> [root@alarm boot]# cat /proc/mtd
> dev: size erasesize name
> mtd0: 08000000 00020000 "NAND 128MiB 3,3V 8-bit"
> mtd1: 00e00000 00020000 "boot"
> mtd2: 07200000 00020000 "rootfs"
> I dont know how to modify this.

Power up, interrupt serial console and change the bootargs

setenv bootargs 'root=/dev/sda2 console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 rootwait ubi.mtd=2,512 mem=128M poweroutage=yes mtdparts=41000000.nand:14m(boot),-(data)'

and then

boot

After booted into Debian, check it again

cat /proc/mtd

Before you start flashing u-boot, look at what I've posted above (those are special attentions for your case with a bad block in the 1st 2M):
http://forum.doozan.com/read.php?3,16017,27042#msg-27042

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

Hi Bodhi,

Thanks for the post.
I changed the bootenv, after typing cat /proc/mtd.

dev:    size   erasesize  name
mtd0: 08000000 00020000 "NAND 128MiB 3,3V 8-bit"
mtd1: 00e00000 00020000 "boot"
mtd2: 07200000 00020000 "rootfs"

I have Arch Linux on the HDD not Debian, is that a problem? Or can u just proceed with flashing the nand?

The attention you asked for:

[root@alarm tmp]# /usr/sbin/flash_erase /dev/mtd0 0x0 6
Erasing 128 Kibyte @ 80000 -- 66 % complete flash_erase: Skipping bad block at 000a0000
Erasing 128 Kibyte @ a0000 -- 100 % complete


# /usr/sbin/nandwrite -s 262144 /dev/mtd0 uboot.2015.10-tld-1.ox820.mtd0.img
Writing data to block 2 at offset 0x40000
Writing data to block 3 at offset 0x60000
Writing data to block 4 at offset 0x80000
Writing data to block 5 at offset 0xa0000
Bad block at a0000, 1 block(s) from a0000 will be skipped
Writing data to block 6 at offset 0xc0000

Edited 3 time(s). Last edit at 03/27/2016 07:40AM by Lithium.

Hi,

Sata-boot needs actually only two things. First is stage 1 loader written directly to a proper space in sata disk (starting from sector 34 if I remember this right). Stage 1 loader (SPL) must be compiled to search U-Boot and environment from disk file system.

Second is some bytes written in start of the disk.

Rest is setting U-boot environment correctly.

If someone still needs this, I can provide those things.

Thanks tilator, but Leggo already done that.

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

Lithium,

I've revised step 6,7,8. Please do steps 6,7,8 again as shown below. And then continue step 9 to the rest. And post output of the entire flashing session here before you reboot.

6. Erase 7 blocks on mtd0

/usr/sbin/flash_erase /dev/mtd0 0x0 7

7. Flash encoded spl stage1 to 0x0

/usr/sbin/nandwrite /dev/mtd0 uboot.spl.2013.10.ox820.850mhz.mtd0.img

8. Flash u-boot to 0x40000

/usr/sbin/nandwrite -s 262144 /dev/mtd0 uboot.2015.10-tld-1.ox820.mtd0.img

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

Hi Bodhi,

Here is the console output:

[root@alarm tmp]# /usr/sbin/flash_erase /dev/mtd0 0x0 6
Erasing 128 Kibyte @ 80000 -- 66 % complete flash_erase: Skipping bad block at 000a0000
Erasing 128 Kibyte @ a0000 -- 100 % complete

# /usr/sbin/nandwrite /dev/mtd0 uboot.spl.2013.10.ox820.850mhz.mtd0.img
Writing data to block 0 at offset 0x0

# /usr/sbin/nandwrite -s 262144 /dev/mtd0 uboot.2015.10-tld-1.ox820.mtd0.img
Writing data to block 2 at offset 0x40000
Writing data to block 3 at offset 0x60000
Writing data to block 4 at offset 0x80000
Writing data to block 5 at offset 0xa0000
Bad block at a0000, 1 block(s) from a0000 will be skipped
Writing data to block 6 at offset 0xc0000
[root@alarm tmp]# /usr/sbin/flash_erase /dev/mtd0 0x00100000 1
Erasing 128 Kibyte @ 100000 -- 100 % complete

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

I think everything went well?

Lithium,

No, you've missed the new step 6 as I revised above (erase 7 blocks). Please redo 6,7,8 as posted above.

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

Oh damm sorry. I missed that. I will do the steps again. Is that okay or should i reboot first?



Edited 2 time(s). Last edit at 03/27/2016 04:29PM by Lithium.

Lithium Wrote:
-------------------------------------------------------
> Oh damm sorry. I missed that. I will do the steps
> again. Is that okay or should i reboot first?

It's OK, no need to reboot.

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

[root@alarm tmp]# /usr/sbin/flash_erase /dev/mtd0 0x0 7
Erasing 128 Kibyte @ 80000 -- 57 % complete flash_erase: Skipping bad block at 000a0000
Erasing 128 Kibyte @ c0000 -- 100 % complete
td0.imglarm tmp]# /usr/sbin/nandwrite /dev/mtd0 uboot.spl.2013.10.ox820.850mhz.m
Writing data to block 0 at offset 0x0
820.mtd0.imgtmp]# /usr/sbin/nandwrite -s 262144 /dev/mtd0 uboot.2015.10-tld-1.ox
Writing data to block 2 at offset 0x40000
Writing data to block 3 at offset 0x60000
Writing data to block 4 at offset 0x80000
Writing data to block 5 at offset 0xa0000
Bad block at a0000, 1 block(s) from a0000 will be skipped
Writing data to block 6 at offset 0xc0000
[root@alarm tmp]# /usr/sbin/flash_erase /dev/mtd0 0x00100000 1
Erasing 128 Kibyte @ 100000 -- 100 % complete
x820.environment.imgsr/sbin/nandwrite -s 1048576 /dev/mtd0 uboot.2013.10-tld-5.o
Writing data to block 8 at offset 0x100000

Why did you changed step 6 for me? I am interested in the process :)
If this went well what should i do next? I still run Linux Arch so i am not able to use apt-get and dpkg.



Edited 1 time(s). Last edit at 03/27/2016 04:33PM by Lithium.

The log is hard to read, but it looks like everything is OK.

You can proceed:

1. On a different Linux box, create the Debian 3.17 rootfs as instructed in this tread.

Scroll down to the section:

Quote

Latest rootfs: Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2 (02 Nov 2014)

And follow the instruction very closely (most importantly, you will need to be root user the whole time while creating the USB rootfs). Also, since this is the new u-boot, the uImage is not need to have DTB embedded. So step 4 should be skipped.

2. After the USB rootfs is ready, shutdow the Pogo, unplug the HDD, plug in the USB rootfs, and power up.

3. Interrupt serial console and get the listing of

printenv

and then, go ahead, boot:

boot

And post the entire serial console log here.

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

Explanation for change in step 6:

Because the bad block is block 5, and the whole flashing process needs 6 blocks. When you flash u-boot image the bad block will be skipped, so the u-boot image will be stored in 2 chunks: block 2-4, and block 6.

Therefore block 6 needs to be erased, too. So in the step 6 instruction we erased 7 blocks, knowing that one block will be skipped.

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



Edited 1 time(s). Last edit at 03/27/2016 04:55PM by bodhi.

Ah i understand, thanks.

The bad console paste has to due with putty console.
I will proceed with the other steps and will let you know how it went.
What is the reason you let me install an older version of Debian?