Custom Query (1418 matches)
Results (7 - 9 of 1418)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1907 | invalid | NVMe device (KINGSTON SNVS2000GB) detected as (S)ATA on macOS | ||
Description |
Please add NMVe M.2 SSD KINGSTON SNVS2000GB smartctl -a disk4 smartctl 7.4 2023-08-01 r5530 [Darwin 24.1.0 arm64] (local build) Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: KINGSTON SNVS2000GB Serial Number: 50026B7282922E70 Firmware Version: S8442101 Device is: Not in smartctl database 7.3/5528 ATA Version is: [No Information Found] Local Time is: Fri Nov 15 13:06:53 2024 +03 SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported. SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled. A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. |
|||
#1902 | duplicate | smartctl Read Device Identity failed: scsi error unsupported field in scsi command | ||
Description |
hello when i try a smartctl on my seagate expansion 4Tb external drive, i have this error message: ~$ sudo smartctl -x /dev/sdf smartctl 7.2 2020-12-30 r5155 [x86_64-linux-6.1.0-0.deb11.21-amd64] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org Read Device Identity failed: scsi error unsupported field in scsi command A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. even if i try this command i have the same error : ~$ sudo smartctl -s on -o on -d sat -T verypermissive -a /dev/sdf smartctl 7.2 2020-12-30 r5155 [x86_64-linux-6.1.0-0.deb11.21-amd64] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org Read Device Identity failed: scsi error unsupported field in scsi command === START OF INFORMATION SECTION === Device Model: [No Information Found] Serial Number: [No Information Found] Firmware Version: [No Information Found] Device is: Not in smartctl database [for details use: -P showall] ATA Version is: [No Information Found] Local Time is: Wed Nov 6 16:49:11 2024 CET SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported. SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled. Checking to be sure by trying SMART RETURN STATUS command. SMART support is: Unknown - Try option -s with argument 'on' to enable it. === START OF ENABLE/DISABLE COMMANDS SECTION === SMART Enable failed: scsi error unsupported field in scsi command Read SMART Data failed: scsi error unsupported field in scsi command SMART Automatic Timers not supported SMART Enable Automatic Offline failed: scsi error unsupported field in scsi command === START OF READ SMART DATA SECTION === SMART Status command failed: scsi error unsupported field in scsi command SMART overall-health self-assessment test result: UNKNOWN! SMART Status, Attributes and Thresholds cannot be read. Read SMART Error Log failed: scsi error unsupported field in scsi command Read SMART Self-test Log failed: scsi error unsupported field in scsi command Selective Self-tests/Logging not supported the only information i found is : ~$ lsusb Bus 008 Device 002: ID 0bc2:231a Seagate RSS LLC Expansion Portable it seems my disk is maybe not in the smartmontools db but i have no more information. how can i do ? thank you very much |
|||
#1898 | wontfix | JSON output is empty in rare cases (smartctl-nc) | ||
Description |
I received a report from a user that basically indicates the JSON output from smartctl is completely empty. No opening/closing brackets or any other text is output to the command line. Example command: smartctl-nc --device={DeviceType} --info --get=security --json pd{PhysicalDeviceNum} This is on Windows 11. I've reviewed the smartctl code, but can't find any clues. This is also a very isolated case and the first time I have seen it, so it may be some system configuration problem, but am hoping someone could point me in the right direction in diagnosing this. Also, the non-JSON commands output without issue. This is strictly JSON related. |