For anyone interested, these mods were accomplished on my QNAP TS-470 Pro by following the guides here, and well as another level1techs forum detailing how to use the UEFI BIOS Updater. Edit: The reason I didn’t link it is because new accounts are limited to only 2 links, and the other is below.
The trick was getting my hands on the QNAP BIOS file as they don’t like giving those files out, so I was able to find a BIOS file on a support forum for its bigger brother, the TS-670 Pro. Since they use almost the same (if not the same) mainboard, it works. Please note that this file will only work for revision 1.x of those motherboards.
Sigh. Since this is a new account, I guess I can’t upload a zip file, so instead I hosted it here. To flash this particular BIOS file, just make a FreeDOS bootable USB drive using Rufus, then add the unzipped files into the drive. Once FreeDOS is loaded on the NAS at startup, just execute the batch file. Good luck!
Hi there Glassman,
I too have a TS-470 Pro and was wondering about NVMe support. Apart from the BIOS update, how did you physically attach the SSD?
The thread goes back 8 years, and I’m not sure I can follow all the different issues and problems people got, but don’t just want to jump straight in flashing a new version of the BIOS. I need to understand what the risks are, can I get back if it all fails, and is there a risk to my current RAID.
Any insight you can give would be most appreciated
Sorry. I actually never saw an email regarding this and only came across the post when I went back onto my old laptop. One of the tabs was still open …
I attached the SSD from buying an NVME PCI-express adapter and installing it. Something like this …
That particular card is a little long for the NAS itself, so I just cut like an inch off the end with a pair of scissors, which is fine because there are no traces in that area, but if you don’t want to do that, just find a shorter one.
Also, yes, you can lose your data if you’re planning to boot something like proxmox or truenas in place of QTS. If you do that, the best thing you can do is plug in a spare drive and backup all your data from your raid with rsync first. Even if you’re just using your new card to host spare drives, backup your data anyway, because there’s always a chance that something can happen during a BIOS update, no matter how safe.
That being said, what do you have to lose? QTS is unsupported on your model now, and the performance is abysmal anyway … always has been.
The guide is here…as you properly already know and that all users should take a deep reading, both modules have the same function, only matters what bios volume available space can handle, for insertion, hence the 2 sizes of the module.
It’s advisable, as stated in the guide, that the user does the proper backups and safeguards for maintaining his system capable of recovering.
I downloaded MMTool V.3.26 and MMTool Aptio 5.02.0024 Mod from https://www.bios-mods.com/, but unfortunately, I can’t open my BIOS QC32AR23.bin file, even after renaming it to *.rom. I get the error message “Error Loading Firmware Image (1h)”. This is the last BIOS I flashed onto my TS 470 Pro, and it works, but unfortunately, it doesn’t support NVMe.
With UEFITool 0.28.0.win32 I can open the *.bin file, but I don’t know which Unicode text “Dxe” in the message I should click to edit it. I’m old and gray (65), but maybe someone can still help me out. Thanks to the moderator for reading my request.
Sir… it’s very well documented in the previous linked guide, i emphasized the term “deep reading”…
Your bios engine is based on AMI Aptio IV Core, if not mistaken…you should use MMTool_4.50.0023 or MMTool_5.00.0007, not higher, do please follow the guide orientation.
Tip: Do a Google search for “MMTool Aptio 4.50.0023” or “MMTool Aptio 5.00.0007”, join the listed TweakTown site, scroll down to the “AMI (UEFI) BIOS Tools” section and download the desired tool.
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at [no address given] to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
One more question: Both programs “MMTool Aptio 4.50.0023” and “MMTool Aptio 5.00.0007” save the file as *.fd. Is it then correct that I rename the file back to *.bin so that I can flash it?
Hi, after much head-scratching, I flashed my motherboard. My last question for now: do I still need a Samsung 950 Pro, or should the flashed BIOS (NvmExpressDxe_Small.ffs) work with NVMe without a special BIOS?
