Welcome! Log In Create A New Profile

Advanced

OpenWrt on Pogoplug V03/Pro

Posted by shv 
shv
OpenWrt on Pogoplug V03/Pro
October 03, 2019 12:52PM
Hello,
I used the following guideline to install OpenWrt on PogoPlug Pro: Link.
The version 18.06.4 seams to work well. I didn't get the Wifi Interface working. SATA seams to be not supported.

The memory layout is defined as follows:
root@OpenWrt:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00040000 00020000 "stage1"
mtd1: 00380000 00020000 "u-boot"
mtd2: 00080000 00020000 "u-boot-env"
mtd3: 009c0000 00020000 "kernel"
mtd4: 07200000 00020000 "ubi"

@bodhi,
How can I access your uboot environment which is located at 00100000 with fw_printenv? It might be a bit dangerous that mtd1/mtd2 don't fit neither to your layout nor to original layout. Openwrt just overwrite kernel and ubi. The kernel is located at 00440000.



Edited 4 time(s). Last edit at 10/03/2019 01:28PM by shv.
Re: OpenWrt on Pogoplug V03/Pro
October 03, 2019 02:46PM
shv,

> I used the following guideline to install OpenWrt on PogoPlug Pro:
> Link.

The above installation method is not very good (looks old).

Better Installation method for the Pogo E02:
https://forum.doozan.com/read.php?4,42279

It should be similar for the Pogo V3 using my released u-boot and the OpenWRT images for the Pogo V3.

> @bodhi,
> How can I access your uboot environment which is
> located at 00100000 with fw_printenv? It might be
> a bit dangerous that mtd1/mtd2 don't fit neither
> to your layout nor to original layout. Openwrt
> just overwrite kernel and ubi. The kernel is
> located at 00440000.

Which u-boot is on your box?

And cat /proc/mtd does not show the layout well (you would have to calculate the offset).

This shows the addresses:
dmesg | grep -i7 "mtd partitions"

-bodhi
===========================
Forum Wiki
bodhi's corner
shv
Re: OpenWrt on Pogoplug V03/Pro
October 04, 2019 12:44AM
bodhi,

I have the following uboot on the Pogoplug Pro:

U-Boot 2013.10-tld-3 (May 15 2014 - 14:54:14) for OXNAS

I used the following steps for the installation of openwrt with the file openwrt-18.06.4-oxnas-ox820-cloudengines-pogoplug-pro-initramfs-uImage on USB stick:

1. stop boot, adapt bootcmd for openwrt: 'nboot 60500000 0 440000; bootm'
## load openwrt from USB-Stick @uboot
2. usb reset; fatload usb 0 64000000 openwrt-18.06.4-oxnas-ox820-cloudengines-pogoplug-pro-initramfs-uImage; bootm 64000000
3. cd /tmp; wget http://downloads.openwrt.org/releases/18.06.4/targets/oxnas/ox820/openwrt-18.06.4-oxnas-ox820-cloudengines-pogoplug-pro-squashfs-ubinized.bin
4. sysupgrade -F openwrt-18.06.4-oxnas-ox820-cloudengines-pogoplug-pro-squashfs-ubinized.bin
5. power cycle, stop boot
## load openwrt from USB-Stick @uboot
6. usb reset; fatload usb 0 64000000 openwrt-18.06.4-oxnas-ox820-cloudengines-pogoplug-pro-initramfs-uImage; bootm 64000000
7. cd /tmp; wget http://downloads.openwrt.org/releases/18.06.4/targets/oxnas/ox820/openwrt-18.06.4-oxnas-ox820-cloudengines-pogoplug-pro-squashfs-sysupgrade.tar
8. sysupgrade openwrt-18.06.4-oxnas-ox820-cloudengines-pogoplug-pro-squashfs-sysupgrade.tar
9. power cycle
10. uci set network.lan.macaddr='<macaddr>'; uci commit; service network restart
11. vi /etc/fw_env.config
/dev/mtd1 0xc0000 0x20000 0x20000

The command
dmesg | grep -i7 "mtd partitions"
doesn't work with openwrt.

I tried the following configuration in /etc/fw_env.config
/dev/mtd1 0xc0000 0x20000 0x20000
and fw_printenv works.

I get the following messages in the log:
[   14.209502] __nand_correct_data: uncorrectable ECC error
[   14.214832] __nand_correct_data: uncorrectable ECC error
[   14.220262] print_req_error: I/O error, dev mtdblock1, sector 2048
Can I resolve this problem somehow?



Edited 18 time(s). Last edit at 10/04/2019 01:12AM by shv.
Re: OpenWrt on Pogoplug V03/Pro
October 04, 2019 01:12AM
shv,

mtd0: 00040000 00020000 "stage1"
mtd1: 00380000 00020000 "u-boot"
mtd2: 00080000 00020000 "u-boot-env"
mtd3: 009c0000 00020000 "kernel"
mtd4: 07200000 00020000 "ubi"

The cat /proc/mtd above gave only a hint how it might work to have the envs location at 0xc0000 in mtd1. But they only show sizes, not location of mtds (mtd definitions can be out of order in term of location offset).

mtd0: 00040000 00020000 "stage1"
mtd2: 00080000 00020000 "u-boot-env"

00040000 + 00080000 = 0xc0000

/dev/mtd1 0xc0000 0x20000 0x20000

Can you post the entire OpenWrt dmesg here?

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: OpenWrt on Pogoplug V03/Pro
October 04, 2019 01:48AM
[   14.209502] __nand_correct_data: uncorrectable ECC error
[   14.214832] __nand_correct_data: uncorrectable ECC error
[   14.220262] print_req_error: I/O error, dev mtdblock1, sector 2048

This migh not be a problem, depending what is going on at that time.

For example, some commands need mtdblock capability to work, so if the kernel was not configured with mtdblock, you will get similar errors when it was accessed by something.

-bodhi
===========================
Forum Wiki
bodhi's corner
shv
Re: OpenWrt on Pogoplug V03/Pro
October 04, 2019 03:22AM
bodhi,

this is the dmesg output of openwrt@pogoplug pro

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.14.131 (buildbot@dbab1e23488d) (gcc version 7.3.0 (OpenWrt GCC 7.3.0 r7808-ef686b7292)) #0 SMP Thu Jun 27 12:18:52 2019
[    0.000000] CPU: ARMv6-compatible processor [410fb025] revision 5 (ARMv7), cr=00c5787d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: Cloud Engines PogoPlug Pro
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] cma: Reserved 64 MiB at 0x64000000
[    0.000000] On node 0 totalpages: 32768
[    0.000000] free_area_init_node: node 0, pgdat c08228e0, node_mem_map c3eda000
[    0.000000]   Normal zone: 256 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 32768 pages, LIFO batch:7
[    0.000000] random: get_random_bytes called from 0xc07008b4 with crng_init=0
[    0.000000] percpu: Embedded 15 pages/cpu s29100 r8192 d24148 u61440
[    0.000000] pcpu-alloc: s29100 r8192 d24148 u61440 alloc=15*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: earlyprintk console=ttyS0,115200
[    0.000000] Bootloader command line (ignored): console=ttyS0,115200 root=LABEL=rootfs-ide rootdelay=10 rootfstype=ext4 mtdparts=41000000.nand:14m(boot),-(data) ubi.mtd=2,512 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=128M poweroutage=yes rootwait
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Memory: 56552K/131072K available (5120K kernel code, 140K rwdata, 616K rodata, 1024K init, 209K bss, 8984K reserved, 65536K cma-reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xc8800000 - 0xff800000   ( 880 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc0600000   (6112 kB)
[    0.000000]       .init : 0xc0700000 - 0xc0800000   (1024 kB)
[    0.000000]       .data : 0xc0800000 - 0xc0823080   ( 141 kB)
[    0.000000]        .bss : 0xc0826710 - 0xc085aca8   ( 210 kB)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] 	RCU event tracing is enabled.
[    0.000000] 	RCU restricting CPUs from NR_CPUS=16 to nr_cpu_ids=2.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] FPGA IRQ chip 0 "interrupt-controller" @ c8804000, 32 irqs, parent IRQ: 16
[    0.000017] sched_clock: 24 bits at 390kHz, resolution 2560ns, wraps every 21474835200ns
[    0.000046] clocksource: oxnas_rps_clocksource_timer: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 19112603332 ns
[    0.000058] timer_oxnas_rps: Registered clocksource rate 390625Hz
[    0.000079] timer_oxnas_rps: Registered clock event rate 6250000Hz prescaler 0 period 62500
[    0.000222] GIC: PPI13 is secure or misconfigured
[    0.000268] GIC: PPI13 is secure or misconfigured
[    0.000448] Console: colour dummy device 80x30
[    0.000496] Calibrating delay loop... 339.14 BogoMIPS (lpj=1695744)
[    0.050357] pid_max: default: 32768 minimum: 301
[    0.050526] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.050549] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.051274] CPU: Testing write buffer coherency: ok
[    0.052418] Setting up static identity map for 0x60100000 - 0x6010005c
[    0.052628] Hierarchical SRCU implementation.
[    0.053404] smp: Bringing up secondary CPUs ...
[    0.054190] GIC: PPI13 is secure or misconfigured
[    0.110563] smp: Brought up 1 node, 2 CPUs
[    0.110594] SMP: Total of 2 processors activated (678.29 BogoMIPS).
[    0.114790] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.114821] futex hash table entries: 512 (order: 2, 16384 bytes)
[    0.119564] pinctrl core: initialized pinctrl subsystem
[    0.120171] NET: Registered protocol family 16
[    0.123909] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.126274] cpuidle: using governor menu
[    0.126376] No ATAGs?
[    0.137843] oxnas-pcie soc:apb-bridge@47000000:pcie-controller@c00000: probe deferral not supported
[    0.138234] pps_core: LinuxPPS API ver. 1 registered
[    0.138250] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.138278] PTP clock support registered
[    0.139133] clocksource: Switched to clocksource oxnas_rps_clocksource_timer
[    0.146291] NET: Registered protocol family 2
[    0.147100] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.147141] TCP bind hash table entries: 1024 (order: 1, 8192 bytes)
[    0.147174] TCP: Hash tables configured (established 1024 bind 1024)
[    0.147315] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.147361] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.147609] NET: Registered protocol family 1
[    0.147658] PCI: CLS 0 bytes, default 32
[    0.148974] No memory allocated for crashlog
[    0.149312] workingset: timestamp_bits=30 max_order=15 bucket_order=0
[    0.155345] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.158635] io scheduler noop registered
[    0.158656] io scheduler deadline registered
[    0.158878] io scheduler cfq registered (default)
[    0.204037] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[    0.208276] console [ttyS0] disabled
[    0.208394] 44200000.serial: ttyS0 at MMIO 0x44200000 (irq = 55, base_baud = 390625) is a 16550A
[    0.702195] console [ttyS0] enabled
[    0.719027] brd: module loaded
[    0.730045] loop: module loaded
[    0.799426] nand: Could not find valid ONFI parameter page; aborting
[    0.805762] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1
[    0.812129] nand: Hynix NAND 128MiB 3,3V 8-bit
[    0.816552] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    0.824130] Scanning device for bad blocks
[    0.909376] 5 fixed-partitions partitions found on MTD device 41000000.nand-controller
[    0.917258] Creating 5 MTD partitions on "41000000.nand-controller":
[    0.923617] 0x000000000000-0x000000040000 : "stage1"
[    0.929699] 0x000000040000-0x0000003c0000 : "u-boot"
[    0.935654] 0x0000003c0000-0x000000440000 : "u-boot-env"
[    0.942036] 0x000000440000-0x000000e00000 : "kernel"
[    0.948026] 0x000000e00000-0x000008000000 : "ubi"
[    0.954887] libphy: Fixed MDIO Bus: probed
[    0.959677] oxnas-dwmac 40400000.ethernet: PTP uses main clock
[    0.965498] oxnas-dwmac 40400000.ethernet: no reset control found
[    1.039211] stmmac - user ID: 0x12, Synopsys ID: 0x35
[    1.044254] oxnas-dwmac 40400000.ethernet: Ring mode enabled
[    1.049940] oxnas-dwmac 40400000.ethernet: DMA HW capability register supported
[    1.057221] oxnas-dwmac 40400000.ethernet: Enhanced/Alternate descriptors
[    1.064005] oxnas-dwmac 40400000.ethernet: Enabled extended descriptors
[    1.070617] oxnas-dwmac 40400000.ethernet: RX Checksum Offload Engine supported
[    1.077895] oxnas-dwmac 40400000.ethernet: COE Type 2
[    1.082949] oxnas-dwmac 40400000.ethernet: TX Checksum insertion supported
[    1.089822] oxnas-dwmac 40400000.ethernet: Wake-Up On Lan supported
[    1.096122] oxnas-dwmac 40400000.ethernet (unnamed net_device) (uninitialized): device MAC address 1e:7e:32:1b:88:62
[    1.106634] oxnas-dwmac 40400000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[    1.123837] libphy: stmmac: probed
[    1.127242] RTL8211DN Gigabit Ethernet stmmac-0:00: attached PHY driver [RTL8211DN Gigabit Ethernet] (mii_bus:phy_addr=stmmac-0:00, irq=POLL)
[    1.139944] RTL8211DN Gigabit Ethernet stmmac-0:03: attached PHY driver [RTL8211DN Gigabit Ethernet] (mii_bus:phy_addr=stmmac-0:03, irq=POLL)
[    1.154621] ledtrig-cpu: registered to indicate activity on CPUs
[    1.160791] hidraw: raw HID events driver (C) Jiri Kosina
[    1.167367] NET: Registered protocol family 10
[    1.173373] Segment Routing with IPv6
[    1.177100] NET: Registered protocol family 17
[    1.181706] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    1.197757] UBI: auto-attach mtd4
[    1.201144] ubi0: attaching mtd4
[    1.327293] ubi0: scanning is finished
[    1.340008] ubi0: attached mtd4 (name "ubi", size 114 MiB)
[    1.345479] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
[    1.352360] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
[    1.359029] ubi0: VID header offset: 512 (aligned 512), data offset: 2048
[    1.365816] ubi0: good PEBs: 912, bad PEBs: 0, corrupted PEBs: 0
[    1.371824] ubi0: user volume: 2, internal volumes: 1, max. volumes count: 128
[    1.379013] ubi0: max/mean erase counter: 10/5, WL threshold: 4096, image sequence number: 1520423943
[    1.388229] ubi0: available PEBs: 0, total reserved PEBs: 912, PEBs reserved for bad PEB handling: 20
[    1.397478] ubi0: background thread "ubi_bgt0d" started, PID 43
[    1.398663] block ubiblock0_0: created from ubi0:0(rootfs)
[    1.408921] ubiblock: device ubiblock0_0 (rootfs) set to be root filesystem
[    1.415887] hctosys: unable to open rtc device (rtc0)
[    1.426503] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.
[    1.435463] Freeing unused kernel memory: 1024K
[    1.826969] init: Console is alive
[    2.077432] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[    2.149404] usbcore: registered new interface driver usbfs
[    2.154931] usbcore: registered new interface driver hub
[    2.160404] usbcore: registered new device driver usb
[    2.166348] Button Hotplug driver version 0.4.1
[    2.172633] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.180157] ehci-platform: EHCI generic platform driver
[    2.389176] oxnas-ehci 40200100.ehci: EHCI Host Controller
[    2.394695] oxnas-ehci 40200100.ehci: new USB bus registered, assigned bus number 1
[    2.402846] oxnas-ehci 40200100.ehci: irq 52, io mem 0x40200100
[    2.429176] oxnas-ehci 40200100.ehci: USB 2.0 started, EHCI 1.00
[    2.436185] hub 1-0:1.0: USB hub found
[    2.440074] hub 1-0:1.0: 2 ports detected
[    2.446912] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[    2.462699] init: - preinit -
[    2.869217] usb 1-1: new high-speed USB device number 2 using oxnas-ehci
[    2.968222] random: jshn: uninitialized urandom read (4 bytes read)
[    3.016217] random: jshn: uninitialized urandom read (4 bytes read)
[    3.057722] random: jshn: uninitialized urandom read (4 bytes read)
[    3.092249] hub 1-1:1.0: USB hub found
[    3.096407] hub 1-1:1.0: 4 ports detected
[    3.178344] RTL8211DN Gigabit Ethernet stmmac-0:00: attached PHY driver [RTL8211DN Gigabit Ethernet] (mii_bus:phy_addr=stmmac-0:00, irq=POLL)
[    3.195274] oxnas-dwmac 40400000.ethernet eth0: IEEE 1588-2008 Advanced Timestamp supported
[    3.203886] oxnas-dwmac 40400000.ethernet eth0: registered PTP clock
[    3.212001] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    4.250096] oxnas-dwmac 40400000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[    4.258368] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    6.480878] mount_root: loading kmods from internal overlay
[    6.501957] kmodloader: loading kernel modules from //etc/modules-boot.d/*
[    6.510305] kmodloader: done loading kernel modules from //etc/modules-boot.d/*
[    6.749504] __nand_correct_data: uncorrectable ECC error
[    6.754800] __nand_correct_data: uncorrectable ECC error
[    6.760158] print_req_error: I/O error, dev mtdblock1, sector 2048
[    6.766548] __nand_correct_data: uncorrectable ECC error
[    6.771921] __nand_correct_data: uncorrectable ECC error
[    6.777223] print_req_error: I/O error, dev mtdblock1, sector 2048
[    6.783377] Buffer I/O error on dev mtdblock1, logical block 256, async page read
[    6.898695] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 110
[    6.932817] UBIFS (ubi0:1): recovery needed
[    7.057154] UBIFS (ubi0:1): recovery completed
[    7.062410] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data"
[    7.070254] UBIFS (ubi0:1): LEB size: 129024 bytes (126 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    7.080153] UBIFS (ubi0:1): FS size: 110960640 bytes (105 MiB, 860 LEBs), journal size 5548032 bytes (5 MiB, 43 LEBs)
[    7.090741] UBIFS (ubi0:1): reserved for root: 4952683 bytes (4836 KiB)
[    7.097331] UBIFS (ubi0:1): media format: w4/r0 (latest is w5/r0), UUID 935F5BF6-BA1D-40BF-BA39-387DEBA2DCBC, small LPT model
[    7.109299] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab
[    7.118425] block: extroot: not configured
[    7.169356] UBIFS (ubi0:1): un-mount UBI device 0
[    7.174087] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" stops
[    7.185792] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 111
[    7.257963] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data"
[    7.265807] UBIFS (ubi0:1): LEB size: 129024 bytes (126 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    7.275704] UBIFS (ubi0:1): FS size: 110960640 bytes (105 MiB, 860 LEBs), journal size 5548032 bytes (5 MiB, 43 LEBs)
[    7.286284] UBIFS (ubi0:1): reserved for root: 4952683 bytes (4836 KiB)
[    7.292907] UBIFS (ubi0:1): media format: w4/r0 (latest is w5/r0), UUID 935F5BF6-BA1D-40BF-BA39-387DEBA2DCBC, small LPT model
[    7.305669] mount_root: loading kmods from internal overlay
[    7.348088] kmodloader: loading kernel modules from /tmp/overlay/upper/etc/modules-boot.d/*
[    7.474216] SCSI subsystem initialized
[    7.492193] usbcore: registered new interface driver usb-storage
[    7.499983] usbcore: registered new interface driver uas
[    7.505479] kmodloader: done loading kernel modules from /tmp/overlay/upper/etc/modules-boot.d/*
[    7.581570] __nand_correct_data: uncorrectable ECC error
[    7.586867] __nand_correct_data: uncorrectable ECC error
[    7.592220] print_req_error: I/O error, dev mtdblock1, sector 2048
[    7.598607] __nand_correct_data: uncorrectable ECC error
[    7.603962] __nand_correct_data: uncorrectable ECC error
[    7.609315] print_req_error: I/O error, dev mtdblock1, sector 2048
[    7.615472] Buffer I/O error on dev mtdblock1, logical block 256, async page read
[    7.728783] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab
[    7.737318] block: extroot: not configured
[    7.780528] mount_root: switching to ubifs overlay
[    7.803179] urandom-seed: Seeding with /etc/urandom.seed
[    7.903887] procd: - early -
[    8.760455] procd: - ubus -
[    8.808727] urandom_read: 3 callbacks suppressed
[    8.808742] random: ubusd: uninitialized urandom read (4 bytes read)
[    8.821386] random: ubusd: uninitialized urandom read (4 bytes read)
[    8.927813] random: ubusd: uninitialized urandom read (4 bytes read)
[    8.936225] procd: - init -
[    9.290065] kmodloader: loading kernel modules from /etc/modules.d/*
[    9.320791] nf_conntrack version 0.5.0 (2048 buckets, 8192 max)
[    9.372441] xt_time: kernel timezone is -0000
[    9.378759] ip_tables: (C) 2000-2006 Netfilter Core Team
[    9.392166] kmodloader: done loading kernel modules from /etc/modules.d/*
[   13.148108] __nand_correct_data: uncorrectable ECC error
[   13.153546] __nand_correct_data: uncorrectable ECC error
[   13.158886] print_req_error: I/O error, dev mtdblock1, sector 2048
[   13.179389] __nand_correct_data: uncorrectable ECC error
[   13.184696] __nand_correct_data: uncorrectable ECC error
[   13.190105] print_req_error: I/O error, dev mtdblock1, sector 2048
[   13.196272] Buffer I/O error on dev mtdblock1, logical block 256, async page read
[   13.232325] RTL8211DN Gigabit Ethernet stmmac-0:00: attached PHY driver [RTL8211DN Gigabit Ethernet] (mii_bus:phy_addr=stmmac-0:00, irq=POLL)
[   13.267479] oxnas-dwmac 40400000.ethernet eth0: IEEE 1588-2008 Advanced Timestamp supported
[   13.276157] oxnas-dwmac 40400000.ethernet eth0: registered PTP clock
[   13.293964] br-lan: port 1(eth0) entered blocking state
[   13.299310] br-lan: port 1(eth0) entered disabled state
[   13.304926] device eth0 entered promiscuous mode
[   13.339829] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
[   16.410088] oxnas-dwmac 40400000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[   16.418360] br-lan: port 1(eth0) entered blocking state
[   16.423636] br-lan: port 1(eth0) entered forwarding state
[   16.429644] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[   79.418759] random: fast init done
[  366.759280] usb 1-1.4: new high-speed USB device number 3 using oxnas-ehci
[  366.920284] usb-storage 1-1.4:1.0: USB Mass Storage device detected
[  366.927531] scsi host0: usb-storage 1-1.4:1.0
[  368.084766] scsi 0:0:0:0: Direct-Access     Kingston DataTraveler G3  PMAP PQ: 0 ANSI: 0 CCS
[  368.792212] sd 0:0:0:0: [sda] 15495168 512-byte logical blocks: (7.93 GB/7.39 GiB)
[  368.803571] sd 0:0:0:0: [sda] Write Protect is off
[  368.808353] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
[  368.812080] sd 0:0:0:0: [sda] No Caching mode page found
[  368.817379] sd 0:0:0:0: [sda] Assuming drive cache: write through
[  368.876597] random: crng init done
[  368.880043] random: 1 urandom warning(s) missed due to ratelimiting
[  368.886443]  sda: sda1
[  368.900098] sd 0:0:0:0: [sda] Attached SCSI removable disk
[  412.466375] usb 1-1.4: USB disconnect, device number 3
[  456.239101] usb 1-1.4: new high-speed USB device number 4 using oxnas-ehci
[  456.400010] usb-storage 1-1.4:1.0: USB Mass Storage device detected
[  456.406871] scsi host0: usb-storage 1-1.4:1.0
[  457.524139] scsi 0:0:0:0: Direct-Access     Kingston DataTraveler G3  PMAP PQ: 0 ANSI: 0 CCS
[  458.220224] sd 0:0:0:0: [sda] 15495168 512-byte logical blocks: (7.93 GB/7.39 GiB)
[  458.231590] sd 0:0:0:0: [sda] Write Protect is off
[  458.236385] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
[  458.240217] sd 0:0:0:0: [sda] No Caching mode page found
[  458.245527] sd 0:0:0:0: [sda] Assuming drive cache: write through
[  458.304261]  sda: sda1
[  458.317969] sd 0:0:0:0: [sda] Attached SCSI removable disk
[  509.595253] usb 1-1.4: USB disconnect, device number 4
Re: OpenWrt on Pogoplug V03/Pro
October 04, 2019 03:53AM
shv,

[    0.909376] 5 fixed-partitions partitions found on MTD device 41000000.nand-controller
[    0.917258] Creating 5 MTD partitions on "41000000.nand-controller":
[    0.923617] 0x000000000000-0x000000040000 : "stage1"
[    0.929699] 0x000000040000-0x0000003c0000 : "u-boot"
[    0.935654] 0x0000003c0000-0x000000440000 : "u-boot-env"
[    0.942036] 0x000000440000-0x000000e00000 : "kernel"
[    0.948026] 0x000000e00000-0x000008000000 : "ubi"


So the mtds definition in this OpenWRT kernel is from the DTB, not bootargs (bootargs is what we usually run this u-boot with Debian kernel that I released).

And mtd2 is where u-boot env is (not mtd1).

[    0.935654] 0x0000003c0000-0x000000440000 : "u-boot-env"

Your /etc/fw_env.config should be properly specified as mtd2, at location 0, size 512K, sector size 128K.

/dev/mtd2 0x0 00080000 0x20000

Try this and see if your error about mtdbock1 still shows in dmesg.

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 1 time(s). Last edit at 10/04/2019 03:54AM by bodhi.
shv
Re: OpenWrt on Pogoplug V03/Pro
October 04, 2019 04:31AM
bodi,
with the recommended change I get an error using fw_printenv. The ecc error about mtdblock1 still occur.
root@OpenWrt:/# fw_printenv
Warning: Bad CRC, using default environment
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootdelay=5
baudrate=115200

My understanding is that fw_printenv shall access the uboot environment and this is located at 100000. This address is part of mtd1 address space. Therefore I use mtd1 with the offset 0c0000.

The definition of uboot in dtb is much bigger than your uboot is. The address space contains your uboot, your uboot environment and part of the original kernel.



Edited 1 time(s). Last edit at 10/04/2019 04:39AM by shv.
Re: OpenWrt on Pogoplug V03/Pro
October 04, 2019 04:50AM
shv,

Quote

> with the recommended change I get an error using
> fw_printenv.

Of course, you're right :) I forgot that the OpenWrt definition is irrelevant since you are running my u-boot build. Even though it has something in there, it is not usable.

[    0.935654] 0x0000003c0000-0x000000440000 : "u-boot-env"


Quote

> My understanding is that fw_printenv shall access
> the uboot environment and this is located at
> 100000.

Yes. That's where I defined it. So we're back to to that definition!

Quote

The definition of uboot in dtb is much bigger than your uboot is. The address space contains your uboot, your uboot environment and part of the original kernel.

Don't worry about that. This is the correct definition.

cat /etc/fw_env.config 
# pogoplug v3
  /dev/mtd0               0x00100000      0x20000         0x20000

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: OpenWrt on Pogoplug V03/Pro
October 04, 2019 04:55AM
shv,

Get the u-boot envs corrected, and then we'll examine that ECC error.


I think the way OpenWrt DTB defined the MTDs is causing problem.

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 1 time(s). Last edit at 10/04/2019 05:07AM by bodhi.
shv
Re: OpenWrt on Pogoplug V03/Pro
October 04, 2019 06:21AM
bodhi,

with
/dev/mtd0 0x00100000 0x20000 0x20000
I get
root@OpenWrt:/# fw_printenv
Cannot read bad block mark: Invalid argument
I think the right solution is
/dev/mtd1 0xc0000 0x20000 0x20000
fw_printenv works with that.
root@OpenWrt:/# fw_printenv
autoload=no
baudrate=115200
boot=bootm 60500000
boot_stock=run load_nand boot || run load_nand2 boot
bootargs=console=ttyS0,115200n8
bootcmd=usb start; run usb_bootcmd; usb stop; ide reset; run ide_bootcmd; run bootcmd_openwrt; reset
bootcmd_openwrt=nboot 60500000 0 440000; bootm
...



Edited 4 time(s). Last edit at 10/04/2019 06:30AM by shv.
Re: OpenWrt on Pogoplug V03/Pro
October 04, 2019 06:50AM
shv,

The embedded OpenWRT DTB is definitely causing problem. Even though that location is a work around, it is not a complete solution.

I need to think about this a bit.

-bodhi
===========================
Forum Wiki
bodhi's corner
shv
Re: OpenWrt on Pogoplug V03/Pro
October 04, 2019 08:21AM
bodhi,

can the dtb also be responsible that SATA, PCI and Wifi card don't work?
Re: OpenWrt on Pogoplug V03/Pro
October 04, 2019 05:37PM
shv,

> can the dtb also be responsible that SATA, PCI and
> Wifi card don't work?

Most likely yes. But let me take a look at dmesg again to check.

This OpenWRT images seem to be different from the Kirkwood ones.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: OpenWrt on Pogoplug V03/Pro
October 04, 2019 11:52PM
shv,

Looks like this OpenWrt DTB is for the Pogo V3 Classic, not the Pro version. That's what dmesg seems to say (no PCI enumeration). So no Wifi.

[    0.137843] oxnas-pcie soc:apb-bridge@47000000:pcie-controller@c00000: probe deferral not supported

Either that, or the DTB is correct and your box is a Classic, not Pro. Do you have the Pogo V3 Pro box?

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 1 time(s). Last edit at 10/04/2019 11:53PM by bodhi.
shv
Re: OpenWrt on Pogoplug V03/Pro
October 05, 2019 12:58PM
bodhi,

my device is a Pogoplug Pro with RaLink 3390 PCI Wifi card. I compared the kernel files from https://downloads.openwrt.org/releases/18.06.4/targets/oxnas/ox820/ (Pro: cloudengines-pogoplug-pro-squashfs-sysupgrade.tar, V3: cloudengines-pogoplug-series-3-squashfs-sysupgrade.tar). The kernel files are different and the file for Pro contains the string Cloud Engines PogoPlug Pro while the kernel file for V3 contains Cloud Engines PogoPlug Series 3.

-shv
Re: OpenWrt on Pogoplug V03/Pro
October 05, 2019 06:51PM
shv,

This is very suspicious:

[    6.480878] mount_root: loading kmods from internal overlay
[    6.501957] kmodloader: loading kernel modules from //etc/modules-boot.d/*
[    6.510305] kmodloader: done loading kernel modules from //etc/modules-boot.d/*
[    6.749504] __nand_correct_data: uncorrectable ECC error
[    6.754800] __nand_correct_data: uncorrectable ECC error
[    6.760158] print_req_error: I/O error, dev mtdblock1, sector 2048
[    6.766548] __nand_correct_data: uncorrectable ECC error
[    6.771921] __nand_correct_data: uncorrectable ECC error
[    6.777223] print_req_error: I/O error, dev mtdblock1, sector 2048

The way OpenWrt defined the mtds, and the log above, there seems to be an overlay to the empty area after u-boot image and before u-boot-env (this area is in mtd1). This is possibly where they store the modules that needed to be loaded.

I am not familiar with the internals of their installation procedure. So I am not sure how that overlay setup was done. I think it must have been this:

4. sysupgrade -F openwrt-18.06.4-oxnas-ox820-cloudengines-pogoplug-pro-squashfs-ubinized.bin

At this point,

1. On the very slim chance that it could be used erroneously, remove the mtdparts from bootargs. It is not used in OpenWrt kernel anyway:

Quote

[ 0.000000] Bootloader command line (ignored): console=ttyS0,115200 root=LABEL=rootfs-ide rootdelay=10 rootfstype=ext4 mtdparts=41000000.nand:14m(boot),-(data) ubi.mtd=2,512 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=128M poweroutage=yes rootwait


2. If 1 does not help, perhaps you should try their u-boot to see if you still have the same problem.

-bodhi
===========================
Forum Wiki
bodhi's corner
shv
Re: OpenWrt on Pogoplug V03/Pro
October 06, 2019 06:36AM
bodhi,

the directory /etc/modules-boot.d contains just links to files which are stroed in the directory /etc/modules.d. There are text files which conain names or kernel modules which shall be loaded. The kernel modules are located in /lib/modules/4.14.131/<name>.ko.

I will try to remove the definition of mtdparts.

They are using no special/own u-boot but the original u-boot from cloudsystem. They want to prevent to destroy the box while exchanging the u-boot. I think that the memory map is defined to support different devices independent of their memory map.

At which addresses is sector 2048 located in mtdblock1?

I found the following description about the different Openwrt files:

The oxnas images for Lede seem to have a rather large (6) number of images for each target. I've written my conjectures about what each does. Let me know if I get any wrong?
u-boot-initramfs: Used for "live-booting" into a LEDE environment from uBoot. Includes the second-stage uboot, kernel, and a root filesystem.
uImage: The uboot-wrapped kernel. Can be booted from the second-stage uBoot using the bootm command. Included in the other images.
squashfs-ubinized.bin and ubifs-ubinized.bin: Images containing the kernel uImage, either a squashfs or ubifs root filesystem, and (possibly?) the second-stage bootloader. Using these, one can flash a device by halting at the second stage bootloader and using uboot to write to NAND directly.
squashfs-sysupgrade.tar and ubifs-sysupgrade.tar: Sysupgrade images. Can be used to flash the device using the method described above.
Choice of squashfs or ubifs: The squashfs images are used to create a device with a flash layout similar to the one described here 1. In this layout there are two filesystems: read-only squashfs, and (initially empty) read-write ubifs. The two are combined to form the root filesystem using overlayfs.
The ubifs images are used to create a single, read-write ubifs root filesystem.
Trade-offs: squashfs is smaller and potentially longer-lasting on a NAND device, as long as one doesn't plan on writing to it too often. ubifs allows one the option of making many small changes to the root filesystem directly at the cost of being a bit larger and potentially shorter-lasting on a NAND device.

https://forum.openwrt.org/t/lede-on-pogoplug-pro-bad-magic-number/10340/13

-shv



Edited 2 time(s). Last edit at 10/06/2019 09:34AM by shv.
Re: OpenWrt on Pogoplug V03/Pro
October 06, 2019 05:45PM
shv,

Quote

They are using no special/own u-boot but the original u-boot from cloudsystem. They want to prevent to destroy the box while exchanging the u-boot. I think that the memory map is defined to support different devices independent of their memory map.

OK. So that was a first thing that made the installation cumbersome. If they had used my version (or kref's original version) of u-boot, it would have been much better.

I would use UBIFS only. That's how we can make installation easy. And if we worry about NAND, then we would add an overlay directory on top of it.

-bodhi
===========================
Forum Wiki
bodhi's corner
shv
Re: OpenWrt on Pogoplug V03/Pro
October 10, 2019 09:41AM
bodhi,

if I use a current snapshot initramfs PCI and networkinterface seam to work.
root@OpenWrt:/# dmesg|grep pci
[    1.571965] oxnas-pcie 47c00000.pcie-controller: PCIe version/deviceID 0x82510b5
[    1.579435] oxnas-pcie 47c00000.pcie-controller: link up
[    1.585080] oxnas-pcie 47c00000.pcie-controller: PCI host bridge to bus 0000:00
[    1.592422] pci_bus 0000:00: root bus resource [mem 0x48000000-0x49ffffff]
[    1.599267] pci_bus 0000:00: root bus resource [mem 0x4a000000-0x4bdfffff pref]
[    1.606576] pci_bus 0000:00: root bus resource [io  0x0000-0xfffff]
[    1.612846] pci_bus 0000:00: root bus resource [bus 00-7f]
[    1.618344] pci 0000:00:00.0: [1814:3090] type 00 class 0x028000
[    1.618396] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x0000ffff]
[    1.624407] pci 0000:00:00.0: BAR 0: assigned [mem 0x48000000-0x4800ffff]

root@OpenWrt:/# lspci
00:00.0 Network controller: Ralink corp. RT3090 Wireless 802.11n 1T/1R PCIe
Nevertheless the ECC error still occurs and SATA isn't available. It might be OK as rescue system.

-shv



Edited 2 time(s). Last edit at 10/10/2019 12:22PM by shv.
Re: OpenWrt on Pogoplug V03/Pro
October 10, 2019 05:02PM
shv,

> Nevertheless the ECC error still occurs and SATA
> isn't available. It might be OK as rescue system.
>

May be not, if you need to repair the SATA drive while inside the rescue system. If this installation is limited by that, then you might as well use stock OS as rescue system:

https://forum.doozan.com/read.php?4,22570

I have not seen the source code they build this image from, but I guess we need to look at the DTB to see if SATA is activated and go from there.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: OpenWrt on Pogoplug V03/Pro
October 10, 2019 05:05PM
Quote

They want to prevent to destroy the box while exchanging the u-boot.

Going back to this quote. I think it is not a good decision. We can't brick this box.

-bodhi
===========================
Forum Wiki
bodhi's corner
shv
Re: OpenWrt on Pogoplug V03/Pro
October 11, 2019 07:13AM
bodhi,
there is one defined maintainer of ox820 Openwrt code. I tried to contact him but didn't get an answer yet.
I was already using stock OS as rescue system but wanted to see something new.
If I need to rescue the SATA drive I would use another Linux system. Moreover I would need to restore kernel and rootfs in the flash.

-shv



Edited 1 time(s). Last edit at 10/12/2019 12:56AM by shv.
Re: OpenWrt on Pogoplug V03/Pro
October 11, 2019 04:58PM
shv,

> If I need to rescue the SATA drive I would use
> another Linux system.

Not convenient if you have the Pogo running remotely, or if you have the SATA drive inside the case.

-bodhi
===========================
Forum Wiki
bodhi's corner
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: