Asustor Lockerstor 10 Gen3 AS6810T 10 Bay NAS, AMD Ryzen V3C14 Quad-Core, 16GB ECC DDR5 RAM, Dual 10GbE + Dual 5GbE, 4 M.2 NVMe SSD Slots, USB4 40Gbps, Enterprise Grade for Enthusiasts(Diskless)

Working great - nice and fast RAID5 operations. ;-) Was easy to setup.

Larry Moonan · 2025-11-24 · via amazon

I received the delivery without issues, and since the hard drives haven’t arrived yet, I’m currently testing with two M.2 SSDs installed. However, the WOL (Wake on LAN) feature doesn’t seem to work. I registered the MAC address for Wake on LAN in ACC and enabled WOL in the power settings within ADM, but it still doesn’t function. For comparison, the WOL feature works perfectly fine on my QNAP NAS on the same network. If the WOL issue gets resolved, I’ll update this review. Currently, I’m using ADM version 5.0.0.RA82. If it turns out to be a hardware defect... I’d be really stressed. I hope to receive some support to resolve this issue.

Victor · 2024-12-03 · via amazon

Love It. Makes watching movies much easier. Not a steep learning curve to setup.but still room to add features and learn more

Sardex · 2025-04-13 · via amazon

I purchased the Asustor Lockerstor Gen3 AS6710T (10-bay) and populated it with five 26TB Seagate Exos drives in a RAID5 configuration - nearly 100TB of protected storage, or so I thought. The NAS was connected to a UPS. When an extended power outage occurred while I was away, the UPS eventually depleted its battery and the NAS lost power. This single event completely destroyed the Btrfs filesystem. Not the drives - all five drives are perfectly healthy with zero bad sectors according to SMART diagnostics. The RAID array itself is fine and assembled correctly. What failed was the filesystem metadata, specifically the chunk tree and root tree that Btrfs uses to locate data on the drives. I spent over a week attempting recovery: btrfs rescue chunk-recover (20+ hour scans, multiple times) Manual superblock patching with corrected checksums Every mount option and rescue flag available Consultation with AI assistants walking through increasingly aggressive recovery attempts The chunk-recover tool found 65,000+ recoverable chunks but couldn't rebuild the filesystem because multiple critical metadata structures were corrupted simultaneously. The tools kept failing with circular dependency errors - can't fix the chunk tree without the root tree, can't read the root tree without the chunk tree. The data is still physically on the drives. The RAID parity is intact. But without the filesystem metadata, 64TB is completely inaccessible without professional recovery services costing thousands of dollars. Why doesn't this NAS support automatic graceful shutdown when UPS battery runs low? Many UPS units support USB signaling for exactly this purpose. The NAS should have detected the low battery condition and shut down cleanly before power was lost. Instead, it just kept running until it crashed. What's the point of RAID5 redundancy and a UPS investment if the filesystem can be destroyed beyond recovery anyway? Bottom line: Even with proper power protection, this device cannot be trusted with important data unless you're physically present during every power event or have comprehensive offsite backups. The Btrfs filesystem implementation is fragile, and Asustor provides no safety net for extended outages. 64TB of data, gone.

Eric B · 2025-12-19 · via amazon

Best Buy

Not tracked at this retailer

MSI

Not tracked at this retailer

Newegg

Not tracked at this retailer

Newegg (Open Box)

Not tracked at this retailer