QNAP NAS users locked out after firmware update snafu Owners of QNAP network-attached storage (NAS) boxes are finding that a firmware update has left them unable to log into their device, and a reset doesn't seem to fix the issue. The Taiwan-based storage biz specializes in NAS kit and offers a whole portfolio of models to address various needs. However, users are complaining of …
"We recently released the QTS 5.2.2.2950 build 20241114 operating system update and received feedback from some users reporting issues with device functionality after installation.
"In response, QNAP promptly withdrew the operating system update, conducted a comprehensive investigation, and re-released a stable version of QTS 5.2.2.2950 build 20241114 within 24 hours."
Sooo... They changed the version & build numbers to make it obvious. That's helpful.
I've three of their units - luckily none of them affected, but then I don't generally upgrade firmware as soon as it is released.
Best to let others find any "show stoppers" first, then upgrade.
QNAP have done themselves no favours in the way this has been communicated - badly.
Trying to hide "bad news" does nothing but piss customers off.
If you want to take them with you, be open and honest and keep them informed.
I have a QNap NAS and there was one update that was constantly rebooting and I had to downgrade. To downgrade, you have to power off the machine, remove all the hard drives including the M.2 drives if you have them, then turn on the NAS. Once there, you enter an IP address and you are given the option to install a new firmware. After the firmware is installed and the machine rebooted, you turn it off again and put all the drives back.
This is one of the reasons we should stop going "cloud-only/first" and make sure stuff like SSH is still available on the local network if necessary.
If people aren't protecting their storage VLANs against rogue SSH from clients, that's their problem.
But if you gave me SSH to such a device, at least I'd stand half a chance of resetting the password and getting it working again.
(Though it sounds like they've trashed the authentication database, so even that might not work without a recovery mode).
I updated my (home) 453D at the weekend and I got 20241025*. That's my portion of good luck used up for while, I guess. I'm backed up but it would still have been a right pain to sort out - as I'm sure many poor buggers are finding out.
*although, given that there are two "versions" of 20241114 knocking about, who knows what I've actually got.
"The firm said that only a limited number of NAS models were affected "
Same old same old. Do they not realise that for someone who has one of them it's not a limited number? iI's 100% of what they've got.
Anyone who trots out this ancient piece of PR verbiage should stop and think about what they're saying to their customers who were affected. They should also stop and think about what they're saying to potential customers with more wit than the PR mouthpieces (not a high bar).
So, 2024 QNAP are still sh1t at upgrades, communication and questionable with support.
News at 11.
It must be 7+ years since I jumped off that train.
I think most are sh1tshows now. Slightly easier rolling your own and praying... at least unless you have lots of euros in your account/outsource/can give it the support.
Sucks for home and smallbiz users... and then jokers like QNAP play their games. Nearly as bad as those firewall firms with their oh, planned, obsolescence due to incompetence or business planning (MBAs galore).
I hope me and my MBA don't add to the collective bad impression MBA-ites give this qualification :)
When I first installed it, I was so shocked at the number of connections to numerous servers on AWS that were reporting everything being accessed on my NAS, I added many rules to my firewall to redirect needed services such as DNS and NTP to my servers and blocked all access to the Internet for the NAS. My next device will not be QNAP or Synology for that matter.
It does have a useful feature though, the interface turns grey when you manage to block all QNAP'S monitoring, giving some useful feedback.
I have a Thecus NAS that has an "irritating" issue that's never been resolved. I used to power it down when not actively in use, but every so often after a few powerdowns it loses its boot password and refuses to go live again. Thecus provided a script that clears the password, but then you have to start from scratch again setting up access from all the machines that talk to it.
It appears that, despite NAS in principle needing to be robust ands reliable, they're in general thrown together like everything else in IT. What a surprise (!!)
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2025
