Custom Query (1359 matches)

~]$ sudo smartctl -a /dev/sdg
smartctl 7.1 2020-04-05 r5049 [x86_64-linux-4.18.0-425.3.1.el8.x86_64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               SEAGATE
Product:              DKS2E-H4R0SS
Revision:             7FA6
Compliance:           SPC-3
User Capacity:        4,000,787,030,016 bytes [4.00 TB]
Logical block size:   512 bytes
LU is fully provisioned
Rotation Rate:        7200 rpm
Form Factor:          3.5 inches
Logical Unit id:      0x5000c50085880b2f
Serial number:        Z1ZB2BGT0000R627VEN0
Device type:          disk
Transport protocol:   SAS (SPL-3)
Local Time is:        Fri Feb  3 09:09:33 2023 CET
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Enabled

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK
Current Drive Temperature:     0 C
Drive Trip Temperature:        0 C

Elements in grown defect list: 2

Error Counter logging not supported


[GLTSD (Global Logging Target Save Disable) set. Enable Save with '-S on']
Device does not support Self Test logging
[bartosz@nas ~]$ scsi_temperature /dev/sdf
sg_logs -t  /dev/sdf
error opening file: /dev/sdf: Permission denied 
sg_logs failed: Permission denied

~]$ sudo scsi_temperature /dev/sdg
sg_logs -t  /dev/sdg
    SEAGATE   DKS2E-H4R0SS      7FA6
  Current temperature = 43 C
  Reference temperature = 68 C
~]$ 

~]$ lspci |grep -i sas
02:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)

This fault is similar #1346.

Witch version working property with my SAS Disk?

The duration of the long (extended) self-test is reported as 7 minutes. Running the long self-test with smartctl (under linux) indeed takes 7 minutes. Running the extended self test under W7 with Data Lifeguard Diagnostics took about 4 hours and 30 minutes (same disk of course).

I also see that the conveyance test has the same recommended duration as the short self-test, which is unusual. I didn't run these tests on either systems.

Is this a bug in smartctl or in the disk?

Is here anyway to get smartmontools to work on Windows 2012 R2 with nvme drive? This is what I'm seeing on the system.

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Windows\system32>smartctl --scan
/dev/sda -d nvme # /dev/sda, NVMe device
/dev/sdb -d nvme # /dev/sdb, NVMe device
/dev/sdc -d nvme # /dev/sdc, NVMe device
/dev/sdd -d nvme # /dev/sdd, NVMe device
/dev/sde -d nvme # /dev/sde, NVMe device
/dev/sdf -d scsi # /dev/sdf, SCSI device
/dev/csmi6,3 -d ata # /dev/csmi6,3, ATA device

C:\Windows\system32>smartctl -i /dev/sda
smartctl 7.0 2018-12-30 r4883 [x86_64-w64-mingw32-2012r2] (sf-7.0-1)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org

Read NVMe Identify Controller failed: IOCTL_STORAGE_QUERY_PROPERTY(NVMe) failed, Error=1

C:\Windows\system32>