[Help] Diagnosing USB Errors/Disconnects with Terramaster D6-320
Posted: 26 Apr 2025, 16:38
I have three HDDs inside a Terramaster D6-320 that is connected via USB to a Beelink S12 Pro Mini, and pooled together via StableBit Drivepool. Everything is on the latest available software, and on Windows 11.
One of the HDDs' partition table was corrupted, and other strange errors began to prop up, including StableBit Scanner detecting multiple bad sectors.
When I checked the Event Viewer, I found constant "Event 129, UASPStor," with the description "Reset to device, \Device\RaidPort44, was issued (with different RaidPorts each time) and "Event 153, disk" logs, with the description "The IO operation at logical block address 0x24dabc32f for Disk 1 (PDO name: \Device\0000022f) was retried", with different block addresses and disks each time. This is supposedly common with the virtual drivepool disc, but it happened for all physical disks too.
I then retested the HDDs and Terramaster with the same USB cord on another Windows computer. This time StableBit Scanner found zero issues, and the Event Viewer showed no disconnects, and hasn't for days now.
I then ran StableBit Scanner with another external HDD on the Beelink S12 Pro Mini to check if the USB was at fault, and the external HDD scanned flawlessly, with no Event Viewer popups!
I've thus gone through the process of elimination pretty thoroughly, and I can only conclude that it is a specific issue with the Terramaster's "Raid"-type connections and the Beelink. But driver updates haven't helped either.
Just wondering if anyone has experienced anything similar and has some insight? If not, well, this will maybe be helpful to someone who googles it down the line.
Note that this is somewhat similar to another topic someone made on this forum, as seen here viewtopic.php?p=44379&hilit=Beelink#p44379.
One of the HDDs' partition table was corrupted, and other strange errors began to prop up, including StableBit Scanner detecting multiple bad sectors.
When I checked the Event Viewer, I found constant "Event 129, UASPStor," with the description "Reset to device, \Device\RaidPort44, was issued (with different RaidPorts each time) and "Event 153, disk" logs, with the description "The IO operation at logical block address 0x24dabc32f for Disk 1 (PDO name: \Device\0000022f) was retried", with different block addresses and disks each time. This is supposedly common with the virtual drivepool disc, but it happened for all physical disks too.
I then retested the HDDs and Terramaster with the same USB cord on another Windows computer. This time StableBit Scanner found zero issues, and the Event Viewer showed no disconnects, and hasn't for days now.
I then ran StableBit Scanner with another external HDD on the Beelink S12 Pro Mini to check if the USB was at fault, and the external HDD scanned flawlessly, with no Event Viewer popups!
I've thus gone through the process of elimination pretty thoroughly, and I can only conclude that it is a specific issue with the Terramaster's "Raid"-type connections and the Beelink. But driver updates haven't helped either.
Just wondering if anyone has experienced anything similar and has some insight? If not, well, this will maybe be helpful to someone who googles it down the line.
Note that this is somewhat similar to another topic someone made on this forum, as seen here viewtopic.php?p=44379&hilit=Beelink#p44379.