Firmware update 6.9.0 broke my backup

We are looking into this. We've already made some changes in our development of 6.9.1, but more may be needed.

We don't recommend downgrading from 6.9.0. In a major update we do make some changes that are not designed to be rolled back.

Once 6.10.0 is released 6.9 will enter LTS mode and will only receive bug fixes and security updates.

Running 6.9.1 firmware. Two days while still running 6.9.0 the system began sticking at boot up, showing "Failed to boot from USB" even though I was not attempting to boot from USB, but instead booting normally according to scheduled power up/down settings. By unplugging and leaving unplugged for a few minutes, I was able to get it to boot normally and update to 6.9.1. The "Failed to boot from USB" error did not recur this morning when the unit automatically booted up according to automated power setting, but I am getting an endless (3 hours and counting) "Backup button job is in progress" message, even though no backup job is scheduled or should be running. Upon manually restarting the system from the admin page, I was dropped from the admin page and the unit once again returned to the "Failed to boot from USB" status. The only way to get beyond that failure was to manualy unplug the power and wait 15 seconds before plugging back in (once I plugged back in within 2 seconds and the failed status resumed immediately). I've read through this, and other related, threads that are less than three years old. I have not used the backup button, and when manually rebooting checked to make sure it was not stuck and otherwise pressing in/out correctly. This unit has run flawlessly since February 2014. I would say there was a software error relating to the backup button in 6.9.0, and 6.9.1 has not successfully corrected that error. Since the unit otherwise seems to run correctly, and I have access to the data on it with no apparent problems, I'm going to stick with the status quo. I would appreciate, though, if Netgear could get this problem corrected quickly, since it has clearly been identified by a number of users on these pages, and take more care to test the updates before rolling out in the future. Clearly this was a 6.9.0 issue that 6.9.1 was meant to correct, but instead only made it worse.