I have a web/mail server that I'm taking down soon. I have always had its cert get copied over to my Asustor machine for the immich docker app I use. So it appears that I will need to revert to a self-cert for the Asustor system.

Has anyone done that successfully? Had any issues?

Hello, is it possible to run ADM 5 on an older but still capable device like the AS6204T?

Hi everyone,

I'm trying to decide between an ASUSTOR NAS and a Synology NAS, and I'd really appreciate hearing from people who actually use ASUSTOR.

My main use case is pretty simple:

Backing up photos and videos from multiple smartphones.

Backing up files from a few Windows PCs.

Storing family photos and documents.

No Plex, VMs, Docker, or other advanced workloads.

Reliability and ease of use are much more important to me than raw performance but still need to perform.

For those of you who chose ASUSTOR instead of Synology:

Why did you choose it?

Are you happy with your decision?

How has the mobile photo backup experience been?

Is the software stable and easy to use?

If you were buying today, would you still choose ASUSTOR over Synology? Why or why not?

I'd especially appreciate feedback from anyone who has used both brands.

Thanks in advance!

I've currently have an old Synology where I run my plex server but I've grown tired of the anti-consumer stuff and quick money grab schemes they've been doing for a few years now si I'm planing to leave Syology and set my sights on Asustor instead.

What I'm wondering about here is if it's possible to switch the OS on an Asustor? I've wanted to give either Open Media Vault or True/FreeNAS a try but I'm not sure if it's possible to do such a change on Asustor or not?

And as I mentioned above I'm currently running a plex server and wonder which current model of Asustor would be recommended for managing a media server on? Preferably a NAS with four HDD slots and the possibility to add an SSD as well.

Hello guys, since some time I am having a little bit of a trouble backing up my Mac to the NAS.

Basically the laptop says the network drive is unavailable, no matter what I do.

The ONLY way to make it work is to toggle off and back on the tick on the enable SMB service (or on the special MacOS option tick on ADM) and then it instantly starts working.

I reboot my NAS daily so as long as I don't do that tick cycle my TimeMachine does not work.

MacOS is ABLE to access other shares on the same NAS. Why is that?

HI all.

I am using Asustor AS6602T currently updated to the latest version 5.1.3.RI81.

Using Macbook Pro 14 M5 running latest macOS Tahoe 26.5.2.

Today I have noticed that when browsing files on local network on the NAS, the folders in FINDER are looking empty (there is definitely content in those). Browsing on Windows PC works normally. No matter what I've tried, the folders still look empty. (restart NAS, restart macbook, reconnected the NAS, etc.)

All was working normally just a few days ago.

Content on windows PC or on NAS web interface is present normally.

When I try to download the folder content via the web interface to MAC and they try on MAC to copy it into the folder where it was supposed to be located it shows errors (randomly). As if finder cannot copy the same file into that folder because same file is already there, or it simply has issues displaying the content of the target folder.

The operation can't be completed because one or more required items can't be found / error code -43

Permissions on NAS Shared Folder Privileges are set for the specific user to read and write
Services / SMB is enabled, highest SMB version set to SMB3, Lowest SMB set to SMB2, SMB signing set to default, Samba VFS modules are enabled

folder on finder showing no content
https://ibb.co/zgcjwK7
Folder on NAS web interface showing normally
https://ibb.co/KcVNLW49

Any ideas?

I had a fine magnetic dust filter over the 120x120x25 fan on the back of the 6-Bay Gen3 Lockerstor.
Then noticed that the dust was on the inside of it, not the outside.
WHAT?

The fan is pushing air out of the back of the Lockerstor, it's getting brought IN from the 3 sets of dot-holes on top and sides.
AND I presume, through the spaces between drive bays - so, the front of the NAS.

This is WAY harder to stop dust getting in.

If I reverse the fan, and use it to pull air IN then the air goes out through the dot holes and (presumably) the front between bays,
Will that have a drastic negative effect?

Or

How else can I manage dust intake? Especially preventing dust coming in between bays and caking up the bays and drives themselves.
Not to mention dust on SSDs and the boards.

Thanks all

way is asustor not support adm 5.0 on old asustor it can run it.

I have a AS5402T-20AB with two SSDs. It holds a combination of saved TV shows, movies, family videos and family pictures. When I see that the Plex and UPnP2 services are down (because I cannot see the content on my TVs) I usually reboot the unit and they start working again.

Recently I've tried to dig into this more. I disabled both apps for several minutes and enabled them, because I saw something about re-indexing. I've assumed the both these apps failing after only a few days seemed to have a common cause, but I've been checking them daily and noticed that they actually fail independently. A couple of days ago Plex wasn't working but the media server was for UPnP2. I disabled and re-enabled Plex then it started working. Today I noticed the opposite - UPnP2 wasn't working but Plex was. Again, I restarted UPnP2 and it began working again. I never have trouble getting to music, videos or pictures using the mobile apps like AiMusic, AiFoto and AiVideos.

Nothing is really showing up in the system logs. It's plugged directly into my home router and my TVs are wireless from the same device. The firmware is up-to-date and so are the apps.

Any suggestions to further troubleshoot this issue?

I'm looking for a file manager app (total commander / midnight commander) like for asustor. a supported one. Is there any? apt and opkg is seems to be non existent on the nas to simply install a package.

I also went down the route to add opkg to path because by default it's not added by entware.
But after addig it then the wget will fail which try to download the package..

1. The troubleshooting part:

My AS6806T is disappointingly unstable. It spontaniously reboots every few weeks and there's never anything in the logs about it. Set up remote syslog, smnp traps and monitor temps using snmpwalk from an external device and there's nothing to explain why it is happening; one minute the device is looking fine, the next it's rebooting with no warning/message.

The only odd thing I occasionally see is that the the system temp reads as 0 in the GUI and I think one of the fan speeds would read that too, but it's obviously not right as I've checked that the fans are very much running and CPU and HDD temps are completely normal even when it was reading as 0. In fact my experience has been that the system ran for more weeks if that error was present.

Eventhough all other temps looked normal, I set fan speed to max rather than dynamic just to make sure it didn't get hot. Normal temps for me is system: 31 C, CPU: 42 C, 8 x HHDs: 38 - 42 C, 2 x NMVe: 35 C, which I believe should be completely fine.

The only thing in dmesg that looks wrong and I sense may have a connection to this is:

[ 5.973420] [MCU::PIC16F1829] asustor_mcu_probe fail -2
[ 7.509446] [MCU::PIC16F1829] asustor_mcu_probe fail -2
[ 9.045442] [MCU::PIC16F1829] asustor_mcu_probe fail -2
[ 10.581442] [MCU::PIC16F1829] asustor_mcu_probe fail -2
[ 12.757437] [MCU::PIC16F1829] get mcu version F F

Updated the post with the following finding:

I found some older syslog files in: /volume0/@system/kernellog which contained thousands of lines of:

2026-06-14T21:54:11.554616+00:00 AS6808T-1 kernel: i2c_designware AMDI0010:03: controller timed out
2026-06-14T21:54:11.554632+00:00 AS6808T-1 kernel: i2c_designware AMDI0010:03: IC_STATUS = 6
2026-06-14T21:54:11.554634+00:00 AS6808T-1 kernel: i2c_designware AMDI0010:03: no resource, Failed to reset adapter 0
2026-06-14T21:54:12.578624+00:00 AS6808T-1 kernel: i2c_designware AMDI0010:03: controller timed out
2026-06-14T21:54:12.578640+00:00 AS6808T-1 kernel: i2c_designware AMDI0010:03: IC_STATUS = 6
2026-06-14T21:54:12.578642+00:00 AS6808T-1 kernel: i2c_designware AMDI0010:03: no resource, Failed to reset adapter 0

I have some experience with other PIC MCUs from decades past and I'm surprised to see such a thing tiny microcontroller in this device and my gut feeling is that FAN control and possibly watchdog-type functionality could be part of its job description. Anyone know more?

From the system log, I counted that it has crashed/rebooted 25+ times now in little over 16 months. I find that totally unacceptable.

2) I've now ordered parts for a complete DYI NAS-build now as I just cannot tolerate the Asustor NAS being this unstable. It was horrible expensive and with current HDD prices, I opted not to buy any new HDDs.

My thoughts is that since the storage (8 x Exos 20TB in a RAID-6 configuration and brtfs filesystem) looks to be standard Linux "mdadm" software-raid, that it _should_ be possible to simply move all disks over to a new computer and mdadm should be able to re-assemble the correct setup using metadata on the disks and I would lose no data. Am I wrong in thinking it will be that easy?

Is there anyone here who has attempted this, if so, how did it go? or anyone else seeing possible problems here?

This guide uses a missing three-disk RAID 5 Btrfs volume2 (/dev/md2) in a ASUSTOR LOCKERSTOR 6 Gen2 with ADM 5, no NVMe cache as an example.

⚠️ Note: To restore the proper volume configuration data, it is advisable to have a backup copy of your /volume0/usr/etc/volume.conf file.

USE AT YOUR OWN RISK

Problem Context

When disk volumes (such as a RAID 5 array) are temporarily removed from an ASUSTOR NAS to utilize the physical drive bays for alternative purposes (e.g., MyArchive drives), the ADM 5 operating system automatically purges the volume registration entry from its internal configuration database.

Upon reinserting the original drives, the NAS kernel may recognize the physical disks, but the ADM storage daemon ignores the array during startup, rendering it completely invisible in both the web interface (Storage Manager) and the system directory tree, despite the metadata and data remaining completely intact.

After conducting some tests and experiencing some failures, I finally performed a successful procedure. I then created a comprehensive summary in the hope that this guide would be useful to others.

I assume that the user has some Linux knowledge, but any doubts should be answered by the current AIs. For free AI, I recommend using Gemini. I also assume that the user knows how to access the NAS terminal and the status of the missing RAID was good when the disks where removed.

Phase 0: Diagnostic and Array Discovery

Before attempting to mount or register the missing volume, you must determine how the Linux kernel is currently interacting with the reinserted disks. Often, the kernel automatically flags the discovered partitions but locks them inside a temporary, high-numbered Multi-Disk node (such as /dev/md127 or /dev/md126).

1. Check Active Storage Arrays

Run the following command to view the current status of all Multi-Disk devices recognized by the kernel: bash cat /proc/mdstat Scenario: You might only see your main volumes (e.g., md0, md1, md3). However, if a rogue array appears as md127 or md126 showing an inactive or unmapped state alongside your missing drive partitions, it must be cleared.

2. Inspect Block Devices and Partitions

To identify which physical disks are unmapped and belong to your missing array, list all available block devices: ```bash

Use fdisk to review partition layouts

sudo fdisk -l `` Identify the component storage partitions (usually the largest data partition on each drive, e.g.,/dev/sdd4,/dev/sde4,/dev/sdf4`) that correspond to the missing volume.

3. Verify and Stop the Ghost Array

If the drives are trapped inside a temporary container like /dev/md127, you must inspect its details and gracefully shut it down to release the disk resources: ```bash

Verify the underlying metadata of the ghost array

sudo mdadm --detail /dev/md127

Stop the array to free up the physical drives/partitions

sudo mdadm --stop /dev/md127 ```

⚠️ Note: If you skip stopping the ghost array, any subsequent assembly command will fail with a "Device or resource busy" error.

Phase 1: Kernel-Level Assembly and Manual Mount

Once the disk partitions are completely released from temporary kernel locks, force the Linux subsystem to properly assemble the underlying RAID array under a standardized logical node.

```bash

1. Assemble the RAID array using an available floating logical MD node (e.g., /dev/md2)

sudo mdadm --assemble /dev/md2 /dev/sdd4 /dev/sde4 /dev/sdf4 cat /proc/mdstat

2. Create a clean mount point directory in the root tree

sudo mkdir -p /volume2

3. Mount the Btrfs file system manually to verify data health

sudo mount /dev/md2 /volume2 ```

💡 Result: If successful, the array will report a healthy state (e.g., [UUU]), and your files will become instantly accessible via the Command Line Interface (CLI) under /volume2.

Phase 2: Gathering Configuration Data for Generalization

To adapt this procedure for your specific system or share it as a template, collect the following four parameters from your operating environment to build the permanent ADM metadata block.

1. Extract the Exact RAID UUID

The UUID specified in the system configuration files must precisely match the metadata blocks written onto the disk headers. Query the newly assembled device: bash sudo mdadm --detail /dev/md2 | grep -i "UUID" Example Output: UUID : 12345678:abcdef01:23456789:abcdef01

2. Map the ASUSTOR "Index" (Drive Bays)

The Index parameter represents the 0-indexed sequence of the physical drive bays where the array resides. ASUSTOR maps drive letters to numeric indices sequentially: * Bay 1 (sda) ➔ 0 * Bay 2 (sdb) ➔ 1 * Bay 3 (sdc) ➔ 2 * Bay 4 (sdd) ➔ 3 * Bay 5 (sde) ➔ 4 * Bay 6 (sdf) ➔ 5

Application: For an array sitting in physical Bays 4, 5, and 6, the resulting string must be defined as Index = 3,4,5.

3. Match the RAID "Level" Value

ADM reads standard numerical definitions to determine RAID layouts: * RAID 1: Level = 1 * RAID 5: Level = 5 * RAID 6: Level = 6 * Single / JBOD: Level = -1

4. Determine the "Raid" Key Identifier

The Raid variable in the configuration block matches the integer value of the Linux Multi-Disk device wrapper. * If your array is running under /dev/md2, use Raid = 2. * If it is running under /dev/md3, use Raid = 3.

Phase 3: Permanent Registration in ADM 5 UI

ASUSTOR abstracts persistent configurations using an internal symbolic link called .volsystem, which physically routes system parameters to the hidden storage array mounted at /volume0.

```bash

1. Back up the original storage configuration file

sudo cp /volume0/usr/etc/volume.conf /volume0/usr/etc/volume.conf.bak

2. Open the configuration file using a text editor

sudo nano /volume0/usr/etc/volume.conf ```

Scroll to the very end of the file, insert a blank line after the final active volume section and add the missing configuration block.

⚠️ Warning: These values must be adjusted according to your configuration and depend on factors such as volume, RAID level, file system and cache configuration. Use the presented values as a starting point.

ini [volume2] Level = 5 Raid = 2 Total = 3 Option = 0 Ftype = btrfs UUID = 12345678:abcdef01:23456789:abcdef01 Index = 3,4,5 Cachemode = 0 S0UUID = S1UUID = CLevel = 0 CState = -1 CDirty = 0 CUUID = Cnumber = 0 CIndex = Cseqcut = No CsizeMB = 0

Phase 4: Validation & Persistence Verification

1. Hot Detection Check: Because the ADM 5 framework utilizes background file monitoring (such as inotify), saving your modifications to volume.conf will trigger the web GUI daemon to instantly parse the changes. The volume will dynamically materialize inside the Storage Manager app in real-time.
2. Persistence Test: To guarantee the automation routine executes correctly during cold boots without requiring manual shell access, perform a graceful reboot: bash sudo reboot

Final Verified State

Upon reboot, ADM's built-in initialization sequences natively read the injected parameters inside /volume0/usr/etc/volume.conf, automatically assemble the correct multi-disk array, and securely mount the Btrfs layer onto /volume2. Full visibility is permanently restored across File Station, system services, and network shares.

MRiscoC with the assistance of Gemini

yesterday it is working great.. but today when i am transferring data - it shows some files could not be moved from my external sdd to external hdd. what could be the reason and any fix to it? I tried restore factory setting but did not solve it.

external sdd to my hdd inside the nas is okay = no issues

hdd inside the nas to - external hdd + files could not be moved

external sdd to external hdd + files could not be moved

please help external hdd is for my plex server -- currently when using plex still working okay

Recently purchase a AS6704T v2, When I using PLEX to play 4K HEVC video, it lags. Should I replace both RAM to 8gb*2 or just a 16gb on top ? Or it is not the RAM problem at all ?

It said it supports up to 16gb, does it mean the one on top or total RAM ?

Also what is the mhz recommended ? I dont see any recommended RAM here.

Hi everyone, I'm considering choosing a NAS server. I'm considering an Asustor AS5404T or Synology DS925+. (I already have two 16TB WD HC550 drives to start with.)

My problem arises because I want the NAS to backup primarily from my four different phones at home, so that each one has automatic photo backups. I also want to back up my Windows computer and laptop (I've seen support for Synology's ABB app here, but what app use Asustor and how does it work on Asustor?). I also want to view photos and videos on my TV. Is there a dedicated app for viewing them? Unless I'm limited to network sharing? And of course, remote access to my photos and files when I'm away from home is important to me. (And a possible feature where I share a link to my folder/file with someone and they can connect and download only that specific file [because the link itself is valid for, e.g., 48 hours].) For now, I'm not considering installing any applications on the VM, but it's possible that something like a home assistant will appear in the near future. I'm asking for help choosing which NAS to choose (I have a lot of ASUS devices at home, so I'm considering the Asustor, but I don't know anything about using the Asustor system. As for Synology, I've only had contact with the ABB package, and that's it).

• 64Gb Ram (works fine)
• 2 x Optane M10 16Gb as Cache (works fine)
• 1 x 4Tb NVME
• 1 x AQ113 network NVME card
• 6 x 14tb drives in raid 5. 70Tb.

I like this nas, it has a great look, and expandability is great. IMO its the expandability that really puts this NAS into enthusiast space. Shame it wasn't a regular PCIE slot and mount. But the NVME mounts are functional. I wonder about putting a SATA NVME controller in there. Having a bunch of rear sata ports.

Suggestions for the future models:

• Use a better fan (can a 140mm fit?), perhaps with an easy remove magnetic filter?
• Another rear USB port. UPS + Drive expansion? Or USB accessory.
• Consider a better CPU like the J100. Its 50% faster. Intel 1315U (with ECC support and PCIE4). I know there is a Ryzen version, but intel is still great for a NAS CPU with its IGP. This is still a Prosumer media device, so IGP is still probably more useful than just raw horsepower. PCIE4 would mean 2 x 10Gb ethernet, and still have 4 NVME with PCIE4 bandwidth.
• Shame there is no 2.5 storage, I know, I know, its too much, but if some of the space was reconfigured it may have been possible to have some internal 2.5 SSD in this 6 bay.

My ASUSTOR AS6604T LCD Panel won't turn on anymore.
What can I do?
I restarted it but it still doesn't work. I turned it off and on again after a few minutes, the LCD Panel is dead.

Question regarding admin access to user folders. I have added a friend to my Lockerstor, she want to upload photos or what not to stop using google drive. Great. I have been fiddling with settings for two days trying to make it so admin accounts can't access the contents of her user folder. I can't for the life of me get it to work. Is it not possible to keep the admin out of individual user accounts stuff since ya know, admin and all? I have been looking at permissions through access control, used the file explorer to edit individual folders and set the owner as the only one to access it and denied access to groups and others, but still, can see it all. I have even tried checking the permissions through ssh, but still.....its driving me nuts!!

Hey all,

Preface/situation: I am no expert. I'm a guy with media and I want it to last and set up a NAS to do so. I had 2 12tb HDDs on RAID 1 (I like redundancy). They were 95% full, and I've been planning this expansion.

I installed 2 new 12tb HDDs (now total of 4) and converted to RAID 6 (still like redundancy).

(I also have a backup of my media, but local. I can't afford offsite/cloud storage for that much data.)

Process: I've been watching the process unfold on ADM, and have noticed something I could not find in documentation online (though I might have missed it): ADM first converted 2 HDDs @ RAID 1 to 3 HDDs @ RAID 5... now that it completed that, it has added my 4th drive, and is now converting the whole mess to RAID 6.

I was afraid I had made a mistake and chose RAID 5 instead of 6, but I noticed that only 3 drives were being used to convert to RAID 5, so I waited, thinking there might be an extra step. I was actually right.

TL;DR: Today I learned that going from RAID 1 to RAID 6 is a two-step process that includes going through RAID 5 in the middle.

Edit to add: the whole process took about six days. My drives were both 95% full. As mentioned in my post, I added two new drives to two existing drives. I then followed the instructions to convert from raid one to raid six. The ADM first converted from RAID 1 with the two original drives to RAID 5 with three drives (ignoring the fourth), and then converted that to rate 6 while adding the fourth drive. The second process of converting from RAID 5 to RAID 6 took at least twice as much time as converting from RAID 1 with two drives to RAID 5 with three drives.

I hope this can be helpful to someone. Good luck!

Hello. The App Central widget apparently installed a non-docker version of nginx to reverse proxy https-http for installed apps such as immich, sabnzbd, etc. This was fine when I was simply using my LAN to access things, but now I have a public IP address available and cannot figure out how to do these two things:

Generate certificates for the following: videos.mydomain.com to Jellyfin, photos.mydomain.com to Immich and files.mydomain.com to NextCloud. The Web Center ADM app says I have no implementation or web server installed. It appears the general solution for DNS-01 challenge certificate generation is certbot, but I cannot find Asustor specific installation instructions that do not involve CloudFlare. PHP3 and pip3 are installed and functioning.

Setup reverse proxy's for each of the apps listed with appropriate certificates. I don't much care if I use ADM's reverse proxy or something else, but would like some assistance getting these three services configured on https on the public address.

My router is already configured to only allow 80 and 443 to the NAS.

TIA

Bonjour, j'ai un disque dur wd800ffbx sur mon nas asustor as6302t, mais le soucis c'est que lorsque je branche sur mon nas (en jingle), il est inactif.

Comment le résoudre svp car j'jai des données de 8To dessus et je n'ai pas de PC pour faire la manipulation avec un docker SATA.

Cordialement,

Is anyone having issues since updating to this version?

Ok home Asustor. I am looking for some input.

I have a reasonable home lab, but I am disappointed with my NAS. Its a Asustor Lockstar Gen2 6 6706t.. 6x14tb, 64Gb ram, a 4Tb SSD.. Nice.. Raid 5.

However when doing thumbnails it sucks, very laggy, and really seems to be hit hard with raid 5 thrashing.. My AI image server is pointing to this, so generating hundreds of large many Mb images, and then when trying to view all the mess its making the thrashing for thumbnails. It can take 20-30 seconds to get one thumbnail (but then lots come in pretty soon I assume its creating 10 thumb nails at the same time and not caching writes.).

I was looking at using 2 x 16Gb Optanes as cache (you need two under raid, although it will do Raid5 with 3 - but I want to keep my 4tb NVME as a workspace, and I have 10GbE AQ113 nvme to add 10GbE to it).

I thought the ram would solve my problem, but it doesn't seem to be caching writes, and it doesn't solve the raid 5 problems with small files. Seems great for reads.

Is 2 x 16Gb Optane enough, it would seem to be enough for small files ~30mb, low latency, high endurance. I have some 512Gb PCIE4 NVME I can use, but that seems like a waste for just cache, and honestly I worry about write cycles.. I have loads of ram for network buffering and read buffering, but the write stuff particularly with small files across a 6 drive raid 5 is painful. Sustain writes are fine..

These 16Gb Optane are cheap.. $10 USD delivered. Would this solve my problem and does anyone else use them? While 16Gb isn't that big, its still almost a minute of 2.5GbE bandwidth. So when writing lots of small files intermixed with reads, or thumbnailing etc it would seem to offer a big performance boost. It has lots of ram, the disks are fast, and I have 4tb nvme in there anyway.

Is anyone else using these?