TERRAMASTER D6-320 External Hard Drive Enclosure - USB 3.2 Gen2 10Gbps Type-C HDD Storage Hot Swappable Plug and Play (Diskless)

I purchased the D2-320 2-bay RAID enclosure with USB 3.2 Gen 2 10 GbpsMy purpose with this unit was to mirror (RAID1) two 6TB WD Reds with a Linux machine. I’m not familiar with this brand, so I decided to test it a little before copying a lot of my files over to the D2-320.Getting everything working was pretty easy.I pulled out each bay, installing the drive was pretty easy, no screws needed. They provide a video on it if you’re unsure. I set the selector on the back of the unit to RAID1, shoved in both drives, connected the USB (drives are powered but won’t spin up until the USB is connected), then held the RESET button with the provided pin until the disk lights flashed. The system found one drive - as it should have.I wrote approximately 18K files and directories of various sizes to the array and then without disconnecting the USB or turning off the power, I pulled out one drive. I then connect the pulled drive directly to another computer to see that the files were in fact written to the drive. They were. All good to go.I replaced the drive. Both lights are green. Since no changes had been made to either drive, this is perfect, it didn’t try to rebuilt the arrayNext, I pulled the second drive out hot. Then connected that drive to the other computer and checked to make sure all files were also written to this drive as well. They were! It is working as it should be.I then created a couple files on the other drive and then replaced the pulled drive back into the D2-320. One drive light was blinking green, the other blinking yellow. According to the online documentation, this means it is rebuilding the RAID1 mirror. Perfect .. Everything is performing as expected. It did take a few hours to rebuild .. but these are 6TB drives, so that was expected.The USB cable provided seems adequate, USB C on both ends. If you need a different cable, consider that when purchasing.Average 1G file write 156 MB/s, average 1G read 221MB/s. Slow but these are mechanical drives connected via USB. Acceptable. Later, I watched a video using Jellyfin and reading, transcoding, and streaming worked perfectly fine.The large fan is quiet and seems to keep the drives cool. Airflow looks to be sufficient. How noisy the unit will be will depend on your drives. Some are louder than others.These drives will be part of a system I have in place which will be up and running 24/7. I’ll be very interested in seeing how well the Terramaster D2-320 performs in the long run. I’ll post updates after I have used them for some time.

Setup was easy and everything worked great right out of the box

After a week of use, I’m cautiously optimistic. No major issues, the one issue that did pop up was perfectly handled by the device hardware and firmware allowing a quick graceful fix. Will report back later after more use, but for now I recommend it for an affordable but reliable 10Gbps enclosure with both m.2 and SATA support.Why am I optimistic?I’ve already written 16TB to it, via two sustained 48+ hour zfs send. Pretty solid stress tests, I thinkMy configuration:Enclosure set to “Single Disk” (the default , passes through each drive)4x 16TB WD Red SATA drives (ZFS raidz2)4x 2TB WD Black m.2 NVME drives (ZFS mirrored pair, special for metadata and < 16kb blocks)Setup- The SATA sleds are tool-less, really nice. No major issues- m.2 was also easy once I checked the manual to see how to access the compartment (remove 2 screws, slide forward)First BootOne of the 4 SATA disks wasn’t being seen by the OS. I checked the helpful LEDs and sure enough one was not lit. Powered it all down, swapped the drive with another in a different bay. Booted up. Same issue with the same drive, different bay. So it’s the drive, not the bay. I knew the drive was functional (and had live data on it) so I swapped it back after first blowing into the connector in case there was dust or something. I also reconnected the tool-less rails, and was really deliberate when sliding in the tray of the problematic drive. Powered up - issue resolved. User error perhaps, but it’s fine nowFirst WeekI set up the ZFS pool as described above and immediately started a zfs send | zfs recv to copy an 8TB dataset to the new zpool on the DAS. Performance was as expectedRoughly ~24 hours into the send process, I noticed one of the m.2 drives in the mirrored pair had fallen off the system- the OS could no longer see it. Not a good sign. It was mirrored so the pool was still upThen I noticed the drive had actually had a USB reset - so the OS immediately re-detected it, just with a new device name (sdo instead of sdl).I closed the now-stale LUKS volume, reopened it with the newly assigned device name, added the device back to the pool/cleared the error state and the copy gracefully continued, the pool was healthy. Roughly 36 hours later, the whole operation completed successfully.Then I did it all over again, no issues this timeSo, for now, I’ve decided it might have been a quirk with the USB controller or OS. It might have been some other issue, but I’m not too worried. I haven’t been able to reproduce the issue, and it was handled gracefully by the OS, by ZFS and by the DAS. Everything worked correctly through a spurious failureSo, I’m happy.I deducted one star only because of the two quirks described above, even though neither were provably the fault of the device. If it runs for 6-12 months, I’ll add the 5th starCan’t beat the price, the forums are very active with vendor reps and it seems they take support very seriously and provide firmware updates for both “bugs” as well as configuration changes (to disable power saving features if desired, I think, is one example I saw)Value for money:Can’t best this price.

Worked great right out of the box. Installed the drives, plugged it in and worked perfectly.

I had high hopes that this would help me with my storage needs. I currently have a F4-423 NAS with 4x26tb drives in two RAID1 configs I use for media services. I had two additional 24tb drives so I purchased this D2-320 that I wanted for additional misc. storage. It took multiple tries to get the unit and HDDs to be recognized by the F4, but I was able to get a new Storage Pool 3 and Volume 3. I created shared folders and moved files to it. Everything seemed fine, but then I found that anytime either one, or both, are rebooted the HDDs still show up in the HDD list, but the Storage Pool/Volume/Shared folders for those drives are no longer available. On top of that, if I tested creating a new Storage Pool, it would do it and overwrite the existing data. Then again, once either of them was rebooted everything was gone again. I've attempted powering on in different orders, and according to support and documentation, but it doesn't seem to make a difference. Once a restart of any kind happens, the data is lost. For a Vendor to Vendor product specific to what I am trying to do, it isn't very compatible or stable. Maybe an update in the future will resolve this, but for now I think it's going back.*Not value for money*No ease of installation*No ease of use*Lots of frustration