WD USB HDD Elements 2621 - no medium

Associate
Joined
18 Aug 2020
Posts
26
Location
London
Good day.


I have a problem with WD Elements 2621
Is not mounted.
Information only no medium.
I dont know what happed.
That device have under 3 years.
Please information how fix that.


Thanks.

attachment.php
 
Dear Piotr Bujakowski,

Thank you for contacting Western Digital Customer Service and Support. My name is Rick J.



I understand you are facing issues with the WD Elements drive while using on Linux.



Based on your concern, please allow me to inform you that Western Digital have tested the drives on Mac and Windows operating system. We have not tested the drives on Linux operating systems. I would suggest you to please connect the drive to a Windows and Mac computer and try to access the drive.



If you have any further questions, please reply to this email and we will be happy to assist you further.

Sincerely,
Rick J
Western Digital Customer Service and Support
 
[ 2209.851431] usb 4-5.2: new SuperSpeed USB device number 3 using xhci_hcd
[ 2209.876449] usb 4-5.2: New USB device found, idVendor=1058, idProduct=2621, bcdDevice=10.26
[ 2209.876458] usb 4-5.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2209.876461] usb 4-5.2: Product: Elements 2621
[ 2209.876464] usb 4-5.2: Manufacturer: Western Digital
[ 2209.876466] usb 4-5.2: SerialNumber: 57583832454130415945334D
[ 2209.930826] usb-storage 4-5.2:1.0: USB Mass Storage device detected
[ 2209.931148] scsi host6: usb-storage 4-5.2:1.0
[ 2209.931254] usbcore: registered new interface driver usb-storage
[ 2209.933684] usbcore: registered new interface driver uas
[ 2210.943908] scsi 6:0:0:0: Direct-Access WD Elements 2621 1026 PQ: 0 ANSI: 6
[ 2210.944455] sd 6:0:0:0: Attached scsi generic sg2 type 0
[ 2210.945639] sd 6:0:0:0: [sdb] Spinning up disk...
[ 2211.971377] .
 
I took the path "/dev/sdd" from the screenshot you posted. If you have removed and inserted drives, the path will have changed. Either look again in the file manager for the correct path or consult the output of the first command I suggest (dmesg).

When you run the dmesg command immediately after plugging in the drive you are having problems with, you should get some lines like the following:

[43410.031146] scsi 0:0:0:0: Direct-Access USB SanDisk 3.2Gen1 1.00 PQ: 0 ANSI: 6 [43410.031924] sd 0:0:0:0: [sda] 488374272 512-byte logical blocks: (250 GB/233 GiB) [43410.032587] sd 0:0:0:0: [sda] Write Protect is off [43410.032603] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00 [43410.033324] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [43410.035713] sd 0:0:0:0: Attached scsi generic sg0 type 0 [43410.056781] sda: sda1 [43410.098732] sd 0:0:0:0: [sda] Attached SCSI removable disk

In my case, the drive was allocated the device "sda". Depending on what other drives you have connected, yours might be "sdc" or "sdd". You need to substitute the device you get from the dmesg command into the hdparm command.

The output from the dmesg command I suggested may also provide further information about what may be the problem with your drive.
 
[ 2209.851431] usb 4-5.2: new SuperSpeed USB device number 3 using xhci_hcd
[ 2209.876449] usb 4-5.2: New USB device found, idVendor=1058, idProduct=2621, bcdDevice=10.26
[ 2209.876458] usb 4-5.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2209.876461] usb 4-5.2: Product: Elements 2621
[ 2209.876464] usb 4-5.2: Manufacturer: Western Digital
[ 2209.876466] usb 4-5.2: SerialNumber: 57583832454130415945334D
[ 2209.930826] usb-storage 4-5.2:1.0: USB Mass Storage device detected
[ 2209.931148] scsi host6: usb-storage 4-5.2:1.0
[ 2209.931254] usbcore: registered new interface driver usb-storage
[ 2209.933684] usbcore: registered new interface driver uas
[ 2210.943908] scsi 6:0:0:0: Direct-Access WD Elements 2621 1026 PQ: 0 ANSI: 6
[ 2210.944455] sd 6:0:0:0: Attached scsi generic sg2 type 0
[ 2210.945639] sd 6:0:0:0: [sdb] Spinning up disk...
[ 2211.971377] .
When you got this output, you needed to enter

sudo hdparm -I /dev/sdb

If, when you next try it, you get different output from dmesg, you should use that device name instead. Did you cut off the end of the output from dmesg - there will usually be something after the "Spinning up disk" message?
 
Can you confirm you posted the entirety of the output from the dmesg command?

If you did, then it appears the drive has probably failed - as previously stated, there should be more messages after "Spinning up disk".
 
[ 2880.571386] sd 6:0:0:0: [sdb] tag#0 timing out command, waited 30s
[ 2880.641272] usb 4-5.2: USB disconnect, device number 3
[ 2889.395092] usb 4-5.1: new SuperSpeed USB device number 4 using xhci_hcd
[ 2889.420041] usb 4-5.1: New USB device found, idVendor=1058, idProduct=2621, bcdDevice=10.26
[ 2889.420049] usb 4-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2889.420053] usb 4-5.1: Product: Elements 2621
[ 2889.420055] usb 4-5.1: Manufacturer: Western Digital
[ 2889.420057] usb 4-5.1: SerialNumber: 57583832454130415945334D
[ 2889.423667] usb-storage 4-5.1:1.0: USB Mass Storage device detected
[ 2889.423939] scsi host6: usb-storage 4-5.1:1.0
[ 2890.447344] scsi 6:0:0:0: Direct-Access WD Elements 2621 1026 PQ: 0 ANSI: 6
[ 2890.447630] sd 6:0:0:0: Attached scsi generic sg2 type 0
[ 2890.448715] sd 6:0:0:0: [sdb] Spinning up disk...
[ 2891.471000] ...not responding...
 
Back
Top Bottom