Custom Query (1561 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (460 - 462 of 1561)

Ticket Resolution Summary Owner Reporter
#185 fixed Include device identity in smartd warning emails Christian Franke Christian Franke
Description

A smartd warning email only mentions the /dev/ice name. It should also include device ID, S/N and WWN.

#293 invalid Incomplete support for fixed format sense data somebody maciej3
Description

File scsiata.cpp contains comments claiming that it supports fixed format response to SCSI request sense command (response code 0x70 and 0x71). Indeed, the implementation of sat_device::ata_pass_through() parses such responses correctly and returns true. However, it does not fill the descriptor buffer (adrp). Function smartcommandhandler() in atacmds.cpp calls sat_device::ata_pass_through() and fails if descriptor values are absent, specifically lba_high and lba_mid. It is not clear to me how this should be fixed:

  1. Use a different logic when fixed format is returned (instead of checking lba_high and lba_mid),
  2. Or, issue SCSI request sense command with the DESC bit set, which would force the descriptor format. As that may cause problems with older devices, perhaps a parameter should be introduced, settable in drivedb.h.

User-visible symptoms of this bug are:

  1. smartd refuses to monitor the affected drive, producing an error such as: "Device: /dev/sdd [SAT], not capable of SMART Health Status check"
  2. smartctl shows SMART info correctly, but with a complaint: "SMART STATUS RETURN: incomplete response, ATA output registers missing"

This problem was noticed with external USB drive: WD MyPassport 2TB (WDBY8L0020BBL), USB: 1058:0748

#1914 worksforme Inconsistency between human-readable and json output for SMART Support Yurii Kondrakov
Description

Querying the info for a physical device using:

$ smartctl --info /dev/bus/0 -d megaraid,7
# OR
$ smartctl --info /dev/bus/0 -d megaraid,7 --json

yields different results - specifically, the JSON output lacks the following object:

  "smart_support": {
    "available": true,
    "enabled": true
  }

even though the human-readable output reports the support is available:

$ smartctl --info /dev/bus/0 -d megaraid,7

smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.0-130-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Samsung based SSDs
Device Model:     SAMSUNG MZ7KM960HAHP-000FU
Serial Number:    S2TLNX0H700401
LU WWN Device Id: 5 002538 c40374a84
Firmware Version: CSLB
User Capacity:    960,197,124,096 bytes [960 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
TRIM Command:     Available, deterministic, zeroed
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 4c
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Fri Dec 20 03:00:18 2024 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Might be due to the following error produced by using --log=error flag:

"local_time": {
    "time_t": 1734663658,
    "asctime": "Fri Dec 20 03:00:58 2024 UTC"
  },
  "ata_smart_error_log": {
    "summary": {
      "revision": 1,
      "count": 0
    }
  }

Additionally, there is an inconsistency the other way around:

$ sudo smartctl /dev/nvme0 --info

smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.11.0-12-generic] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
... [no SMART availability lines]


$ sudo smartctl /dev/nvme0 --info -j
{
  ...
  "smart_support": {
    "available": true,
    "enabled": true
  }
}

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.