Custom Query (1559 matches)
Results (91 - 93 of 1559)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1441 | fixed | smartctl exit status 4 if SAT layer ignores CK_COND | ||
| Description |
Hello I use a Salcar EHCI "toaster" device with ID_VENDOR_ID=154b and ID_MODEL_ID=8001 smartctl -d sat -H shows "Passed" with bit2 exit status (attached) on a used but healthy 500GB Samsung sata device. smartctl -d sat -x shows most of the expected attributes but quits with bit2 exit status as well (attached) udevadm test /dev/sda attached as well |
|||
| #1233 | invalid | smartctl exit code 4. "scsiPrintFormatStatus: Failed" in -a output | ||
| Description |
After upgrade smartmontools from 6.6-1.el7 to 7.0-1.el7, smartctl exit with code 4. This line is present in the output: scsiPrintFormatStatus: Failed [Input/output error] smartctl -a /dev/bus/0 -d megaraid,44
smartctl 7.0 2018-12-30 r4883 [x86_64-linux-4.14.35-1818.1.6.el7uek.x86_64] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: HGST
Product: HUH721212AL5204
Revision: C3D0
Compliance: SPC-4
User Capacity: 12,000,138,625,024 bytes [12.0 TB]
Logical block size: 512 bytes
Physical block size: 4096 bytes
LU is fully provisioned
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Logical Unit id: 0x5000cca253084a6c
Serial number: 8DG4KATZ
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Fri Sep 6 11:27:00 2019 VLAT
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
scsiPrintFormatStatus: Failed [Input/output error]
Current Drive Temperature: 25 C
Drive Trip Temperature: 85 C
Manufactured in week 43 of year 2017
Specified cycle count over device lifetime: 50000
Accumulated start-stop cycles: 159
Specified load-unload count over device lifetime: 600000
Accumulated load-unload cycles: 168
Vendor (Seagate Cache) information
Blocks sent to initiator = 109731280584704
Error counter log:
Errors Corrected by Total Correction Gigabytes Total
ECC rereads/ errors algorithm processed uncorrected
fast | delayed rewrites corrected invocations [10^9 bytes] errors
read: 0 0 0 0 120567 14366.075 0
write: 0 0 0 0 14168 5367.122 0
verify: 0 0 0 0 396 612007.092 0
Non-medium error count: 0
No Self-tests have been logged
But with another drive of the same model, everything is fine. This text instead of an error string Grown defects during certification <not available> Total blocks reassigned during format <not available> Total new blocks reassigned <not available> Power on minutes since format <not available> |
|||
| #146 | fixed | smartctl does not work on arbitrary symlinks to devices | ||
| Description |
$ ln -s /dev/sda /tmp/foo $ smartctl /tmp/foo smartctl 5.40 2010-07-12 r3124 [x86_64-unknown-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net /tmp/foo: Unable to detect device type ... $ smartctl /dev/sda # this works fine $ smartctl -a /dev/block/8:0 # FAIL, as above $ smartctl /dev/disk/by-path/pci-0000\:00\:1f.2-scsi-0\:0\:0\:0 # this works fine, too Even if all the links point to /dev/sda, only some of them can be specified as arguments to smartctl - which does not make sence IMHO. I would expect any symbolic link (which may be nested quite deep) that finally resolves to a device should allow successful execution of smartctl. In my use case, I have quite a bunch of disks that are used for experiments and switched between machines regularily. Therefore I set up symlinks like /data/dev/disk1 -> /dev/disk/by-id/ABC-123456 with a fixed mapping of the disk$i names and prefer to access the devices via /data/dev/disk$i (and mount them to /data/disk$i) so I don't have to care which /dev/sdX name it currently has (and I don't accidentally access the wrong one - I don't care about the port where it is connected but about the actual physical disk). Using /dev/disk/by-id/ABC-123456 directly is quite cumbersome because they are quite long, look different from vendor to vendor and are not contiguous. UUIDs or something similar is not useful either because the disks get repartitioned and filesystems get recreated regularily. While sfdisk, mkfs, mount, hdparm, ... work in this setup, smartctl does not. Andreas |
|||
