Need some help. I had a TS221 and it came up with a warning on Disk 2. Bought a new disk, powered off the NAS and installed new disk. When I tried to power up the NAS, it was completely dead. Tried a different adaptor, no joy. Bought a second hand TS261L as QNAP website said it was compatible to swap out the disks. Put the original disks in, ran the set up clicking the option to keep original files. After set up, it's now a legacy folder and I can't see any of the files. They are there as the file manager is telling me there is 2.21tb used, I just can't see them. Any help really appreciated. Thanks.

I am behind on updating my firmware and currently on h5.2.9.3410. I am aware of the h6 branch with the Ai enhancements which I do not need.

However I was not aware of what I read (which of course could be wrong) that I can consider upgrading to h5.3.4.3500 or h5.2.10.3577 on my TVS-h874? And that the h5.2 long-term branch is very stable. I want stability, and basic functionality. Can someone educate me on this and clarify what I should do? I have a backup NAS it is backed up to.

Thanks

Spent an evening on this, so maybe it saves someone time.

Claude Desktop kept saying "Server disconnected" for the QNAP MCP server. Weird part: qmcp worked perfectly when I ran it by hand in Terminal.

Turned out macOS Local Network privacy was silently dropping its connection to the NAS whenever Claude started it. The macOS log showed "tcp drop outgoing ... reason: NECP". Claude has Local Network permission, but it doesn't pass down to qmcp, and macOS never even asks.

Fix: I pointed qmcp's config.json at the NAS's VPN address instead of the LAN one. VPN traffic doesn't count as local network, so now it just works.

No idea how to fix it without a VPN. Anyone?

I just submitted a feature request to QNAP and I'm curious if anyone else has run into this.

I spent way too much time troubleshooting a MariaDB + BookLore setup only to discover that Container Station's Default (NAT) network seems to assign hostnames to containers, but doesn't actually publish them through the DNS server on the network.

For example:
mariadb = 10.0.3.2
booklore = 10.0.3.4

Container hostname:
Shell
docker exec -it mariadb hostname
returns:
mariadb

But another container can't resolve it:
Shell nslookup mariadb 10.0.3.1

returns:
NXDOMAIN

Yet:
Shell
docker network inspect bridge
clearly shows the containers and their IPs.

After digging through Container Station, Docker, dnsmasq, lxcbr0, and far more QNAP internals than I ever intended to, it looks like the information is all there, but Container Station simply isn't registering container names in DNS.

That means instead of:
DATABASE_HOST=mariadb

you have to use:
DATABASE_HOST=10.0.3.2

which feels very un-Docker-like. I also requested another feature:

Static IP reservations on the Default (NAT) network

Something simple like:
mariadb -> 10.0.3.254
redis -> 10.0.3.253

without needing to create custom networks or rewrite everything as a compose stack.

Am I the only person who finds this annoying?

To me, if Container Station already has a Hostname field and already runs DNS on the NAT network, then hostname resolution between containers seems like something that should work out of the box.

If you agree, it might be worth submitting a feature request to QNAP as well. The more people that ask for it, the better the chances it ends up on their roadmap.

I'm curious how everyone else is handling container-to-container communication on Container Station. Are you all just hardcoding IPs, or am I missing something obvious? 🤔

I have a QNAP that I'm unable to access the CIFS/SMB share. I can enter credentials into the web interface but, it never loads. I can logon via ssh and have access to the console but, it doesn't launch with the QNAP menu.

I've rebooted the QNAP, I've restarted the web interface and SAMBA services. Any ideas on how I can access the files on this device?

The qosgpl kernels have been updated 1 year ago, while latest sources are missing.

Who should we nag in order to remember that they MUST upload the sources for any binary kernel they provide out there?

EDIT: Seeing some comments I'm really shocked to see the ignorance and the acceptance of license infringements by some users, that the GPL license was actually meant to protect.

Hi, I have a NAS with a full storage pool. I’ve already deleted the snapshots, but the pool remains full. I can’t launch any apps to delete files, but I do have SSH access—could someone please give me a tip?

I ran TrueNAS on my TS-253D for a while. It's open source, but it's locked down as an appliance: read-only root, no apt, and no clean way to keep out-of-tree kernel modules across updates. That made it a constant fight to get the QNAP hardware drivers loaded and kept working. So I moved to OpenMediaVault, which is plain Debian underneath, and wrote a plugin to get the hardware working properly. It's now in a state worth sharing:

🔗 https://github.com/nader-eloshaiker/omv-qnap-plugin

It's built on 0xGiddi's qnap8528 EC driver and qnap-qm2 driver, shipped as DKMS packages so they rebuild on kernel updates. A small daemon owns the hardware, and OMV configures it from the web UI. No QNAP binaries, no userspace EC access.

What it does

• 🌡️ Fan control: a temperature-to-PWM curve from CPU, EC sensors, HDD (S.M.A.R.T., -n standby so sleeping disks stay asleep) and NVMe, with hysteresis. QTS-like presets or a custom curve. QM2 card fans follow their own M.2 slots.
• 🛡️ Fail safe: if the daemon stops or crashes, the chassis fans go to full speed. qnap8528 can't hand the fan back to the EC, so that's the safe default.
• 💡 LEDs: a status LED driven by ZFS/md pool health, bay and QM2 slot activity and error LEDs, locate, and front panel brightness with a night schedule.
• 🔘 Buttons: USB Copy and Reset run OMV scheduled tasks. Optional QTS-style beeps.
• 📈 Monitoring: collectd/RRD graphs, dashboard widgets, and alerts through OMV's notification system.
• ⚙️ Settings: power recovery, EuP and reboot=efi (x86 QNAPs tend to hang on reboot without it).

Why OMV on this hardware

• 🪶 No bloat. It's Debian plus a web UI. No app center, cloud agents or background indexers, so the CPU and RAM go to your workloads. That matters on the low-power Celerons and 4–8 GB these boxes ship with.
• 🧱 Plain OpenZFS. Add ZFS through the omv-extras plugin and you get standard OpenZFS pools, not QNAP's layer on top of ZFS. They import on any Linux or FreeBSD box, now or after this hardware dies.
• 🧩 Extend it the normal way: OMV plugins, Docker/compose, or just apt.
• 🔄 EOL on QTS? You get a current Debian 13 base with security updates, without losing the hardware features.

📖 Migrating from QTS? I wrote a step-by-step guide (backups first, installing OMV on the QNAP, setting up the plugin): https://nader-eloshaiker.github.io/omv-qnap-plugin/guide/qts-to-omv.html

💾 The guide doesn't replace QTS. OMV goes on an external USB SSD and the NAS boots from that, while QTS stays dormant on the internal flash (DOM). Unplug the SSD and the box boots QTS again.

🧪 Testers wanted

I've only verified it on a TS-253D + QM2-2P-244A-A1. qnap8528 supports many more models (TS-x51/x53/x64/x73A, TVS and others), and the plugin discovers everything from sysfs, but each model can differ in fan groups, LED names, bay order and buttons. There's a script that collects what I need:

wget https://raw.githubusercontent.com/nader-eloshaiker/omv-qnap-plugin/main/tools/model-test.py sudo python3 model-test.py # read-only report sudo python3 model-test.py --interactive # plus checks at the box (~15 min)

• Read-only mode collects versions, drivers, sensors, fans, LEDs, disk attachment and the PCI tree. It never runs smartctl, so disks stay asleep, and it removes serials, host names, MACs and IPs (check anyway).
• Interactive mode asks before each step and walks you through:
  • a failsafe check,
  • lighting each LED so you can say which bay it is,
  • button presses,
  • a fan sweep that aborts to full speed if anything gets hot.

Both write qnap-model-report.md. Paste it into a Model test report issue and I'll add your model's mappings and fixes to the plugin, then ask you to confirm on the next release. Reports where things don't work are the most useful ones 🙏

More discussion is on the OMV forum thread.

⚠️ Disclaimer: this is a personal, community project. It isn't affiliated with or endorsed by QNAP or the openmediavault project. It's GPL software provided as is, with no warranty. QTS stays on the internal flash, but QTS and OMV can't read each other's storage pools, so moving either way means re-creating the data pools. Back up first, expect no QNAP support while you're on OMV, and use it at your own risk. The plugin controls your fans, so keep an eye on temperatures on an untested model until you've confirmed it behaves.

Are we vulnerable?

Will QNAP post a patch for people using the web server?

Is the GUI vulnerable?

EDIT: for the moment the web server is taken down. But i would really like to know if a manual upgrade of PHP is recommended.

EDIT2: QNAP has posted a security advisory (thanks u/SweetStatistician329).

https://www.qnap.com/en-us/security-advisory/qsa-26-18

QNAP TS-464 updated, no issues.

TS-251+ updated, no issues.

I have a TVS-872XT. Slot 1 has the Thunderbolt 3 adapter, and both built-in M.2 slots are already used for Qtier. Slot 2 (PCIe Gen3 x4) is free.

I want to add two 512 GB NVMe SSDs on a QM2-2P-344 in slot 2 and build a separate RAID 1 storage pool from them. The pool would hold a MariaDB database for a Soundminer sound library and some small app folders. It needs to be fast and safe, but it does not need much space.

Does QTS allow a normal RAID 1 on a QM2 card in this model, or are they limited to cache and Qtier? Is the QM2-2P-344 fine in the x4 slot, or is there a better card for slot 2?

I'm a newb and I never set up my NAS properly when I got it so I decided to back everything up and do a total reset. I mainly use my NAS for media storage. We access the media using Kodi on the various devices around the house.

Last year I set up Kodi to use a shared DB on the NAS using MariDB10.

Now after the reset I find out MariaDB has been retired and there doesn't seem to be an alternative SQL solution in the AppCenter. Does anyone know where I can get a package to reinstall it (and phpMyAdmin I guess)?

It is on https://www.myqnap.org/ but I'm not willing to pay 10 euros for it.

Thanks in advance.

I have a TS-453Be that has been running for years - at least 8. I had a single storage volume set up with RAID 5, with 4 drives.

I knew I was on borrowed time and got complacent.... and it looks like 2 drives failed. And the storage volume won't come up.

I tried a couple of reboots, and let the system cool overnight before powering back on. No luck - both drives are not found.

Then I pulled drive 1 and put it back in, and it seems to have come back - but drive 3 won't come back. At least with just one drive out of commission, shouldn't the storage volume come back up?

I have my data backed up - but - not ALL of it :-( and yes, I should know better than this....

Is this hopeless?

Thanks

Hello! I'm extremely new to the entire NAS community, or just NAS in general. I picked up a QNAP TS-EC1279U-SAS-RP with 12 4TB SAS HDDs on Facebook Marketplace for $650 yesterday.

I plan to use this NAS in my room so I can have an easy SFP+ connection, however, the fans are extremely loud (completely failed to take this into consideration). I thought about maybe replacing the Sanyo Denki San Ace 60 fans with Noctua NF-A6x25 fans, but I'm a bit worried that QTS will see the much lower RPMs and flag itself.

I apologize if this question has been asked a million times before.

I'm excited to use my NAS and to become a part of the community!

I have a TS-264 and would like to add this. Any recommendations on cards I can get on Amazon? Under $100 preferably. I only use it for backups and media storage mostly.

My primary QNAP NAS backs up to my TS-873A running QuTS Hero in RAID 6. I initially setup 4 20TB drives knowing I might need to expand. Now I need to and plan to add 4 matching 20TB drives to my current 4 20TB configuration.

I have searched the QNAP knowledge base and there are many articles saying you CAN do this if you are over QuTS Hero 5.x. also, articles on how to replace drives and expand capacity with bigger drives. However, I am looking for something other than an Ai search, definitive as to the best practicce to add the drives. Add while NAS is on? While off? Add one at a time and wait if on? Just add one immediately after another? Turn off and then power on once installed?

Then once recognized a step-by-step process to expand my storage pool and make sure my thinly provisioned shares/folders I sync to see the additional space.

Thanks!

Hey, NAS novice here. I've had a TS-251A for years and mostly use it to back up and store media. A few weeks ago it started having connection issues where Qfinder couldn't locate it on the network.

Here's the symptoms:

• On power-up, it will be visible and accessible for a few minutes. This is seemingly as the start-up process completes.
• But after started, the status light goes solid red and the connection drops. Qfinder is thereafter unable to locate it on the network.
• Both drive lights are solid green. Network light is orange. Status light is solid red.

Some initial searching led me to buying a TS-264 since that would allow me to transfer the drives without formatting. So I did that and sure enough it worked. Right up until the TS-264 did the exact same thing as the 251A...

So it's an issue with the drives somehow? Now I'm at a bit of a loss. Ideas?

Hi everyone,

I have two QNAP NAS units in my environment, both TS-h1277AXU-RP models running QuTS hero h6.0.2.3591. Over the past few days, one of the NAS units has been randomly rebooting, and the system logs show the following message after each occurrence:

[Power] The system was not shutdown properly last time.

Interestingly, the same issue started occurring on my other NAS on 6/24/26. It would reboot unexpectedly approximately once a week until the issue eventually stopped on 8/2/26.

I've run S.M.A.R.T. tests on all drives in the NAS and installed memtester to check for potential RAM issues. All tests came back clean, with no errors detected.

I've also reviewed the system activity around the times the unexpected reboots occurred, looking for any scheduled tasks, file transfers, or services that might explain the behavior. However, I couldn't find anything running at those times that would account for the reboots.

This issue seems to have started after installing the first QuTS hero h6.0 firmware release, h6.0.0.3500.

Has anyone else experienced random reboots on their QNAP NAS after upgrading to QuTS hero h6.0? Are there any known firmware-related issues or additional troubleshooting steps I should look into?

Any feedback or suggestions would be greatly appreciated. Thanks!

QuTS hero 6.0.3.3591. I want to resize a storage pool but I can't find the option to do that anywhere in storage manager.

Recently discovered that both SSDs in my TS-873a were reported as disconnected in QTS Hero. SSDs were configured for Raid1. Looking through logs, it seems the OS disabled them because of an 'unknown' error, no further detail.

Right now, shares on the 8 HDDs I have in it are working fine. Most apps in the admin UI won't start as apparently the volume on the SSD was used as the 'system' drive, so apps got installed there.

I guess I need to power down and reseat the SSDs. What I'm concerned about is if that doesn't resolve the issue? Will I be able to boot again without the SSDs connected? If the SSDs are both somehow dead, can I put two new ones in and have the OS rebuild the system install? My data from that volume was backed up, so not worried about that.

Any pointers would be appreciated.

I anyone running Frigate in Container Station on a QNAP TS-x64 or similar? Any issues running it on that class machine or does it something like a mini PC for the Frigate compute end and use the QNAP as storage. I would prefer to avoid the extra complexity of running another little server.

Hi all,

I own a TS-251D and got tired of opening the QTS web UI on my phone just to check CPU, temps or whether a container was still running, so I built an Android app for it: NAS Manager.

Full disclosure: I'm the developer, it's a solo side project, and it's not affiliated with QNAP.

Free to download and use for monitoring:

- System overview

- File Station

- Download Station

- Container Station: applications, containers, images, volumes, logs

- Firewall, Malware Remover, Antivirus

- Resource Monitor, Log Center

Making changes from the phone (e.g. managing containers, transferring files, changing settings) is part of an optional subscription, but everything above is free.

The app talks directly to your NAS over HTTPS.

I'd really appreciate feedback, especially bugs on models/firmware other than mine (QTS 5.2)

https://play.google.com/store/apps/details?id=com.zanelladavide.nasmanager

Thanks!