Forum Discussion

Aspirant

Sep 03, 2015

Solved

Unable to FW update

I have this same problem when attempting to upgrade from 6.2.5 except that if I power cycle the box, it reboots in 6.2.0. What can I do to upgrade to the latest FW since 6.2.0 on my box has issues wi...

Installation & Upgrade

jzeevi
Sep 04, 2015
Using a tip from JennC about trying to update manually, instead of through the web interface, I was able to point at the 6.2.5 zip file, run the update and reboot.

After a few minutes of activity on the NAS, it came up indicated 6.2.5 is now the FW level.

Thanks to JennC and mdgm for their support on this.

Now on to functional testing! (Can I actually copy large amounts of data to/from the NAS? - which was the lockup problem before SW upgrades last year).

josef

jzeevi

Aspirant

Sep 03, 2015

Additional info: in the kernel log, around the time of the reboot, I found this:

mvSFlashInit ERROR: Unknown SPI flash device!
Sep 01 15:46:24 JZNas kernel: ERROR: sflash_probe - Failed to initialize the SFlash.
Sep 01 15:46:24 JZNas kernel: armada-nand armada-nand.0: Initialize HAL based NFC in 8bit mode with DMA Disabled using BCH 4bit ECC
Sep 01 15:46:24 JZNas kernel: NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)
Sep 01 15:46:24 JZNas kernel: Bad block table found at page 65472, version 0x01
Sep 01 15:46:24 JZNas kernel: Bad block table found at page 65408, version 0x01
Sep 01 15:46:24 JZNas kernel: mtd: no mtd-id

in the FWBroker.log, there are several entries indicating that 6.2.5 is being looked at, but no indication (that I can tell :-)) of what it's doing with that info.

I'm sure there's other important details int he logs, I just am not familiar enough with the files to know.

josef