Custom Query (1291 matches)


Show under each result:

Results (76 - 78 of 1291)

Ticket Resolution Summary Owner Reporter
#877 invalid Workaround for supporting SATADOM DamianW

Hello Community,

I have tested smartctl command line interface with Innodisk SATADOM-ML 3ME (30 GB capacity) and I saw that there is a hang.

Problem is in file ataprint.cpp, in section: Read SMART Log directory

As a workaround I would propose to add additional input argument -d satadom, if this argument is passed, drive is treated like normal sat drive but it will not enter the "Read SMART Log directory" section

#1251 fixed TOSHIBA N300 4TB (HDWQ140) not in the smartctl/smartd database Christian Franke Damien


My hard drive TOSHIBA N300 4TB (HDWQ140) is not in smartctl database. In attachment the smartmontools report.

Device Model:     TOSHIBA HDWQ140
Serial Number:    XXX
LU WWN Device Id: XXX
Firmware Version: FJ1M
User Capacity:    4,000,787,030,016 bytes [4.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        Not in smartctl database [for details use: -P showall]

My Drivedb.h version is:

{ "$Id: drivedb.h 4955 2019-09-28 17:43:32Z chrfranke $",

Can you add my hard drive to smartctl database, please ?

Thank you very much.

Best regards.

#1502 fixed LaCie d2 PROFESSIONAL 0x059f:0x10b8 works with -d sat Christian Franke Mark Petersen

I just bought an LaCie? d2 PROFESSIONAL.

And to my disappointment smartctl reported

/dev/sda: Unknown USB bridge [0x059f:0x10b8 (0x001)]

After looking at the supported devices list I took the chance and used

smartctl -d sat -a

And all works now i get full access to every S.M.A.R.T function and Self Test works.

Note: See TracQuery for help on using queries.