@treepleks,
Looking at your u-boot envs, I think you must have skipped this most important section:
iConnect original u-boot envs is at a different location than 0xC0000. If you are running Arch, the envs location is the same as the original one, and it is not 0xC0000.
So if you did ignore these requirements :), the only way to recover now is to connect a serial console. Connect serial console and I'll help get you running again.
Looking at your u-boot envs, I think you must have skipped this most important section:
Quote
This assumes that your plug has been installed with Jeff's official installation script. The official installation script does not cover iConnect and Netgear Stora. For these 2 boxes, u-Boot envs might have been defined at a different location. So note that fact and check your iConnect/Netgear Stora /etc/fw_env.config. If the envs are at a different location than 0xC0000, then I would recommend only flashing this new u-Boot for these 2 boxes if you have serial console working, as a precaution. After flashing U-Boot image, your original U-Boot envs will have to be re-entered manually again before rebooting.
1. uBoot envs config and mtd partitions are already define as followed:
cat /etc/fw_env.config
# MTD device name Device offset Env. size Flash sector size Number of sectors
/dev/mtd0 0xc0000 0x20000 0x20000
cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00400000 00020000 "uImage"
mtd2: 02000000 00020000 "rootfs"
mtd3: 0db00000 00020000 "data"
iConnect original u-boot envs is at a different location than 0xC0000. If you are running Arch, the envs location is the same as the original one, and it is not 0xC0000.
So if you did ignore these requirements :), the only way to recover now is to connect a serial console. Connect serial console and I'll help get you running again.