12
submitted 1 week ago by [email protected] to c/[email protected]

I plug in an external 1TB Crucial X8 portable SSD via USB but the OS can't detect it. I used to use the SSD as external storage for a PS4. I can plug it into my phone and a Chromebook and both detect the drive automatically. I've tried reformatting the drive via my phone and the Chromebook, I have connected it via 3 different USB ports, and tried another USB cable, all with no success.

What else can I try?

top 8 comments
sorted by: hot top new old
[-] [email protected] 9 points 1 week ago* (last edited 1 week ago)

Does it detect the drive itself via an fdisk -l?

What does dmesg say?

[-] [email protected] 2 points 1 week ago

fdisk -l does not detect the drive.

dmesg | less says:

[ 397.817177] usb 1-2.2: new high-speed USB device number 8 using xhci_hcd [ 398.008829] usb 1-2.2: New USB device found, idVendor=0634, idProduct=5600, bcdDevice= 1.00 [ 398.008836] usb 1-2.2: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 398.008839] usb 1-2.2: Product: Crucial X8 SSD [ 398.008842] usb 1-2.2: Manufacturer: Micron Technology Inc [ 398.008844] usb 1-2.2: SerialNumber: 1950E328848A [ 398.050672] scsi host7: uas [ 398.941402] scsi 7:0:0:0: Direct-Access Micron Crucial X8 SSD 0 PQ: 0 ANSI: 6 [ 398.944414] sd 7:0:0:0: Attached scsi generic sg4 type 0 [ 400.317609] sd 7:0:0:0: [sde] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB) [ 400.317757] sd 7:0:0:0: [sde] Write Protect is off [ 400.317760] sd 7:0:0:0: [sde] Mode Sense: 43 00 00 00 [ 400.318003] sd 7:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 400.318081] sd 7:0:0:0: [sde] Preferred minimum I/O size 512 bytes [ 400.318086] sd 7:0:0:0: [sde] Optimal transfer size 33553920 bytes [ 400.325350] sde: sde1 [ 400.325432] sd 7:0:0:0: [sde] Attached SCSI disk [ 444.986115] usb 1-2.2: USB disconnect, device number 8 [ 445.013859] sd 7:0:0:0: [sde] Synchronizing SCSI cache [ 445.175859] sd 7:0:0:0: [sde] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 450.120178] [UFW BLOCK] IN=enp4s0 OUT= MAC=01:00:5e:00:00:01:48:5d:36:2c:51:00:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=47108 DF PROTO=2 [ 575.140669] [UFW BLOCK] IN=enp4s0 OUT= MAC=01:00:5e:00:00:01:48:5d:36:2c:51:00:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=43202 DF PROTO=2

[-] [email protected] 4 points 1 week ago

Is this an older build of PopOS that perhaps doesn't have exfat compatibility in its kernel?

[-] [email protected] 2 points 1 week ago
[-] [email protected] 4 points 1 week ago* (last edited 1 week ago)

are exfat-fuse or exfatprogs packages installed?

Can the popOS install format the USB? is it listed in lsusb?

[-] [email protected] 1 points 1 week ago

popOS cannot format the drive, at least, it cannot see it in Disks. lsusb shows the drive

Bus 001 Device 021: ID 0634:5600 Micron Technology, Inc. Crucial X8 SSD

[-] [email protected] 1 points 1 week ago* (last edited 1 week ago)

Does lsblk list a block dev for it?

[-] [email protected] 1 points 1 week ago

Run dmesg -w or dmesg --follow, press control-L to clear the screen (all of that stuff is irrelevant), then plug in and unplug the drive a few times. If you get messages, then the kernel can recognize the drive. Press control-C when you're done.

this post was submitted on 02 Jun 2025
12 points (92.9% liked)

Linux Questions

1974 readers
23 users here now

Linux questions Rules (in addition of the Lemmy.zip rules)

Tips for giving and receiving help

Any rule violations will result in disciplinary actions

founded 2 years ago
MODERATORS