Hello, I recently bought a lockerstore AS6706T gen 2 and from a couple of days it became quite noisy. At first I thought an hard drive was bad but after removing all of them the noise was still there and came out it is PSU's fan. How can I fix this? Is there a warranty?

I have a 4 bay AS3304T V2 with two RAID1 arrays.

If I buy a AS5402T 2 bay can I pull one of the RAID1 from the 3304 and put in the 2 bay and retain array? I see migration info says you can go 2 bay to 4 but nothing about other way …

Assume all on latest firmware etc.

I tried updating my NAS tonight and kept getting errors. Then I went to the website for a manual download and was greeted with this...

I have an ASUSTOR AS5404T.

It had 6 drives:

Vol 1: 2xNVMe SSD

Vol 2: 2x1 TB HD in slot 1 and 2

Vol 3: 2x8 TB HD in slot 3 and 4

I had a couple of 2 TB drives left over from another thing so I was going to update the 2x1 TB drives because why not.

I started the "upgrade volume by replacing with bigger hard drives" process.

I turned it off, replaced the first drive in slot 1, volume 2 with a 2TB SSD, and started again.

Upon booting it again, I see both of Vol 2 and Vol 3 are being rebuilt. Vol 2 is now the old 1TB drive and one of the 8TB drives. Vol 3 is now the new SSD and the other 8TB drive. I realize the 2TB SSD had been in this NAS before and I probably hadn't replaced it. So now one of the 8TB drives is being overwritten with the content from the 1TB drive and the other one is being overwritten by whatever old crap is on the new 2TB drive.

I do have plenty of recent backups of everything so it's not a disaster.

Both volumes are still rebuilding. I figured turning it off and removing the hard drives mid-rebuild is probably going to make things worse.

- Any advice or clever idea on how to conveniently recover, short of restoring backups?

- For next time, would wiping the drive before (using another device) have prevented this, or does the NAS keep track of drives by serial numbers or something?

- Is it just me or is this incredibly weird and dangerous behavior? Sure - the drive had data on it, but it is in a different slot than it's ever been before, both my volumes got completely re-arranged, and zero confirmation on anything? I get that the new drive in slot 1 was assigned to vol 3 if it had been part of that before, but how the h*ck could the drive in slot 3 just be moved into volume 2?

Reviewed the announced CVE and patched quickly given the apparently severity. Quick reboot and everything appears to be in order. NAS not nuked.

I had a disk light up red, so I hotswapped it immediately. However, on checking the history it was media read errors and not bad blocks and looking at the pulled disk with CrystalDisk it's in good shape. So I want to use it to replace the next disk that actually goes bad. Question, is, do I need to reformat it, or otherwise do some preparation, or can I just hotswap it in and the NAS will treat it like a new disk, or will it get confused and mess up my data with the old data?

I'm getting really frustrated trying to do something that seems like it should be easy: I want to set-up a nightly recurring backup, which simply maintains a 1:1 mirror of my shares (docs, pics, videos) on an external removable USB HDD.

The problem is, no matter how I set-up my backup job in Backup Central (ADM v5.1.4.RL21), the job NEVER removes files from the USB backup volume which have been deleted from the NAS. If I delete a file from the NAS, it remains forever on the USB backup. If I rename a file on the NAS, or move a file, a new file is created on the USB backup reflecting the file's new name or location -- but the old files remain there, also.

Which is a total mess. This behavior will fill-up my USB Backup-drive with needless copies of files, and will also prove extremely confusing to sort through in the event that I ever need to rely on it as a backup.

How can I make the NAS maintain a 1:1 mirror of my shares on a USB Backup Drive, preferably maintained on a nightly basis?

=== FURTHER DETAILS ===

I have the AS5404T. It contains 2 (two) 14TB Seagate Ironwolf Pro NAS drives. These drives are housed in bays 1 and 2, and they're set-up in a Raid 1 array, where the two drives mirror each other for a measure of data-safety/fault-tolerance.

There are four SMB shares configured. Let's call them:

PicsVids
CreativeArchives
MoviesTV
MyDocs

These shares are all working well, and I can access them from my PC, my laptop, and my phone -- both at home, and over Tailnet VPN when I'm away.

I'm attempting to back things up to two 22TB Seagate Expansion USB HDD's (5400-speed), which are both ext4-formatted. The idea is, I will have only one of these drives connected at a time. A nightly backup should run, maintaining a mirror of my SMB Shares on the connected USB drive. Once a week, I swap the drive out with the other one, so that I always have one connected and one disconnected. I do that so that, in the event of a power-surge that wipes out everything, I'll have only lost a week's worth of data at most.

I've tried configuring my backup job various ways in Backup Central -- both as "multiple items to single location," and as "one on one folder backup." I've tried both with "Archive Mode" selected and deselected. Google Gemini told me I should deselect an option called "Keep extra files at the destination" -- but that option does not exist.

Out of the job-options, the only one I've played around with is "Archive Mode." And while having that option de-selected does DRAMATICALLY increase the time it takes for a backup to complete -- to the degree that I'm fairly sure that with Archive Mode de-selected, it's actually doing a complete backup of every file every time, rather than just backing-up changes -- in either case, the job fails to delete files that were deleted since the last time the job ran.

I've left all the other options deselected in every case, since none of them seem relevant:
Support sparse files replication
Support symbolic link replication
Eject USB device when backup completes (I don't want it ejected)
Mission Mode (I don't want the job to terminate after a certain time; I want it to finish)

Anyway, any help in this matter is appreciated. I can't believe it's been such a tough nut to crack. I feel like, for most home-users like myself, this would be the preferred way of making backups. But shoot, maybe I'm a weirdo?

Hi r/asustor,

My AS5402T came missing one of the heatsink screws causing it to overheat constantly. The heatsink is supposed to be held by two screws on diagonal corners, but mine only had a single screw installed. Unfortunately, I realized this issue after the return period, but while it is still under warranty. They have issued an RMA. However, somehow they are expecting me to cover the shipping cost. They manufactured the unit with a missing part and now it's the customer's duty to spend more money to get a complete unit. How does this make sense? That should be the operational cost of having a bad QC department.

I requested a prepaid label from the technical support, waiting for a reply (which is usually once in 24hr). Does anyone else have other ideas on what to do/try in the meantime?

Thank you all

Update:

Asustor technical support has provided a prepaid shipping label. Thank you everyone for the other ideas.

Hey everyone,

I built a community site called ASUSTOR Repo Community (ARC) for sharing third-party ASUSTOR NAS apps.

URL: https://www.asustorapps.org/

The goal here is just to have an open place where developers and users can share and find these community packages.

If you have an app you'd like to share, feel free to upload it, and I'd love to get any feedback or suggestions on the site!

Been running into an issue for weeks now with a support ticket every time the power is cycled. My volume is present and shows 60% full and has no visible data or folders. Support does some SSH commands that have not been shared and magically I can see my files again. The first item that was mentioned to me was an issue with a SMART test and required me to replace one of my drives, they are all healthy now. The suggestion now is to do a factory reset with the drives installed and wipe all the volumes and basically start over. I have asked multiple times what the SSH commands are with no response and this solution would require me to fork over another $500 to get resolved buying more drives.

This is obviously some sort of a bug and the firmware update/disk defragment/disk checking utilities have not fixed the problem

I've been trying to troubleshoot this issue without success while attempting to perform an ADM update. Are there any known ways around this, or do I have to perform a manual update?

Hello guys, I had a RAID with 2 WD RED Disks, I replaced one of the two which was in slot-1.

The RAID-1 rebuilt correctly and all works, but as you can see now the new disk in slot-1 is repeated two times (?) with the same data in the GUI, plus every time I turn on the NAS it says the RAID is broken with 1 faulty disk(s), while in reality it's working. What could I do?

I've got a 2-disk NAS, but storage is slowly filling up. The drives are still relatively new so I don't want to throw them out yet, but I want more storage.
Are there some (relatively simple) ways to connect more drives to the NAS next to the 2 internal HDD's?

Hey folks,

I've got an Asustor Drivestor 4 Pro AS3304T with 4x 12 TB SeaGate IronWolf NAS drives. One drive threw a S.M.A.R.T. error so I bought a replacement MDD 14 TB NAS drive (which registers as a Toshiba when plugged in). It's setup in RAID10 and everything I've read online (and my own recollection from upgrading storage) is that I just need to remove the faulty disk and replace it with the new disk. I did that, Asustor detects the new disk and shows no errors on that disk, but it is not syncing it or rebuilding the RAID10 at all. Status on the new disk is "Inactive."

What am I missing here?

-Update 1-
None of the drives are 4K native hard discs.
The new MDD has a firmware version of 4904. All of the older drives are firmware version SC60. I don't know if this mismatch is a problem--I haven't read of it being a problem anywhere.

-Update 2-
The issue was resolved by formatting the disc. It took me at least eight tries to format, I had given up hope but tried it one more time. Thank you to those who pitched in. I'll reflair this post and leave it up in the hopes it may help answer someone else's question down the line.

My NAS prompted an ADM update early this week. Ever since applying it, all my systems have daily trouble connecting to it, saying the provided credential is incorrect. I domain joined it and added the security groups to various permissions so authentication would be automatic. All user credentials are working properly except the NAS this week. It put me on ADM 4.3.3.RWC1 and it doesn't look like there's a rollback option.

I do also have some local users in the NAS from original setup. Mapping drives with those credentials ends up with the same problems. It's happening with both Linux and Windows clients that have mapped the drives.

Is this a known issue? Is there a fix?

EDIT: Solved for now. Microsoft bypassed WSUS and pushed a server update to all of my Server 2025 systems without my approval and that broke AD authentication on the NAS. Rolling back the update broke domain trust relationship with everything that wasn't a server so I had to unjoin and rejoin everything. That ended up fixing the issue. AD authentication to NAS shares is stable again.

Hi all,

Anyone had any luck setting up Cloudflare R2 as the target for Cloud Backup Center?

Every time I try I get the error

Invalid access key. (Ref. 5001)

This occurs despite correctly copy/pasting the server, access key ID, and secret access key.

My hunch is that it's trying something outside of the permissions boundary of my bucket-scoped object read/write token, but I'll be damned if I'm going to give it admin access to my R2 account.

Anyone set this up successfully? All the usual resources are coming up dry.

My vomume1 hdd is showing bad sector .. I want to use volume2 as main app center and remove volume1 .. how to do that ..

I am using As5402t-5074

I'm writing to report a reproducible USB 3.0 compatibility issue with my Terramaster 2-bay enclosure that I believe is related to UAS (USB Attached SCSI) support on its ASMedia USB-SATA bridge (USB ID 174c:1356).

Setup:

\- Terramaster 2-bay enclosure, 2 drives configured as an 8TB RAID1 mirror via the enclosure's hardware switch

\- Volume formatted exFAT

\- Connected via USB to a Linux (Debian) host

Issue:

When connected to a USB 3.x port on the host, the enclosure experienced intermittent I/O errors (dmesg showed "Synchronize Cache failed" and improper unmount messages) that required remounting to resolve. During a large file transfer, one of the drives went fully offline with repeated WRITE I/O errors, forcing the filesystem into read-only mode to protect data.

Diagnosis:

dmesg logs pointed to UAS protocol timeouts between the host's USB 3.x controller and the enclosure's ASMedia bridge, including "uas_zap_pending" and "data cmplt err -71" command timeout entries. I attempted a usb-storage quirk on the host to disable UAS for this device, but this caused the host to hang during boot with the drive active but the OS never reaching login, so I reverted that change.

Workaround:

Connecting the enclosure to a USB 2.0 port instead of USB 3.x resolved the issue entirely - clean mounts, no I/O errors, and no UAS timeouts in dmesg, since USB 2.0 doesn't negotiate UAS. I also verified data integrity separately using chkdsk on a Windows machine, which found only minor volume bitmap corruption (no bad sectors, all files intact) and repaired it cleanly.

Questions:

1. Is this a known compatibility issue between this enclosure's ASMedia bridge and UAS on certain USB 3.x host controllers?

2. IAnyone aware of a firmware update planned or available that addresses UAS stability, so I can use USB 3.0 speeds reliably instead of relying on USB 2.0 as a workaround?

Just came back from a days work and wanted to check how far my merge was and say my nas was not reachable .. so did the logical thing and checked.

So basicly my ups got activated (while thare was nog woper outage) and that switched everything off (usb was not connected to the nas) so after running without ups everything was fine exept the nas.

My led on the powerbrick (asustor trafo) is on

Nas screen and leds are off

Powerbutton does nothing

After everything off and plugging back in does nothing

Pls help... :(

I bought renewed drives when I bought my unit, and I'm on my 3rd failed drive (yay). Fortunately they have not caused me any data loss or issues. Unfortunately I am out of warranty, and I don't want to keep these drives (WD/HGST Ultrastar 10tb drives) or buy from this seller again. Looking at my options I know I cannot go down in size, but what about going up in size? that shouldn't cause me any issues, but I cannot utilize the additional space, Unless I replace all the drives with the same, correct? if I upgrade them all slowly over time, would I then be able increase capacity after they are all upgraded to larger drives?

I have Asustor Drivestor 2 Gen 2 and most of the time it is sat there with the drives spun down so no real heat being generated but the fan noise is so loud. I was wondering if there is some command you can run to stop the fan. There is not much in the settings as it will not allow me to set a curve of zero.

Looking for the exact kernel .config used to build ADM5.1.3_x86_64_kernel_6.6.x (published on the asgpl SourceForge GPL source releases), or the corresponding vmlinuz/kernel image if it has CONFIG_IKCONFIG embedded.

Context: I'm on an FS6706T running ADM 5.1.4.RL21 (kernel 6.6.x, TRUESUBLEVEL 44). I'm trying to build an out-of-tree r8152 module (to add RTL8159 chipset support, USB ID 0bda:815a, which isn't in ADM's stock driver) against the published GPL kernel source.

The module builds fine and has the correct device alias, but fails to load with:

"module r8152: .gnu.linkonce.this_module section size must match the kernel's built struct module size at run time"

This points to a struct layout mismatch between my build (generic x86_64_defconfig) and whatever config flags Asustor actually used - things like CONFIG_MODULE_SIG, debug options, or other struct-affecting options that differ from the defaults.

I don't have access to /proc/config.gz, /boot, or anything in /volume0 on the NAS itself - none of the usual places expose the running config.

If anyone has:

1. The actual .config Asustor used for this kernel/ADM version, or

2. A vmlinuz/kernel image with IKCONFIG embedded I could extract it from, or

3. Has successfully built and loaded a custom out-of-tree module (r8152 or otherwise) against a recent ADM x86_64 kernel and knows which config flags matter

...I'd really appreciate a pointer. Happy to share my current .config and build logs if that's useful for comparison.

Thanks!

Sorry, excited newbie question, potentially quite stupid:

if I add a USB wifi dongle to an Asustor Drivestor 2 Pro AS3302T would it be able to connect to my home network?

Within ten minutes of opening the box, my disks were initialized and I skipped the tutorial - but upon skipping the tutorial, it led me to disable SFTP and terminal services until I configured fully / needed it or not.

A ton of polish, largely saturates internal read and write speeds over 2.5g nic.

My life just got so much easier managing the family media. Worth double what I paid imho . Highly highly recommended for file serving and cloud services