this post was submitted on 18 May 2025
11 points (86.7% liked)

Linux

10641 readers
128 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 2 years ago
MODERATORS
[email protected]
11
SSD Drive Problem (lemmy.world)
submitted 2 weeks ago by [email protected] to c/[email protected]
14 comments fedilink hide all child comments
 

I have a new WD Blue 1TB ssd hard drive that doesn't want to get formatted or mounted. When I attach the drive via USB I get an error message of:

Unable to Mount 1.0 Tb volume
An operation is already pending

Eventually I get:

Unable to Mount 1.0 Tb volume
timeout was reached

I have a Lenovo Thinkpad T570 running Linux Mint 22.1 Xia base. "GParted" and "Disks" don't see the drive. Is there something I can do to access the disc or is it toast?

all 16 comments
sorted by: hot top controversial new old
[–] [email protected] 0 points 2 weeks ago

@floppingfish Might check places on your desktop.

[–] [email protected] 0 points 2 weeks ago (1 children)

@floppingfish It says operation already pending. In Ubuntu and many other Linux distros, when you plug in a USB device it mounts automatically, take a look at df and see if you don't have a new partition mounted somewhere you didn't expect.

[–] [email protected] 1 points 2 weeks ago

Thanks for the suggestion, unfortunately it didn't show up using df

[–] [email protected] 6 points 2 weeks ago (2 children)

Check the output of dmesg after plugging it in.

[–] [email protected] 1 points 2 weeks ago

I was first getting an error about my Fing agent. I uninstalled the Fing snap and now I am getting:

Unable to Mount 1.0 Tb volume Error mounting /dev/sdb1/ at...: can't read superblock on /dev/sdb1/

Thanks!

[–] [email protected] 6 points 2 weeks ago (1 children)

Better yet, run sudo dmesg --follow beforehand, and watch the output there while plugging it in.

[–] [email protected] 1 points 2 weeks ago (1 children)

So far it is showing

usb 2-4: new SuperSpeed USB device number 11 using xhci_hcd [211819.412449] usb 2-4: New USB device found, idVendor=2537, idProduct=1068, bcdDevice= 1.00 [211819.412468] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [211819.412477] usb 2-4: Product: NS1068 [211819.412484] usb 2-4: Manufacturer: Norelsys [211819.412491] usb 2-4: SerialNumber: 0123456789ABCDE [211819.415262] usb-storage 2-4:1.0: USB Mass Storage device detected [211819.415608] usb-storage 2-4:1.0: Quirks match for vid 2537 pid 1068: 800000 [211819.415722] scsi host1: usb-storage 2-4:1.0 [211821.975537] scsi 1:0:0:0: Direct-Access ATA WD Blue SA510 2. 0100 PQ: 0 ANSI: 6 [211821.976781] sd 1:0:0:0: Attached scsi generic sg1 type 0 [211821.985294] sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB) [211821.985686] sd 1:0:0:0: [sdb] Write Protect is off [211821.985704] sd 1:0:0:0: [sdb] Mode Sense: 43 00 00 00 [211821.986069] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [211822.033052] sdb: sdb1 [211822.034239] sd 1:0:0:0: [sdb] Attached SCSI disk [211851.555550] usb 2-4: reset SuperSpeed USB device number 11 using xhci_hcd [211877.091031] usb 2-4: reset SuperSpeed USB device number 11 using xhci_hcd [211902.626842] usb 2-4: reset SuperSpeed USB device number 11 using xhci_hcd

[–] [email protected] 1 points 2 weeks ago (1 children)

Some more

                          usb 2-4: reset SuperSpeed USB device number 11 using xhci_hcd

[211953.700655] usb 2-4: reset SuperSpeed USB device number 11 using xhci_hcd [211979.236790] usb 2-4: reset SuperSpeed USB device number 11 using xhci_hcd [211979.249917] sd 1:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=152s [211979.249940] sd 1:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 00 00 08 00 00 00 08 00 [211979.249950] blk_print_req_error: 752 callbacks suppressed [211979.249959] I/O error, dev sdb, sector 2048 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 [211979.249982] buffer_io_error: 21278 callbacks suppressed [211979.249988] Buffer I/O error on dev sdb1, logical block 0, lost async page write [212004.768420] usb 2-4: reset SuperSpeed USB device number 11 using xhci_hcd [212030.306531] usb 2-4: reset SuperSpeed USB device number 11 using xhci_hcd

[–] [email protected] 5 points 2 weeks ago (1 children)

I/O errors, nice. What kind of disk is this? Removable USB case? Fixed one? Are you able to test the disk in another case or directly plugged into a mainboard?

[–] [email protected] 1 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

WD Blue SSD drive in a removable case. I'll try it another machine.

Same issue on a different machine :-(

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

As @[email protected] suggested, try plugging it in directly on an internal port, not via USB. Then you figure out whether the USB converter is faulty or the SSD itself is broken.

[–] [email protected] 4 points 2 weeks ago

Attach it directly instead of USB.