Hi!
I recently aquired for just a few € a Pogoplug V3 (POGO-P24). It had been modified in an unknown way, but I managed to use the serial console to remove some strange static IP configuration and reset the SSH password so that I now have SSH access.
I tried to boot the rootfs from 17 May 2020 but it didn't work (I didn't try to find out why because this wasn't a priority).
Then I tried to proceed to install uBoot following the great instructions provided in these forums. However, when checking the contents of proc/mtd I found the following:
Also, am I right to assume that bad blocks should pose no problem?
I recently aquired for just a few € a Pogoplug V3 (POGO-P24). It had been modified in an unknown way, but I managed to use the serial console to remove some strange static IP configuration and reset the SSH password so that I now have SSH access.
I tried to boot the rootfs from 17 May 2020 but it didn't work (I didn't try to find out why because this wasn't a priority).
Then I tried to proceed to install uBoot following the great instructions provided in these forums. However, when checking the contents of proc/mtd I found the following:
/tools # cat /proc/mtd dev: size erasesize name mtd0: 08000000 00020000 "NAND 128MiB 3,3V 8-bit" mtd1: 00e00000 00020000 "boot" mtd2: 07200000 00020000 "rootfs"Should it be safe to proceed? I think I managed to backup there mtd but I cannot backup current envs (fw_printenv returns a memory allocation error and blparam is nowhere to be found).
Also, am I right to assume that bad blocks should pose no problem?
<6>[ 1.670000] Scanning device for bad blocks <4>[ 1.710000] Bad eraseblock 653 at 0x0000051a0000 <4>[ 1.740000] Bad eraseblock 954 at 0x000007740000Thanks!