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?
The problem with your new WD Blue 1TB SSD that won’t format or mount could be related to several devices, from hardware issues to improper disk organization. Here are some steps to help you understand the situation and possibly get your drive back up and running. 1.Checking the basic connection and power 2. Checking the disk visibility in the system Open the terminal and run: lsblk See if the disk is displayed as /dev/sdX (where X is the drive letter). If the disk is not displayed, the problem is either in the hardware or in the USB interface. 3. Plug in the disk and immediately run: dmesg | tail -n 30 This will show the last kernel messages related to the disk plug-in. If there are any errors or timeouts, this is an important diagnostic sign. 4. Using fdisk or parted If the disk is visible in lsblk as /dev/sdX, sudo fdisk -l /dev/sdX and sudo parted /dev/sdX print If the commands do not respond or give errors, this also indicates problems with the disk. 5. If the drive is not visible or constantly “freezes” Perhaps the USB-SATA adapter or the drive case is faulty. Sometimes USB ports on laptops provide little power - try connecting to a port with a higher power supply or through an active USB hub with power. If possible, remove the drive from the case and connect it directly to SATA in another PC. 6. If you have access to Windows, check the disk in programs such as Victoria HDD/SSD, CrystalDiskInfo If the disk does not appear in the system at all, it is most likely a hardware failure. If the disk is visible but not formatted, you can try “wipefs” and creating a new partition table. If nothing helps, and the disk is new, we recommend contacting the WD warranty service.
@Mirokhodets @floppingfish Actually the Linux kernel will not treat an nvme as /dev/sd, it will be /dev/nvme0n1 or some such.
Why?
@Mirokhodets Perhaps because nvme requires different treatment than a rotary drive and so is treated as a different device. I’m not psychic or at least not to the degree necessary to read the developers mind, but if it were I that would be why I would do so.
Attach it directly instead of USB.
Check the output of dmesg after plugging it in.
Better yet, run
sudo dmesg --follow
beforehand, and watch the output there while plugging it in.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
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
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?
WD Blue SSD drive in a removable case. I’ll try it another machine.
Same issue on a different machine :-(
@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.
@floppingfish Might check places on your desktop.