[RESOLVED] update-oxnas Script Failing @ NAND MTD Erase

[bgulla]

One of my pros doesn't want to upgrade to the new kernel via warhead's update-oxnas.sh script. I have followed the directions to a T and even tried the .nopci and .pci versions and neither of them will work. After this fail, I am able to boot to a fresh 05 tarball but not the latest. If I pacman -Syu after running the script, I am unable to reboot.

The Badness (some output for update-oxnas.sh)
$this->bbcode_second_pass_code('', 'Copying if necessary...
Placing updates...
Depmod...
WARNING: could not open /lib/modules/2.6.31.6_SMP_820/modules.builtin: No such file or directory
Flashing Kernel to slot A...
Erase Total 20 Units
Performing Flash Erase of length 131072 at offset 0x540000
MTD Erase failure: Input/output error
Writing data to block 40 at offset 0x500000
Writing data to block 41 at offset 0x520000
Writing data to block 42 at offset 0x540000
Bad block at 540000, 1 block(s) from 540000 will be skipped
Writing data to block 43 at offset 0x560000
Writing data to block 44 at offset 0x580000
Writing data to block 45 at offset 0x5a0000
Writing data to block 46 at offset 0x5c0000
Writing data to block 47 at offset 0x5e0000
Writing data to block 48 at offset 0x600000
Writing data to block 49 at offset 0x620000
Writing data to block 50 at offset 0x640000
Writing data to block 51 at offset 0x660000
Writing data to block 52 at offset 0x680000
Writing data to block 53 at offset 0x6a0000
Writing data to block 54 at offset 0x6c0000
Writing data to block 55 at offset 0x6e0000
Writing data to block 56 at offset 0x700000
Writing data to block 57 at offset 0x720000
Writing data to block 58 at offset 0x740000')

warhead said "If it is indeed "screwed up" that will be fine, as I keep 2 copies in NAND for just this case.", but I am unsure about what I need to do moving forward. any help?

[WarheadsSE]

Alright, then it looks like it is indeed falling back to "slot B" kernel in u-boot. This is a good thing

You will need to tweak your uboot's bootcmd line to use load_custom_nand2 vs load_custom_nand, and then have it write the new kernel to "slot B".

Do you have a working blparam ?

$this->bbcode_second_pass_quote('WarheadsSE', 'D')o you have a working blparam ?

[WarheadsSE]

Actually, assuming you have a working blparam or not, in the end shouldn't matter, but might *slightly* decrease boot time by not trying to load the kernel from the bad spot in nand.

You simply need to change your script to alter the write address, (B00000 vs 500000) as you will see by simply running blparam and reading the load_custom_nand2 (it contains the address). Do not botch this, just change '5' to 'B' in the script, for both erase & write.

[bgulla]

BOOM. donated.

[WarheadsSE]

[fuchini]

Hello, was having this same problem and just fixed thanks to this. Changing "5" to "B" was enough.

Thanks a lot WarheadsSE.