NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Can't resolve ERR: BAD FIRMWARE on NV+
My little 2007 NV+ is finally giving me fits after years of good use.
Here's the chronology. I was at work the entire time and did nothing manually.
At 7:08 AM the NAS alerted me of an SATA reset and recommended a resync
At 7:42 AM the NAS started a resync
At 12:18 PM the resync completed and declared redundant
At 1:07 PM the NAS alerted that the disk on channel 1 failed and was shutting down automatically in 30 minutes
At 1:08 PM the NAS alerted of a disk ADD event on channel 1
At 1:09 PM the NAS said disk initialization was successful
At 1:10 PM the NAS started a resync
At 5:19 PM the resync completed and was declared fully redundant
Once I arrived home that night I shut down the NAS and ordered a new drive to replace the failed (?) channel 1 disk. The new disk arrived and upon booting to replace it I was presented with ERR: BAD FIRMWARE on the front readout when I powered up.
I've tried resetting the firmware (5 sec on the reset button) with the original array in as well as booting once with each of the 3 disks in the array removed. (As in this thread: http://www.readynas.com/forum/viewtopic.php?f=7&t=76552) So far no luck. BAD FIRMWARE at every step.
My next step was to try a Boot Recovery via this method (http://www.readynas.com/kb/faq/boot/how_can_i_perform_a_boot_recovery_using_a_usb_flash_device) but I want to be 100% certain that it doesn't impact data on the array. I foolishly have not backed up the NAS in months so I'm exposed.
Will this leave my data unharmed?
If this failed, I was going to remove all 3 drives in the current array to keep my data safe, insert the new drive and perform a Factory Default.
Any advice appreciated!
Todd
Here's the chronology. I was at work the entire time and did nothing manually.
At 7:08 AM the NAS alerted me of an SATA reset and recommended a resync
At 7:42 AM the NAS started a resync
At 12:18 PM the resync completed and declared redundant
At 1:07 PM the NAS alerted that the disk on channel 1 failed and was shutting down automatically in 30 minutes
At 1:08 PM the NAS alerted of a disk ADD event on channel 1
At 1:09 PM the NAS said disk initialization was successful
At 1:10 PM the NAS started a resync
At 5:19 PM the resync completed and was declared fully redundant
Once I arrived home that night I shut down the NAS and ordered a new drive to replace the failed (?) channel 1 disk. The new disk arrived and upon booting to replace it I was presented with ERR: BAD FIRMWARE on the front readout when I powered up.
I've tried resetting the firmware (5 sec on the reset button) with the original array in as well as booting once with each of the 3 disks in the array removed. (As in this thread: http://www.readynas.com/forum/viewtopic.php?f=7&t=76552) So far no luck. BAD FIRMWARE at every step.
My next step was to try a Boot Recovery via this method (http://www.readynas.com/kb/faq/boot/how_can_i_perform_a_boot_recovery_using_a_usb_flash_device) but I want to be 100% certain that it doesn't impact data on the array. I foolishly have not backed up the NAS in months so I'm exposed.
Will this leave my data unharmed?
If this failed, I was going to remove all 3 drives in the current array to keep my data safe, insert the new drive and perform a Factory Default.
Any advice appreciated!
Todd
5 Replies
Replies have been turned off for this discussion
- Can you power down, remove your disks (label order), connect your disks to your PC and test them e.g. using SeaTools to test SeaGate disks? It's possible you may have more than one bad disk.
A factory default with just a spare disk (must not be from your array) is a good way to help isolate where the problem is. - The NAS works just fine with a spare disk.
I'm on a Mac so no access to SeaTools to check the 3 in my array. Are there alternatives? Will Smart Utility (http://www.volitans-software.com/smart_utility.php) work for purposes of diagnosing the problem?
Thanks, mdgm! - O.K. So it sounds like the problem is with the disks or other hardware.
Boot Recovery won't help if the internal flash is fine (which it sounds like it is).
Checking the SMART stats on the disks can be useful, not as good as running e.g. SeaTools, but the next best thing. - I'll see if I can't snag a PC from work to run SeaTools.
What might next steps be if the disk (or -eek- disks) are bad? What if they are all fine?
Todd - Either way you may wish to consider an initial diagnostics data recovery contract if your data is important to you.
Trying to fix the problem yourself may just make things worse.
Checking the disks using non-destructive tests should be fine though.
Do note that one of your disks may appear to your computer to be unformatted. It is not. Do not let your computer wipe it.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
