bodhi, I decided to check bodhi's corner and I like the 'buy a virtual beer' idea. I just made a donation to MSF (Medecins Sans Frontieres/Doctors Without Borders). You do so much here(sharing knowledge), this is the least we can do.by normc - Debian
Well, oK, one more to this thread. The instructions that you wrote for upgrading u-boot and Debian on the Pogo E02 are 100% perfect and this exercise was a total success. root@pogoplug:~# uname -a Linux pogoplug.home.arpa 5.14.9-kirkwood-tld-1 #1.0 PREEMPT Sat Oct 2 17:41:27 PDT 2021 armv5tel GNU/Linux Another satisfied customer.... :)by normc - Debian
> Please get these info, to be sure that you are ready: bodhi, The same bad block is reported in dmesg: root@pogoplug:~# dmesg | grep -i bad [ 10.012571] Scanning device for bad blocks [ 10.055596] Bad eraseblock 326 at 0x0000028c0000 root@pogoplug:~# cat /proc/mtd dev: size erasesize name mtd0: 00100000 00020000 "u-boot" mtd1: 00500000 00020000 "uImage&quby normc - Debian
Quotebodhi Regarding flashing u-boot with the bad blocks, you can check to see if it in the gaps (unused blocks). Hey bodhi, You got me thinking with your comment. If I understand correctly, you think that there is a possibility that I could still flash a new u-boot successfully? I know it is risky but based on the report below and the address of the bad eraseblock, can you easily identifyby normc - Debian
I recently found my old pink Pogoplug E02 (very old version of Debian) and I decided to play with it to see if I could bring it up to a more recent Debian. I followed the instructions in this forum from a number of new and older posts. Unfortunately, because of a report of a bad block on my device, I decided not to upgrade the u-boot as per the warning. ## If you have bad blocks on mtd0, youby normc - Debian