I'm using Windows 11 with a Transcend Jet SJ25M3 external hard drive. I want it to appear in File Explorer and work with Transcend Elite, but Windows Disk Management shows the drive as "Unallocated" and "Not Initialized." The options to initialize it, assign a drive letter, or create a New Simple Volume are either missing or grayed out. I've already replaced the USB cable, but the drive still doesn't appear normally anywhere. I tried using DiskPart, and the drive did appear in `list disk`, but `convert gpt` failed with "Data error (cyclic redundancy check)." How can I make Windows recognize and use the drive?
3 Answers
The fact that it appears in `list disk` only means Windows can detect some device information; it doesn’t prove the disk can communicate correctly. Check whether DiskPart reports the correct capacity and whether the disk is marked online. If it shows the wrong size, zero bytes, or errors when selecting or querying it, that strongly suggests a failed drive, USB bridge, or power issue. A drive letter cannot be assigned until the hardware responds normally and a valid partition can be created.
Be careful with `clean`, initialization, and formatting: those operations can destroy existing data. If the drive contains anything important, stop attempting repairs and use a professional recovery service. If it’s empty or you don’t need the data, test another USB port, another computer, and—if this model allows it—a different enclosure or adapter. If the CRC error continues, the sensible solution is replacement or a warranty claim rather than creating a new volume.
A cyclic redundancy check error usually points to a hardware or connection problem, not just a missing partition. Try the drive directly in a rear USB 3.x port rather than through a hub or front-panel connector, and test it on another computer if possible. If it gives the same error elsewhere, the drive or its USB enclosure is probably failing. Disk Management and Transcend Elite won’t be able to fix a device that can’t reliably read or write sectors.
It was encouraging that DiskPart could see it, but the CRC error makes sense. I’ll test it on another computer and avoid trying more destructive commands for now.