View Product Page

This article documents the macOS Tahoe 26.x NVMe/SATA non-mounting issue affecting Satechi USB-C enclosures and docks, provides a structured troubleshooting sequence for support agents and customers, explains the PCIe Gen 4 reinitialization bug, and defines the warranty escalation path when hardware replacement is warranted.

Issue Overview, macOS Tahoe 26.x Overview

Symptom

• Primary: Drive is enumerated and visible in Apple Menu → About This Mac → System Information → USB / NVMe, but does not appear in Finder, Disk Utility, or Terminal (diskutil list).
• Secondary: Drive may intermittently appear and immediately disappear from Disk Utility upon connection.
• Edge case: Some users report the volume mounts successfully after 3-5 reconnects, then fails again after sleep/wake cycle.

Root Cause

macOS Tahoe 26.x introduced a kernel-level change to how the IOUSBMassStorageDriver handles USB-attached block devices.

Specifically, the new AppleStorageDrivers.kext in Tahoe 26.0-26.2 includes a stricter device-ready handshake timeout (reduced from 5 s → 800 ms) that fast NVMe controllers pass inconsistently during enumeration. Apple has acknowledged the regression internally. A fix is expected in Tahoe 26.3.

Affected Configurations

• OS: macOS Tahoe 26.0, 26.1, 26.2 (all editions)
• Chips: All Apple Silicon, M1, M1 Pro, M1 Max, M1 Ultra, M2, M2 Pro, M2 Max, M2 Ultra, M3, M3 Pro, M3 Max, M4, M4 Pro, M4 Max
• Drive types: M.2 NVMe (PCIe Gen 3 & Gen 4) and M.2 SATA SSDs connected via USB-C enclosure or Satechi dock
• Not affected: Internal Apple SSD, Thunderbolt-native NVMe, Intel-based Macs

PCIe Gen 4 Reinitialization Issue

PCIe Gen 4 NVMe drives exhibit an additional, distinct failure mode on Tahoe 26.x beyond the general timeout regression.

What Happens

• When a PCIe Gen 4 drive is attached to a USB 3.2 Gen 2×2 bridge chip (e.g., ASMedia ASM2364), the bridge performs a link-speed negotiation that Tahoe 26.x’s USB stack aborts prematurely.
• The drive controller enters a partial power state (“link training loop”) and cannot respond to subsequent SCSI/NVMe commands until power is fully cycled, a simple unplug/replug does not clear it.
• Symptom is identical to Section 01 (visible in System Info, not mounting) but persists even after standard hub reinitialization steps.

How to Identify PCIe Gen 4 Failure Specifically 

1. Open Terminal and run: log stream --predicate 'subsystem == "com.apple.iokit.IOUSBMassStorage"' --level debug
2. Attempt to connect the drive.
3. If you see repeated IOReturn: 0xe00002ed or kIOUSBDeviceTransactionTimedOut within 1 second of connection, this is the PCIe Gen 4 reinitialization bug, not a hardware fault.

Resolution for PCIe Gen 4 Drives

Full power cycle required: Unplug the enclosure from the Mac AND remove the enclosure's USB-C cable from its own power source (if bus-powered, wait 30 seconds for capacitors to discharge). Then reconnect. A simple unplug-replug will not work.

• If the drive still fails to mount after full power cycle: proceed to Section 03 (Troubleshooting Steps).
• PCIe Gen 4 drives on macOS Sequoia 15.x are unaffected. If urgent data access is needed, temporarily booting from a Sequoia external volume is a reliable workaround.

Troubleshooting Steps

Follow steps in order. Document which steps were completed before offering replacement:

Step 1, Confirm Drive Visibility

4. Apple Menu → About This Mac → More Info → System Report → USB (or NVMe). Confirm the drive’s model name appears here.
5. Open Disk Utility → View → Show All Devices. Note whether the drive appears, even if greyed out.
6. In Terminal, run diskutil list. Note full output for escalation notes.

Step 2, Energy Saver Adjustment

7. System Settings → Displays → Advanced → enable "Prevent automatic sleeping on power adapter when display is off".

Step 3, Full Hub Reinitialization

9. Unplug all accessories from the dock/hub.
10. Disconnect the dock/hub from the Mac.
11. For bus-powered enclosures: wait 30 seconds for full capacitor discharge.
12. Restart the Mac (do not use Sleep or Fast User Switching).
13. After full restart, reconnect the hub, then the drive.

Step 4, Apple Silicon Power Cycle (All M-Series)

14. Shut down the Mac via Apple Menu → Shut Down. Wait for all LEDs to go dark.
15. Wait 30 seconds.
16. Mac mini only: disconnect the power cable for 30 seconds, then reconnect.
17. Press the power button. Allow full boot before reconnecting the drive.

Step 5, macOS Recovery Mount Attempt

18. Restart into macOS Recovery: hold Power button on Apple Silicon until Options appears, then click Options → Continue.
19. Open Disk Utility from Recovery and attempt to mount the drive.
20. If the drive mounts in Recovery but not in Tahoe: this confirms a Tahoe OS-level bug.
21. If the drive does not mount in Recovery: the drive or enclosure may have a hardware fault

Warranty Escalation Path

Replacement is needed if ANY of the following are true:

•  Drive does not appear in System Information at all (no enumeration)

•  Drive does not mount in macOS Recovery (rules out Tahoe OS bug)

•  Drive was working on Tahoe, then stopped after a non-OS-update event (drop, overheating, etc.)

•  Enclosure shows physical damage, abnormal heat, or burning smell

Related Articles

• Mac Mini M4 Stand & Hub with SSD Enclosure - Setup & Troubleshooting Guide
• Internal Troubleshooting - Mac Mini M4 Stand & Hub with SSD Enclosure | ST-GNMMES
• Quick Start Guide - Mac Mini M4 Stand & Hub with SSD Enclosure | ST-GNMMES
• Technical Specifications - Mac Mini M4 Stand & Hub with SSD Enclosure | ST-GNMMES
• Device Compatibility - Mac Mini M4 Stand & Hub with SSD Enclosure | ST-GNMMES