Hi guys!
Yesterday night I tried to update u-boot on my NSA325v2 with stock firmware.
I followed all of the instructions until the step 8.b and I forgot to do the step 8.c:
Luckily I saved my mtd0 and the environment at step 3:
The problem is that I stored the last files in the hard drive of the NAS (configured in RAID 1).
Finally at step 8.f, thinking to still reboot with the stock firmware, I used
Now, the NAS doesn't boot, but I have an active serial console.
How can I boot the stock firmware (preserving the new u-boot to install debian in future)?
If I boot the stock firmware I will be able to access to the environment file stored on it and set the right mtdparts and ethaddr.
Thank you for help!
Ivan
Yesterday night I tried to update u-boot on my NSA325v2 with stock firmware.
I followed all of the instructions until the step 8.b and I forgot to do the step 8.c:
fw_printenv > current_envs.txtI went on until:
Quote
bodhi
Then for all boxes, restore these 2 envs using the saved envs text in step c (replace xxx with the real saved values)
fw_setenv mtdparts 'xxxxxxxxx' fw_setenv ethaddr 'xx:xx:xx:xx:xx:xx'
Luckily I saved my mtd0 and the environment at step 3:
Quote
bodhi
Dumping NAND mtd0:
nanddump --noecc --omitoob -l 0x80000 -f mtd0 /dev/mtd0Save envs:
fw_printenv > current_envs.txt
The problem is that I stored the last files in the hard drive of the NAS (configured in RAID 1).
Finally at step 8.f, thinking to still reboot with the stock firmware, I used
fw_setenv dtb_fileand rebooted the NAS.
Now, the NAS doesn't boot, but I have an active serial console.
How can I boot the stock firmware (preserving the new u-boot to install debian in future)?
If I boot the stock firmware I will be able to access to the environment file stored on it and set the right mtdparts and ethaddr.
Thank you for help!
Ivan