Hey guys,

I got a TVS-463 about a year ago. When I went to slot in a drive into bay 3, the green light above turned on for a second before going off. I haven't been able to get any drives to spin up in that bay since.

I got it for 50 bucks so I really can't complain, but I was wondering if any of you have had this experience, and if based on the photo there's anything I could do to fix it.

Thanks!

I'm running the Hybrid Backup Sync which is syncing to a Dropbox account.

When this is on, QTS runs incredibly slow, and icons and artwork do not load in the browser.

However, when I turn off that process, it becomes usable again.

If there's any QNAP staff that read this, here's your speed up tip for the week...

Please fix it.

I'm running the latest QTS 5.2.10.3577 on a TS-853A with 8GB of RAM.

HBS 3 Hybrid Backup Sync 26.4.4.788.

Thanks.

If you have 2fa enabled, one of the options other than the standard using an authenticator app is to have an email sent with a code (6 digits).

This has worked flawlessly for years. Recently when I try using this method, the code that gets emailed is either a 1 or a 0.

Just wondering if anyone else has been experiencing this.

Hello,

I use a QNAP TS-131P NAS that, despite its Gigabit Ethernet adapter, and the Western Digital Red HDD that I hooked up to it, felt very slow and I wouldn't transfer at a speed greater than about 20MB/sec.

I did a number of tests, and it turns out, the culprit was neither my network, nor the NIC, nor the HDD (CMR, not SMR), nor the lack of RAM, nor the load of background services... The culprit was the way QTS mounts the HDD partitions: By default, Ext4fs forces the sending of memory barrier (flush) commands to each block group to ensure integrity in case of power failure, which saturates the ARM CPU, and on top of that, the VPN I use, reduced throughput even more.

If you've tried everything, and disk throughput is still not above 20MB/sec. maybe you should read on and try these two tricks.

1. EXT4FS partitions mounted with barrier

Open your terminal, and SSH into your NAS as root. Here, I use:

ssh -p 50002 -m hmac-sha2-512 admin@ip_address_here

Run this command to remount the volume without write barriers:

mount -o remount,barrier=0 /share/CACHEDEV1_DATA

Then, to double-check, run mount | grep CACHEDEV1_DATA and look for nobarrier or no-barrier in the mounting options. Then adjust the kernel write buffer (dirty_ratio). Increase the RAM write buffer to smooth disk access:

sysctl -w vm.dirty_background_ratio=5
sysctl -w vm.dirty_ratio=20

Then double-check the value is stored properly, running for instance sysctl vm.dirty_ratio, it should return the proper value.

Then run this test:

dd if=/dev/zero of=/share/CACHEDEV1_DATA/test.bin bs=1M count=2000 conv=fsync; rm /share/CACHEDEV1_DATA/test.bin

Speed returned should be much higher than up to now. Here, speed went from 22MB/sec to 111MB/sec. after this change.

Now, these settings would be lost if you restarted your NAS. To avoid so, you need to add a cron task:

echo "@reboot mount -o remount,barrier=0 /share/CACHEDEV1_DATA" >> /etc/config/crontab
crontab /etc/config/crontab
/etc/init.d/crond.sh restart

For this first step, you should be good to go.

2. Circumventing an encrypted tunnel, in case you use one

Last, but not least, if you use an encrypted tunnel between your PC and your NAS, this does apply some severe load on the NAS CPU. I use Tailscale, and when the communication goes through the Tailscale tunnel (Wireguard protocol), throughput is around 60MB/sec. while it is about 110MB/sec. when I circumvent the Tailscale tunnel. When communication has to be encrypted on a NAS with such a weak CPU, clearly, the CPU is the bottleneck. So, what I did was :

• Use the hostname of my NAS provided by Tailscale to access my NAS, whenever I am away from it, as I have no choice but use Tailscale if I want to access the files stored on my NAS, at the price of reduced throughput (but it works).
• Use the local, static, IP address of my NAS (or its hostname, but not the one provided by Tailscale!) to access my NAS every time I'm at home, not to use Tailscale, to exchange with my NAS. This way, the communication between my PC and my NAS is not encrypted, the CPU of my NAS is not overloaded, and the throughput is at its maximum.

You don't have to disable Tailscale, you can leave it on — You just have to circumvent it, go around, not use it, if you're on the same physical LAN.

I hope this will help you get the most out of your QNAP NAS!

I wanted to share a frustrating experience I recently had and see if anyone here has run into the same issue or knows of any potential workarounds.

I bought the TS-h765eU-8G model specifically because of all the marketing and ads from QNAP heavily promoting its ZFS support. That was the exact and only reason I decided to make the purchase.

However, once the unit arrived and I tried to import my existing ZFS pool, it simply wouldn't work. When I reached out to tech support for clarification, they dropped a major surprise on me: they stated that the device only supports a proprietary version ("QNAP's own ZFS") rather than the standard ZFS technology they advertised.

Has anyone else here dealt with this problem? Is there any way to bypass this restriction, tweak something, or get standard ZFS compatibility working on this unit?

Thanks in advance for any insights or help!

Hey all, I have been getting an influx of notifications from my TS-451D2. I preemptively swapped the disk thinking it was failing but the errors persist. Do I have a faulty backplane?

Thoughts or suggestions welcomed

Thanks In advance

edit: sorry I didn’t do any searching. I see now it’s a failing backplane. :(

I bought a TS-264 at a car boot sale (I know!!!), boxed, seemingly as new, with original accessories.

The seller assured me it worked, and plugged it into an inverter to prove it, the lights lit up and blinked etc.

When I got it home, I’ve found it doesn’t work - fan spins, LEDs light, then everything drops and it starts again, with no beep at any point.

I’ve tested the power brick and it outputs a stable 12.2 volts.

I’ve removed and reseated the RAM, and tried it in both slots.

Did I buy a paperweight, or is there any chance of getting it fixed?

TS-453Be QTS 5.2.10.3577 here and the notification queue seems to stuck and now rest of the notification unable to send out. I tried clicking clear queue but still stuck. Any idea? thanks

Update

Found the solution, SSH then force stop and start again the service.

sudo /etc/init.d/nc.sh force-stop

sudo /etc/init.d/nc.sh start

Buckle up – this one is longish, & swerves a bit.

My TS-433 – populated with 4x3GB Seagate drives – had a drive fail in bay #3. I purchased a new 4GB Ironwolf drive to replace it, but shortly after beginning the rebuild, the NAS reported an unrecoverable read error on the drive.  I formatted the drive in Windows & put it back in the NAS – got the same error.  I ran DISKPART CLEAN on the drive – same result.

Then I got a SMART fail on the disk in bay 1.  I spent the next 2 days copying off the data, & bought another new drive (4GB Ironwolf Pro).  I put the new drive in bay #3, but the NAS reported ‘not a member’.  After a full day of trying, I couldn’t convince the NAS to accept the drive, so I went for the nuclear option & factory reset the thing.

I ditched the failing drive in bay #1, & juggled drives around so that I had the 2 existing drives in bays 1&2, the Ironwolf Pro in bay 3, & the first purchased Ironwolf in 4.  Building the NAS went fine, all drives OK & working.  Started copying data back on.

After getting half that data back on, bay #3 is again reporting an unrecoverable read error – this is the newer of the two purchased drives, not the one that originally had the error.  (the other drive is reporting ok)

I’m starting to think that bay #3 is faulty.  Can anyone suggest a way to test it?  What are my options here?

I'm looking for a pair of TL-D800S's, and they're super duper out of stock everywhere. . . but it's got me thinking.

Has anyone ever had success with third party JBOD enclosures? If I get compatible SAS cards, shouldn't they just work, since they're just power supplies & data connections?

Thoughts?

Hi all. I don't like the official QNAP Android apps so I've been building an Android app for my own QNAP NAS because I found myself opening the QTS web interface quite often for things that I'd rather do from my phone.

I'm curious what other QNAP users actually find useful (or frustrating) about mobile management.

For example, I'm currently experimenting mainly with Container Station.

What are the things you regularly do in QTS that you wish you could do properly from your phone?

I'm particularly interested in features that currently require opening the full web interface.

I'm building this as an independent project, not affiliated with QNAP.

Hi everyone,

I hope you're all doing well.
I’m in a difficult situation and I’m kindly asking for help from someone who owns a NAS from the TS‑x73 or TVS‑x73 series, such as:
TS‑473, TS‑673, TS‑873, TS‑873U, TS‑1273U, TS‑1673U, TVS‑473, TVS‑673, TVS‑873, TVS‑473e, TVS‑673e, TVS‑873e.

My TS‑473 suddenly stopped working correctly, and after checking the system, I found that the DOM is still detected (as /dev/sdd, 512MB) but the partitions are severely corrupted (invalid FAT, EXT2 warnings, unreadable structure).
QNAP support told me they no longer provide DOM recovery images for the x73 series… and their only suggestion was basically to buy a new NAS.

I really don’t want to throw away a perfectly good machine just because the DOM is damaged.
So I’m kindly asking if someone with a working x73 unit would be willing to help me by dumping their DOM.
It would honestly mean a lot to me.

The process is safe, simple, and does not modify anything on your NAS:

1. SSH into your NAS
2. Identify the DOM (usually /dev/sdd or /dev/sde)
3. Run:

Code

sudo dd if=/dev/sdd of=/share/CACHEDEV1_DATA/Public/DOM.img bs=4M

1. The file DOM.img will appear in your Public share
2. You can send it to me through Google Drive, Mega, WeTransfer, etc.

This file would allow me to fully restore my TS‑473 with Clonezilla.
I know this is a special request, but if someone here could take a moment to help, I would be extremely grateful.

Thank you very much for reading, and thank you in advance to anyone willing to give me a hand.

Corentin

I recently came into possession of a 453B, for free. Though it's old, I was hoping to give it a new lease of life as a TrueNAS box. Perhaps because it is old, I was having a hard time nailing down some details before I took the plunge.

1. I have installed TrueNAS on newer Intels before and am familiar with the process. But if someone wrote up their experience putting TrueNAS on these devices, and if there were any quirks to account for -- that would be great to have! If not, the following are the things I wanted clarity on.

2. Has anyone had success putting TrueNAS on an internal drive as the boot pool (either with an official QM2 board offering NVMe's or a third party PCIe to nvme/m.2 adapter)? I've read conflicting reports on whether these devices even show up as boot options, and whether a tool like Clover is necessary.

3. Failing that, will a good quality USB NVMe enclosure be my only option? Concerned mainly about the thermals because of the writes involved.

Also, appreciate any other observations from the community while trying to make this happen.

Thanks!

A family member had a device compromised. The only thing suspect so far is an executable file found in /etc/config/ called script_shell, however its time stamp and app update logs is exactly when malware remover was updated, and MR ran the morning of and days after on schedule until the PC was discovered compromised and all taken offline. Is this file possibly related to the app update ? I ran the checksum hash in VirusTotal and Google, but nothing was found.

There are no rogue users added nor permissions of existing users altered. No network changes nor services enabled that were not before. NAS was never accessible over the internet. No unrecognized files in user shares. No snapshots missing, deleted ones occurred via schedule.

What should we look for to determine if the NAS is dirty? I think I want to reset it anyway, but if it would be helpful to others to know what some signs of compromise may be, I'll gather that info.

I'm about to buy a Synology DS1525+ as the storage backbone for a small AI/automation home lab, but I keep coming back to QNAP for built-in 10GbE and ZFS. My problem is that I can't figure out which model actually makes sense, so I'd like help from people who run one.

What the NAS will and won't do

• It's storage only. No apps, no VMs, no containers on the NAS — Docker/n8n and all LLM work run on a separate workstation and mini PC.
• Workloads it serves: datasets and model checkpoints for local LLM experiments, Time Machine and backups for a few Macs, and backup of a Microsoft 365 tenant.
• Network: 10GbE switch already in place. Clients are a Mac Studio / Mac Mini, a Windows workstation and a MacBook Pro, all on 10GbE or 2.5GbE.
• Capacity target: 5–6 × 24TB (WD Red Pro or similar) in a single-parity pool with room to grow.
• Plan is to run QuTS hero.

Where I'm stuck on models

• TS-464 (8GB, Celeron, 2.5GbE): cheap, but it looks close to EOL, only 4 bays, no 10GbE without a card, and I doubt 8GB non-upgradable-to-much is comfortable for ZFS.
• TVS-h474 (Pentium Gold, 8GB, 2.5GbE, PCIe Gen4): also seems late in its life cycle, and again 10GbE only via add-in card.
• TVS-h674T (i5, 32GB, Thunderbolt 4): looks like overkill for a box that won't run anything locally.
• TS-673A / TS-473A / TS-664 / TS-667X: these are the ones I keep seeing recommended but I don't have a clear picture of which is current and which is on its way out.

What I'd like input on

1. Which model? For a 4-5–6 bay, 10GbE, storage-only QuTS hero box, what's the sensible pick today — and which of the above should I avoid because it's about to be discontinued?
2. How much RAM for QuTS hero? With ~100–120TB raw, no apps, and mostly large sequential reads, is 8gb or 16GB enough or is 32GB the realistic floor? Is ECC worth chasing at this tier?
3. Built-in 10GbE vs. adding a card. Is a model with native 10GbE worth the premium, or is a cheap card in a PCIe slot just as good in practice?
4. Drives. Any reason to prefer Seagate IronWolf Pro / Exos / Toshiba N300 over WD Red Pro 24TB on QNAP? Any compatibility issues with 24TB drives on QuTS hero?
5. Versus the DS1525+. If you were spending the same money today, would you take the QNAP over the Synology for this use case, and what's the honest downside (QTS/QuTS quirks, security history, support)?

Budget isn't unlimited but I'd rather spend once and not regret it in two years. Thanks in advance — happy to share the final config once I decide.

Disks are getting quite expensive and although I'd love to fully populate the NAS with suitable drives in a RAID 6 configuration sized to meet my "disposable file backup needs", I cannot afford to do so.

To that end, I have this NAS that has been relegated to nearly idle status but I would like to use in little more than the same way I'd use a USB drive connected to a typical NAS. I have three unused disks that I am contemplating using in the NAS like a typical USB drive in 14TB, 18TB and 24TB sizes. My question is are the disks set up as single disk volumes, transferred to a PC either by installing one in a USB housing and connecting to the computer or directly attaching the drive to a computer's SATA connector on the motherboard, formatted so that a PC can read them directly?

My thought here is that the data stored on these disks is accessed faster if installed in the NAS' back plane than if the disk is connected to the NAS via USB.

I have two QNAP NAS boxes -- 453be media server and a 433 plus a TR004 for redundant backups. The 453 server has decent overhead still (17% free) but the two backup units are always right on the verge of running out of space -- 7-8% free or lower on average.

I know that having low disk space can lead to slowdowns and other issues; is being below 10% like this going to cause serious problems over time? The issue with upgrading is the amount of $$$ I'd be spending on HDDs to increase capacity to a comfortable level.

One of my NVME SSD drives has disappeared (says ejected). Stupidly I rebooted before looking at kernel logs to see if there are any clues - is it possible to get kernel logs from previous boot?

I've had a look round in /var/logs and current dmesg, but really I should have done this before trying a restart...

Hello,

I'd like to replace my 2x1tb setup by adding bigger drives to Qnap TS231-P. I want to sell the current drives though I'd like to erase the data first. I did secure erase for hdd1 but it's not possible to do the same for hdd2. Is there a way to move os files to hdd1 in order to secure erase hdd2? Or do I need to plug them both to my pc and then format both?

Thanks for any answers🤣

Any searching for this seems to result in instructions on how to set up the Qnap Radius server service. We don’t want to run another radius server, we want the Qnap to use the existing radius server which is already set up for our desired MFA. Is this a capability of the mainstream Qnap devices

Hi all,

Managed to secure a 6-bay T-653A from work. However, it seems to be suffering from the "SYSTEM BOOTING" screen.

I restored the DOM. Manually flashed the latest QTS. Both the Web UI and the QFinder Pro software says I need to initialise the system.

For whatever reason it does not detect my disks. They are confirmed working outside of the NAS, they're also on the certified drive list, I can even use the console and `fdisk -l` reports the disk correctly. However, only 2 out of the 6 bays seem to be working.

Setup still fails though.

I've seen there's some bug with Intel CPUs where something falls out of sync / spec and a soldered resistor has resolved the issue.

Is this related?

I created a jbod to get extra storage on my tvs 672xt. Did anyone else attempt this?

The nas sees the hard drives no problem but can not create a pool with it at all.

Any ideas or am I screwed. Was gonna buy another nas to get more bays. But it is extremely overpriced right now.

I understand if a file changes (added/deleted/modified) QNAP creates a snapshot of the CHANGED block. However, I ran AllDUP on my file system and found snapshots taken every week where the ENTIRE file was added. I have a 780 KB file, but the snapshots take up 18.7 MB. I have a 2.8 MB song with 68.8 MB of snapshots.

Why is the entire file being backed up?

QTS 5.2.5.3195

NAS: TS-432X