Linux Device Hacking - Rescue System

Router witch Openwrt and BCM6756 transfer to other Router (9 replies)

Quantummaster — Wed, 19 Nov 2025 16:45:42 -0600

Hello,
can you help me please.
i have a Router with Openwrt and BCM6756 and it run well.
Yes i know this is very special.
I call it Router A.

2x Router B the little brother of Router A:
I flash the Image from Router A to Router B.
Router B start the bootloader dont load the image from Nand.
And no Network and no usb
After i change the Boardid i have Network Access and usb
But i chacnge it the Bootloader to test say: Need Hard Reset. I think one die.

I have SSH and Serial Access to Router A and B.
I have MTD and Nanddump with openwrt from Router A.

Can you Help me please:
Plan 1: Router B bootloader and Router A Openwrt.
Plan 2: Router B boot from Nanddump?
Plan 3: I write the mtd (only image mtd) from Router A to Router B?
Plan 4: Usb boot Router B with Nanddump from router A.

Thankyou :-)

Bricked stora ms2100 -- need help (35 replies)

tiaderosa — Fri, 26 Dec 2025 00:22:02 -0600

Hi,
forgive me if I'm not very precise as I'm newbee in Uboot and embedded linux
My STORA with stock FW had broblem lately with flashing blu led and no connection. I've setup a serial connection to check what was wrong. I got NAND error PEB & LEB that prevented the UBIFS to be mounted to set and load /newroot. I got access to basic Linux system through serial connection in putty.

I then tried to boot from usb following the indication found in "https://github.com/evgkirov/stora-debian-install"; and I have modified the uboot env variables accordingly.

The new booting process started ok but ended with a crc error. Below the log I got.

__  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_ 
| | | |___|  _ \ / _ \ / _ \| __| 
| |_| |___| |_) | (_) | (_) | |_ 
 \___/    |____/ \___/ \___/ \__| 
 ** MARVELL BOARD: RD-88F6281A LE 

U-Boot 1.1.4 (Sep  4 2009 - 09:36:11) Marvell version: 3.4.14

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CEE60

Soc: 88F6281 A0 (DDR2)
CPU running @ 1000Mhz L2 running @ 333Mhz
SysClock = 333Mhz , TClock = 200Mhz 

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size  64MB 
DRAM CS[1] base 0x04000000   size  64MB 
DRAM Total size 128MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:256 MB
CRC in Flash: 0fa09806, Calculated CRC: 0fa09806

CPU : Marvell Feroceon (Rev 1)

Streaming disabled 
Write allocate disabled

Module 0 is RGMII
Module 1 is TDM

USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0, egiga1 [PRIME]
Hit any key to stop autoboot:  3 ??? 2 ??? 1 ??? 0 
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
.
....
......
............
.
........................
.
.........................
........................
.
.........................
.........................
.........................
.......

1927896 bytes read
.
.
...
......
............
.
........................
.
.........................
........................
.
.........................
.........................
.........................
........................
.
.........................
.........................
.........................
.........................
.........................
.........................
.........................
........................
.
.........................
.........................
.........................
.........................
.........................
.........................
.........................
........................
.
.........................
.........................
.........................
........................

7338563 bytes read
## Booting image at 00200000 ...
   Image Name:   Linux-3.10.26-stora
   Created:      2014-01-13  20:27:45 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1927832 Bytes =  1.8 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 00800000 ...
   Image Name:   initramfs-3.10.26-stora
   Created:      2014-01-13  20:27:54 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7338499 Bytes =  7 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... Bad Data CRC

tried to set the uboot env variables back to the original to come back to the previous stage as I wanted to try another way. No success as the new booting was stopping with a Marvell >> prompt.

I looked into the Uboot command help and I found the command "resetenv" saying "Return all environment variable to default.". So I executed it and then gave a reset.

Marvell>> resetenv

Erase Env parameters offset 0xa0000... done
Warning: Default Environment Variables will take effect Only after RESET 
Marvell>> reset

         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_ 
| | | |___|  _ \ / _ \ / _ \| __| 
| |_| |___| |_) | (_) | (_) | |_ 
 \___/    |____/ \___/ \___/ \__| 
 ** MARVELL BOARD: RD-88F6281A LE 

U-Boot 1.1.4 (Sep  4 2009 - 09:36:11) Marvell version: 3.4.14

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CEE60

Soc: 88F6281 A0 (DDR2)
CPU running @ 1000Mhz L2 running @ 333Mhz
SysClock = 333Mhz , TClock = 200Mhz 

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size  64MB 
DRAM CS[1] base 0x04000000   size  64MB 
DRAM Total size 128MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:256 MB
CRC in Flash: ffffffff, Calculated CRC: 619d86db
+++++++++++++++++++++++++++Checksum Error!++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++Checksum Error!++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++Checksum Error!++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++Checksum Error!++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++Checksum Error!++++++++++++++++++++++++++++++
## Error: environment overflow, "stdin" deleted
## Error: environment overflow, "stdout" deleted
## Error: environment overflow, "stderr" deleted

CPU : Marvell Feroceon (Rev 1)
## Error: environment overflow, "console" deleted
## Error: environment overflow, "mainlineLinux" deleted
## Error: environment overflow, "CASset" deleted
## Error: environment overflow, "enaMonExt" deleted
## Error: environment overflow, "enaCpuStream" deleted
## Error: environment overflow, "enaWrAllo" deleted
## Error: environment overflow, "pexMode" deleted
## Error: environment overflow, "disL2Cache" deleted
## Error: environment overflow, "setL2CacheWT" deleted
## Error: environment overflow, "disL2Prefetch" deleted
## Error: environment overflow, "enaICPref" deleted
## Error: environment overflow, "enaDCPref" deleted
## Error: environment overflow, "sata_dma_mode" deleted
## Error: environment overflow, "MALLOC_len" deleted
## Error: environment overflow, "ethprime" deleted
## Error: environment overflow, "netbsd_en" deleted
## Error: environment overflow, "vxworks_en" deleted
## Error: environment overflow, "bootargs_root" deleted
## Error: environment overflow, "bootargs_end" deleted
## Error: environment overflow, "image_name" deleted
## Error: environment overflow, "bootcmd" deleted
## Error: environment overflow, "standalone" deleted
## Error: environment overflow, "bootdelay" deleted
## Error: environment overflow, "disaMvPnp" deleted
## Error: environment overflow, "disaMvPnp" deleted
## Error: environment overflow, "ethaddr" deleted
## Error: environment overflow, "ethmtu" deleted
## Error: environment overflow, "eth1addr" deleted
## Error: environment overflow, "eth1mtu" deleted
## Error: environment overflow, "mvPhoneConfig" deleted
## Error: environment overflow, "mvNetConfig" deleted
## Error: environment overflow, "usb0Mode" deleted
## Error: environment overflow, "yuk_ethaddr" deleted
## Error: environment overflow, "nandEcc" deleted
## Error: environment overflow, "hddPowerCtrl" deleted
## Error: environment overflow, "netretry" deleted
## Error: environment overflow, "rcvrip" deleted
## Error: environment overflow, "loadaddr" deleted
## Error: environment overflow, "autoload" deleted
## Error: environment overflow, "enaAutoRecovery" deleted

Streaming disabled 
Write allocate disabled

Module 0 is RGMII
Module 1 is TDM

USB 0: device mode
PEX 0: interface detected no Link.
Net:   ## Error: environment overflow, "ethact" deleted
egiga0, egiga1## Error: environment overflow, "ethact" deleted

USB:   scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
Trying to load image from USB flash drive using FAT FS
reading /flashware.img

** Unable to read "/flashware.img" from usb 0:1 **
Trying to load image from USB flash drive using ext2 FS partition 0
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - usb 0:0 **
Trying to load image from USB flash drive using ext2 FS partition 1

** Unable to read "/flashware.img" from usb 0:1 **
Couldn't load recovery image from USB flash drive, Trying network interface
Aquiring an IP address using DHCP...
## Error: environment overflow, "ethact" deleted
*** ERROR: `ethaddr' not set
## Error: environment overflow, "ethact" deleted
egiga1 no link
## Error: environment overflow, "ethact" deleted
## Error: environment overflow, "ethact" deleted
*** ERROR: `ethaddr' not set
## Error: environment overflow, "ethact" deleted
egiga1 no link
## Error: environment overflow, "ethact" deleted
## Error: environment overflow, "ethact" deleted
*** ERROR: `ethaddr' not set
## Error: environment overflow, "ethact" deleted
egiga1 no link
## Error: environment overflow, "ethact" deleted
Failed to retreive an IP address assuming default ()!
Starting the Recovery process to retreive the file...
## Error: environment overflow, "ethact" deleted
*** ERROR: `ethaddr' not set
## Error: environment overflow, "ethact" deleted
egiga1 no link
## Error: environment overflow, "ethact" deleted
Failed
Power Button is pressed!
MPP Sel: 00000530, Data IN Enable: 00020058, Data In Polarity: 00000040, Data In: 00000010
Power Button is released!
MAC: 00:01:8D:F6:7E:01, IP: 10.246.126.1
## Error: environment overflow, "ethaddr" deleted
## Error: environment overflow, "ipaddr" deleted
## Error: environment overflow, "serverip" deleted
## Error: environment overflow, "netmask" deleted
## Error: environment overflow, "image_name" deleted
## Error: environment overflow, "console" deleted
## Error: environment overflow, "bootargs_root" deleted
## Error: environment overflow, "rootpath" deleted
## Error: environment overflow, "ethact" deleted
*** ERROR: `serverip' not set
## Error: environment overflow, "bootargs" deleted
## Booting image at 00800000 ...
   Image Name:   initramfs-3.10.26-stora
   Created:      2014-01-13  20:27:54 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7338499 Bytes =  7 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... Bad Data CRC

The printenv command repleys with a lot of "ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ" characters on the screen and "Environment size: 131069/131068 bytes" at the end.

I try to restore the old env variable one by one (I have the output of the original "printenv results") but set env seems not to work. Below an example:

Marvell>> setenv baudrate=115200
Marvell>> saveenv
Saving Environment to NAND...
Erasing Nand...Writing to Nand... done
Marvell>> printenv baudrate
## Error: "baudrate" not defined

I've read a recovery procedures but I'm confused on what to do to recover my Stora.

Can you please help me ?

Thanks
Regards

de-bricking a Lacie 2Big NAS (14 replies)

romiz — Fri, 23 Jan 2026 10:38:02 -0600

Hi everyone,
I'm asking for help in de-bricking a Lacie 2Big NAS: I wiped the bootloader.
I wonder if anyone of you could send a copy of the stock u-boot or a different but working version.

I know that u-boot should be very board-specific and the device is exactly this as reported on lacie-nas.org (https://lacie-nas.org/doku.php?id=2big_nas).
I don't know if the same u-boot can be used on different boards by (auto?-)selecting the proper device tree blob, but on the same site at https://downloads.lacie-nas.org/u-boot/lacie-stock/ there's one single u-boot binary showing inside the string "Marvell version: 1.7.3 - LaCie version: 1.4.alpha_3".
Any experience about it?

Last resort will be to build a version for that device.

Thanks

Debian/OpenWrt - built-in NAND flash - Promwad-ThinClient/Depo Sky A60/AK-Systems AK1100 and AK-systems IP-Plug (57 replies)

cmp18 — Mon, 12 Jan 2026 04:12:07 -0600

DO NOT FLASH OTHER DEVICES! This UBI only for specific NAND flash (Samsung NAND 1GiB 3,3V 8-bit, Manufacturer ID: 0xec, Chip ID: 0xd3)

1) Debian (rootfs via debootstrap, systemd logs in ram)
Link (images and howto)

2) OpenWRT with official OpenWRT kernel (kmod packages are working)
(official openwrt kernel config for kirkwood without HIGHMEM, therefore only 768Mb RAM visible)
Link (images and howto)

3) Original FW and sources (u-boot and kernel)
(debian 6 based with XFCE, root password: nosoup4u, user password: secret)
Link
mirrors: (1, 2)

Work/dont work:
+serial
+ethernet
+usb
+mini pci-e
+sound (and buzzer connected to sound codec) (in openwrt need custom kmods - you can use debian if you need sound)
+video (in openwrt need custom kmods + kernel patches - you can use debian if you need video)

_______________________________________________________________________________________________
Additional links:
My experience
topic in which we are working whit FDT (dtb/dts) (usb, pci-e,...)
topic with latest kirkwood kernel (you can use this kernel with this openwrt, but you will need unpack and put modules in the right folder, and sometimes there will be kmod dependency errors when installing packages (errors do not affect anything))

===========================================================================================
If you want to compile OpeWRT by yourself, there is an excellent instruction, very detailed and with a description of many nuances (but for make custom images need skills).
or,
if you dont have skills are satisfied with everything by default, we will create uImage and rootfs for our device based on firmware from similar device, like in this my article (from my web site):

https://debianlive.ru/2025/02/depo-sky-a60-ak-systems-ak1100-%d0%bd%d0%b0-openwrt-%d0%ba%d0%b0%d0%ba-%d0%bb%d0%b5%d0%bd%d0%b8%d0%b2%d0%b0%d1%8f-%d0%bd%d0%b5%d0%b4%d0%be%d1%81%d0%b1%d0%be%d1%80%d0%ba%d0%b0-%d1%81%d1%82%d0%b0/

OpenWrt on TBS MOI+ (24 replies)

ri8 — Sat, 08 Feb 2025 16:31:23 -0600

bodhi,

having

SoC:   Kirkwood 88F6282_A1
Model: TBS MOI+
DRAM:  512 MiB
Core:  19 devices, 14 uclasses, devicetree: separate
NAND:  512 MiB
Loading Environment from NAND... OK
In:    serial
Out:   serial
Err:   serial
pcie0.0: Link up
Net:   eth0: ethernet-controller@72000
Hit any key to stop autoboot:  0 
MOI+> mtd     
  mtd mtdparts
MOI+> mtdparts 

device nand0 , # parts = 2
 #: name		size		offset		mask_flags
 0: uboot               0x00100000	0x00000000	0
 1: data                0x1ff00000	0x00100000	0

active partition: nand0,0 - (uboot) 0x00100000 @ 0x00000000

defaults:
mtdids  : nand0=orion_nand
mtdparts: mtdparts=orion_nand:1m(uboot),-(data)
MOI+>

1. how i have change $mtdparts in order to be able to make visible to the u-boot an ubi partition
i made from debian on mtd1

root@debian:~# ubiattach /dev/ubi_ctrl -m 1

[   77.885942][ T1188] ubi0: attaching mtd1
[   78.607169][ T1188] ubi0: scanning is finished
[   78.637189][ T1188] ubi0: attached mtd1 (name "data", size 511 MiB)
[   78.643508][ T1188] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
[   78.656313][ T1188] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
[   78.664050][ T1188] ubi0: VID header offset: 512 (aligned 512), data offset: 2048
[   78.671819][ T1188] ubi0: good PEBs: 4088, bad PEBs: 0, corrupted PEBs: 0
[   78.678824][ T1188] ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
[   78.686986][ T1188] ubi0: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 693956855
[   78.696956][ T1188] ubi0: available PEBs: 0, total reserved PEBs: 4088, PEBs reserved for bad PEB handling: 80
[   78.707212][ T1190] ubi0: background thread "ubi_bgt0d" started, PID 1190
UBI device number 0, total 4088 LEBs (527450112 bytes, 503.0 MiB), available 0 LEBs (0 bytes), LEB size 129024 bytes (126.0 KiB)
root@debian:~# mount.ubifs /dev/ubi0_0 /mnt/ubifs/
[   96.833144][ T1192] UBIFS (ubi0:0): Mounting in unauthenticated mode
[   96.849615][ T1193] UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 1193
[   96.981245][ T1192] UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[   96.989437][ T1192] UBIFS (ubi0:0): LEB size: 129024 bytes (126 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[   97.000456][ T1192] UBIFS (ubi0:0): FS size: 262821888 bytes (250 MiB, 2037 LEBs), max 2048 LEBs, journal size 9033728 bytes (8 MiB, 71 LEBs)
[   97.013457][ T1192] UBIFS (ubi0:0): reserved for root: 0 bytes (0 KiB)
[   97.020025][ T1192] UBIFS (ubi0:0): media format: w4/r0 (latest is w5/r0), UUID 7C65E193-A894-4039-ACB0-40659E388690, small LPT model
root@debian:~# file /mnt/ubifs/boot/uImage 
/mnt/ubifs/boot/uImage: u-boot legacy uImage, Linux-2.6.35.14, Linux/ARM, OS Kernel Image (Not compressed), 3546932 bytes, Wed Mar 26 08:08:36 2014, Load Address: 0X008000, Entry Point: 0X008000, Header CRC: 0X64D64730, Data CRC: 0X102A26D8
root@debian:~#

2. since you've mentioned OpenWrt as rescue system on nand(i have 500MB on mtd1),
which image you'd suggest for this box

root@debian:~# ethtool -i eth0

driver: mv643xx_eth
version: 1.4
firmware-version: N/A
expansion-rom-version: 
bus-info: platform
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no

Regards,
alex

======
bodhi edited: please use code tags (formatted code button) to post log.

Flash NSA325v2 to stock (1 reply)

sheratann — Fri, 06 Dec 2024 20:28:05 -0600

Hi,

I had debian installed and uboot 2017 installed on 2 NSA325v2s and I want to go back to stock firmware because I am giving them away.

Does anyone have the stock MTD0 so I can reflash?

Let's gift a new life to my poor old Iomega ix4-200d (1 reply)

mundodisco — Mon, 23 Sep 2024 17:39:05 -0500

Hi everyone!

I own an Iomega ix4-200d NAS, with four 2TB disks. I tried installing OpenWRT but even latest version cannot detect the four disks (just bays #3 and #4).
So... I would like to try another approach. Can anyone suggest another option, 100% compatible with this NAS? Take into account that it has Kirkwood architecture, 512MB RAM and USB 2.0 ports.

I was thinking of some Linux distro from a USB pendrive... a good brand pendrive, 3.0 (but connected to USB 2.0 ports). Which one do you recommend? Is there any tutorial on how to edit (again) the u-boot to boot from this pendrive (and to correctly install this Linux distro?

Sorry for so many questions guys!

Regards...
Gabriel

Factory restore Dockstar - Help needed (23 replies)

Zasshi — Mon, 23 Sep 2024 14:23:26 -0500

Hello,
I own a couple of Dockstars that have been running linux for a few years, thanks to this forum tutorials and useful tools.

Now one of the Dockstars is bricked, and I'd like to restore it to the factory software (pogo...?) but I don't know how...
Moreover I can't find a guide with the needed software anymore.

So, could someone help me to restore the original firmware, please?

Thanks!

Netboot feasible? (5 replies)

aaronouthier — Sun, 02 Jun 2024 22:15:57 -0500

Hello,

I have 3 old products in the series (2 Different Seagate GoFlex NAS series: 1 with 1x 3.5" bay, and 1 with 2x 2.5" bays; Also a NetGear Home NAS product with 2x tray-less 3.5" HDD bays - I forgot the name of it).

I have a PFsense router, which has a DHCP server capable of sending DHCP parameters required for netbooting. I also have 2 home lab servers running Proxmox, and the know-how to administer a Linux system from the command-line.

My main question is: is it possible to get these old NAS boxes to Netboot using only the available, onboard flash storage?
Secondary to that is: Is it worth the effort?

I realize the second question is subjective and more a matter of opinion. I'm just trying to gauge how much Ibuprofen I'm liable to need, so to speak.

Also, is anyone able to help me get started? If it's possible to do, I can probably figure it out eventually. Some help from those more experienced would be great.

I have a rescue USB in one of the systems with an old RootFS. I'm not sure if it'll be useful/needed. All 3 were converted to USB boot using instructions in these forums at one time.

pogoplus 02 (13 replies)

gov — Sun, 11 Feb 2024 12:35:37 -0600

hello all...
i have a pogoplus E02 which i used to run archlinux arm on it...long ago...i think flashed jeff uboot at that time and used to run arch linux...

now i want to use pogoplus e02 but i cant ssh into it...how can i ssh into it....please can anyone point me to the complete guide..Thanks

Rescue system for Pogoplug E02 - Best Option? (2 replies)

bowent@encorecsl.com — Wed, 17 Jan 2024 17:42:08 -0600

Greetings, I have a pink Pogoplug E02 which is running Debian from a USB Drive.
It will not boot without the USB installed. Here is the boot log (booting without USB):

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:13:18 -0700)
Pogo E02

SoC:   Kirkwood 88F6281_A0
DRAM:  256 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Hit any key to stop autoboot:  0
Initializing devices...
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'
Loading envs from usb 0...
** Bad device usb 0 **
Loading envs from usb 1...
** Bad device usb 1 **
Loading envs from usb 2...
** Bad device usb 2 **
Loading envs from usb 3...
** Bad device usb 3 **
Loading envs from ide 0...
** Bad device ide 0 **
Loading envs from ide 1...
** Bad device ide 1 **
Loading envs from ide 2...
** Bad device ide 2 **
Loading envs from ide 3...
** Bad device ide 3 **
Loading envs from mmc 0...
** Bad device mmc 0 **
Loading envs from mmc 1...
** Bad device mmc 1 **
Loading envs from mmc 2...
** Bad device mmc 2 **
Loading envs from mmc 3...
** Bad device mmc 3 **
running scan_disk ...
Scan device usb
device usb 0:1
** Bad device usb 0 **
device usb 1:1
** Bad device usb 1 **
device usb 2:1
** Bad device usb 2 **
device usb 3:1
** Bad device usb 3 **
Scan device ide
Unknown command 'ide' - try 'help'
device ide 0:1
** Bad device ide 0 **
device ide 1:1
** Bad device ide 1 **
device ide 2:1
** Bad device ide 2 **
device ide 3:1
** Bad device ide 3 **
Scan device mmc
Unknown command 'mmc' - try 'help'
device mmc 0:1
** Bad device mmc 0 **
device mmc 1:1
** Bad device mmc 1 **
device mmc 2:1
** Bad device mmc 2 **
device mmc 3:1
** Bad device mmc 3 **
loading uImage ...
** Bad device usb 0 **
loading uInitrd ...
** Bad device usb 0 **
loading DTB /boot/dts/kirkwood-pogo_e02.dtb ...
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
PogoE02>

I'd like for the Pogoplug to boot some O/S with the USB removed.
I have no image for the original O/S, so that's probably not an option.
Rescue v2 looks good, but I am not sure it is compatible with E02.
What is the recommended rescue systen for E02?
Thanks for these forums and your wisdom (couldn't have gotten this far without help from this site).

rootfs backup - best way to make a secure copy of usb stick (2 replies)

alazarski — Wed, 10 Jan 2024 09:31:08 -0600

Good day, II’d like to make an exact copy of my usb stick with Debian. I’m afraid that usb stick will deteriorated and finally going down. I’ve made a lot of work on it e.g. kernel update, services configuration. What is in your opinion make a backup usb ?

Help! Akitio mycloudmini using stock kernel but missing system setting files (125 replies)

Popo — Tue, 09 Jan 2024 22:28:32 -0600

Hi,

I have akitio mycloudmini used oem factory firmware,
at yesterday , I want to try to modify root's passord.
So, I backup and save the zip file.
open it, modify 'shadow ' file to my admin password for root.
after did that, I use 'Restore' to upload zip file to server then click 'restart' to reboot.

at the long long time, i can't 'Ping' machine IP, so that I force reboot machine by push button.

after power on , I use serial console and Putty to watch the log,
I found that , passwd/shadow/fstab/...blablaba....every each setting file was gone.

please see the log attachment.

I saw UBI File System can mount and 'Login:' show ....
I though whole the file system can work after I fix all of the setting files.
But, How can I mount MTDBLOCK ? (Boot from HDD and mount ubifs recovery all of the files, maybe ok ? But, How to ?)

I always know my U-Boot is Ver.1.1.2,
less function to 'saveenv'/'boot' .......so that I can't force into single mode to rescue my setting-files.

have any idea ?

OR

I am sure 'bootm' can execute!
try pass through TFTP to download uImage ?

tftp 0x60003000 uImage <===??????what image????
tftp 0x60500000 ??????.dtb <=== need it?
setenv bootargs ${bootargs} single init=/bin/sh
bootm 0x60003000 - 0x60500000

have any suggestion ?

Stage-1 Bootloader 一  8月 30 10:55:36 CST 2010
Attempting to set PLLA to 700MHz ...
  plla_ctrl0 : 0x0000000A
  plla_ctrl1 : 0x000E0000
  plla_ctrl2 : 0x001B01A0
  plla_ctrl3 : 0x00000016
PLLA Set

Setup memory, testing
Reading NAND, Image 0
  Hdr len: 0x0001A0D8
  Hdr CRC: 0x330E1A94
 OK


U-Boot 1.1.2 (Dec 24 2010 - 12:42:28)

U-Boot code: 60D00000 -> 60D1A0D8  BSS: -> 60D1E790
RAM Configuration:
        Bank #0: 60000000 256 MB
SRAM Configuration:
        64KB at 0x50000000
NAND:256 MiB
Using default environment

In:    serial
Out:   serial
Err:   serial
Setting Linux mem= boot arg value
Hit any key to stop autoboot:  0
$
$ printenv
bootcmd=run extinguishled boot_nand
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"
load_nand=nboot 60500000 0 440000
load_nand2=nboot 60500000 0 A40000
lightled=ledfail 1
extinguishled=ledfail 0
boot=bootm 60500000
boot_nand=run load_nand boot || run load_nand2 boot || run lightled
stdin=serial
stdout=serial
stderr=serial
bootargs=root=ubi0:rootfs ubi.mtd=2,512 rootfstype=ubifs console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=256M poweroutage=yes

Environment size: 576/8188 bytes

setenv bootargs ${bootargs} single init=/bin/sh && reset

$ printenv
Unknown command 'printenv' - try 'help'
$ printenv
bootcmd=run extinguishled boot_nand
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"
load_nand=nboot 60500000 0 440000
load_nand2=nboot 60500000 0 A40000
lightled=ledfail 1
extinguishled=ledfail 0
boot=bootm 60500000
boot_nand=run load_nand boot || run load_nand2 boot || run lightled
stdin=serial
stdout=serial
stderr=serial
bootargs=root=ubi0:rootfs ubi.mtd=2,512 rootfstype=ubifs console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=256M poweroutage=yes single init=/bin/sh

Environment size: 596/8188 bytes
$ boot
Unknown command 'boot' - try 'help'
$ boot
Unknown command 'boot' - try 'help'
$ help
?       - alias for 'help'
base    - print or set address offset
bdinfo  - print Board Info structure
bootm   - boot application image from memory
bootp   - boot image via network using BootP/TFTP protocol
cmp     - memory compare
cp      - memory copy
crc32   - checksum calculation
echo    - echo args to console
exit    - exit script
fg - flash gpio    
go      - start application at address 'addr'
help    - print online help
iminfo  - print header information for application image
ledfail - Extinguish (0) or light (1) failure LED
loop    - infinite loop on address range
md      - memory display
mm      - memory modify (auto-incrementing)
mtest   - simple RAM test
mw      - memory write (fill)
nand    - NAND sub-system
nboot   - boot from NAND device
nm      - memory modify (constant address)
nwboot          - NAND Write boot information
otp    - OTP sub-system
ping    - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
rarpboot- boot image via network using RARP/TFTP protocol
reset   - Perform RESET of the CPU
run     - run commands in an environment variable
setenv  - set environment variables
sg - set gpio    < (1) high (0) low>
test    - minimal test like /bin/sh
tftpboot- boot image via network using TFTP protocol
version - print monitor version
$ version

U-Boot 1.1.2 (Dec 24 2010 - 12:42:28)
$ reset
Resetting...

printenv and try to setenv watch


Stage-1 Bootloader 一  8月 30 10:55:36 CST 2010
Attempting to set PLLA to 700MHz ...
  plla_ctrl0 : 0x0000000A
  plla_ctrl1 : 0x000E0000
  plla_ctrl2 : 0x001B01A0
  plla_ctrl3 : 0x00000016
PLLA Set

Setup memory, testing
Reading NAND, Image 0
  Hdr len: 0x0001A0D8
  Hdr CRC: 0x330E1A94
 OK


U-Boot 1.1.2 (Dec 24 2010 - 12:42:28)

U-Boot code: 60D00000 -> 60D1A0D8  BSS: -> 60D1E790
RAM Configuration:
        Bank #0: 60000000 256 MB
SRAM Configuration:
        64KB at 0x50000000
NAND:256 MiB
Using default environment

In:    serial
Out:   serial
Err:   serial
Setting Linux mem= boot arg value
Hit any key to stop autoboot:  0
$ printenv  bootargs
bootargs=root=ubi0:rootfs ubi.mtd=2,512 rootfstype=ubifs console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=256M poweroutage=yes
$ setenv bootargs "XXXXX single init=/bin/sh"
$ print
bootcmd=run extinguishled boot_nand
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"
load_nand=nboot 60500000 0 440000
load_nand2=nboot 60500000 0 A40000
lightled=ledfail 1
extinguishled=ledfail 0
boot=bootm 60500000
boot_nand=run load_nand boot || run load_nand2 boot || run lightled
stdin=serial
stdout=serial
stderr=serial
bootargs=XXXXX single init=/bin/sh

Environment size: 457/8188 bytes
$

mycloudmini can boot success from u-boot but miss password/shadow files


Stage-1 Bootloader 一  8月 30 10:55:36 CST 2010
Attempting to set PLLA to 700MHz ...
  plla_ctrl0 : 0x0000000A
  plla_ctrl1 : 0x000E0000
  plla_ctrl2 : 0x001B01A0
  plla_ctrl3 : 0x00000016
PLLA Set

Setup memory, testing
Reading NAND, Image 0
  Hdr len: 0x0001A0D8
  Hdr CRC: 0x330E1A94
 OK


U-Boot 1.1.2 (Dec 24 2010 - 12:42:28)

U-Boot code: 60D00000 -> 60D1A0D8  BSS: -> 60D1E790
RAM Configuration:
        Bank #0: 60000000 256 MB
SRAM Configuration:
        64KB at 0x50000000
NAND:256 MiB
Using default environment

In:    serial
Out:   serial
Err:   serial
Setting Linux mem= boot arg value
Hit any key to stop autoboot:  0
Extinguish LED

Loading from device 0: 256MiB 3,3V 8-bit (offset 0x440000)
   Image Name:   Linux-2.6.31.6-fast-20110114
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3056816 Bytes =  2.9 MB
   Load Address: 60008000
   Entry Point:  60008000
## Booting image at 60500000 ...
   Image Name:   Linux-2.6.31.6-fast-20110114
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3056816 Bytes =  2.9 MB
   Load Address: 60008000
   Entry Point:  60008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux..................................................................................................................................................................................... done, booting the kernel.
Linux version 2.6.31.6-fast-20110114 (thom@11z) (gcc version 4.5.1 (GCC) ) #1 SMP Fri Jan 14 13:58:20 CST 2011
CPU: ARMv6-compatible processor [410fb025] revision 5 (ARMv7), cr=00c5387f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: Oxsemi NAS
1 memory region
Ignoring unrecognised tag 0x00000000
Memory policy: ECC disabled, Data cache writealloc
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
Kernel command line: root=ubi0:rootfs ubi.mtd=2,512 rootfstype=ubifs console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=256M poweroutage=yes
PID hash table entries: 1024 (order: 10, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 256MB = 256MB total
Memory: 253696KB available (5260K code, 310K data, 136K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:96
OX820_RPS_init_irq: interrupts 64 to 96
Console: colour dummy device 80x30
console [ttyS0] enabled
Calibrating delay loop... 279.34 BogoMIPS (lpj=1396736)
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
Calibrating local timer... 349.98MHz.
CPU1: Booted secondary processor
Calibrating delay loop... 279.34 BogoMIPS (lpj=1396736)
Brought up 2 CPUs
SMP: Total of 2 processors activated (558.69 BogoMIPS).
NET: Registered protocol family 16
Number of DMA channels = 4, version = 4
Reserving a DMA channel for DirectRAID
Allocating 218 SRAM generic DMA descriptors
bio: create slab  at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
cfg80211: Calling CRDA to update world regulatory domain
NET: Registered protocol family 2
Switched to NOHz mode on CPU #0
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
Switched to NOHz mode on CPU #1
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
NET: Registered protocol family 1
Create fragment cache
fuse init (API version 7.12)
SGI XFS with security attributes, large block/inode numbers, no debug enabled
msgmni has been set to 496
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x44200000 (irq = 55) is a 16550A
brd: module loaded
loop: module loaded
ox820sata: OX820 sata core.
scsi0 : oxnassata
scsi1 : oxnassata
ata1: SATA max UDMA/133 irq 50
ata2: SATA max UDMA/133 irq 50
ata1: SATA link down (SStatus 0 SControl 300)
ata2: SATA link down (SStatus 0 SControl 300)
NAND device: Manufacturer ID: 0xad, Chip ID: 0xda (Hynix NAND 256MiB 3,3V 8-bit)
Scanning device for bad blocks
Creating 2 MTD partitions on "NAND 256MiB 3,3V 8-bit":
0x000000000000-0x0000026c0000 : "Boot partition"
0x0000026c0000-0x000010000000 : "Data Partition"
UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI warning: ubi_eba_init_scan: cannot reserve enough PEBs for bad PEB handling, reserved 11, need 17
UBI: attached mtd2 to ubi0
UBI: MTD device name:            "Data Partition"
UBI: MTD device size:            217 MiB
UBI: number of good PEBs:        1738
UBI: number of bad PEBs:         0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 1738
UBI: number of PEBs reserved for bad PEB handling: 11
UBI: max/mean erase counter: 800/105
UBI: image sequence number: 1359814330
UBI: background thread "ubi_bgt0d" started, PID 398
Probing for Synopsis GMAC, unit 0
eth0: use mtd hwaddr
eth0: Tuning GMAC 0 RGMII timings
eth0: PHY is Realtek RTL8211D, type 0x001cc914
eth0: GMAC ver = 53, vendor ver = 18 at 0xe1400000, IRQ 40
eth0: Found PHY at address 3, type 0x001cc914 -> 10/100/1000
eth0: Ethernet addr: 00:01:d2:12:00:fa
probe() eth0: Leon x2 clock
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky 
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Start USB clocks
oxnas-ehci oxnas-ehci.0: OXNAS EHCI Host Controller
oxnas-ehci oxnas-ehci.0: new USB bus registered, assigned bus number 1
oxnas-ehci oxnas-ehci.0: irq 39, io mem 0x00000000
oxnas-ehci oxnas-ehci.0: USB 0.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
IRQ 53 uses trigger mode 0; requested 3
input: gpio-keys as /devices/platform/gpio-keys/input/input0
irq 54: nobody cared (try booting with the "irqpoll" option)
[] (unwind_backtrace+0x0/0xe0) from [] (__report_bad_irq+0x78/0xa8)
[] (__report_bad_irq+0x78/0xa8) from [] (note_interrupt+0x184/0x1f0)
[] (note_interrupt+0x184/0x1f0) from [] (handle_level_irq+0x108/0x130)
[] (handle_level_irq+0x108/0x130) from [] (asm_do_IRQ+0x54/0xa8)
[] (asm_do_IRQ+0x54/0xa8) from [] (__irq_svc+0x38/0xc0)
Exception stack(0xcf813b48 to 0xcf813b90)
3b40:                   cf813b90 ffff8bf5 00000000 00000000 00000102 c0593ac0
3b60: cf812000 cf812000 c0023530 c056e040 c05a1d60 00000000 00000002 cf813b90
3b80: c0050b8c c00506e8 20000113 ffffffff
[] (__irq_svc+0x38/0xc0) from [] (__do_softirq+0x50/0x140)
[] (__do_softirq+0x50/0x140) from [] (irq_exit+0x84/0xa0)
[] (irq_exit+0x84/0xa0) from [] (asm_do_IRQ+0x58/0xa8)
[] (asm_do_IRQ+0x58/0xa8) from [] (__irq_svc+0x38/0xc0)
Exception stack(0xcf813be8 to 0xcf813c30)
3be0:                   c059437c 60000013 e510001c 00000000 00000000 e510001c
3c00: c0573454 00000000 00000029 60000013 00000000 cf813d94 e500001c cf813c30
3c20: c0034b58 c03eec80 20000013 ffffffff
[] (__irq_svc+0x38/0xc0) from [] (_spin_unlock_irqrestore+0x18/0x1c)
[] (_spin_unlock_irqrestore+0x18/0x1c) from [] (ox820_gpio_direction_output+0x60/0xa8)
[] (ox820_gpio_direction_output+0x60/0xa8) from [] (gpio_direction_output+0xcc/0xf0)
[] (gpio_direction_output+0xcc/0xf0) from [] (i2c_start+0x18/0x44)
[] (i2c_start+0x18/0x44) from [] (bit_xfer+0x24/0x4b0)
[] (bit_xfer+0x24/0x4b0) from [] (i2c_transfer+0xb0/0xf0)
[] (i2c_transfer+0xb0/0xf0) from [] (i2c_smbus_xfer+0x290/0x54c)
[] (i2c_smbus_xfer+0x290/0x54c) from [] (i2c_smbus_read_i2c_block_data+0x4c/0x74)
[] (i2c_smbus_read_i2c_block_data+0x4c/0x74) from [] (ds1307_probe+0x350/0x608)
[] (ds1307_probe+0x350/0x608) from [] (i2c_device_probe+0x6c/0x84)
[] (i2c_device_probe+0x6c/0x84) from [] (driver_probe_device+0x78/0x164)
[] (driver_probe_device+0x78/0x164) from [] (bus_for_each_drv+0x60/0x8c)
[] (bus_for_each_drv+0x60/0x8c) from [] (device_attach+0x70/0x88)
[] (device_attach+0x70/0x88) from [] (bus_probe_device+0x24/0x44)
[] (bus_probe_device+0x24/0x44) from [] (device_add+0x3d0/0x4b4)
[] (device_add+0x3d0/0x4b4) from [] (i2c_new_device+0xbc/0x124)
[] (i2c_new_device+0xbc/0x124) from [] (i2c_register_adapter+0x124/0x1a8)
[] (i2c_register_adapter+0x124/0x1a8) from [] (i2c_add_numbered_adapter+0xb0/0xc8)
[] (i2c_add_numbered_adapter+0xb0/0xc8) from [] (i2c_gpio_probe+0x184/0x244)
[] (i2c_gpio_probe+0x184/0x244) from [] (platform_drv_probe+0x18/0x1c)
[] (platform_drv_probe+0x18/0x1c) from [] (driver_probe_device+0x78/0x164)
[] (driver_probe_device+0x78/0x164) from [] (__driver_attach+0x8c/0x90)
[] (__driver_attach+0x8c/0x90) from [] (bus_for_each_dev+0x54/0x80)
[] (bus_for_each_dev+0x54/0x80) from [] (bus_add_driver+0x98/0x230)
[] (bus_add_driver+0x98/0x230) from [] (driver_register+0x78/0x13c)
[] (driver_register+0x78/0x13c) from [] (i2c_gpio_init+0xc/0x30)
[] (i2c_gpio_init+0xc/0x30) from [] (do_one_initcall+0x30/0x1a0)
[] (do_one_initcall+0x30/0x1a0) from [] (kernel_init+0x16c/0x1f8)
[] (kernel_init+0x16c/0x1f8) from [] (kernel_thread_exit+0x0/0x8)
handlers:
[] (gpio_keys_isr+0x0/0x8c)
Disabling IRQ #54
rtc-ds1307 0-0068: rtc core: registered m41t00 as rtc0
i2c-gpio i2c-gpio.0: using pins 41 (SDA) and 42 (SCL)
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
Registered led device: hddaerr
Registered led device: hddberr
Registered led device: system
Registered led device: firmware
Registered led device: usbcopy
TCP cubic registered
NET: Registered protocol family 10
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
rtc-ds1307 0-0068: setting system clock to 2023-11-19 20:42:42 UTC (1700426562)
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=noautodetect
md: Autodetecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size:   220502016 bytes (215334 KiB, 210 MiB, 1709 LEBs)
UBIFS: journal size:       9033728 bytes (8822 KiB, 8 MiB, 71 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:10.
Freeing init memory: 136K
                Welcome to Fedora
                Press 'I' to enter interactive startup.
Starting udev: /bin/chown: invalid user: `root:disk'
/bin/chown: invalid user: `root:disk'
/bin/chown: invalid user: `root:disk'
/bin/chown: invalid user: `root:disk'
/bin/chown: invalid user: `root:disk'
/bin/chown: invalid user: `root:disk'
/bin/chown: invalid user: `root:disk'
/bin/chown: invalid user: `root:disk'
/bin/chown: invalid user: `root:lp'
/bin/chown: invalid user: `root:lp'
/bin/chown: invalid user: `root:lp'
/bin/chown: invalid user: `root:lp'
[  OK  ]
Setting hostname localhost:  [  OK  ]
Checking filesystems
WARNING: couldn't open /etc/fstab: No such file or directory
Checking all file systems.
[  OK  ]
warning: can't open /etc/fstab: No such file or directory
mount: can't find / in /etc/fstab or /etc/mtab
Mounting local filesystems:  warning: can't open /etc/fstab: No such file or directory
[  OK  ]
chown: invalid user: `root:root'
                                Enabling /etc/fstab swaps:  swapon: /etc/fstab: open failed: No such file or directory
                                                                                                                      [FAILED]

** (process:699): WARNING **: Couldn't create log file /var/log/ConsoleKit/history (No such file or directory)
init: ck-log-system-start main process (699) terminated with status 1
Entering non-interactive startup
Scan raid infomation:
mdadm: No arrays found in config file or automatically
Restoring /var/log to tmpfs:
  mount tmpfs on /var/log...
  extract backup logs to /var/log...
10 blocks
error: bad top line in state file /var/lib/logrotate.status
error: could not read state file, will not attempt to write into it
error: bad top line in state file /var/lib/logrotate.status
error: could not read state file, will not attempt to write into it

Starting portreserve: [  OK  ]
Starting system logger: [  OK  ]
Starting system message bus: Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry

Unknown username "avahi" in message bus configuration file
Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry

Unknown username "root" in message bus configuration file
Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry

Unknown group "avahi" in message bus configuration file
Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry

Unknown username "root" in message bus configuration file
Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry

Unknown username "root" in message bus configuration file
Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry

Unknown username "root" in message bus configuration file
Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry

Unknown username "root" in message bus configuration file
Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry

Unknown username "root" in message bus configuration file
Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry

Unknown username "root" in message bus configuration file
Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry

Failed to start message bus: Could not get UID and GID for username "dbus"
[FAILED]
/etc/rc3.d/S24avahi-daemon: line 40: /etc/sysconfig/network: No such file or directory
Starting cups: [  OK  ]
Retrigger failed udev events[  OK  ]
Starting xinetd: [  OK  ]
/etc/rc3.d/S57ntpdate: line 18: /etc/sysconfig/network: No such file or directory
NTP server not specified in /etc/ntp/step-tickers or /etc/ntp.conf
/etc/rc3.d/S58ntpd: line 29: /etc/sysconfig/network: No such file or directory
Starting ntpd: [  OK  ]
/etc/rc3.d/S60nas: line 28: /etc/sysconfig/network: No such file or directory
Starting NAS (nas):  fastcgi buttons diskmon
Starting lighttpd: 2023-11-19 20:42:56: (server.c.756) can't find username lighttpd
[FAILED]
[FAILED] atd: [FAILED]
swapon: /etc/fstab: open failed: No such file or directory
Starting NAS LED (nasled): sqlite3: cannot locate your home directory!
product was "akitio"
 nas-service/etc/rc3.d/S99nasled: line 83: /etc/nas/spindown: No such file or directory

Starting smartd: [  OK  ]

Fedora release 12 (Constantine)
Kernel 2.6.31.6-fast-20110114 on an armv6l (/dev/ttyS0)

localhost login:

Bad Block Nand NAS326 (3 replies)

RRRrrr — Wed, 18 Oct 2023 12:35:03 -0500

Sorry for my English. Using translator

Every time you reboot the device, the settings and password are reset

Reason:

Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
nand_read_bbt: bad block at 0x0000001a0000
nand_read_bbt: bad block at 0x0000002c0000
nand_read_bbt: bad block at 0x000000400000
nand_read_bbt: bad block at 0x00000ad40000
nand_read_bbt: bad block at 0x00000aee0000

Bad Block in the first mtd2 block:

0x000000400000-0x000000e00000 : "Config"

Because of this, the contents of the entire mtd2 are not readable
- Is it possible to change the nand markup by moving the mtd2 section one block?
- If I install Debian on USB according to your instructions, will I still have the factory Web Interface?
- In one of your posts you wrote that you have an original full dump nand NAS 326. Can you send it to me to replace Nand chip?

HowTo: openWrt on OXNAS boxes (73 replies)

chessplayer — Sat, 20 Aug 2022 05:11:35 -0500

How to install OpenWrt on OXNAS boxes

This thread is based on my tutorial HowTo: OpenWrt on Kirkwood boxes (Attention: if it is one of the Kirkwood Pogoplugs you have, it is that tutorial you want to follow!). The basic approach is
the same for the OXNAS', but some modifications are required (and, as we will see, not everything is perfect as of the original writeup of this tutorial on August 1st, 2022)

chessplayer's edit (Aug 15th, 2022): Quite some insights have been gained over the last two weeks, so I will update this first post today to reflect these at least, although this is still work in progress.The points where this is visible are still marked by using a light blue color.

The procedure described in this thread is confirmed to work for both the Pogoplug Pro as well as the classic v3.

Credits

As always, credits are due to bodhi as well as to shv for his post on the subject and similarly to echowarrior108 for his efforts and also to David Golle over at OpenWrt.

Assumptions

I assume that the box in question has the latest uBoot and is able to boot a USB device with the latest kernel and rootfs according to the first two links in section Oxnas plugs of the wiki.

However, it will be absolutely necessary to be able to reach the box via netconsole or serial console.

The plan

We now want to install OpenWrt on our box. The steps we will need to take are

Boot into debian and do some modifications to the uBoot environment variables
Download, rename and copy to a FAT32 USB drive an OpenWrt Image
Reboot the box without a USB device but with netconsole to interact with it <- this is crucial
Use netconsole to boot OpenWrt image from the USB drive created before
SSH into OpenWrt and make sure the uBoot environment is found <- this is crucial
Install to NAND via sysupgrade OpenWrt
Boot from NAND and SSH into OpenWrt and make sure the uBoot environment is always found (which is possible, but does not yet have quite the desired effect)
Do some additional configuration
Enjoy!

Implementation
So, let us look at these steps in more detail.

1. Modify uBoot variables

First, we need to boot the box to debian, log in and then do the following:

fw_setenv mtdparts 'mtdparts=41000000.nand:14m(boot),-(data)'
fw_setenv partition 'nand0,0'
fw_setenv set_bootargs_owrt 'setenv bootargs console=ttyS0,115200 $mtdparts'
fw_setenv bootcmd_owrt 'run set_bootargs_owrt; nboot 60500000 0 440000; bootm'

All the other variables can stay the way they were before, but we have to add the OpenWrt boot option to the bootcmd. If we still have bodhi's environment variables as they came, this would be:

fw_setenv bootcmd 'run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_owrt'

The important part is to add 'run bootcmd_owrt' to the bootcmd you are currently using. So, if you changed something, e.g. to be able to boot with a separate boot partition or from SATA or anything like that, just append the OpenWrt boot option to the one you are using.

2. Download an OpenWrt image

Next, we need the appropriate image. Start on the release page of OpenWrt and choose the one you like best and then navigate to

/targets/oxnas/ox820/

Then, download the uImage appropriate for your box. Rename it to uImage and place it in the root of a FAT32 formatted USD device.

Remark: When this tutorial was written, it meant that I used version 21.02.3, so concretely

this image for the classic Pogoplug v3
this image for the Pogoplug Pro

Hint: It makes sense to keep the browser tab open for the actual installation to NAND in step 6.

3. Reboot to NAND with (net)console

Then, we need to reboot the box without the debian USB device, but with a way of interacting with it, preferably via netconsole. The latter needs to be started on the server beforehand with

nc -l -u -p 6666

Wait until after a few error messages you see the prompt, e.g.

OX820>

in the console window (alternatively, you can force this via a keystroke during the bootdelay, if you configured one).

Then, make sure OpenWrt lives in a clean environment by erasing the ubi partition:

nand erase.part data

4. Reboot with OpenWrt image

Insert the drive you created in step 2 into the box and boot it by issuing the following command at the (net)console prompt:

usb reset; fatload usb 0 0x60500000 uImage; bootm 0x60500000

This should end with

Starting kernel ...

in the console output, meaning that OpenWrt is now running in RAM.

5. Log in to OpenWrt

Find the IP address of your box and ssh into it (user root without password). The following step is absolutely crucial but does not yet quite work the way we would expect.

Verify your mtd layout. Ideally, (see bodhi's u-Boot post) it should be:

root@OpenWrt:# cat /proc/mtd

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

Instead, what it will probably be (at least it was for me) is:

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"

This means that for OpenWrt, the boot-section is further subdivided, while the ubi-/data-section is the same - so that is promising. However, since apparently our mtdparts-definition from step 1 was not picked up, we will have to calculate a bit in order to specify where fw_printenv should find the uBoot environment.

Temporarily generate or modify /etc/fw_env.config
Check whether the file /etc/fw_env.config has the following contents (which is easily calculated from the above MTD layout in comparison to bodhi's):

/dev/mtd1 0xc0000 0x20000 0x20000

If not or if the file does not exist at all, the easiest way to modify/generate it is

echo '/dev/mtd1 0xc0000 0x20000 0x20000' > /etc/fw_env.config

Afterwards, check that the uBoot environment is found by printing the variables to screen using

fw_printenv

Remarks:

Since OpenWrt only runs in RAM at the moment, this is a temporary change. If you want to be able to access the uBoot environment from the OpenWrt rescue system later on, this step will most likely have to be repeated (see step 7 below).
If you would rather modify an existing file, you can do so using vim (which is pre-installed in OpenWrt). If, like me, you do not want to learn vim and prefer nano, you can instead do
```
  opkg update && opkg install nano  
```

6. Install to NAND

Finally, we can perform a sysupgrade of OpenWrt/LEDE either using the LUCI WIF (Web Interface) or the command line. Since we are already logged in via ssh, I only describe the latter option, while the former may be found, e.g., in step 4.b of Jörg's original post for the Kirkwoods. Before we start the upgrade process, however, we should remove all USB-drives to make sure that the reboot after the sysupgrade really does read from NAND.

We must do:

opkg update
opkg install ca-certificates
cd /tmp
wget 
sysupgrade

this upgrade file for the classic Pogoplug v3
this upgrade file for the Pogoplug Pro

The upgrade process will result in an automatic reboot.

7. Boot from NAND and log in to OpenWrt

It is, unfortunately, quite certain that OpenWrt in NAND also cannot find the uBoot environment (as before in the case of the image loaded into RAM). Therefore, you have to repeat step 5. above in order to be able to modify the uBoot environment. This time, it will be a permanent modification of /etc/fw_env.config allowing you to make changes to the uBoot environment using your new rescue system.

At least, this is the whole idea. But, unfortunately, while we can READ the environment now, trying to write something to it will yield the following result:

root@OpenWrt:~# fw_setenv testvar 'something'
Can't open /dev/mtd1: Permission denied
Error: can't write fw_env to flash

So, (as of August 15th, 2022) some additional work will be needed to make OpenWrt a viable option as a rescue system in connection with bodhi's uBoot.

8. Further configuration

Install nano (and more, if desired)
This step is completely optional, especially if you are happy to use vim. If not, do

opkg update
opkg install nano

Then you can use nano for the upcoming modifications (and opkg to install a bunch of additional packages, if you so desire).
Remark: Software installation may also be done via the LUCI WIF (see, e.g., the sibling thread for the Kirkwoods)

MAC-Address
Other than the Kirkwood boxes, the OXNAS' seem not to pick up the ethaddr from the uBoot-environment. This results in a randomly assigned MAC-address at each boot and therefore (usually) ia a different IP on the local LAN for the box after each boot - definitely undesirable. Therefore, we must make use of OpenWrt's config options (as explained fully in the documentation). There are two ways of achieving this:

Option 1: within the ssh-console

nano /etc/config/network

Modify this by specifying the MAC-address (option macaddr) of your box at the appropriate locations. This should look like:

config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'xxxx:yyyy:zzzz::/48'

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'eth0'
        # add option here
        option macaddr '00:25:31:xx:yy:zz'

config interface 'lan'
        option device 'br-lan'
        option proto 'dhcp'

config interface 'lan6'
        option device 'br-lan'
        option proto 'dhcpv6'

config device
        option name 'eth0'
        # add option here
        option macaddr '00:25:31:xx:yy:zz'

Option2: using LUCI WIF

You just open https:// in your webbrowser and press "Login". Then, navigate to "Network -> Interfaces" and choose the "Devices"-tab. Then press the "Configure ..."-button for both "br-lan" and "eth0" and input the MAC-address there.

Edit ubootenv
This is just for sanity, since OpenWrt also specifies the location of the uBoot-environment in the file /etc/config/ubootenv. This should for reasons of sanity reflect the values we also specified in /etc/fw_env.config and should therefore be modified to look like this:

config ubootenv
        option dev '/dev/mtd1'
        option offset '0xc0000'
        option envsize '0x2000'
        option secsize '0x2000'
        option numsec '1'

Unfortunately, this also does not yield a writeable uBoot-environment ...

9. Enjoy

Can openwrt be installed to and boot from USB? (13 replies)

pm4888 — Mon, 02 May 2022 16:01:58 -0500

For PogoE02 device.

NAS542 Bricked - boot loop (4 replies)

manticore — Wed, 23 Feb 2022 01:52:27 -0600

Hi,

I was tempted to upload a new image from debian from http://seafile.servator.de/nas/zyxel/images/
after uploading to the SD card debian-nas-bullseye-21.214-armhf.img.gz the system started correctly.
In the next step I did a kernel upgrade to linux-image-3.2.102-1-nas5xx-armhf.zip and unfortunately it did not work properly.
As recommended before rebooting, I ran the rollback routine sudo / firmware / sbin / info_setenv next_bootfrom 1
Errors have occurred and the NAS has restarted.

He has fallen into a noose since then and I cannot save him.
I tried:
- universal_usb_key_func-2015-10-12
- NAS540_521AATB3C0_Upgradekey
- I connected the serial port but the kosola only shows "bushes" and the NAS restarts.

I am asking you for help and suggestions.

manticore

openwrt on pogoplug pro v3 (12 replies)

echowarrior108 — Wed, 28 Oct 2020 11:16:30 -0500

I currently installed openwrt into nand from the openwrt website, I can post the link if anyone likes as it works well. Feel free to add to this:)

ZyXel NSA325 V1 - Erased NAND what now (2 replies)

vex88 — Sat, 20 Jun 2020 16:25:20 -0500

Hey all,

I was playing with fire and made a fundamental mistake with the command erase nand in uBoot. I am trying to write/flash the uBoot now, but I think I managed to brick it completely. When connected to Serial, I don't have any input options. Can someone confirm if it is possible to restore or if it is impossible at that point.

Thanks for any reply :)

Rescue System for Pogo V4/Mobile using OpenWrt (Install with NetConsole) (47 replies)

iSKUNK! — Thu, 07 May 2020 16:53:40 -0500

This post is the final installation instruction:

https://forum.doozan.com/read.php?4,100764,101409#msg-101409

=======

Hello,

I have a Pogoplug Mobile device (POGO-V4-A1-01) with SSH and telnet access enabled.

I would like to get rid of the original Pogoplug OS completely, and reflash the on-board memory with OpenWRT. However, I'd also like to have netconsole, and the ability to boot off a root filesystem on a USB drive. It is unclear that the U-Boot builds that OpenWRT provides have these capabilities, and in any event not only is their installation process not as well-documented as the ones here, their process assumes serial console access, which I do not have (not least since this would require soldering).

Would it be feasible to use bodhi's U-Boot together with an on-board OpenWRT image?

====
bodhi edit: I've changed the thread title to make it easier to search for. And point to the installation instruction inside this thread.

nsa325 v1 is bricked or dead. Serial and kwboot didn't work (5 replies)

phane — Wed, 25 Dec 2019 17:23:49 -0600

Hi.

I've got NSA235 v1 NAS from my friend. He didn't remember is it worked at all.

When I plug a power cord the NAS turns on HDD2 and power LEDs and starts spinning the cooler. But in 20-30 seconds power LED blinks and cooler stops spinning and then starts again.

I did my homework and read various topics regarding NSA325 unbricking. I tried to connect via serial console (I have prolific PL2303 USB adapter and the FTDI FT232RL one).

I downloaded uboot image and tried to load it.

kwboot  -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.nsa325.mtd0.kwb  -p

But no success - it shows only that:

Sending boot message. Please reboot the target.../

And never stops spinning.

Is anything can be done or NAS is completely dead?

OpenWrt on Pogoplug V03/Pro (24 replies)

shv — Sat, 19 Oct 2019 21:46:10 -0500

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.

HowTo: OpenWrt on Kirkwood boxes (54 replies)

chessplayer — Wed, 03 Dec 2025 07:02:41 -0600

chessplayer's edit (Aug 14th, 2022): Since there is obviously renewed interest in the subject starting, apparently, in June this year and there is now also a sibling thread for the OXNAS machines, some new insights have been gained (or resurfaced), which is why I am making some corrections and/or additions. Thanks go to many people for this, first and foremost, obviously, to bodhi, but also to daviddyer for his post from three years ago. This goes along with an apology for my dismissing his part A at the time, which now turns out to be essential, especially for the OXNAS, but apparently also for some of the Kirkwood boxes.

Another point is that I am removing all references to LEDE (which was the project's name for a brief period only, but it was during this period that the thread this tutorial is based on was written - this is how it crept in), since it does not have a place here anymore now (and should not have had when this HowTo was originally written).

My major changes will be reflected in dark blue.

========

How to install OpenWrt on Kirkwood boxes

This thread is a new version of one started by joerg_999 since I did run into a few problems with that one and I wanted to suggest a way which seems slightly easier to me and is also more general, since it is not restricted to Pogo E02. Also, I believe Jörg's post is missing a crucial step in connection with bodhi's uBoot. But, a big "Thank you!" goes to Jörg for his original post.

The procedure described in this thread is confirmed to work for Dockstar, GoFlexNet, GoFlexHome, Zyxel NSA325, ZyxelNSA320 (see the hints in steps 1. and 2. for these), Pogo v4 (see the link in bodhi's edit above as well as the hint in steps 1 and 5 for this box), and Pogo E02, so I am confident it will also work for the other Kirkwood boxes OpenWrt provides images for ;-)

Assumptions

I assume that the box in question has the latest uBoot and is able to boot a USB device with the latest kernel and rootfs according to the first two links in section Kirkwood plugs of the wiki.

Remark: The procedure described below also seems to work with older uBoots in connection with older kernels and rootfs, which I tested with a GoFlexNet.

However, it will be absolutely necessary to be able to reach the box via netconsole or serial console.

The plan

We now want to install OpenWrt on our box. The steps we will need to take are

Boot into debian, do some checks on and make some modifications to the uBoot environment variables
Download, rename and copy an OpenWrt Image to a FAT32 USB drive
Reboot the box without a USB device but with netconsole to interact with it and erase NAND <- this is crucial
Boot OpenWrt image from the USB drive created before
SSH into OpenWrt and make sure the uBoot environment is found <- this is crucial
Install to NAND via sysupgrade in OpenWrt
Boot from NAND and SSH into OpenWrt and make sure the uBoot environment is always found
Optionally apply some modifications to OpenWrt
Enjoy!

Implementation
So, let us look at these steps in more detail.

1. Modify uBoot variables

First, we need to boot the box to debian and log in. Then, we perform some checks and add to the environment.

1.a Check mtdparts definition

fw_printenv mtdparts

Expected output is

for most boxes (confirmed for Seagate's Dockstar, GoFlexHome, GoflexNet, Cloudengines Pogo E02):
```
  mtdparts=mtdparts=orion_nand:0x100000@0x0(u-boot),-@0x100000(ubi)  
```

for Cloudengines Pogo v4 (Mobile) (see bodhi's amendment)

  mtdparts=mtdparts=orion_nand:0x200000@0x0(u-boot),-@0x100000(ubi)

for Zyxel NSA32x:
```
  mtdparts=mtdparts=orion_nand:1M(u-boot),512K(uboot_env),512K(key_store),512K(info),10M(etc),10M(kernel_1),48896K(rootfs1),10M(kernel_2),-(rootfs2)
```
Important note: This must be changed on the Zyxels for the following to work, so if for some reason you need the above layout, you will have to figure out the necessary modifications yourself!

On these Zyxels, you should change that to
```
  fw_setenv mtdparts 'mtdparts=orion_nand:0x100000@0x0(u-boot),-@0x100000(ubi)'
```
(same as for Pogo E02 or the old Seagate boxes)

Remark: This might be true for other Zyxel boxes also, but those I do not have and cannot test on.

If the output is not as expected, make the appropriate modifications (as exemplified above for the Zyxels)!

1.b Add to uBoot environment

We then need to augment the uBoot environment as follows:

fw_setenv partition 'nand0,0'
fw_setenv set_bootargs_owrt 'setenv bootargs console=ttyS0,115200 $mtdparts'
fw_setenv bootcmd_owrt 'run set_bootargs_owrt; ubi part ubi; ubi read 0x800000 kernel; bootm 0x800000'

All the other variables can stay the way they were before, but we have to add the OpenWrt boot option to the bootcmd. If we still have bodhi's environment variables as they came, this would be:

fw_setenv bootcmd 'run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_owrt'

targets/kirkwood/generic

Then, download the uImage appropriate for your box. Rename it to uImage and place it in the root of a FAT32 formatted USB device.

Remark for Zyxel NSA320: Although the NSA320 is not officially supported by OpenWrt and they subsequently do not provide a uImage or sysupgrade for it, @kblayout over in the OpenWrt forum confirmed that this very HowTo also works for that machine (scroll to bottom of the linked post). All you will have to do is use the uImage and sysupgrade for the NSA325. I can confirm this - all five NSA320s I have at my disposal were flashed this way!

Hint: It makes sense to keep the browser tab open for the actual installation to NAND in step 6.

3. Interact with uBoot in (net)console

Then, we need to reboot the box without the debian USB device, but with a way of interacting with it, preferably via netconsole. The latter needs to be started on the server beforehand with

nc -l -u -p 6666

Wait until after a few error messages you see the prompt, e.g.

Dockstar>

in the console window.

Then, make sure OpenWrt lives in a clean environment by erasing the ubi partition:

nand erase.part ubi

4. Reboot to RAM with OpenWrt image

Insert the drive you created in step 2 into the box and boot it by issuing the following command at the (net)console prompt:

To get a correct mtd layout in OpenWrt, set_bootargs_owrt must be run before the bootm

usb reset; fatload usb 0 0x800000 uImage; run set_bootargs_owrt; bootm 0x800000

This should end with

Starting kernel ...

in the console output, meaning that OpenWrt is now running in RAM.

5. Log in to OpenWrt

Find the IP address of your box and ssh into it (user root without password). The following step is absolutely crucial (according to bodhi; see the first reply) in connection with bodhi's environment from the uBoot post, as I can tell from experience, since without it, I ran into problems when I first tried the procedure from Jörgs original post on a Dockstar (see my description there of how to remedy the issue if things have gone awry).

Verify your mtd layout, it should be:

root@OpenWrt:/tmp# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00100000 00020000 "u-boot"
mtd1: 07f00000 00020000 "ubi"

Or, in case of the Pogo v4 (mobile):

┌─[root@pogo-mobile]─[~]
└──> cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00200000 00020000 "u-boot"
mtd1: 07f00000 00020000 "ubi"

Temporarily generate or modify /etc/fw_env.config
Check whether the file /etc/fw_env.config has the following contents:

# MTD device name       Device offset   Env. size       Flash sector size       Number of sectors
/dev/mtd0 0xc0000 0x20000 0x20000

If not, or the file does not exist at all, the easiest way to generate/overwrite it is

echo '/dev/mtd0 0xc0000 0x20000 0x20000' > /etc/fw_env.config

Afterwards, check that the uBoot environment is found by printing the variables to screen using

fw_printenv

Remark: Since OpenWrt only runs in RAM at the moment, this is a temporary change. If you want to be able to access the uBoot environment from the OpenWrt rescue system later on, this step will most likely have to be repeated (see step 7 below).

6. Install to NAND

Finally, we can perform a sysupgrade of OpenWrt either using the LUCI WIF (Web Interface) or the command line. Since we are already logged in via ssh, I only describe the latter option, while the former may be found, e.g., in step 4.b of Jörg's original post. We must do:

opkg update
opkg install ca-certificates
cd /tmp
wget 
sysupgrade

The desired upgrade file may be found the same way as we found the image in step 2 above starting from the release page (but, ideally, you kept the browser tab open in step 2). There you can just copy the link address to the sysupgrade file (tar or bin depending on the release) and paste it into the ssh window.

Remark: For older releases of OpenWrt, there might be more you have to install. E.g., for 18.06.2, ca-bundle, libustream-openssl, and ubi-utils were needed as well.

The upgrade process will result in an automatic reboot (during which I removed the USB stick, but that may not be necessary).

7. Boot from NAND and log in to OpenWrt

It is, unfortunately, quite certain that OpenWrt in NAND also cannot find the uBoot environment (as before in the case of the image loaded into RAM). Therefore, you have to repeat step 5. above in order to be able to modify the uBoot environment. This time, it will be a permanent modification of /etc/fw_env.config allowing you to make changes to the uBoot environment using your new rescue system.

Remark: If ever you decide to do a sysupgrade later on, be it via LUCI WIF or ssh, be aware that you will most probably have to repeat this after the sysupgrade, since only the files in /etc/config seem to be saved and restored during the process!

8. Optional Modifications
Seeing that OpenWrt will most probably only serve as a last resort on these boxes, these modifications are entirely optional, of course. Nonetheless, some people may find them useful, so I thought I would include them in the updated post. All of these modifications can be done via the LUCI WIF and that is what I will describe here. Alternatively, it may be done directly by modifying the relevant files or using opkg via ssh, but whoever wants to do that may figure out themselves how to. The LUCI WIF is reached via

https://

Install additional packages
First, you should update the package lists in System - Software by klicking on the button Update lists .... Afterwards, you can use the Filter-box to find the packages you are looking for. One of those should be ca-certificates. Also, personally, I do not use vim and prefer nano, which I therefore installed.
Set MAC-Address
Should you experience the problem that OpenWrt does not respect the MAC address provided via uBoot or if you want to test something which requires a different MAC-address, you can achieve this by going to Network - Interfaces and navigating to the Devices tab, where you should set the MAC-address for both br-lan as well as eth0 to the desired value via the Configure ... button.
Remark: These changes will result in a different IP address to be assigned if you use DHCP, so when the confirmation pop-up appears, you will have to find out the new IP address in time and point your browser to that one for the changes to take effect! Otherwise, they will be rolled back!
Change hostname and Timezone
This can be done via System - System and making the appropriate modifications in the corresponding fields of the General Settings tab.
Dark Design
Also in System - System, you can navigate to the Language and Style tab and choose your design.
Remark: If you also want to be able to choose a different language, you first have to install the relevant language pack.

9. Enjoy

========
bodhi's edit: removed my notice about Pogoplug V4.

Bricked Pogo E02 after attempting OpenWRT install (6 replies)

Tom Cooper — Sat, 29 Jun 2019 15:38:17 -0500

A few years back, I attempted to install OpenWRT on my Pink PogoPlug E02. Something went wrong and it wouldn't boot again. I tossed it in a box and threatened to get back to it one day.

That day has come.
I hooked up the serial console and this is what I get:

U-Boot 2014.10 (Jul 24 2015 - 20:11:30)
Pogo E02

SoC:   Kirkwood 88F6281_A0
DRAM:  256 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Hit any key to stop autoboot:  3 ??? 2 ??? 1 ??? 0 
UBI: attaching mtd1 to ubi0
UBI: scanning is finished
UBI: attached mtd1 (name "mtd=3", size 126 MiB) to ubi0
UBI: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 512
UBI: VID header offset: 512 (aligned 512), data offset: 2048
UBI: good PEBs: 1006, bad PEBs: 2, corrupted PEBs: 0
UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
UBI: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 0
UBI: available PEBs: 0, total reserved PEBs: 1006, PEBs reserved for bad PEB handling: 18
** File not found /boot/zImage **
** File not found /boot/pogo_e02.dtb **
Unmounting UBIFS volume rootfs!
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr " command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr " command.
Aborting!
Bad Linux ARM zImage magic!
PogoE02>

The current environment is:

printenv
baudrate=115200
bootargs=console=ttyS0,115200 mtdparts=orion_nand:0xe0000@0x0(uboot),0x20000@0xe0000(uboot_env),0x100000@0x100000(second_stage_uboot),-@0x200000(root) ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs rw
bootargs_root=ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs rw
bootcmd=setenv bootargs ${console} ${mtdparts} ${bootargs_root}; ubi part root; ubifsmount ubi:rootfs; ubifsload 0x800000 ${kernel}; ubifsload 0x700000 ${fdt}; ubifsumount; fdt addr 0x700000; fdt resize; fdt chosen; bootz 0x800000 - 0x700000
bootdelay=3
cesvcid=xxxxxx
console=console=ttyS0,115200
ethact=egiga0
ethaddr=00:25:31:00:96:75
fdt=/boot/pogo_e02.dtb
ipaddr=192.168.1.43
kernel=/boot/zImage
mtddevname=uboot
mtddevnum=0
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:0xe0000@0x0(uboot),0x20000@0xe0000(uboot_env),0x100000@0x100000(second_stage_uboot),-@0x200000(root)
nand_erasesize=20000
nand_oobsize=40
nand_writesize=800
partition=nand0,0
serverip=192.168.1.117
stderr=serial
stdin=serial
stdout=serial

Environment size: 1066/131068 bytes
PogoE02>

I remember that some bad spots in the nand caused my problems...

PogoE02> nand info

Device 0: nand0, sector size 128 KiB
  Page size      2048 b
  OOB size         64 b
  Erase size   131072 b
PogoE02> nand bad

Device 0 bad blocks:
  01840000
  06520000
PogoE02>

I would like to install a current version of OpenWRT, if possible.
It seems like I'm not too far away from getting this back up.

I have the tftp server up and running. It seems I just need to flash the current stuff, but somehow deal with the bad blocks.

Can anyone point me in the right direction?
Thanks for any help.
Tom

OpenWrt installation failure (19 replies)

balanga — Thu, 06 Jun 2019 17:15:51 -0500

I followed this guideline
https://openwrt.org/toh/seagate/goflexhome

for installing OpenWrt on a GoFlex Home unit but unfortunately on reboot it didn't boot OpenWrt :( ...

NAS>> reset


<------> -- NAS EXPLORER --
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_.
| | | |___|  _ \ / _ \ / _ \| __|.
| |_| |___| |_) | (_) | (_) | |_.
 \___/    |____/ \___/ \___/ \__|.
 ** QSI BOARD: NAS-PLUG LE.

U-Boot 1.1.4 (Jun 10 2010 - 08:28:13) Marvell version: 3.4.27
QSI NAS version: 1.0.4

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFB00

Soc: 88F6281 A1 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz.

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 128MB.
DRAM Total size 128MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:256 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled.
Write allocate disabled

USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  3 ^H^H^H 2 ^H^H^H 1 ^H^H^H 0.

NAND read: device 0 offset 0x100000, size 0x600000

Reading data from 0x100000 --   0% complete.Reading data from 0x10f000 --   1% complete.Reading data from 0x11e800 --   2% complete.Reading data from 0x12e000 --   3% complete.Read
 6291456 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2010-06-17   5:37:59 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2095148 Bytes =  2 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC
NAS>> exit
Unknown command 'exit' - try 'help'
NAS>> ~
[EOT]

Any suggestions as to what happened or what to do?

Does this install require a particular U-Boot to be installed for it to work?

(Apologies if I've posted this in the wrong section)

NANDDUMP (3 replies)

balanga — Mon, 25 Feb 2019 16:46:22 -0600

I used to have a copy of nanddump but it has disappeared and can't seem to find a place to download it...

Following some code here https://openwrt.org/toh/seagate/goflexhome for doing a backup it says:

cd /tmp
mkdir backup
mount /dev/sda1 /tmp/backup
wget http://plugapps.com/os/pogoplug/uboot/nanddump
chmod +x nanddump
./nanddump -nf backup/mtd0 /dev/mtd0
./nanddump -nf backup/mtd1 /dev/mtd1
./nanddump -nf backup/mtd2 /dev/mtd2
umount /dev/sda1

but this no longer retrieves nanddump. Where can I get it? Preferably by wget http rather than wget https...

Remote reset for Pogoplug E02 or GoFlex Net? (5 replies)

lorenzo — Mon, 18 Feb 2019 14:52:19 -0600

(First time poster so don't hesitate to point me to existing ressources/posts that I may have missed when searching)

Hi all,

I'm planning to leave powered-on a PogoPlug E02 or a GoFlex Net (most likely the GoFlex net) in a second home.

In case something happens, I'll have a second machine (currently HP microserver, running VmWare ESX, with remote management card), that I could wake/power-on remotely, and then connect to the E02 or GoFlex, using the serial console.

My problem is how to 'reset' the board: I installed uBoot + Debian (on E02 but will look into GoFlex Net soon) and everything works well, however if the Linux kernel hangs for any reason, I don't know if I can remotely reset the board.

Currently, I'm power-cycling it by commanding a relay from the HP microserver, but wondering if something simpler could be achieved.

Therefore:
1. is it possible to reset through the serial connection?
2. is there some kind of hardware watch dog mechanism on the board (so that if kernel hangs, the watch dog will detect this and reset automatically the board) ?
3. would the JTAG/OpenOCD approach allow reset (I think so but never used JTAG yet) ?

All advices are welcome, thanks for your help!

JTAG wiring (1 reply)

balanga — Tue, 26 Jun 2018 13:07:00 -0500

I'm hoping to resurrect a bricked GoFlex Home dock using a Bus Pirate, but have never done anything like this before. My understanding is that I need to connect a cable between the Bus Pirate and the GFH unit, but I'm don't know which wires to connect to which pins.
Does anyone know where I can find a wiring diagram?

Restoring GoFlex Home Stock system (11 replies)

balanga — Thu, 07 Mar 2019 14:05:05 -0600

If I kwboot my GoFlex Home unit, which still has the original Stock firmware on it, can I backup the system to an external device and restore it if necessary?

OpenWrt on GoFlex Home (4 replies)

balanga — Sat, 02 Jun 2018 17:05:04 -0500

Apparently OpenWrt can be installed on a GoFlex Home unit....

Does anyone have experience of this and pointers about how to do this?