Welcome! Log In Create A New Profile

Advanced

Backup and Restore NAND mtds - Pogoplug V4 original MTD partitions

Posted by bodhi 
Backup and Restore NAND mtds - Pogoplug V4 original MTD partitions
July 24, 2014 05:17PM
Since a lot of people have been getting the Pogo V4/Mobile lately, just thought I'd repost the download link to one of my Pogo V4s original MTDs here. In case anybody wants to revert to stock, and can't do it because they have already installed newer U-Boot.

Dowload at Dropbox:
pogoplug_v4_mtd_original.tar.bz2
md5
064a298c89ae5a1b207061e11b401930

You only need to use mtd0 to restore u-boot. And that's enough to go back to stock. Other mtds are included in the tarball just in case the whole NAND needs to be restored :)

And if you use these mtd partitions to restore, please remember to reset the cesvcid to your own number :), and also reset ethaddr to your own box, so that you can continue using Pogoplug service. The environment variable looks like this:
cesvcid=V88XBRRLWPC9WYGQxxxxxxxxx

A. How to restore NAND in Linux (any distro):
====================================

Warning: Don't do this if you have any bad block in these MTD partitions, especially mtd0 (check your dmesg). And also do this at your own risk, it's highly recommended that you have serial console attached to recover from any bad flash.

The original mtd0 was saved using the following nanddump command:

/tmp # ./nanddump -nf usb/mtd0 /dev/mtd0
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00200000...

So in order to restore mtd0 back, you can use flash_erase and nandwrite. Below are actual flashing and output. Your output should look exactly like these. If not, don't reboot, and post the question here.

1. make sure the mtparts are correct
# fw_printenv mtdparts
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
2. Erase mtd0:
#flash_erase /dev/mtd0 0 16
Erase Total 16 Units
Performing Flash Erase of length 131072 at offset 0x1e0000 done
3. Write mtd0 backup file back to NAND:
# nandwrite -on /dev/mtd0 mtd0
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
Writing data to block 4 at offset 0x80000
Writing data to block 5 at offset 0xa0000
Writing data to block 6 at offset 0xc0000
Writing data to block 7 at offset 0xe0000
Writing data to block 8 at offset 0x100000
Writing data to block 9 at offset 0x120000
Writing data to block 10 at offset 0x140000
Writing data to block 11 at offset 0x160000
Writing data to block 12 at offset 0x180000
Writing data to block 13 at offset 0x1a0000
Writing data to block 14 at offset 0x1c0000
Writing data to block 15 at offset 0x1e0000

If you need to restore mtd1 to mtd4, then calculate the number of blocks for each mtd (i.e. a block is 128K, 1M is 8 blocks).

NOTE:

The nanddump command above is to back up your own box and later restore it to the same box. To backup mtd0 (or other mtds), make it a little more robust so that it can be used in different boxes without problem (thanks restamp for suggestion), use the following format:

nanddump --noecc --omitoob -l 0x80000 -f mtd0 /dev/mtd0


B. How to restore NAND in Serial Console:
==================================


Here is what to do if you've decided that you need to restore NAND mtd0 in serial console to go back to stock OS. Assuming only mtd0 was messed up (that's how it usually happens). If the entire NAND was messed up, then use this procedure to restore mtd0 and then calculate the offset and size of the rest of the other mtds. If you're not sure, pls post questions in this thread.

Caveats: This is something I would not recommend doing, unless you can no loger boot into Debian or Arch. Because If you can use kwboot to boot the box, then you can boot Debian or Arch quite easily, without doing this procedure. See the Debian kernel/rootfs thread for how to create the Debian 4.4 rootfs to use with this box.

The procedure below has a lot more risk of errors occurred than flashing NAND mtd0 from Linux command line (section A).

Prerequisites

r1. This procedure requires a working serial console connected to the Pogo V4. And knowledge how to use kwboot to boot the latest version of u-boot.

r2. Download the latest u-boot, and kwboot binary as described in the u-boot thread to the serial console server (where you run kwboot). Create a single partition, type Ext3, USB thumbdrive. Copy your backup mtd0 to this USB drive root folder. Plug this USB drive into the Pogo V4 top USB port.

Restore NAND mtd0

1. Connect serial console and use kwboot to boot the Pogo V4. See davygravy instruction for more details. I'm assume that you already know how to use kwboot.

Run kwboot and interrupt serial console when you see the countdown:
./kwboot  -t -B 115200 /dev/ttyUSB0 -b uboot.2016.05-tld-1.pogo_v4.mtd0.kwb  -p
Expected output
Sending boot message. Please reboot the target...-
Sending boot image...
  0 % [......................................................................]
<snip>
 95 % [......................................................................]
 97 % [......................................................................]
 99 % [....................................]
[Type Ctrl-\ + c to quit]

U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700)
Pogoplug V4

SoC:   Kirkwood 88F6192_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  128 MiB
MMC:   kwsdio: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Hit any key to stop autoboot:  0

2. Verify the mtdparts is correct for Pogo V4

mtdparts
Expected output

device nand0 <orion_nand>, # parts = 5
 #: name		size		offset		mask_flags
 0: u-boot              0x00200000	0x00000000	0
 1: uImage              0x00300000	0x00200000	0
 2: uImage2             0x00300000	0x00500000	0
 3: failsafe            0x00800000	0x00800000	0
 4: root                0x07000000	0x01000000	0

active partition: nand0,2 - (uImage2) 0x00300000 @ 0x00500000

defaults:
mtdids  : none
mtdparts: none

3. Start the USB drive

usb start
Expected output

starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found

4. Load the backup mtd0. Here the stock mtd0 backup file name was mtd0.pogo_v4

ext2load usb 0:1 0x800000 /mtd0.pogo_v4
Expected output
2097152 bytes read in 1318 ms (1.5 MiB/s)


5. Erase mtd0

nand erase 0x0 0x200000
Expected output
NAND erase: device 0 offset 0x0, size 0x200000
Erasing at 0x1e0000 -- 100% complete.
OK

6. Flash mtd0.pogo_v4 to NAND mtd0

nand write 0x800000 0x0 0x200000
Expected output

NAND write: device 0 offset 0x0, size 0x200000
 2097152 bytes written: OK

7. Reset the box to boot with stock u-boot
reset
Expected output:

The stock u-boot banner and other info. And then it will proceeed to boot stock OS.

DONE.


C. Note
==========

Also see here for exaplanation about nanddump and flash_erase:

http://forum.doozan.com/read.php?3,29362,29887#msg-29887

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner



Edited 10 time(s). Last edit at 09/06/2016 02:30AM by bodhi.
Re: Pogoplug V4 original MTD partitions
July 24, 2014 10:40PM
Thanks for posting this.

Can you clarify if this is for the Pogoplug Series 4 or Mobile or does it even matter?

Also, what are the instructions for restoring the various mtd partitions back? Thanks
Re: Pogoplug V4 original MTD partitions
July 25, 2014 01:15AM
grayman4hire Wrote:
-------------------------------------------------------
> Thanks for posting this.
>
> Can you clarify if this is for the Pogoplug Series
> 4 or Mobile or does it even matter?
>
> Also, what are the instructions for restoring the
> various mtd partitions back? Thanks

I think it's the same for V4 or Mobile (you would have to try to confirm, no guarantee though). Except that your ceboardver environment variable should be the correct one. Here is the Pogo V4 ceboardver:

ceboardver=PPV4A3

I've added flashing instruction in the 1st post.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Danilo
Re: Pogoplug V4 original MTD partitions
May 13, 2015 09:13AM
Hello,
a friend of mine gave me a bricked Pogoplug v4, in which manner I could not understand.
So I put a serial port on it and tried this tutorial to revert it to original, since USB thumb method doesn't work.
Serial access is OK, but i' m stuck at step 1.
When I type fw_printenv mtdparts, I get -/bin/sh: fw_printenv: not found.
I tried that on preboot (CE) also, and got the same response..

Any idea? Thank you
Re: Pogoplug V4 original MTD partitions
May 13, 2015 03:19PM
Danilo,

If you booted with serial console, and gained access to the Linux prompt, then it must be the Pogo OS. If you're not sure, post the output of
uname -a
or post the entire output of:
dmesg

In Pogo OS, fw_printenv is not available, the command to list envs is: blparam. It's in one of the sub directories under /usr/local/sbin/cloudengines or /usr/local/bin/cloudengines. Be careful, don't execute it with any parameter, just blparam to list the envs:

For example:
/usr/sbin/cloudengines/bin/blparam

And to get the correct NAND tools, you can find them here:
http://forum.doozan.com/read.php?2,11663,11713#msg-11713

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
I used dmesg and received bad block warnings:

[    0.960000] Scanning device for bad blocks
[    0.990000] Bad eraseblock 495 at 0x000003de0000
[    0.990000] Bad eraseblock 496 at 0x000003e00000
[    1.010000] Bad eraseblock 867 at 0x000006c60000
[    1.030000] Using static partition definition
[    1.030000] Creating 5 MTD partitions on "nand_mtd":
[    1.040000] 0x000000000000-0x000000200000 : "u-boot"
[    1.040000] 0x000000200000-0x000000500000 : "uImage"
[    1.050000] 0x000000500000-0x000000800000 : "uImage2"
[    1.050000] 0x000000800000-0x000001000000 : "failsafe"
[    1.060000] 0x000001000000-0x000008000000 : "root"

Does this mean I cannot use the restore? is there another way?
It is not bricked, just want factory restore.
Re: Backup and Restore NAND mtds - Pogoplug V4 original MTD partitions
October 04, 2015 03:55PM
rlimas,

> It is not bricked, just want factory restore.

The bad blocks are not in mtd0. So you could restore mtd0, which is all you need to do. When you install newer u-boot, only mtd0 was written.

Before you do this, I would strongly recommend connecting connecting serial console, or only if you would be willing to connecting one should anything goes wrong.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Hello bodhi

Could you plz help me double check the commands below?

Erase mtd1:
#flash_erase /dev/mtd1 0 24 ( All mtd device's start address is "0" ?)

Erase mtd2:
#flash_erase /dev/mtd2 0 24

Erase mtd3:
#flash_erase /dev/mtd3 0 64

Erase mtd4:
#flash_erase /dev/mtd4 0 896

==============================================================
My problem is my pogo v4 series it maybe flashed firmware of pogo v4mobile before, so now it can't load sata HDD,
I now wanna the function of sata hdd, shall i reflash all from mtd0 to mtd4?
/tmp # cat /proc/mtd
dev: size erasesize name
mtd0: 00200000 00020000 "u-boot"
mtd1: 00300000 00020000 "uImage"
mtd2: 00300000 00020000 "uImage2"
mtd3: 00800000 00020000 "failsafe"
mtd4: 07000000 00020000 "root"

===============================

it seems that mtd4 is 70M, not 112M, anything wrong?
Re: Backup and Restore NAND mtds - Pogoplug V4 original MTD partitions
October 15, 2015 01:55PM
Ryan,

> My problem is my pogo v4 series it maybe flashed
> firmware of pogo v4mobile before, so now it can't
> load sata HDD,
> I now wanna the function of sata hdd, shall i
> reflash all from mtd0 to mtd4?

No need to. When you install u-boot, only mtd0 was written. However, are you booting this to Debian or Arch? if you can boot this Pogo V4, then you only need to install new u-boot from this thread:
http://forum.doozan.com/read.php?3,12381

Quote

mtd4: 07000000 00020000 "root"

This is OK. It's 0x07000000 in hex.

If you'd like to confirm before installing new u-boot, post your dmesg log here, and also post your currently installed u-boot version here too.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Hello bodhi
Thanks your helping!

1) my pogo v4 series is second hand for me ,and i am not good at Linux, so i don't know where to confirm my currently installed u-boot version, and dmesg log's location. would you plz give me a guidance?

2)few days ago, i have downloaded attached files above:pogoplug_v4_mtd_original.tar.bz2 . and I unrar it in win7, then i have restore the original mtd0 to my pogo,but after that my pogo v4 still cannot load sata hdd.

3)i have read topic ' 2014.07 U-Boot Kirkwood '.
there question.
Erase mtd0
flash_erase /dev/mtd0 0 4
In this topic :flash_erase /dev/mtd0 0 16. Should I used “4” or "16" blocks?

thank you very much~~
Re: Backup and Restore NAND mtds - Pogoplug V4 original MTD partitions
October 15, 2015 10:32PM
Ryan Wrote:
-------------------------------------------------------
> Hello bodhi
> Thanks your helping!
>
> 1) my pogo v4 series is second hand for me ,and i
> am not good at Linux, so i don't know where to
> confirm my currently installed u-boot version, and
> dmesg log's location. would you plz give me a
> guidance?

Boot the Pogo. Log into Debian, at the command line , execute:
dmesg

Capture the output and post here.

>
> 2)few days ago, i have downloaded attached files
> above:pogoplug_v4_mtd_original.tar.bz2 . and I
> unrar it in win7, then i have restore the original
> mtd0 to my pogo,but after that my pogo v4 still
> cannot load sata hdd.
>

The old u-boot can't boot SATA. You need to install new-u-boot. The backup mtd above is the original MTD, i.e. stock .


> 3)i have read topic ' 2014.07 U-Boot Kirkwood '.
> there question.
> Erase mtd0
> flash_erase /dev/mtd0 0 4
> In this topic :flash_erase /dev/mtd0 0
> 16. Should I used “4” or "16" blocks?
>

They are 2 different procedures.

Quote

> flash_erase /dev/mtd0 0 4

Erase 4 blocks (512K) to flash u-boot, which is 512K.

Quote

> In this topic :flash_erase /dev/mtd0 0 16

Erase 16 blocks (2M) to flash the orginal mtd0, which is 2M.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
>Boot the Pogo. Log into Debian, at the command line , execute:
>dmesg

>Capture the output and post here.

dmesg
<5>[ 0.000000] Linux version 2.6.31.8 (afenn@kt) (gcc version 4.3.2 (sdk3.3-ct-ng-1.4.1) ) #4 Tue Aug 23 13:00:50 PDT 2011
<4>[ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
<4>[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
<4>[ 0.000000] Machine: Feroceon-KW
<4>[ 0.000000] Using UBoot passing parameters structure
<4>[ 0.000000] Ignoring unrecognised tag 0x41004345
<4>[ 0.000000] Memory policy: ECC disabled, Data cache writeback
<7>[ 0.000000] On node 0 totalpages: 32768
<7>[ 0.000000] free_area_init_node: node 0, pgdat c0413670, node_mem_map c042d000
<7>[ 0.000000] Normal zone: 256 pages used for memmap
<7>[ 0.000000] Normal zone: 0 pages reserved
<7>[ 0.000000] Normal zone: 32512 pages, LIFO batch:7
<4>[ 0.000000] Built 1 zonelists in Zone order, mobility grouping off. Total pages: 32512
<5>[ 0.000000] Kernel command line: console=ttyS0,115200 root=ubi0:rootfs ubi.mtd=4,2048 rootfstype=ubifs
<4>[ 0.000000] PID hash table entries: 512 (order: 9, 2048 bytes)
<6>[ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
<6>[ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
<6>[ 0.000000] Memory: 128MB = 128MB total
<5>[ 0.000000] Memory: 118356KB available (3852K code, 261K data, 124K init,0K highmem)
<6>[ 0.000000] Hierarchical RCU implementation.
<6>[ 0.000000] NR_IRQS:128
<4>[ 0.000000] Console: colour dummy device 80x30
<6>[ 0.000000] Calibrating delay loop... 799.53 BogoMIPS (lpj=3997696)
<4>[ 0.230000] Mount-cache hash table entries: 512
<6>[ 0.230000] CPU: Testing write buffer coherency: ok
<6>[ 0.230000] NET: Registered protocol family 16
<6>[ 0.230000] Feroceon L2: Enabling L2
<6>[ 0.230000] Feroceon L2: Cache support initialised.
<4>[ 0.230000]
<4>[ 0.230000] CPU Interface
<4>[ 0.230000] -------------
<4>[ 0.230000] SDRAM_CS0 ....base 00000000, size 128MB
<4>[ 0.230000] SDRAM_CS1 ....disable
<4>[ 0.230000] SDRAM_CS2 ....disable
<4>[ 0.230000] SDRAM_CS3 ....disable
<4>[ 0.230000] PEX0_MEM ....base e0000000, size 128MB
<4>[ 0.230000] PEX0_IO ....base f2000000, size 1MB
<4>[ 0.230000] PEX1_MEM ....no such
<4>[ 0.230000] PEX1_IO ....no such
<4>[ 0.230000] INTER_REGS ....base f1000000, size 1MB
<4>[ 0.230000] NFLASH_CS ....base fa000000, size 2MB
<4>[ 0.230000] SPI_CS ....base f4000000, size 16MB
<4>[ 0.230000] BOOT_ROM_CS ....no such
<4>[ 0.230000] DEV_BOOTCS ....no such
<4>[ 0.230000] CRYPT_ENG ....base f0000000, size 2MB
<4>[ 0.230000]
<4>[ 0.230000] Marvell Development Board (LSP Version KW_LSP_5.1.3_patch18)-- RD-88F6192A-NAS Soc: 88F6192 A1 LE
<4>[ 0.230000]
<4>[ 0.230000] Detected Tclk 166666667 and SysClk 200000000
<4>[ 0.230000] Marvell USB EHCI Host controller #0: c403e740
<4>[ 0.730000] PEX0 interface detected Link X1
<7>[ 0.730000] pci 0000:00:01.0: reg 10 64bit mmio: [0x40000000-0x4000ffff]
<7>[ 0.730000] pci 0000:00:01.0: reg 18 64bit mmio: [0x40010000-0x40010fff]
<7>[ 0.730000] pci 0000:00:01.0: reg 20 64bit mmio: [0x40011000-0x40011fff]
<7>[ 0.740000] pci 0000:00:01.0: supports D1
<6>[ 0.740000] pci 0000:00:01.0: PME# supported from D0 D1 D3hot
<6>[ 0.740000] pci 0000:00:01.0: PME# disabled
<6>[ 0.740000] PCI: bus0: Fast back to back transfers disabled
<4>[ 0.740000] mvPexLocalBusNumSet: ERR. Invalid PEX interface 1
<4>[ 0.750000] bio: create slab <bio-0> at 0
<5>[ 0.750000] SCSI subsystem initialized
<6>[ 0.750000] usbcore: registered new interface driver usbfs
<6>[ 0.750000] usbcore: registered new interface driver hub
<6>[ 0.750000] usbcore: registered new device driver usb
<6>[ 0.750000] NET: Registered protocol family 2
<6>[ 0.750000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
<6>[ 0.750000] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
<6>[ 0.750000] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
<6>[ 0.750000] TCP: Hash tables configured (established 4096 bind 4096)
<6>[ 0.750000] TCP reno registered
<6>[ 0.750000] NET: Registered protocol family 1
<6>[ 0.750000] cpufreq: Init kirkwood cpufreq driver
<7>[ 0.750000] cpufreq: High frequency: 800000KHz - Low frequency: 200000KHz
<7>[ 0.750000] cpufreq: Setting CPU Frequency to 800000 KHz
<7>[ 0.750000] cpufreq: Setting PowerSaveState to off
<6>[ 0.760000] XOR registered 4 channels
<6>[ 0.760000] XOR 2nd invalidate WA enabled
<4>[ 0.760000] cesadev_init(c000d7fc)
<4>[ 0.760000] mvCesaInit: sessions=640, queue=64, pSram=f0000000
<6>[ 0.760000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
<6>[ 0.770000] msgmni has been set to 231
<6>[ 0.770000] alg: No test for cipher_null (cipher_null-generic)
<6>[ 0.770000] alg: No test for ecb(cipher_null) (ecb-cipher_null)
<6>[ 0.770000] alg: No test for digest_null (digest_null-generic)
<6>[ 0.770000] alg: No test for compress_null (compress_null-generic)
<6>[ 0.780000] alg: No test for stdrng (krng)
<6>[ 0.780000] alg: No test for hmac(digest_null) (hmac(digest_null-generic))
<6>[ 0.790000] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
<6>[ 0.790000] io scheduler noop registered
<6>[ 0.790000] io scheduler anticipatory registered (default)
<4>[ 0.790000] Initializing ths8200_init
<4>[ 0.790000] Initializing dove_adi9889_init
<6>[ 0.810000] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
<6>[ 0.810000] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
<6>[ 0.810000] console [ttyS0] enabled
<4>[ 0.820000] Integrated Sata device found
<4>[ 0.830000] IRQ 21/mvSata: IRQF_DISABLED is not guaranteed on shared IRQs
<6>[ 0.850000] scsi0 : Marvell SCSI to SATA adapter
<6>[ 0.860000] scsi1 : Marvell SCSI to SATA adapter
<4>[ 0.870000] Loading Marvell Ethernet Driver:
<4>[ 0.870000] o Cached descriptors in DRAM
<4>[ 0.880000] o DRAM SW cache-coherency
<4>[ 0.880000] o 1 Giga ports supported
<4>[ 0.880000] o Single RX Queue support - ETH_DEF_RXQ=0
<4>[ 0.890000] o Single TX Queue support - ETH_DEF_TXQ=0
<4>[ 0.890000] o TCP segmentation offload (TSO) supported
<4>[ 0.900000] o Large Receive offload (LRO) supported
<4>[ 0.900000] o Receive checksum offload supported
<4>[ 0.910000] o Transmit checksum offload supported
<4>[ 0.910000] o Network Fast Processing (Routing) supported - (Disabled)
<4>[ 0.920000] o Driver ERROR statistics enabled
<4>[ 0.930000] o Proc tool API enabled
<4>[ 0.930000] o SKB Reuse supported - (Disabled)
<4>[ 0.930000] o SKB Recycle supported - (Disabled)
<4>[ 0.940000] o Rx descripors: q0=128
<4>[ 0.940000] o Tx descripors: q0=532
<4>[ 0.950000] o Loading network interface(s):
<4>[ 0.950000] o register under mv88fx_eth platform
<4>[ 0.960000] o eth0, ifindex = 2, GbE port = 0
<4>[ 0.960000]
<4>[ 0.960000] mvFpRuleDb (c45b1000): 1024 entries, 4096 bytes
<4>[ 0.970000] Counter=0, opIdx=6, overhead=16
<4>[ 0.970000] Counter=1, opIdx=2, overhead=0
<4>[ 0.980000] Counter=2, opIdx=1, overhead=18
<4>[ 0.980000] Counter=3, opIdx=2, overhead=0
<6>[ 0.990000] tun: Universal TUN/TAP device driver, 1.6
<6>[ 0.990000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
<6>[ 1.000000] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)
<6>[ 1.010000] Scanning device for bad blocks
<4>[ 1.060000] Using static partition definition
<5>[ 1.060000] Creating 5 MTD partitions on "nand_mtd":
<5>[ 1.070000] 0x000000000000-0x000000200000 : "u-boot"
<5>[ 1.070000] 0x000000200000-0x000000500000 : "uImage"
<5>[ 1.080000] 0x000000500000-0x000000800000 : "uImage2"
<5>[ 1.080000] 0x000000800000-0x000001000000 : "failsafe"
<5>[ 1.090000] 0x000001000000-0x000008000000 : "root"
<5>[ 1.100000] UBI: attaching mtd4 to ubi0
<5>[ 1.100000] UBI: physical eraseblock size: 131072 bytes (128 KiB)
<5>[ 1.110000] UBI: logical eraseblock size: 126976 bytes
<5>[ 1.110000] UBI: smallest flash I/O unit: 2048
<5>[ 1.120000] UBI: sub-page size: 512
<5>[ 1.120000] UBI: VID header offset: 2048 (aligned 2048)
<5>[ 1.130000] UBI: data offset: 4096
<5>[ 1.350000] UBI: attached mtd4 to ubi0
<5>[ 1.360000] UBI: MTD device name: "root"
<5>[ 1.360000] UBI: MTD device size: 112 MiB
<5>[ 1.360000] UBI: number of good PEBs: 896
<5>[ 1.370000] UBI: number of bad PEBs: 0
<5>[ 1.370000] UBI: max. allowed volumes: 128
<5>[ 1.380000] UBI: wear-leveling threshold: 4096
<5>[ 1.380000] UBI: number of internal volumes: 1
<5>[ 1.390000] UBI: number of user volumes: 1
<5>[ 1.390000] UBI: available PEBs: 0
<5>[ 1.400000] UBI: total number of reserved PEBs: 896
<5>[ 1.400000] UBI: number of PEBs reserved for bad PEB handling: 8
<5>[ 1.410000] UBI: max/mean erase counter: 1/0
<5>[ 1.410000] UBI: image sequence number: 0
<6>[ 1.420000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
<6>[ 1.420000] ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
<6>[ 1.430000] ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
<5>[ 1.440000] UBI: background thread "ubi_bgt0d" started, PID 452
<6>[ 1.470000] ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
<6>[ 1.490000] ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00
<6>[ 1.490000] usb usb1: configuration #1 chosen from 1 choice
<6>[ 1.500000] hub 1-0:1.0: USB hub found
<6>[ 1.500000] hub 1-0:1.0: 1 port detected
<6>[ 1.510000] xhci_hcd 0000:00:01.0: xHCI Host Controller
<6>[ 1.510000] xhci_hcd 0000:00:01.0: new USB bus registered, assigned bus number 2
<6>[ 1.520000] xhci_hcd 0000:00:01.0: irq 9, io mem 0xe0000000
<4>[ 1.530000] usb usb2: config 1 interface 0 altsetting 0 endpoint 0x81 has no SuperSpeed companion descriptor
<6>[ 1.540000] usb usb2: configuration #1 chosen from 1 choice
<7>[ 1.540000] xHCI xhci_add_endpoint called for root hub
<7>[ 1.540000] xHCI xhci_check_bandwidth called for root hub
<6>[ 1.540000] hub 2-0:1.0: USB hub found
<6>[ 1.550000] hub 2-0:1.0: 4 ports detected
<6>[ 1.550000] Initializing USB Mass Storage driver...
<6>[ 1.550000] usbcore: registered new interface driver usb-storage
<6>[ 1.560000] USB Mass Storage support registered.
<6>[ 1.570000] usbcore: registered new interface driver ums-datafab
<6>[ 1.570000] usbcore: registered new interface driver ums-freecom
<6>[ 1.580000] usbcore: registered new interface driver ums-jumpshot
<6>[ 1.580000] usbcore: registered new interface driver ums-sddr09
<6>[ 1.590000] usbcore: registered new interface driver ums-sddr55
<6>[ 1.600000] usbcore: registered new interface driver ums-usbat
<6>[ 1.600000] mice: PS/2 mouse device common for all mice
<6>[ 1.610000] i2c /dev entries driver
<7>[ 1.610000] cpufreq: Setting CPU Frequency to 800000 KHz
<7>[ 1.610000] cpufreq: Setting PowerSaveState to off
<6>[ 1.620000] sdhci: Secure Digital Host Controller Interface driver
<6>[ 1.620000] sdhci: Copyright(c) Pierre Ossman
<5>[ 1.630000] mmc0: mvsdio driver initialized, using GPIO 27 for card detection
<6>[ 1.640000] usbcore: registered new interface driver usbhid
<6>[ 1.640000] usbhid: v2.6:USB HID core driver
<6>[ 1.650000] TCP cubic registered
<6>[ 1.650000] NET: Registered protocol family 17
<6>[ 1.660000] RPC: Registered udp transport module.
<6>[ 1.660000] RPC: Registered tcp transport module.
<4>[ 1.670000] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
<5>[ 1.740000] UBIFS: recovery needed
<5>[ 1.840000] UBIFS: recovery completed
<5>[ 1.850000] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
<5>[ 1.850000] UBIFS: file system size: 110850048 bytes (108252 KiB, 105 MiB, 873 LEBs)
<5>[ 1.860000] UBIFS: journal size: 9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
<5>[ 1.870000] UBIFS: media format: w4/r0 (latest is w4/r0)
<5>[ 1.870000] UBIFS: default compressor: lzo
<5>[ 1.880000] UBIFS: reserved for root: 0 bytes (0 KiB)
<4>[ 1.880000] VFS: Mounted root (ubifs filesystem) on device 0:11.
<6>[ 1.890000] Freeing init memory: 124K
<5>[ 4.260000] eth0: started
<4>[ 13.780000] IRQ 93 uses trigger mode 0; requested 3
<6>[ 13.790000] input: gpio-keys as /devices/platform/gpio-keys.0/input/input0
<6>[ 13.810000] xce_ebtn: Pogoplug series V4 eject button initialized.
<4>[ 13.950000] ufsd: module license 'Commercial product' taints kernel.
<4>[ 13.950000] Disabling lock debugging due to kernel taint
<5>[ 13.990000] ufsd: driver (8.6 (U86_S[2012-02-28-18:39:23]), LBD=ON, delalloc, ioctl) loaded at bf00c000
<5>[ 13.990000] NTFS support included
<5>[ 13.990000] Hfs+/HfsX support included
<5>[ 13.990000] For 'CloudEngines_PogoPlug_2011-08-03'
<4>[ 14.320000] rtusb init rt2870 --->
<6>[ 14.330000] usbcore: registered new interface driver rt2870
<4>[ 14.360000] Cloud Engines XCE Init [Version: 3.9.0.4]
<6>[ 14.360000] XCE: CPU MEMORY MAP:
<6>[ 14.360000] XCE: -- 0x00001000 - 0xbeffffff (3055 MB) User Space Mappings
<6>[ 14.370000] XCE: -- 0xbf000000 - 0xbfffffff ( 16 MB) Kernel module space
<6>[ 14.380000] XCE: -- 0xc0000000 - 0xc7ffffff ( 128 MB) Kernel direct-mapped ram
<6>[ 14.390000] XCE: -- 0xc8800000 - 0xe7ffffff ( 504 MB) Kernel vmalloc space
<6>[ 14.390000] XCE: -- 0xe8000000 - 0xfeffffff ( 367 MB) Kernel platform space
<6>[ 14.400000] XCE: CPU FEATURES:
<6>[ 14.400000] XCE: -- I Cache: enabled
<6>[ 14.410000] XCE: -- D Cache: enabled
<6>[ 14.410000] XCE: -- Branch Predict: disabled
<6>[ 14.420000] XCE: -- MMU: enabled
<6>[ 14.420000] XCE: -- Alignment Abort: enabled
<6>[ 14.430000] XCE: BLPARAMS: -- Loading properties [c4bebefc].
<6>[ 14.440000] XCE: BLPARAMS: -- MTD @ [c45c0c00].
<6>[ 14.440000] XCE: BLPARAMS: Locating parameter block...
<6>[ 14.450000] XCE: BLPARAMS: reading 2048 bytes @ a0000
<6>[ 14.450000] XCE: Loaded Property Size: 2048
<6>[ 14.460000] XCE: - 'ceboardver' -> 'PPV4A3'
<6>[ 14.460000] XCE: - 'cesvcid' -> 'ARK5H2NU65M8MQEQSXCRDTEN8E'
<6>[ 14.470000] XCE: -- ICache Prefetch: enabled
<6>[ 14.470000] XCE: -- DCache Prefetch: enabled
<6>[ 14.480000] XCE: -- L2 Cache: enabled
<6>[ 14.480000] XCE: -- L2 Prefetch: disabled
<6>[ 14.490000] XCE: -- L2 Writethrough: disabled
<6>[ 14.490000] XCE: -- Write Allocate: disabled
<6>[ 14.500000] XCE: -- Streaming: disabled
<6>[ 14.500000] XCE: Current GPIO State:
<6>[ 14.500000] XCE: GPIO L OUT: 0x01e18400
<6>[ 14.510000] XCE: GPIO L OE: 0xfe004800
<6>[ 14.510000] XCE: GPIO L BLINK: 0x00000000
<6>[ 14.520000] XCE: GPIO L POL: 0x28000000
<6>[ 14.520000] XCE: GPIO L IN: 0x11e00000
<6>[ 14.520000] XCE: GPIO H OUT: 0x00000008
<6>[ 14.530000] XCE: GPIO H OE: 0x00000005
<6>[ 14.530000] XCE: GPIO H BLINK: 0x00000000
<6>[ 14.540000] XCE: GPIO H POL: 0x00000000
<6>[ 14.540000] XCE: GPIO H IN: 0x00000008
<6>[ 14.720000] XCE: BLPARAMS: -- Loading properties [c4b73ecc].
<6>[ 14.730000] XCE: BLPARAMS: -- MTD @ [c45c0c00].
<6>[ 14.730000] XCE: BLPARAMS: Locating parameter block...
<6>[ 14.740000] XCE: BLPARAMS: reading 2048 bytes @ a0000
<6>[ 14.740000] XCE: BLPARAMS: reading 2048 bytes @ a0800
<6>[ 14.750000] XCE: BLPARAMS: reading 2048 bytes @ a1000
<6>[ 14.760000] XCE: BLPARAMS: reading 2048 bytes @ a1800
<6>[ 20.090000] XCE: XCE: LED -> DISCONNECTED
<5>[ 29.400000] eth0: link up, full duplex, speed 1 Gbps
<6>[ 145.630000] XCE: XCE: LED -> CONNECTED
<4>[ 209.420000] bad rx status 2f800841, (crc error)
<4>[ 215.270000] bad rx status 2f8602c9, (crc error)
<4>[ 279.500000] bad rx status 2cc7fff9, (crc error)
<4>[ 313.320000] bad rx status 6fa2cc61, (crc error)
<4>[ 416.810000] bad rx status 2f82d271, (crc error)
/ # [ 901.520000] bad rx status 2f841929, (crc error)
[ 905.690000] bad rx status 2f8548e1, (crc error)
[ 908.280000] bad rx status 2f872cf1, (crc error)
[ 909.210000] bad rx status 2f85d1f9, (crc error)
[ 920.880000] bad rx status 6f861529, (crc error)
[ 1082.100000] bad rx status 2fc2f1d9, (crc error)
[ 1128.690000] bad rx status 2cc7fff9, (crc error)
[ 1218.810000] bad rx status 2cc7fff9, (crc error)
[ 1227.660000] bad rx status 2fa16c39, (crc error)
[ 1298.610000] bad rx status 2cc7fff9, (crc error)


======================================================================================================

I tried 2014.7 u-boot kirkwood and have error info below:

~ # cat /etc/fw_env.config
cat: can't open '/etc/fw_env.config': No such file or directory
~ # cat /proc/mtd
dev: size erasesize name
mtd0: 00200000 00020000 "u-boot"
mtd1: 00300000 00020000 "uImage"
mtd2: 00300000 00020000 "uImage2"
mtd3: 00800000 00020000 "failsafe"
mtd4: 07000000 00020000 "root"


~ # fw_printenv
-sh: fw_printenv: not found

~ # blparam > current_envs.txt
-sh: blparam: not found

~ # dmesg | grep -i 'bad'
<6>[ 1.010000] Scanning device for bad blocks
<5>[ 1.370000] UBI: number of bad PEBs: 0
<5>[ 1.400000] UBI: number of PEBs reserved for bad PEB handling: 8
<4>[ 209.420000] bad rx status 2f800841, (crc error)
<4>[ 215.270000] bad rx status 2f8602c9, (crc error)

How can i use the command above?

Thanks~!

Best regards
Hello bodhi

I have posted dmesg above, plz give me help with your convinience. Thanks!
Re: Backup and Restore NAND mtds - Pogoplug V4 original MTD partitions
October 17, 2015 12:07AM
Ryan,

> ~ # blparam > current_envs.txt
> -sh: blparam: not found
>

You are running stock OS. So blparam is at /usr/local/cloudengines/bin/

/usr/local/cloudengines/bin/blparam > current_envs.txt

And you have no bad blocks. It is safe to flash new u-boot.

But serial console is highly recommended, if you can, connect it first.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Hello bodhi

I tried

but error below ( ls can see command blparam, but -sh: blparam: not found)

~ # cd /usr/local/cloudengines/bin
/usr/local/cloudengines/bin # blparam > current_envs.txt
-sh: blparam: not found
/usr/local/cloudengines/bin # ls
blparam e2fsck hbplug_init rt3070sta.ko xce.low.ffpreset
chkhfs ejectbutton.ko hbusbpr udhcpc_ra0_init xce.medium.ffpreset
chkntfs ffmpeg hbwd ufsd.ko xce.veryhigh.ffpreset
current_envs.txt gpio_keys.ko ntfs_3g xce.ffpreset
dcraw hbixc ppsync xce.high.ffpreset
dosfsck hbplug ppvseg xce.ko
/usr/local/cloudengines/bin #
hello bodhi

I think i had made mistake.
I have finished 2014.07 U-Boot Kirkwood(http://forum.doozan.com/read.php?3,12381)
instuction A and B. including flashing uboot.2014.07-tld-2.environment.bodhi.tar
and after reboot the green led flashing and resetting always, info below:

U-Boot 2014.07-tld-2 (Sep 19 2014 - 16:13:05)
Pogoplug V4

SoC: Kirkwood 88F6192_A1
DRAM: 128 MiB
WARNING: Caches not enabled
NAND: 128 MiB
MMC: kwsdio: 0
In: serial
Out: serial
Err: serial
Net: egiga0
Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found

Reset IDE: ide_preinit failed

no USB devices available

no IDE devices available
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
** Bad device mmc 0 **
** Bad device mmc 0 **
** Bad device mmc 0 **
ERROR: can't get kernel image!

Reset IDE: ide_preinit failed
** Bad device size - ide 0 **
** Bad device size - ide 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
resetting ...

and now what can i do? i wanna use my.pogoplug.com sevice and in my.pogoplug.com can see hdd driver.

Thanks~
Re: Backup and Restore NAND mtds - Pogoplug V4 original MTD partitions
October 17, 2015 05:17PM
Ryan Wrote:
-------------------------------------------------------
> hello bodhi
>
> I think i had made mistake.
> I have finished 2014.07 U-Boot
> Kirkwood(http://forum.doozan.com/read.php?3,12381)
>
> instuction A and B. including flashing
> uboot.2014.07-tld-2.environment.bodhi.tar
> and after reboot the green led flashing and
> resetting always, info below:
>
> U-Boot 2014.07-tld-2 (Sep 19 2014 - 16:13:05)
> Pogoplug V4
>
> SoC: Kirkwood 88F6192_A1
> DRAM: 128 MiB
> WARNING: Caches not enabled
> NAND: 128 MiB
> MMC: kwsdio: 0
> In: serial
> Out: serial
> Err: serial
> Net: egiga0
> Hit any key to stop autoboot: 0
> (Re)start USB...
> USB0: USB EHCI 1.00
> scanning bus 0 for devices... 1 USB Device(s)
> found
> scanning usb for storage devices... 0
> Storage Device(s) found
>
> Reset IDE: ide_preinit failed
>
> no USB devices available
>
> no IDE devices available
> (Re)start USB...
> USB0: USB EHCI 1.00
> scanning bus 0 for devices... 1 USB Device(s)
> found
> scanning usb for storage devices... 0
> Storage Device(s) found
> ** Bad device usb 0 **
> ** Bad device usb 0 **
> Wrong Image Format for bootm command
> ERROR: can't get kernel image!
> ** Bad device mmc 0 **
> ** Bad device mmc 0 **
> ** Bad device mmc 0 **
> ERROR: can't get kernel image!
>
> Reset IDE: ide_preinit failed
> ** Bad device size - ide 0 **
> ** Bad device size - ide 0 **
> Wrong Image Format for bootm command
> ERROR: can't get kernel image!
> resetting ...
>
> and now what can i do? i wanna use my.pogoplug.com
> sevice and in my.pogoplug.com can see hdd driver.
>
> Thanks~

Does booting with USB rootfs work Ok?

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Backup and Restore NAND mtds - Pogoplug V4 original MTD partitions
October 17, 2015 09:56PM
Ryan,

Let me see if I understood you correctly: the USB rootfs works fine, and now you are looking for a way to boot stock OS?

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Hello bodhi

First I registered the pogo on website my.pogoplug.com , and when i insert a HDD in SATA SLOT, i can't find the hdd disk in my.pogoplug.com, but usb disk is ok. so i thought it must be the firmware is mistake, so i want to reflash mtd0 . After flshing mtd0 of your original one , it still cannot find sata HDD in my.pogoplug.com. And so i upgrade the 2014.07 U-Boot . After that cannot boot correctly,green led flashing always.

I don't know how to boot usb rootfs, so i don't know whether it is fine.

I wanna boot stock OS and wanna find the HDD[ SATA SLOT] in my.pogoplug.com.

I am sorry that bothering you so much, but hope your help too.

thanks~!
Re: Backup and Restore NAND mtds - Pogoplug V4 original MTD partitions
October 18, 2015 12:24PM
Ryan,

The best way to boot stock and use pogoplug.com is to restore mtd0 using my backup. And you also need to adjust the cesvcid like I described in the first post. And reboot. After that if pogoplug.com finds your plug, then it should see the HDD.

BTW, are you also aware that pogoplug.com needs a paid subscription to use?

So the bottom line is if you want to use pogoplug.com , don't install new u-boot. There is a way to use new u-boot and boot stock OS, but it is not simple to set up.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
hello bodhi

Before I restore mtd0 in ssh, but now in TTL mode , the command seems that not effective.

can you help me the procedure to restore mtd0 in ttl mode?

thanks~!

================================================

ps: i use pogoplug.com because its apps in mobilephone is convinience for me.
Re: Backup and Restore NAND mtds - Pogoplug V4 original MTD partitions
October 18, 2015 10:20PM
Ryan Wrote:
-------------------------------------------------------
> hello bodhi
>
> Before I restore mtd0 in ssh, but now in TTL mode
> , the command seems that not effective.
>
> can you help me the procedure to restore mtd0 in
> ttl mode?
>
> thanks~!
>
> ================================================
>
> ps: i use pogoplug.com because its apps in
> mobilephone is convinience for me.

I would avoid restore mtd using serial console. So if you can do it in Linux, then it would be best.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
hi bodhi

now what methods can do it in linux? plz give me help

thanks
Re: Backup and Restore NAND mtds - Pogoplug V4 original MTD partitions
October 19, 2015 02:19AM
Ryan Wrote:
-------------------------------------------------------
> hi bodhi
>
> now what methods can do it in linux? plz give me
> help
>
> thanks

Step 2 and step 3 in the first post in the section

Quote

How to restore:

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner



Edited 1 time(s). Last edit at 10/19/2015 02:20AM by bodhi.
hi bodhi,

In my case, how i can get in linux ?

my pogo now cannot link via SSH. Is there another method?

thanks~
Re: Backup and Restore NAND mtds - Pogoplug V4 original MTD partitions
October 20, 2015 05:49PM
hi bodhi

after installing Debian rootfs on USB and boot from it on pogoV4, and error info below:

U-Boot 2014.07-tld-2 (Sep 19 2014 - 16:13:05)
Pogoplug V4

SoC: Kirkwood 88F6192_A1
DRAM: 128 MiB
WARNING: Caches not enabled
NAND: 128 MiB
MMC: kwsdio: 0
In: serial
Out: serial
Err: serial
Net: egiga0
Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found

Reset IDE: ide_preinit failed

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

Part Start Sector Num Sectors UUID Type
1 2048 3930112 00000000-01 83
loading envs from usb 0 ...
** File not found /boot/uEnv.txt **

no IDE devices available
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
EHCI timed out on TD - token=0x90008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x90008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
** ext4fs_devread read error - block
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
** Can't read partition table on 0:0 **
** Invalid partition 1 **
## 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 ... Bad Data CRC
ERROR: can't get kernel image!
** Bad device mmc 0 **
** Bad device mmc 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!

Reset IDE: ide_preinit failed
** Bad device size - ide 0 **
** Bad device size - ide 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
resetting ...

can you give me help which step be mistake?
Re: Backup and Restore NAND mtds - Pogoplug V4 original MTD partitions
October 28, 2015 11:23AM
Ryan

It seems your rootfs was not created correctly. Try following the instruction to create 3.16 rootfs again. You can post the entire log of how you do this here, perhaps you missed a certain step or some importan tinstruction?

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
hello bodhi

Procedure below:

1)I used ParagonPartitionManager V12 to make Ext3 partition in the USB DISK.

2) plug this usb disk into the front panel of POGO-E02.(with openwrt)

3) under win7 I run Xshell to connect a POGO-E02 with openwrt via SSH.

4) then entry the LINUX OPENWRT and use command in XSHELL:
cd /mnt/sdb1
tar -xjf Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar.bz2
it tell me error "j" is not optional.

so use "tar -xf Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar.bz2"
it tell me error "invalid tar magic"

5) because cannot tar the file. I extract it in win7 with WINRAR.

6) after extracting, I entry the folder /mnt/sdb1 via FTP.

7) upload the files extracted moment ago by FTP. after that I think I finish the USB disk installing.
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: