Custom Query (1415 matches)
Results (97 - 99 of 1415)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1875 | invalid | smartctl -o off does not work for some SSDs | ||
| Description |
The following is the command log. smartctl -o off /dev/sdg ; smartctl -c /dev/sdg | grep 'Auto Offline' ; smartctl -a /dev/sdg | head
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.6.23] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Automatic Offline Testing Disabled.
Auto Offline Data Collection: Enabled.
Auto Offline data collection on/off support.
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.6.23] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Crucial/Micron Client SSDs
Device Model: CT2000MX500SSD1
Serial Number: 2037E4AF6329
LU WWN Device Id: 5 00a075 1e4af6329
Firmware Version: M3CR032
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
I understand that some drives are irregular and refuse to enable/disable some features, but if a drive refuses, it would be at least nice to set exit status to non-0. |
|||
| #1339 | invalid | smartctl -n standby wakes WD USB drive | ||
| Description |
I have several USB drives from different vendors, including WD.
I have found that for a particular drive model, This is a WD Elements Desktop 4TB drive. Device Model: WDC WD40EMAZ-11LW3B0 Full smartctl -x attached. I am happy to run debugs, etc. over the next week or so, after which I may have to return the drive as unfit. |
|||
| #284 | invalid | smartctl -l selftest does not show running selftest status with Toshiba MK2002TSKB | ||
| Description |
smartctl -l selftest does not show running selftest status with Toshiba MK2002TSKB HDD To reproduce: 1) Launch selftest: smartctl -t long /dev/sdX 2) Try to check the status after some time: smartctl -l selftest /dev/sdX result: there is no running selftest logged, selftest will appear in log only after completition. Workaround: Lauch another selftest:
Smartctl will show the status of current running selftest:
Platform: CentOS 6.3, 6.4 smartmontools 6.1 |
|||
