USB Hub or Multi-Bay Dock Failed?
Your Drives Are Almost Certainly Fine.
When a multi-bay USB dock, Thunderbolt enclosure, or RAID-capable external chassis stops responding, every drive inside goes dark at once. That simultaneous failure is your clue: the drives did not fail. The enclosure's hub controller, power management IC, or Thunderbolt bridge chip failed. We extract each drive, connect it directly to PC-3000 via native SATA or SAS, and recover your data.
Free evaluation. No data = no charge.
How Multi-Bay Enclosure Controllers Work
A multi-bay enclosure (Sabrent 4-bay dock, OWC ThunderBay, Promise Pegasus, StarTech dual-bay) contains a hub controller that manages communication between the host computer and two or more independent drives. The controller handles protocol translation (USB, Thunderbolt, or eSATA to native SATA/SAS), port multiplier logic, and power distribution to each drive bay.
Some enclosures also run hardware RAID (RAID 0, 1, 5, or 10) on the controller chip itself. When the controller fails, the host computer loses access to all drives simultaneously. The drives continue to function; they have simply lost their communication path.
This is distinct from a single-drive USB-C bridge board failure, which affects only one drive in a one-drive enclosure. Hub controller failures affect every drive simultaneously because all bays share one controller chip.
Hub Controller Architecture
JMicron JMB585, ASMedia ASM1166, Marvell 88SE9230, or proprietary ASIC
Distributes 12V/5V to each bay via independent voltage rails
Routes data between host interface and individual drive bays
Standard 3.5" or 2.5" SATA/SAS drives, hot-swap in some models
How Hub Controllers Fail
Hub controller failures look identical to a multi-drive failure from the user's perspective: all drives vanish. The pattern of simultaneous failure across all bays is the diagnostic key.
Power Supply or PMIC Failure
Multi-bay enclosures use external 12V DC power supplies (typically 36W-120W). When the power brick fails or the internal PMIC blows a regulator, drives receive no power. The enclosure may power its indicator LEDs from USB standby power while the drives sit unpowered. Plugging in the wrong voltage adapter (19V laptop charger into a 12V input) destroys the PMIC and can cascade to the hub controller.
Thermal Failure of Hub Chip
Hub controller chips running four simultaneous drives generate enough heat to exceed their rated thermal envelope in enclosures with no fan. The chip develops solder joint microfractures from repeated thermal cycling and eventually stops responding. NVMe enclosures using ASMedia ASM2362 bridge chips are particularly susceptible due to the combined thermal load of NVMe drives and bridge controller in a sealed housing.
Hub Controller Firmware Corruption
Power loss during a firmware update or an unclean disconnect during a RAID rebuild can corrupt the controller's firmware. The chip powers on but cannot initialize its port multiplier logic. Drives are physically connected but the controller cannot enumerate them. Symptoms: enclosure appears in Device Manager as a generic "USB Mass Storage Device" with no child drives listed.
Cold Solder Joints on SATA Controller
The SATA controller chip (JMicron JMB585 for five ports, ASMedia ASM1166 for six) routes data between the host interface and individual drive bays. These BGA-packaged chips develop cold solder joints from thermal stress. Symptoms often start as intermittent detection of one bay, progressing to all bays failing as more joints fracture.
Wrong AC Adapter Voltage
Multi-bay docks use barrel-jack DC inputs with no polarity protection on some budget models. Plugging in a 19V laptop adapter into a 12V dock blows the 5V TVS diode first, then cascades to the PMIC and hub controller. In some cases, the overvoltage propagates through the SATA power pins and damages the drive PCBs. This requires board-level diagnosis of both the enclosure and each drive.
Thunderbolt Bridge IC Failure
Thunderbolt enclosures (Promise Pegasus, OWC ThunderBay) use dedicated Thunderbolt controller ICs (Intel JHL series) that bridge PCIe to the internal SATA/SAS controller. When this IC fails, the enclosure disappears from Thunderbolt device enumeration entirely. The internal drives and SATA controller may be fine; only the Thunderbolt bridge has failed.
How to Diagnose Hub Controller Failure vs. Drive Failure
Before assuming your drives have failed, check for these hub controller failure indicators. Do not run recovery software, chkdsk, or fsck on drives connected through a failing controller.
- Check simultaneous failure. Did all drives in the enclosure stop responding at the same time? Individual drives fail independently; simultaneous failure across all bays points to the controller or power supply.
- Test the power supply. Measure the DC adapter output voltage with a multimeter. Multi-bay docks typically require 12V DC. If the adapter is outputting 0V or the wrong voltage, replace it before concluding the controller failed.
- Check the enclosure's USB/Thunderbolt enumeration. Open Device Manager (Windows) or System Information > USB (macOS). If the enclosure enumerates as a USB hub but shows no attached drives, the hub controller has partially failed or its firmware is corrupted.
- Listen to the drives. Power on the enclosure and listen. If drives spin up normally (no clicking, grinding, or beeping), the drives themselves are likely healthy. The controller is the failure point.
- Do not extract and immediately reformat. If you remove a drive from a hardware RAID enclosure and connect it directly, the OS may prompt you to initialize or format the disk. Do not accept. The drive contains RAID metadata and partial stripe data that professional tools can reconstruct.
Mid-Transfer Disconnects Are Not Corruption
A common misdiagnosis that leads to data loss.
When a hub controller overheats during sustained file transfers, it drops the USB or Thunderbolt connection mid-write. The file transfer fails. The OS may report the target file system as corrupted. Users frequently respond by running chkdsk or Disk Utility First Aid on the affected drive.
This is the wrong response. The file system inconsistency was caused by a hardware disconnect, not by logical corruption. Running chkdsk or fsck on a drive connected through a failing controller causes additional disconnects during the repair scan, compounding the damage with each retry.
The correct response: remove the drive from the enclosure, connect it directly to a computer via a native SATA connection (not through another USB enclosure), and then evaluate file system integrity. If the drive is healthy on a direct SATA connection, the "corruption" was a controller-induced phantom.
Enclosures and Docks We Commonly See
Sabrent 4-Bay USB 3.0 Dock
USB 3.0 to SATA
Controller: JMicron JMB585
PMIC failure from sustained 4-drive load. Budget thermal design with no fan.
OWC ThunderBay 4
Thunderbolt 3 to SATA
Controller: Intel Thunderbolt + Marvell SATA
Thunderbolt bridge IC failure after firmware update interruption. Internal SATA controller usually survives.
Promise Pegasus R4/R6
Thunderbolt to SAS/SATA
Controller: Promise hardware RAID + Thunderbolt
Hardware RAID controller failure. Drives contain RAID metadata; do not initialize on extraction.
StarTech Dual-Bay Dock
USB 3.1 to SATA
Controller: JMicron JMS561 or JMS578
USB-C connector pad cracking from cable strain. Hot-swap socket oxidation causing intermittent detection.
Mediasonic ProBox 4-Bay
USB 3.0 to SATA
Controller: JMicron JMB585
Fan failure leads to hub controller thermal shutdown. Power supply degradation under sustained 4-drive load.
QNAP TR-004 / TR-002
USB 3.2 Gen 2 to SATA
Controller: QNAP proprietary + JMicron
Hardware RAID mode stores config on controller flash; software RAID mode stores on drives. Recovery approach differs.
How We Recover Data From a Failed Enclosure Controller
Diagnosis
We test the enclosure power supply, inspect the controller PCB under magnification, and determine whether the failure is the hub controller, PMIC, Thunderbolt bridge, or the drives themselves.
Drive Extraction
Each drive is removed from the enclosure and labeled by bay position. Bay position matters for RAID reconstruction: stripe order must match the original configuration.
Direct Imaging via PC-3000
Each drive connects directly to PC-3000 via native SATA or SAS, bypassing the failed hub controller entirely. We create sector-by-sector images of all drives independently.
RAID Reconstruction (if applicable)
For enclosures running hardware RAID, we use PC-3000 RAID edition to reconstruct the array from individual drive images. RAID metadata on the drives identifies stripe size, parity distribution, and drive order.
Hub Controller Failure Recovery Pricing
Hub controller failures are among the most affordable recoveries because the drives inside are usually undamaged. Per-drive pricing follows our standard tiers. RAID reconstruction from multiple drive images is quoted separately based on array complexity.
| Service Tier | Price | Description |
|---|---|---|
| Simple CopyLow complexity | $100 | Your drive works, you just need the data moved off it Functional drive; data transfer to new media Rush available: +$100 |
| File System RecoveryLow complexity | From $250 | Your drive isn't recognized by your computer, but it's not making unusual sounds File system corruption. Accessible with professional recovery software but not by the OS Starting price; final depends on complexity |
| Firmware RepairMedium complexity – PC-3000 required | $600–$900 | Your drive is completely inaccessible. It may be detected but shows the wrong size or won't respond Firmware corruption: ROM, modules, or translator tables corrupted; requires PC-3000 terminal access Standard drives at lower end; high-density drives at higher end |
| Head SwapHigh complexity – clean bench surgery50% deposit | $1,200–$1,500 | Your drive is clicking, beeping, or won't spin. The internal read/write heads have failed Head stack assembly failure. Transplanting heads from a matching donor drive on a clean bench 50% deposit required. Donor parts are consumed in the repair |
| Surface / Platter DamageHigh complexity – clean bench surgery50% deposit | $2,000 | Your drive was dropped, has visible damage, or a head crash scraped the platters Platter scoring or contamination. Requires platter cleaning and head swap 50% deposit required. Donor parts are consumed in the repair. Most difficult recovery type. |
Hardware Repair vs. Software Locks
Our "no data, no fee" policy applies to hardware recovery. We do not bill for unsuccessful physical repairs. If we replace a hard drive read/write head assembly or repair a liquid-damaged logic board to a bootable state, the hardware repair is complete and standard rates apply. If data remains inaccessible due to user-configured software locks, a forgotten passcode, or a remote wipe command, the physical repair is still billable. We cannot bypass user encryption or activation locks.
All tiers: Free evaluation and firm quote before any paid work. No data, no fee on simple copy, file system, and firmware tiers. Head swap and surface damage require a 50% deposit because donor parts are consumed in the attempt.
Target drive: The destination drive we copy recovered data onto. You can supply your own or we provide one at cost. For ultra-high-capacity drives (20TB and above), the target drive costs approximately $400+ due to the large media required. All prices are plus applicable tax.
Technical Methodology: Multi-Bay Recovery
Sector Translation and Format Differences
Some multi-bay enclosure controllers perform 4K-to-512e sector size translation at the hub level. When the enclosure presents 4K sectors to the host OS, the file system is formatted with 4K alignment. Extracting the drive and connecting it directly to a computer that expects 512-byte sectors can cause the OS to report the disk as RAW or unformatted.
This is not corruption. The file system is intact; the sector addressing is offset. PC-3000 handles sector translation during imaging, mapping the drive's native sector size to the format the file system expects. Do not initialize or reformat the drive.
Hardware RAID vs. Software RAID Enclosures
Hardware RAID enclosures (Promise Pegasus, QNAP TR-004 in RAID mode) store RAID metadata and stripe configuration on the controller itself and on the individual drives. When the controller fails, the RAID metadata on the drives remains intact. PC-3000 RAID edition reads this metadata to reconstruct stripe size, block order, and parity distribution.
Software RAID enclosures (JBOD mode on most docks) present each drive as an independent disk. These are the simplest recoveries: extract each drive, image independently, recover files from each image.
Overvoltage Damage Assessment
When the wrong AC adapter has been used, we inspect the enclosure PCB under magnification for blown TVS diodes and shorted PMICs. If the overvoltage propagated to the drives via the SATA power pins, each drive PCB is inspected individually. Blown 5V TVS diodes on drive PCBs are replaceable via microsoldering. If the overvoltage reached the drive's preamp or motor controller, the recovery escalates to a head swap or surface damage tier.
Multi-Bay Enclosure Failure FAQ
Can I recover data when my multi-bay enclosure controller fails?
Yes. Multi-bay enclosure controller failures are independent of the drives they housed. We extract each drive, connect them directly to PC-3000 via native SATA or SAS, and image them independently. If the enclosure ran a RAID configuration, we reconstruct the array from the individual drive images.
How do I tell if the hub controller failed or if my drives failed?
If all drives in a multi-bay dock became inaccessible simultaneously, the controller is the most likely failure point. Individual drives fail independently. When two or more drives in the same enclosure stop responding at the same time, the hub controller, its power management IC, or the enclosure power supply has failed.
Does removing drives from a multi-bay enclosure destroy the RAID?
No. Most hardware RAID enclosures write RAID metadata to the drives, so removing them preserves the array structure. Some enclosures store additional configuration on the controller flash, but professional recovery tools like PC-3000 can reconstruct the array from on-drive metadata and known RAID parameters.
My enclosure drops drives during large file transfers. Is this a controller issue?
Likely. Hub controller chips that overheat under sustained I/O drop drives from the bus. This looks like file system corruption but is actually a hardware disconnect. Replace the enclosure or connect drives directly via SATA before running any file system repair tools.
I plugged the wrong power adapter into my dock. Can the drives be saved?
It depends on whether the overvoltage reached the drives. The enclosure PMIC and TVS diodes are designed to absorb voltage spikes, but budget enclosures may lack adequate protection. We inspect both the enclosure PCB and each drive PCB individually to determine the extent of damage.
Data Recovery Standards & Verification
Our Austin lab operates on a transparency-first model. We use industry-standard recovery tools, including PC-3000 and DeepSpar, combined with strict environmental controls to make sure your hard drive is handled safely and properly. This approach allows us to serve clients nationwide with consistent technical standards.
Open-drive work is performed in a ULPA-filtered laminar-flow bench, validated to 0.02 µm particle count, verified using TSI P-Trak instrumentation.
Transparent History
Serving clients nationwide via mail-in service since 2008. Our lead engineer holds PC-3000 and HEX Akademia certifications for hard drive firmware repair and mechanical recovery.
Media Coverage
Our repair work has been covered by The Wall Street Journal and Business Insider, with CBC News reporting on our pricing transparency. Louis Rossmann has testified in Right to Repair hearings in multiple states and founded the Repair Preservation Group.
Aligned Incentives
Our "No Data, No Charge" policy means we assume the risk of the recovery attempt, not the client.
Technical Oversight
Louis Rossmann
Louis Rossmann's well trained staff review our lab protocols to ensure technical accuracy and honest service. Since 2008, his focus has been on clear technical communication and accurate diagnostics rather than sales-driven explanations.
We believe in proving standards rather than just stating them. We use TSI P-Trak instrumentation to verify that clean-air benchmarks are met before any drive is opened.
See our clean bench validation data and particle test videoRelated Recovery Services
Multi-bay dock or hub controller failed?
Free evaluation. We diagnose whether the controller or the drives failed, and recover from both.