[SOLVED] how to check if my SSD is broken?

testware · 2024-07-23 12:18:50

$lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 1 0B 0 disk

$fdisk
don't print anything about sda, only about other storage

$cfdisk /dev/sda
cfdisk: cannot open /dev/sda: Invalid argument

$smartctl -a /dev/sda
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.9.10-arch1-1] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

Read NVMe Identify Controller failed: scsi error unsupported scsi opcode

$mkfs.ext4 /dev/sda
mke2fs 1.47.1 (20-May-2024)
mkfs.ext4: Device size reported to be zero. Invalid partition specified, or
partition table wasn't reread after running fdisk, due to
a modified partition being busy and in use. You may need to reboot
to re-read your partition table.

Last edited by testware (2024-07-23 15:45:22)

mpan · 2024-07-23 13:08:12

The output seems like it’s an SD card reader and the card isn’t inserted. Are you sure this is SSD? If yes, please provide the output of lsblk and the journal output from boot time.

Also, please put logs or terminal interaction into [code][/code] tags.

Last edited by mpan (2024-07-23 13:09:16)

testware · 2024-07-23 13:28:48

I'm not 100% sure if it's an SSD, but I think so.
It's an external storage device, i connect it via USB-C.

The output of $lsblk is above.

$sudo journalctl -k | grep sda
Jul 23 15:22:55 X-Ware kernel: sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK
Jul 23 15:22:55 X-Ware kernel: sd 0:0:0:0: [sda] Sense Key : Illegal Request [current]
Jul 23 15:22:55 X-Ware kernel: sd 0:0:0:0: [sda] Add. Sense: Invalid field in cdb
Jul 23 15:22:55 X-Ware kernel: sd 0:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 B)
Jul 23 15:22:55 X-Ware kernel: sd 0:0:0:0: [sda] 0-byte physical blocks
Jul 23 15:22:55 X-Ware kernel: sd 0:0:0:0: [sda] Write Protect is off
Jul 23 15:22:55 X-Ware kernel: sd 0:0:0:0: [sda] Mode Sense: 37 00 00 08
Jul 23 15:22:55 X-Ware kernel: sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Jul 23 15:22:55 X-Ware kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk

Last edited by testware (2024-07-23 13:34:46)

cryptearth · 2024-07-23 14:08:33

the path /dev/sdX hints to scsi/sata/sas connection
so if this is an external enclosure via usb it likely has an usb-sata bridge chip an a regular sata ssd in it - if able open it and have a look
could also be an SD card - which often also show up as a /dev/sdX path
does this externsl enclosure has any information on it like manufacturer or a model name/number?

testware · 2024-07-23 14:32:56

I took the chip from a old Laptop that i broke.
And do it in a USB-C case for a NVME or SATA M.2, and used it as a USB-stick with ventoy.

On the Storage are this information:
solid state Driver
kxg60znv512G
FW AGXA4103
Kioxia corporation

Last edited by testware (2024-07-23 14:33:37)

mpan · 2024-07-23 15:12:22

Once again: put logs or terminal interaction into [code][/code] tags.

The log is not complete: it misses everything that happened before this error. From what is given, it seems that either there is a communication issue or the chip in the enclosure is broken. The message seems to not be from the SSD itself.

Start with using a different USB cable, different USB port; If the enclosure has an external power power option, use it. If neither of that helps, try using the SSD directly in some computer (or adapter) that is known to be working.

At this point I see no reason to assume the SSD is broken.

Last edited by mpan (2024-07-23 15:15:21)

seth · 2024-07-23 15:35:30

@testware, stop grepping around.
Run "dmesg -w" and attach the drive. Post the output that generates.

testware · 2024-07-23 15:49:32

After I removed the memory once to get the memory specification and then plugged it back into the USB-C enclosure.
Everything worked again.

Can you tell me how you recognized that it was not the SSD but something else.?

Last edited by testware (2024-07-23 15:51:37)

mpan · 2024-07-23 19:47:28

testware wrote:

Can you tell me how you recognized that it was not the SSD but something else.?

Recognized? No. As for making a reasonably good guess to prioritize tasks:

Primarily knowing, how those adapters work. They present a virtual USB Mass Storage class device, which is only backed by the actual, physical storage medium.⁽¹⁾ So the message was likely to come from the controller, not the SSD.

Coupled with years of experience in debugging issues — the kind of experience, which makes one have good heuristics about the message, despite not being able to point to any particular part of the message or understanding it exactly.

Supported by seeing enough of those cases to expect different kind of behavior, if that was the SSD itself. A partial breakage of controller’s logic is a relatively rare occurance. Usually it will not work at all, be permanently read-only and otherwise operational, fall off the line during operations, or fail during reads or writes.
____
⁽¹⁾ Controllers capable of presenting the SCSI interface (USB Attached SCSI, UAS) are rare, only available since USB 3, and notably more expensive.

Last edited by mpan (2024-07-23 19:47:55)

javi-amarant · Yesterday 23:20:44

ey there!

I’m having similar trouble with a USB drive (/dev/sda) that I cannot mount or access. Here’s what I’ve tried:

I attempted to mount the device using different filesystems (NTFS, EXT4, EXFAT), but each time I get errors such as "Failed to read bootsector" or "Can't read superblock."

Running ntfsfix returns the error "Failed to read bootsector" and "Unrecoverable error."

I also tried running fsck on the drive, but it gives the error "The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem."

It seems the partition table might be damaged, as the system doesn't recognize the device properly (I don’t see any partitions in testdisk or gparted).

I suspect the disk may have filesystem corruption or partition issues, but I'm not sure how to proceed.

Below is the dmesg log:

[225972.708879] usb 3-3: new high-speed USB device number 43 using xhci_hcd
[225972.848698] usb 3-3: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=f0.01
[225972.848719] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[225972.848725] usb 3-3: Product: Ugreen Storage Device
[225972.848729] usb 3-3: Manufacturer: Ugreen
[225972.848733] usb 3-3: SerialNumber: 012345678944
[225972.883758] usb-storage 3-3:1.0: USB Mass Storage device detected
[225972.884841] scsi host0: usb-storage 3-3:1.0
[225973.925300] scsi 0:0:0:0: Direct-Access Realtek RTL9210 1.00 PQ: 0 ANSI: 6
[225973.926262] sd 0:0:0:0: Attached scsi generic sg0 type 0
[225973.934482] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK
[225973.934497] sd 0:0:0:0: [sda] Sense Key : Illegal Request [current]
[225973.934503] sd 0:0:0:0: [sda] Add. Sense: Invalid command operation code
[225973.935155] sd 0:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 B)
[225973.935165] sd 0:0:0:0: [sda] 0-byte physical blocks
[225973.935735] sd 0:0:0:0: [sda] Write Protect is off
[225973.935742] sd 0:0:0:0: [sda] Mode Sense: 37 00 00 08
[225973.936350] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[225973.937231] sd 0:0:0:0: [sda] Attached SCSI disk

Any ideas? thank youu

seth · Today 08:22:05

Did you see #6 & #8 ?
R/n the drive doesn't respond and shows up as 0-size, filesystem or partition operations are pointless at that state, there's no filesystem because there's no partition because there's no storage capacity.

schard · Today 10:57:18

@javi-amarant please do not hijack solved threads.

Closing.

Arch Linux

#1 2024-07-23 12:18:50

[SOLVED] how to check if my SSD is broken?

#2 2024-07-23 13:08:12

Re: [SOLVED] how to check if my SSD is broken?

#3 2024-07-23 13:28:48

Re: [SOLVED] how to check if my SSD is broken?

#4 2024-07-23 14:08:33

Re: [SOLVED] how to check if my SSD is broken?

#5 2024-07-23 14:32:56

Re: [SOLVED] how to check if my SSD is broken?

#6 2024-07-23 15:12:22

Re: [SOLVED] how to check if my SSD is broken?

#7 2024-07-23 15:35:30

Re: [SOLVED] how to check if my SSD is broken?

#8 2024-07-23 15:49:32

Re: [SOLVED] how to check if my SSD is broken?

#9 2024-07-23 19:47:28

Re: [SOLVED] how to check if my SSD is broken?

#10 Yesterday 23:20:44

Re: [SOLVED] how to check if my SSD is broken?

#11 Today 08:22:05

Re: [SOLVED] how to check if my SSD is broken?

#12 Today 10:57:18

Re: [SOLVED] how to check if my SSD is broken?

Board footer