Opened 8 months ago

Last modified 7 months ago

#1461 new enhancement

WD Elements WDBWLG0100HBK-EESN (WDC WD101EMAZ-11G7DA0)

Reported by: bigla Owned by:
Priority: minor Milestone: undecided
Component: drivedb Version:
Keywords: usb hdd Cc:

Description


Attachments (2)

smartctl-WD-WDBWLG0100HBK-EESN.txt (12.0 KB) - added by bigla 8 months ago.
WD Elements 25A3 10TB with Model Name WDBWLG0100HBK-EESN containing WDC WD101EMAZ-11G7DA0
smartctl70-WD-WDBWLG0100HBK-EESN.txt (14.4 KB) - added by bigla 7 months ago.
Results of older smartctl version.

Download all attachments as: .zip

Change History (7)

Changed 8 months ago by bigla

WD Elements 25A3 10TB with Model Name WDBWLG0100HBK-EESN containing WDC WD101EMAZ-11G7DA0

comment:1 Changed 8 months ago by bigla

Things I that were unclear for me after reading the FAQ entry :

  • I wasn't sure what kind of ticket I should create.
  • I am not sure what exactly the correct Model number is, I put the one I found printed on the shipping box.

While the box showed:

P/N:
WDBWLG0100HBK-XB
Model:
WDBWLG0100HBK-EESN

smartctl -a /dev/sdb showed

Vendor:               WD
Product:              Elements 25A3

sudo smartctl -a /dev/sdb -d sat showed

Device Model:     WDC WD101EMAZ-11G7DA0

Let me know how I can improve my contribution.

comment:2 in reply to:  1 Changed 8 months ago by TheDragonFire961

Replying to bigla:

Things I that were unclear for me after reading the FAQ entry :

  • I wasn't sure what kind of ticket I should create.
  • I am not sure what exactly the correct Model number is, I put the one I found printed on the shipping box.

While the box showed:

P/N:
WDBWLG0100HBK-XB
Model:
WDBWLG0100HBK-EESN

smartctl -a /dev/sdb showed

Vendor:               WD
Product:              Elements 25A3

sudo smartctl -a /dev/sdb -d sat showed

Device Model:     WDC WD101EMAZ-11G7DA0

Let me know how I can improve my contribution.

Looks like your initial smartctl -a /dev/sdb command returned the ID for the bridge, rather than the drive itself, which is what we're interested in. The smartctl -a /dev/sdb -d sat would be the device model we want here.

comment:3 Changed 8 months ago by Christian Franke

Summary: WD Elements WDBWLG0100HBK-EESNWD Elements WDBWLG0100HBK-EESN (WDC WD101EMAZ-11G7DA0)

comment:4 Changed 8 months ago by Christian Franke

Component: alldrivedb
Keywords: usb hdd added
Milestone: undecided

What is the USB-Id of the device?

Looks like the USB detection did not work here. Normally -d sat should be not needed for WDC USB drives. If no -d is specified and an unknown USB device is detected, smartctl should fail with Unknown USB bridge ... instead of implicitly using -d scsi.

comment:5 Changed 7 months ago by bigla

I have to admit, I used a different(=newer) version of smartctl for my initial post (smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.11.4-arch1-1])

This time I am using: smartctl 7.0 2018-12-30 r4883 [x86_64-linux-3.10.0-1160.15.2.el7.x86_64] on CentOS7

smartctl -a /dev/sdb now (correctly?) yields the same as smartctl -a /dev/sdb -d sat:

Device Model:     WDC WD101EMAZ-11G7DA0

On the System (CentOS7) I use for this comment the ID found is:

ID 1058:25a3 Western Digital Technologies, Inc. Elements Desktop (WDBWLG)

====
EDIT:

Since this time, on the initially used machine, smartctl -a /dev/sdb yields the same as smartctl -a /dev/sdb -d sat
I also have to assume the results from my initial smartctl -a /dev/sdb were actually results from smartctl -a /dev/sdb1. So it is probably my bad.

The USB ID here is the same as on CentOS7 above.

Last edited 7 months ago by bigla (previous) (diff)

Changed 7 months ago by bigla

Results of older smartctl version.

Note: See TracTickets for help on using tickets.