NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

RNASguy's avatar
RNASguy
Luminary
Aug 22, 2012

Firmware upgrade fail #19255699

Had a fail when I attempted to update firmware from 4.1.8 to 4.1.9 as follows:

Issue with Firmware update for:
ReadyNAS Duo serial # 24M3037701D1A
This chassis was replaced on March 21, 2012 under warranty on RMA # 1086906

Problem:
NAS was running fine and I rec’d an email that there was a firmware update available to 4.1.9 I then downloaded the update to a folder on one of my networked computers. On the NAS dashboard I went to the update tab and browsed to the downloaded 4.1.9 file. And clicked update. I rec’d a message that I needed to reboot the NAS to complete the update.

After the reboot I rec’d an email that said:

“Firmware update failed verifying flash.”

The NAS was NOT accessible over the net. I forced a shutdown by holding down the power button, and then did a reboot. On reboot the blue power button does a slow blink On-Off, and the both drive lights blink On-Off. I then did a forced shutdown again.

What next.

28 Replies

Replies have been turned off for this discussion
  • One further note on this issue:

    The Putty telnet client when connecting to the NAS box in tech support mode did not report anything. But, I tried a different client called Absolute Telenet from:
    celestialsoftware.net

    It reports a successful connection, but there is still no log on prompt.

    bc
  • I have updated the case file.

    The network will be up until 9pm today Pacific Time.

    bc
  • Ok, so here is an update on the saga of the failed firmware up date:

    Spent three hours with tech support level 2. Tech came to the conclusion that the flash mem chip was bad. I was doubtful about this as failure occurred only when the firmware update was applied. But, it could be, as the update may be larger and write to areas on the flash that were not accessed before.

    A recap of what we did: a USB flash drive boot (4th flash on the boot menu for the Duo v1). The box came up and was accessible. But, without the USB drive resident, it would not boot. That concluded my tech support call, ending with the idea that the flash chip was bad.

    We (the tech and I) were using Rawrite32 to create the image on the USB thumb drive. I was using the 4.1.9 firmware as located here:

    http://www.readynas.com/download/RAIDiator/RAIDiator-4.1.9

    The tech told me that it didn’t really matter that we were using 4.1.9 and 4.1.8 was the original version on the box. And, I was told that the box would copy over the 4.1.9 to the internal flash, if it could. Well, once it came up Frontview showed it was running on 4.1.8 not the .9 that was on the USB drive. And, when we pulled the USB drive and did a reboot it failed.

    So after the call I tried to find a copy of 4.1.8, to try a USB boot with that version. But I could not find one on an official site. (Don’t trust other unknown downloads.) But, what I did find was an image copy of 4.1.8 that was really a different file than what we originally tired. It is located here:

    http://www.readynas.com/download/support/ReadyNAS_USB_Flash_Recovery-4.1.8.img

    I then burned this to the USB drive using Rawrite32. Behavior was entirely different. It booted up and ran for awhile then shut down. This is just what the kb article sez at:

    http://www.readynas.com/kb/faq/boot/how_can_i_perform_a_boot_recovery_using_a_usb_flash_device

    So after it shut down I pulled the USB drive and attempted a boot. It failed. So I did the USB boot again. This time after the shut down that is built into the img file, I did normal boot up and left the USB drive in place. I let it cook for long while till the box showed no activity. I then did a normal shutdown, pulled the USB drive out and did a boot. It came up normal like nothing had ever happened. Frontview reports no issues and it is running on 4.1.8.

    At this point I am reluctant to shut it down, and even more so I am reluctant to try an update to 4.1.9.

    I have a second Duo, and I am reluctant to try an update to 4.1.9 on that box.

    At this point I’m thinking of moving to a RNDP600U (Ultra 6 plus), and just leave the older boxes behind. BUT, if anyone knows anything about the flash chip I could play with it (it is out of warranty) and try a new flash mem chip on the board.
  • Well, here's an update on the update:

    I got brave, and since it seemed that I could boot the box off USB if it failed, I did a normal shut down. I did a boot up and ... guess what... it came up normal.

    So... what is really going on here... If it was bad flash, why does it boot normal, now, with out the USB drive. I still won't try a 4.1.9 update.... don't trust it.

    bc
  • mdgm-ntgr's avatar
    mdgm-ntgr
    NETGEAR Employee Retired
    Yes the USB Boot Recovery image is a special image designed to write the firmware to the flash.

    The problem could be that the flash is failing or perhaps failing memory (have you tried running the memory test a few times?. See http://www.readynas.com/kb/faq/hardware/is_there_a_way_i_can_verify_if_my_memory_is_good and http://www.readynas.com/forum/viewtopic.php?f=11&t=26993)

    A possibility is that some sectors on the flash may have failed. When the firmware was flashed using the USB Boot Recovery these sectors would have been ignored as they were reallocated and future firmware updates hopefully would work fine.

    I wouldn't update to 4.1.9 due to an ownership issue. I'd either wait for 4.1.10 or try 4.1.10 beta (http://www.readynas.com/forum/viewtopic.php?f=17&t=59222) if you want to upgrade.
  • re: mem test. When these boxes were installed I upgraded to 1GB on both. At that time I ran the memtest about 10 times on each box. I have not done that since this update issue. But, thanks for the suggestion. Does that also test the flash chip, or as I thought just test the RAM memory. I'll run it a few times in any case and report back if it shows any issue.

    bc
  • mdgm-ntgr's avatar
    mdgm-ntgr
    NETGEAR Employee Retired
    It just tests the RAM. RAM is unlikely to be the issue as USB Boot Recovery worked but still worth a check.

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More