Hi,
i may be able to provide you with the contents of the mtdparts as well
After several year of using Archlinux on one NSA-325 V2 (nicknamed A) and keeping another one in stock (nicknamed B), I plan to give away both.
I have exploited the information provided by Bodi in the the post
"Backup and Restore NAND mtds - Pogoplug V4 original MTD partitions"
https://forum.doozan.com/read.php?3,29362,29392
I would like your comments on the steps I plan to follow
1/ enable rsh on B
2/ using PuTTY, log into B as admin
3/ verify the size of Partitions
$this->bbcode_second_pass_code('', 'cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00020000 "uboot"
mtd1: 00080000 00020000 "uboot_env"
mtd2: 00080000 00020000 "key_store"
mtd3: 00080000 00020000 "info"
mtd4: 00a00000 00020000 "etc"
mtd5: 00a00000 00020000 "kernel_1"
mtd6: 02fc0000 00020000 "rootfs1"
mtd7: 00a00000 00020000 "kernel_2"
mtd8: 02fc0000 00020000 "rootfs2"')
4/ verify can write to public folder on first drive
$this->bbcode_second_pass_code('', 'ls /i-data/1c4ced0b/autre/')
5/ dump the content of each partition
I have a question : should I use the options --omitbad and -l 0x80000 ??
It seems the option --noecc is not available
$this->bbcode_second_pass_code('', './sbin/nanddump --omitoob -f /i-data/1c4ced0b/autre/mtd0 /dev/mtd0
./sbin/nanddump --omitoob -f /i-data/1c4ced0b/autre/mtd1 /dev/mtd1
./sbin/nanddump --omitoob -f /i-data/1c4ced0b/autre/mtd2 /dev/mtd2
./sbin/nanddump --omitoob -f /i-data/1c4ced0b/autre/mtd3 /dev/mtd3
./sbin/nanddump --omitoob -f /i-data/1c4ced0b/autre/mtd4 /dev/mtd4
./sbin/nanddump --omitoob -f /i-data/1c4ced0b/autre/mtd5 /dev/mtd5
./sbin/nanddump --omitoob -f /i-data/1c4ced0b/autre/mtd6 /dev/mtd6
./sbin/nanddump --omitoob -f /i-data/1c4ced0b/autre/mtd7 /dev/mtd7
./sbin/nanddump --omitoob -f /i-data/1c4ced0b/autre/mtd8 /dev/mtd8')
6/execute fw_printenv
$this->bbcode_second_pass_code('', './zyxel/sbin/fw_printenv
bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=/dev/nfs rw init=/init
bootcmd=nand read.e 0x2000000 $(kernel_addr) 0xA00000; bootm 0x2000000
bootdelay=2
baudrate=115200
loads_echo=0
ipaddr=10.4.52.165
serverip=10.4.52.7
rootpath=/srv/ubuntu
netmask=255.255.255.0
nandEcc=1bit
kernel_addr=C80000
MODEL_ID=AE03
PRODUCT_NAME=NSA-325v2
FEATURE_BIT=00
CONTRY_TYPE=FF
VENDOR_NAME=MitraStar Technology Corp.
run_diag=yes
ethaddr=xx:xx:xx:xx:xx:xx
root@NSA325:')
I am quite surprise to see the IP address for ipaddr and serverip
7/ using PuTTY, log into A as root
8/ transfer the files to A
9/ verify the partitions match the earlier one
$this->bbcode_second_pass_code('', ' cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00020000 "uboot"
mtd1: 00080000 00020000 "uboot_env"
mtd2: 00080000 00020000 "key_store"
mtd3: 00080000 00020000 "info"
mtd4: 00a00000 00020000 "etc"
mtd5: 00a00000 00020000 "kernel_1"
mtd6: 02fc0000 00020000 "rootfs1"
mtd7: 00a00000 00020000 "kernel_2"
mtd8: 02fc0000 00020000 "rootfs2"')
10/ Check that ther are no bad blocks
$this->bbcode_second_pass_code('', 'dmesg | grep -i bad')
11/ install nandwrite and fw_printenv
$this->bbcode_second_pass_code('', 'pacman -S mtd-utils uboot-tools')
12/ verify nandwrite is where it is expected
$this->bbcode_second_pass_code('', 'ls ./usr/bin/na*
./usr/bin/named-journalprint ./usr/bin/namei ./usr/bin/nanddump ./usr/bin/nandwrite
./usr/bin/named-rrchecker ./usr/bin/nameif ./usr/bin/nandtest ./usr/bin/nano')
13/ verify fw_printenv is here it is expected
$this->bbcode_second_pass_code('', 'ls ./usr/bin/fw_printenv
./usr/bin/fw_printenv')
14/ edit the fw_configuration file and append 2 lines
$this->bbcode_second_pass_code('', 'nano ./etc/fw_env.config')
$this->bbcode_second_pass_quote('', 'N')AS325
/dev/mtd1 0x0 0x20000 0x20000