How to check the status of SAS disks on a physical server?

Question

linux

Hello.

There is a physical server, it has 2 SAS disks of 146 GB.
You need to monitor the status of disks yourself.
I decided to use smartctl, but the output of some information is not entirely clear to me.
A health check seems to show that everything is fine:
smartctl -H /dev/sda
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19.0-13-amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

smartctl -H /dev/sdb
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19. 0-13-amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

No...
smartctl -a /dev/sda
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19.0-13-amd64] ( local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor: FUJITSU
Product: MBA3147RC
Revision: 0103
User Capacity: 147,086,327,808 bytes [147 GB]
Logical block size: 512 bytes
Rotation Rate: 15000 rpm
Logical Unit id: 0x500000e01b717ab0
Serial number: BJA0P8502D8M
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Sat Jun 5 09:40:29 2021 EDT
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: 28 C
Drive Trip Temperature: 65 C

Manufactured in week 21 of year 2008
Specified cycle count over device lifetime: 50000
Accumulated start-stop cycles: 32
Elements in grown defect list: 0

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 3064 0 0 0 743273.006 0
write: 0 0 0 0 0 297758.540 0

Non-medium error count: 27

No self-tests have been logged

smartctl -a /dev/sdb
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19.0-13-amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor: FUJITSU
Product: MAX3147RC
Revision: 0104
User Capacity: 147,086,327,808 bytes [147 GB]
Logical block size: 512 bytes
Rotation Rate: 15000 rpm
Logical Unit id: 0x500000e0137d1e10
Serial number: DQ00P6B00K3R
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Sat Jun 5 09:41:34 2021 EDT
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: 26 C
Drive Trip Temperature: 65 C

Manufactured in week 47 of year 2006
Specified cycle count over device lifetime: 10000
Accumulated start-stop cycles: 36
Elements in grown defect list: 0

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 2861 0 0 0 106968.637 0
write: 0 1014 0 0 0 20376.950 0

Non-medium error count: 83

No self-tests have been logged

Please help decipher this output. What should you pay attention to?
For example. What they are responsible for:
Specified cycle count over device lifetime: 50000
Specified cycle count over device lifetime: 10000
Non-medium error count: 27
Non-medium error count: 83

At what output values ​​is it best to replace?
And why is SMART itself not displayed?

Thanks in advance!

Answer 1

SMART is not shown because you didn't ask for it. Replacement, if there is an array with redundancy, is usually carried out when one of the disks falls out of it for serious reasons (there are also false positives, albeit relatively rarely).

Answer 2

smartctl -A /dev/sdX full smart output