As my BIOS displayed a fancy "splash screen" instead of the boot information that is quoted in the Recovery article, I again could not see, that the DOM wasn´t even recognized. I followed the QNAP Wiki: Firmware Recovery (x86) guide and attached keyboard and monitor to the NAS. Because I had no monitor attached to the NAS at this point, I did not recognize that the DOM was not even visible as a boot device in system BIOS. I thought, the data on the DOM was corrupted during firmware update and tried to fix this, as the NAS just went out of warranty a month before (as always.).
Restart without HDD installed also failed (ex post: obviously). This was because of a broken DOM module, but I did not know at this point. build 20170606 the process exited with error code 999 - Execute Update Image Failed (see QNAP Wiki). Prehistory - Why I had to do this: During the firmware update from 4. I´ve really put some effort into this document in order to spare you guys the time I spend figuring this out and the money for unnecessary replacement hardware, but of course: I take absolutely no responsibility for anything you do while following this guide! Only do this, if your device is out of warranty and you are out of other recovery options! Otherwise contact QNAP support and refer to the official BIOS recovery guide in the QNAP Wiki. If you are an electronics expert and have specific flashing hardware using SPI technology available you may use this instead. This HowTo document features the use of a Raspberry PI to do the actual BIOS flashing.
Hi, I´m pretty proud of myself right now, because I could save my TS-651 mainboard after QNAP support stated this was impossible and a mainboard replacement was the only option left.
0 kommentar(er)
