I just need a little help or clarification. I've got a Pogo-E02 that I've installed Jeff's uBoot successfully. Although I'm currently not boot and running an OS off a USB drive, I'd like to play with the pogoplug services and try to mount the /dev/mtdblock3 partition to install optware.
I have done this successfully, but only with a stock un-altered Pogo-E02, following Aaron Randalls notes at this page.
http://aaronrandall.com/blog/customising-your-pogoplug/
I understand (I think) that Jeff's uBoot script does a backup of the original uBoot somewhere but I really don't care or need the original uBoot image.
Does anyone know if Jeff's script does something to the mtdblock3 partition or why I can't seem to use it have the uBoot install? Would I just need to completely revert back to stock? I don't see why I couldn't keep Jeff's uBoot image and just scrape the original one.
When I try to mount /dev/mtdblock3..
Pogoplug:/$ mount /dev/mtdblock3 /opt
mount: mounting /dev/mtdblock3 on /opt failed: Invalid argument
Any help or advice would be appreciated.
Here is some current stats of the Pogo-E02
Pogoplug:/usr/sbin$ cat /proc/partitions
major minor #blocks name
31 0 1024 mtdblock0
31 1 4096 mtdblock1
31 2 32768 mtdblock2
31 3 93184 mtdblock3
Pogoplug:/usr/sbin$ cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00400000 00020000 "uImage"
mtd2: 02000000 00020000 "root"
mtd3: 05b00000 00020000 "data"
Pogoplug:/usr/sbin$ ./fw_printenv mtdparts
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)