I can recover to the wrong F_TS-X53_20140916-1.2.8.img (and even upgrade that to the latest firmware for the F_TS-X53_). But Qnap won’t continue the setup because it will never detect my drives (I can go into the console and type cat /proc/scsi/scsi and it will list the drives I inserted, so I know the hardware is ok).
So I need to cross-upgrade back to the correct F_TS-X53U_ firmware. But Qnap Finder won’t let me cross upgrade as it detects the new firmware (X53U) is not the same branch as the old (X53) firmware. And when I try to cross upgrade from the web ui of the latest QTS 5.2.3.3006 for TS-X53 Pro, I get the message: “Update failed. Please check the firmware version.”
Any way to override this check and force install the correct firmware for my TS-1253U-RP?
I couldn’t get it to work when using your link because I get an error about not having /mnt/update and I don’t have initialized disks in the NAS. So I followed the instructions at Manually updating the firmware | QNAP
It didn’t block me from the cross-grade, and there were no errors until the end of the install:
Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
Update Finished.
BusyBox v1.24.1 (2025-01-08 02:15:39 CST) multi-call binary.
Usage: dirname FILENAME
Strip non-directory suffix from FILENAME
/bin/cat: /mnt/update/newver: No such file or directory
Default volume not found.
The NAS was unusable after that, so I recovered to the wrong F_TS-X53_20140916-1.2.8.img again (because the F_TS-X53U_20141125-1.2.8.img on Qnap’s server is corrupt), made both /mnt/update and /mnt/update/newver before performing the upgrade, but at the end, it still gave the error about /mnt/update/newver.
Any more ideas on how to get around the /mnt/update/newver problem?
It’s too bad Qnap won’t simply correct the corrupt F_TS-X53U_20141125-1.2.8.img on their server… now I need to do all these additional steps to try and get it to work when it could have been much simpler!