Mac Freezes With a Seagate Expansion 26TB: Separate Dock Identification From Drive Failure
TL;DR:
Power down your Seagate Expansion 26TB immediately and do not initialize or repair it, because the "Sabrent 26TB" label only identifies the replacement dock's bridge rather than erased data, while the repeated Mac freezes and five-minute spin-ups strongly indicate physical hardware failure.
● Click Ignore if macOS prompts to initialize the disk, and immediately stop all home scans, SMART tests, or TestDisk attempts that will consume the remaining readable lifespan of the failing drive.
● Send the drive for a professional assessment if the files are irreplaceable, as software recovery cannot stabilize a mechanical drive that persistently stalls, resets, or disappears from Disk Utility.
● Perform a controlled, read-only image copy using tools like GNU ddrescue to a sufficiently large healthy destination drive only if the disk becomes consistently readable without long stalls.
Ask AI for a summary
ChatGPT
Perplexity
Gemini
Claude
Grok
Do not initialize, erase, or repair this disk. The combination of repeated Mac freezes, very slow spin-up, disappearing storage access, and unreadable files is more concerning than the fact that macOS now labels the USB device “Sabrent 26TB.” Seeing the docking-station name does not prove the original Seagate data was erased.
The owner in this Seagate Expansion 26TB case reported that the external drive locked up a MacBook, stopped appearing in Disk Utility, and could not be browsed by TestDisk. After removing the bare disk from its enclosure and putting it into a Sabrent SATA dock, it sometimes took roughly five minutes to start and macOS asked to initialize it. Attempts to read health information were also unsuccessful.
Does “Sabrent 26TB” Mean the Files Are Gone?
No. A USB-to-SATA bridge can report its own device name while presenting a connected disk to the operating system. A physical capacity or device name shown in Terminal is not proof that the disk is reading data sectors or that its partition contents are intact. Likewise, failure to fetch SMART information through a dock is inconclusive because not every bridge passes those commands through reliably.
The repeated lockups and long initialization delay are separate red flags. They leave open several hardware or interface possibilities; the Reddit symptoms cannot establish a specific failed component.
Choose Between One Identification Check and Professional Recovery
Next Decision
- Files are irreplaceable: Power the disk down and request a professional assessment that explicitly covers high-capacity drives and the observed long-start/lockup symptoms. Describe the original enclosure and the Sabrent bridge changes.
- Disk becomes consistently readable, with no long stalls: A qualified operator may consider controlled, read-only imaging to a healthy destination large enough for the source. GNU ddrescue documentation explains error-aware imaging, but it is not a cure for mechanical instability.
- Disk stalls, resets, or repeatedly disappears: Stop home scans, SMART tests, partition repairs, and further dock experiments; more retries can consume the remaining readable time.
If macOS offers Initialize, choose Ignore while data recovery is unresolved. Seagate’s physical-drive troubleshooting guidance advises consulting recovery professionals before continuing with serious physical symptoms. Software recovery cannot make an unresponsive disk stable.