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?

  • who@feddit.org
    link
    fedilink
    English
    arrow-up
    6
    ·
    2 days ago

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

    • floppingfish@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 days ago

      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

      • floppingfish@lemmy.worldOP
        link
        fedilink
        English
        arrow-up
        3
        ·
        2 days ago

        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

        • JASN_DE@feddit.org
          link
          fedilink
          English
          arrow-up
          5
          ·
          2 days ago

          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?

          • floppingfish@lemmy.worldOP
            link
            fedilink
            English
            arrow-up
            3
            ·
            edit-2
            2 days ago

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

            Same issue on a different machine :-(

            • Successful_Try543@feddit.org
              link
              fedilink
              English
              arrow-up
              1
              ·
              edit-2
              21 hours ago

              As @catloaf@lemm.ee 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.