Custom Query (1560 matches)

do you know when the toshiba 14TB MG07ACA14TE drive will be included in the smartctl database?

Device Model:     TOSHIBA MG07ACA14TE
Serial Number:    XXX
LU WWN Device Id: XXX
Firmware Version: 0101
User Capacity:    14,000,519,643,136 bytes [14.0 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        Not in smartctl database [for details use: -P showall]

Drivedb.h version is:

  { "$Id: drivedb.h 4900 2019-03-18 21:53:04Z samm2 $",

C:\Users\FME>smartctl -i sdb
smartctl 7.0 2018-12-30 r4883 [x86_64-w64-mingw32-w10-1809] (sf-7.0-1)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org

Warning: Limited functionality due to missing admin rights
=== START OF INFORMATION SECTION ===
Device Model:     ST1000LM035-1RK172
Serial Number:    WDELLTBT
Firmware Version: SDM2
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   [No Information Found]
Local Time is:    Tue Apr 16 16:13:41 2019 HB
SMART support is: Available - device has SMART capability.
                  Enabled status cached by OS, trying SMART RETURN STATUS cmd.
SMART support is: Enabled

I have two systems in which this is the case. The most recent just showed up today. What I did was this:

1. MegaCli64 commands: a) offline the drive (the hot spare begins rebuild) b) prepare for removal
2. Replace the drive
3. MegaCLI64 command to set the replaced drive as the new hot spare

After this, smartctl -H -d megaraid,<drive> /dev/sda fails, "INQUIRY failed". MegaCli64 reports the drive's perfectly fine, and is a hot spare.

Updated CentOS 7.6.1810, smartctl 6.5, from package smartmontools-6.5-1.el7.x86_64, which is the most current.