You are not logged in.

Pages: 1

#1 2022-06-18 12:21:01

impossibleveins23
Member
From: Israel
Registered: 2022-06-18
Posts: 171

[RESOLVED] No block device after replacing HD Drive enclosure

Hi,

I recently replaced HD on 2 Western Digital external enclosures.
The USB device is recognized but no block device present.
I had to add udev rule so device won't be recognized as mtp-device.

journalctl output:

Jun 18 15:13:36 shiny kernel: usb 2-3: new SuperSpeed USB device number 5 using xhci_hcd
Jun 18 15:13:36 shiny mtp-probe[14297]: checking bus 2, device 5: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-3"
Jun 18 15:13:36 shiny mtp-probe[14297]: bus: 2, device: 5 was not an MTP device
Jun 18 15:13:36 shiny kernel: usb 2-3: New USB device found, idVendor=1058, idProduct=1230, bcdDevice=10.50
Jun 18 15:13:36 shiny kernel: usb 2-3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Jun 18 15:13:36 shiny kernel: usb 2-3: Product: My Book 1230
Jun 18 15:13:36 shiny kernel: usb 2-3: Manufacturer: Western Digital
Jun 18 15:13:36 shiny kernel: usb 2-3: SerialNumber: 575833324443315032584837
Jun 18 15:13:36 shiny kernel: usb-storage 2-3:1.0: USB Mass Storage device detected
Jun 18 15:13:36 shiny kernel: scsi host0: usb-storage 2-3:1.0
Jun 18 15:13:37 shiny mtp-probe[14323]: checking bus 2, device 5: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-3"
Jun 18 15:13:37 shiny mtp-probe[14323]: bus: 2, device: 5 was not an MTP device
Jun 18 15:13:37 shiny kernel: scsi 0:0:0:0: Direct-Access     WD       My Book 1230     1050 PQ: 0 ANSI: 6
Jun 18 15:13:37 shiny kernel: scsi 0:0:0:1: Enclosure         WD       SES Device       1050 PQ: 0 ANSI: 6
Jun 18 15:13:37 shiny kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Jun 18 15:13:37 shiny kernel: ses 0:0:0:1: Attached Enclosure device
Jun 18 15:13:37 shiny kernel: ses 0:0:0:1: Attached scsi generic sg1 type 13
Jun 18 15:13:37 shiny kernel: sd 0:0:0:0: [sda] Spinning up disk...
Jun 18 15:13:37 shiny kernel: ses 0:0:0:1: Failed to get diagnostic page 0x1
Jun 18 15:13:37 shiny kernel: ses 0:0:0:1: Failed to bind enclosure -19

udevadm monitor --udev output when connecting the drive:

UDEV  [4665.368427] add      /devices/virtual/workqueue/scsi_tmf_0 (workqueue)
UDEV  [4665.896723] add      /devices/pci0000:00/0000:00:14.0/usb2/2-3 (usb)
UDEV  [4665.897741] add      /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0 (usb)
UDEV  [4665.898307] add      /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/host0 (scsi)
UDEV  [4665.898775] add      /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/host0/scsi_host/host0 (scsi_host)
UDEV  [4665.899261] bind     /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0 (usb)
UDEV  [4665.901598] bind     /devices/pci0000:00/0000:00:14.0/usb2/2-3 (usb)
UDEV  [4666.398321] add      /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/host0/target0:0:0 (scsi)
UDEV  [4666.399131] add      /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/host0/target0:0:0/0:0:0:1 (scsi)
UDEV  [4666.399688] add      /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/host0/target0:0:0/0:0:0:0 (scsi)
UDEV  [4666.399827] bind     /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/host0/target0:0:0/0:0:0:1 (scsi)
UDEV  [4666.400559] add      /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/host0/target0:0:0/0:0:0:0/scsi_device/0:0:0:0 (scsi_device)
UDEV  [4666.401284] add      /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/host0/target0:0:0/0:0:0:0/scsi_disk/0:0:0:0 (scsi_disk)
UDEV  [4666.401500] add      /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/host0/target0:0:0/0:0:0:1/scsi_device/0:0:0:1 (scsi_device)
UDEV  [4666.401897] add      /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/host0/target0:0:0/0:0:0:0/scsi_generic/sg0 (scsi_generic)
UDEV  [4666.402100] add      /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/host0/target0:0:0/0:0:0:0/bsg/0:0:0:0 (bsg)
UDEV  [4666.402240] add      /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/host0/target0:0:0/0:0:0:1/scsi_generic/sg1 (scsi_generic)
UDEV  [4666.402451] add      /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/host0/target0:0:0/0:0:0:1/bsg/0:0:0:1 (bsg)

udev rule content:

SUBSYSTEMS=="usb", ENV{MODALIAS}=="1058:1230", ENV{MODALIAS}="usb-storage"

lsblk output:

                                                                                                                                                      [0]
NAME        MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
sda           8:0    0     2T  0 disk
nvme0n1     259:0    0 238.5G  0 disk
├─nvme0n1p1 259:1    0   1.9G  0 part  /boot
│                                      /efi
├─nvme0n1p2 259:2    0    96G  0 part
│ └─root    254:0    0    96G  0 crypt /home
│                                      /.snapshots
│                                      /btrfs
│                                      /
├─nvme0n1p3 259:3    0  16.6G  0 part  [SWAP]
└─nvme0n1p4 259:4    0  93.8G  0 part

lsub output:

Bus 002 Device 005: ID 1058:1230 Western Digital Technologies, Inc. My Book (WDBFJK)

usb-devices output:

T:  Bus=02 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#=  5 Spd=5000 MxCh= 0
D:  Ver= 3.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 9 #Cfgs=  1
P:  Vendor=1058 ProdID=1230 Rev=10.50
S:  Manufacturer=Western Digital
S:  Product=My Book 1230
S:  SerialNumber=575833324443315032584837
C:  #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=8mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E:  Ad=02(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=81(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms

Any help would be apprecitated smile

Last edited by impossibleveins23 (2022-07-02 07:45:28)

* Good formatted problem description will cause good and quick solution smile
* Please don't forget to mark as [SOLVED].

Offline

#2 2022-06-18 12:50:20

frostschutz
Member
Registered: 2013-11-15
Posts: 1,647

Re: [RESOLVED] No block device after replacing HD Drive enclosure

WD MyBook enclosures don't accept other drives without hardware modification (Winbond chip, disconnect Pin 7+8)

Offline

#3 2022-06-25 09:23:00

impossibleveins23
Member
From: Israel
Registered: 2022-06-18
Posts: 171

Re: [RESOLVED] No block device after replacing HD Drive enclosure

Thanks for your answer.
I saw this youtube and thought it would allow me to replace with another WD drive (WE Red).

I'll try this have / get me another encolsure.

* Good formatted problem description will cause good and quick solution smile
* Please don't forget to mark as [SOLVED].

Offline

#4 2022-07-02 07:44:31

impossibleveins23
Member
From: Israel
Registered: 2022-06-18
Posts: 171

Re: [RESOLVED] No block device after replacing HD Drive enclosure

To update, following removing the chip "leg", made the eclosure recognize the HD. Marking resolved.

Last edited by impossibleveins23 (2022-07-02 07:44:50)

* Good formatted problem description will cause good and quick solution smile
* Please don't forget to mark as [SOLVED].

Offline

Pages: 1

Board footer

Powered by FluxBB