No smartd configured by default?
minimos
4 Posts
February 23, 2024, 10:24 amQuote from minimos on February 23, 2024, 10:24 amHello,
I might have overlooked the installation guide, but it seems that my Petasan cluster doesn't run periodically SMART tests.
I was chasing a ceph error, and through manual run of smartctl I found out that a couple of disks have errors (one per node) and need to be replaced.
But in Petasan dashboard all is green (except for the ceph health warning).
Should I set by myself smartd running on each node, and if so is there a recommended configuration to use?
Thanks
P.S.: I have already set zero weight to the OSDs using the faulty disks, and after 12 hours their usage is down to 1%.
Meanwhile I'm waiting for the delivery of the replacement disks, so I can replace them soon.
Hello,
I might have overlooked the installation guide, but it seems that my Petasan cluster doesn't run periodically SMART tests.
I was chasing a ceph error, and through manual run of smartctl I found out that a couple of disks have errors (one per node) and need to be replaced.
But in Petasan dashboard all is green (except for the ceph health warning).
Should I set by myself smartd running on each node, and if so is there a recommended configuration to use?
Thanks
P.S.: I have already set zero weight to the OSDs using the faulty disks, and after 12 hours their usage is down to 1%.
Meanwhile I'm waiting for the delivery of the replacement disks, so I can replace them soon.
Last edited on February 23, 2024, 10:28 am by minimos · #1
admin
2,930 Posts
February 23, 2024, 12:19 pmQuote from admin on February 23, 2024, 12:19 pm
- Can you please show the smarctl test command you run and output showing error.
- If you do to the Physical Disk List ui page, and click on the disk to show info, does it show smartctl error
- We have a notification service that sends email notification in case of newly detected smart errors. You should configure the users/admin emails to receive this notification. We do not show it on dashboard.
- Can you please show the smarctl test command you run and output showing error.
- If you do to the Physical Disk List ui page, and click on the disk to show info, does it show smartctl error
- We have a notification service that sends email notification in case of newly detected smart errors. You should configure the users/admin emails to receive this notification. We do not show it on dashboard.
minimos
4 Posts
February 27, 2024, 9:14 amQuote from minimos on February 27, 2024, 9:14 amHello,
when I logged on one of the petasan nodes and saw in dmesg there were some errors I ran a "smartctl -t short /dev/sdf" command, and below is the output.
Unfortunately, I see that smartctl test is considered 'passed' even if the disk begins to show some errors. I guess that's why Petasan doesn't report any issue in the physical disk list.
One question though, how often does Petasan trigger a smartctl test (if it does) ?
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-4.12.14-28-petasan] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: HGST Ultrastar He6
Device Model: HGST HUS726060ALA640
Serial Number: <redacted>
LU WWN Device Id: 5 000cca 232e4acae
Firmware Version: AHGNT1EN
User Capacity: 6,001,175,126,016 bytes [6.00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Wed Feb 21 16:52:29 2024 EET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 121) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 57) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: (1100) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0
2 Throughput_Performance 0x0005 094 094 054 Pre-fail Offline - 491
3 Spin_Up_Time 0x0007 205 205 024 Pre-fail Always - 507 (Average 465)
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 53
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 71
7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 130 130 020 Pre-fail Offline - 12
9 Power_On_Hours 0x0012 097 097 000 Old_age Always - 24280
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 53
22 Helium_Level 0x0023 100 100 025 Pre-fail Always - 100
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 1103
193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 1103
194 Temperature_Celsius 0x0002 181 181 000 Old_age Always - 33 (Min/Max 20/44)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 5
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 5
199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 54 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 54 occurred at disk power-on lifetime: 24255 hours (1010 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 e6 9a 78 00 40 Error: UNC at LBA = 0x0000789a = 30874
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 00 80 77 00 40 00 27d+02:09:27.068 READ FPDMA QUEUED
2f 00 01 10 00 00 00 00 27d+02:09:24.751 READ LOG EXT
2f 00 01 10 00 00 00 00 27d+02:09:24.751 READ LOG EXT
60 00 08 80 77 00 40 00 27d+02:09:22.485 READ FPDMA QUEUED
60 00 00 80 75 00 40 00 27d+02:09:22.485 READ FPDMA QUEUED
Error 53 occurred at disk power-on lifetime: 24255 hours (1010 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 e6 9a 78 00 40 Error: UNC at LBA = 0x0000789a = 30874
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 80 77 00 40 00 27d+02:09:24.751 READ FPDMA QUEUED
60 00 00 80 75 00 40 00 27d+02:09:22.485 READ FPDMA QUEUED
60 00 18 80 8e 07 40 00 27d+02:09:22.470 READ FPDMA QUEUED
60 00 10 80 73 00 40 00 27d+02:09:22.470 READ FPDMA QUEUED
60 80 08 80 72 00 40 00 27d+02:09:22.470 READ FPDMA QUEUED
Error 52 occurred at disk power-on lifetime: 24252 hours (1010 days + 12 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 49 b7 d2 01 40 Error: UNC at LBA = 0x0001d2b7 = 119479
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 00 00 d2 01 40 00 26d+22:26:42.152 READ FPDMA QUEUED
60 80 10 80 d8 01 40 00 26d+22:26:39.876 READ FPDMA QUEUED
60 00 08 00 d5 01 40 00 26d+22:26:39.876 READ FPDMA QUEUED
ea 00 00 00 00 00 00 00 26d+22:26:39.788 FLUSH CACHE EXT
60 08 00 68 ee 1d 40 00 26d+22:26:39.773 READ FPDMA QUEUED
Error 51 occurred at disk power-on lifetime: 24252 hours (1010 days + 12 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 49 b7 d2 01 40 Error: UNC at LBA = 0x0001d2b7 = 119479
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 00 00 d2 01 40 00 26d+22:26:39.744 READ FPDMA QUEUED
60 80 18 00 c1 0f 40 00 26d+22:26:37.469 READ FPDMA QUEUED
60 80 10 80 d8 01 40 00 26d+22:26:37.469 READ FPDMA QUEUED
60 00 08 00 d5 01 40 00 26d+22:26:37.469 READ FPDMA QUEUED
60 00 30 80 05 16 40 00 26d+22:26:37.444 READ FPDMA QUEUED
Error 50 occurred at disk power-on lifetime: 24244 hours (1010 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 e6 9a 78 00 40 Error: UNC at LBA = 0x0000789a = 30874
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 00 80 77 00 40 00 26d+15:19:27.393 READ FPDMA QUEUED
2f 00 01 10 00 00 00 00 26d+15:19:25.076 READ LOG EXT
2f 00 01 10 00 00 00 00 26d+15:19:25.076 READ LOG EXT
60 00 08 80 77 00 40 00 26d+15:19:22.811 READ FPDMA QUEUED
60 00 00 80 75 00 40 00 26d+15:19:22.811 READ FPDMA QUEUED
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed: read failure 90% 24255 119479
# 2 Short offline Completed without error 00% 14732 -
# 3 Extended offline Completed without error 00% 2206 -
# 4 Short offline Completed without error 00% 2045 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Hello,
when I logged on one of the petasan nodes and saw in dmesg there were some errors I ran a "smartctl -t short /dev/sdf" command, and below is the output.
Unfortunately, I see that smartctl test is considered 'passed' even if the disk begins to show some errors. I guess that's why Petasan doesn't report any issue in the physical disk list.
One question though, how often does Petasan trigger a smartctl test (if it does) ?
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-4.12.14-28-petasan] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, http://www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: HGST Ultrastar He6
Device Model: HGST HUS726060ALA640
Serial Number: <redacted>
LU WWN Device Id: 5 000cca 232e4acae
Firmware Version: AHGNT1EN
User Capacity: 6,001,175,126,016 bytes [6.00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Wed Feb 21 16:52:29 2024 EET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 121) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 57) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: (1100) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0
2 Throughput_Performance 0x0005 094 094 054 Pre-fail Offline - 491
3 Spin_Up_Time 0x0007 205 205 024 Pre-fail Always - 507 (Average 465)
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 53
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 71
7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 130 130 020 Pre-fail Offline - 12
9 Power_On_Hours 0x0012 097 097 000 Old_age Always - 24280
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 53
22 Helium_Level 0x0023 100 100 025 Pre-fail Always - 100
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 1103
193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 1103
194 Temperature_Celsius 0x0002 181 181 000 Old_age Always - 33 (Min/Max 20/44)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 5
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 5
199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 54 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 54 occurred at disk power-on lifetime: 24255 hours (1010 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 e6 9a 78 00 40 Error: UNC at LBA = 0x0000789a = 30874
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 00 80 77 00 40 00 27d+02:09:27.068 READ FPDMA QUEUED
2f 00 01 10 00 00 00 00 27d+02:09:24.751 READ LOG EXT
2f 00 01 10 00 00 00 00 27d+02:09:24.751 READ LOG EXT
60 00 08 80 77 00 40 00 27d+02:09:22.485 READ FPDMA QUEUED
60 00 00 80 75 00 40 00 27d+02:09:22.485 READ FPDMA QUEUED
Error 53 occurred at disk power-on lifetime: 24255 hours (1010 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 e6 9a 78 00 40 Error: UNC at LBA = 0x0000789a = 30874
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 80 77 00 40 00 27d+02:09:24.751 READ FPDMA QUEUED
60 00 00 80 75 00 40 00 27d+02:09:22.485 READ FPDMA QUEUED
60 00 18 80 8e 07 40 00 27d+02:09:22.470 READ FPDMA QUEUED
60 00 10 80 73 00 40 00 27d+02:09:22.470 READ FPDMA QUEUED
60 80 08 80 72 00 40 00 27d+02:09:22.470 READ FPDMA QUEUED
Error 52 occurred at disk power-on lifetime: 24252 hours (1010 days + 12 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 49 b7 d2 01 40 Error: UNC at LBA = 0x0001d2b7 = 119479
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 00 00 d2 01 40 00 26d+22:26:42.152 READ FPDMA QUEUED
60 80 10 80 d8 01 40 00 26d+22:26:39.876 READ FPDMA QUEUED
60 00 08 00 d5 01 40 00 26d+22:26:39.876 READ FPDMA QUEUED
ea 00 00 00 00 00 00 00 26d+22:26:39.788 FLUSH CACHE EXT
60 08 00 68 ee 1d 40 00 26d+22:26:39.773 READ FPDMA QUEUED
Error 51 occurred at disk power-on lifetime: 24252 hours (1010 days + 12 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 49 b7 d2 01 40 Error: UNC at LBA = 0x0001d2b7 = 119479
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 00 00 d2 01 40 00 26d+22:26:39.744 READ FPDMA QUEUED
60 80 18 00 c1 0f 40 00 26d+22:26:37.469 READ FPDMA QUEUED
60 80 10 80 d8 01 40 00 26d+22:26:37.469 READ FPDMA QUEUED
60 00 08 00 d5 01 40 00 26d+22:26:37.469 READ FPDMA QUEUED
60 00 30 80 05 16 40 00 26d+22:26:37.444 READ FPDMA QUEUED
Error 50 occurred at disk power-on lifetime: 24244 hours (1010 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 e6 9a 78 00 40 Error: UNC at LBA = 0x0000789a = 30874
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 00 80 77 00 40 00 26d+15:19:27.393 READ FPDMA QUEUED
2f 00 01 10 00 00 00 00 26d+15:19:25.076 READ LOG EXT
2f 00 01 10 00 00 00 00 26d+15:19:25.076 READ LOG EXT
60 00 08 80 77 00 40 00 26d+15:19:22.811 READ FPDMA QUEUED
60 00 00 80 75 00 40 00 26d+15:19:22.811 READ FPDMA QUEUED
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed: read failure 90% 24255 119479
# 2 Short offline Completed without error 00% 14732 -
# 3 Extended offline Completed without error 00% 2206 -
# 4 Short offline Completed without error 00% 2045 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Last edited on February 27, 2024, 9:14 am by minimos · #3
admin
2,930 Posts
February 27, 2024, 12:11 pmQuote from admin on February 27, 2024, 12:11 pmYes the problem is that the drive reports itself as passed. Sometimes different vendors, device models sometimes report things differently.
We check drive health if you open/get info on the drive in UI under Physical Disk List. We also check every 10 min in a notification service which sends email notification if you enable it for users.
Yes the problem is that the drive reports itself as passed. Sometimes different vendors, device models sometimes report things differently.
We check drive health if you open/get info on the drive in UI under Physical Disk List. We also check every 10 min in a notification service which sends email notification if you enable it for users.
Last edited on February 27, 2024, 12:28 pm by admin · #4
minimos
4 Posts
February 28, 2024, 10:30 amQuote from minimos on February 28, 2024, 10:30 amOk thanks. Sorry, I didn't quite get, does the notification service check every 10 minuts only if some disk has reported error (sending a mail), or does also trigger a complete SMART test (which I suppose it would be a short one)?
I'm still not clear if I should configure the smartd service to independently launch SMART tests or not (short test frequently, long tests perhaps monthly).
If Petasan already does it, I'd avoid my own cronjob as it could launch concurrent tests.
Ok thanks. Sorry, I didn't quite get, does the notification service check every 10 minuts only if some disk has reported error (sending a mail), or does also trigger a complete SMART test (which I suppose it would be a short one)?
I'm still not clear if I should configure the smartd service to independently launch SMART tests or not (short test frequently, long tests perhaps monthly).
If Petasan already does it, I'd avoid my own cronjob as it could launch concurrent tests.
admin
2,930 Posts
February 28, 2024, 1:17 pmQuote from admin on February 28, 2024, 1:17 pmthe service checks health of the drives, it does not invoke a test itself. errors from regular operations will be reported.
the service checks health of the drives, it does not invoke a test itself. errors from regular operations will be reported.
No smartd configured by default?
minimos
4 Posts
Quote from minimos on February 23, 2024, 10:24 amHello,
I might have overlooked the installation guide, but it seems that my Petasan cluster doesn't run periodically SMART tests.I was chasing a ceph error, and through manual run of smartctl I found out that a couple of disks have errors (one per node) and need to be replaced.
But in Petasan dashboard all is green (except for the ceph health warning).Should I set by myself smartd running on each node, and if so is there a recommended configuration to use?
Thanks
P.S.: I have already set zero weight to the OSDs using the faulty disks, and after 12 hours their usage is down to 1%.
Meanwhile I'm waiting for the delivery of the replacement disks, so I can replace them soon.
Hello,
I might have overlooked the installation guide, but it seems that my Petasan cluster doesn't run periodically SMART tests.
I was chasing a ceph error, and through manual run of smartctl I found out that a couple of disks have errors (one per node) and need to be replaced.
But in Petasan dashboard all is green (except for the ceph health warning).
Should I set by myself smartd running on each node, and if so is there a recommended configuration to use?
Thanks
P.S.: I have already set zero weight to the OSDs using the faulty disks, and after 12 hours their usage is down to 1%.
Meanwhile I'm waiting for the delivery of the replacement disks, so I can replace them soon.
admin
2,930 Posts
Quote from admin on February 23, 2024, 12:19 pm
- Can you please show the smarctl test command you run and output showing error.
- If you do to the Physical Disk List ui page, and click on the disk to show info, does it show smartctl error
- We have a notification service that sends email notification in case of newly detected smart errors. You should configure the users/admin emails to receive this notification. We do not show it on dashboard.
- Can you please show the smarctl test command you run and output showing error.
- If you do to the Physical Disk List ui page, and click on the disk to show info, does it show smartctl error
- We have a notification service that sends email notification in case of newly detected smart errors. You should configure the users/admin emails to receive this notification. We do not show it on dashboard.
minimos
4 Posts
Quote from minimos on February 27, 2024, 9:14 amHello,
when I logged on one of the petasan nodes and saw in dmesg there were some errors I ran a "smartctl -t short /dev/sdf" command, and below is the output.
Unfortunately, I see that smartctl test is considered 'passed' even if the disk begins to show some errors. I guess that's why Petasan doesn't report any issue in the physical disk list.
One question though, how often does Petasan trigger a smartctl test (if it does) ?smartctl 7.1 2019-12-30 r5022 [x86_64-linux-4.12.14-28-petasan] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org=== START OF INFORMATION SECTION ===
Model Family: HGST Ultrastar He6
Device Model: HGST HUS726060ALA640
Serial Number: <redacted>
LU WWN Device Id: 5 000cca 232e4acae
Firmware Version: AHGNT1EN
User Capacity: 6,001,175,126,016 bytes [6.00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Wed Feb 21 16:52:29 2024 EET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSEDGeneral SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 121) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 57) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: (1100) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0
2 Throughput_Performance 0x0005 094 094 054 Pre-fail Offline - 491
3 Spin_Up_Time 0x0007 205 205 024 Pre-fail Always - 507 (Average 465)
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 53
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 71
7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 130 130 020 Pre-fail Offline - 12
9 Power_On_Hours 0x0012 097 097 000 Old_age Always - 24280
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 53
22 Helium_Level 0x0023 100 100 025 Pre-fail Always - 100
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 1103
193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 1103
194 Temperature_Celsius 0x0002 181 181 000 Old_age Always - 33 (Min/Max 20/44)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 5
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 5
199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0SMART Error Log Version: 1
ATA Error Count: 54 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.Error 54 occurred at disk power-on lifetime: 24255 hours (1010 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 e6 9a 78 00 40 Error: UNC at LBA = 0x0000789a = 30874Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 00 80 77 00 40 00 27d+02:09:27.068 READ FPDMA QUEUED
2f 00 01 10 00 00 00 00 27d+02:09:24.751 READ LOG EXT
2f 00 01 10 00 00 00 00 27d+02:09:24.751 READ LOG EXT
60 00 08 80 77 00 40 00 27d+02:09:22.485 READ FPDMA QUEUED
60 00 00 80 75 00 40 00 27d+02:09:22.485 READ FPDMA QUEUEDError 53 occurred at disk power-on lifetime: 24255 hours (1010 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 e6 9a 78 00 40 Error: UNC at LBA = 0x0000789a = 30874Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 80 77 00 40 00 27d+02:09:24.751 READ FPDMA QUEUED
60 00 00 80 75 00 40 00 27d+02:09:22.485 READ FPDMA QUEUED
60 00 18 80 8e 07 40 00 27d+02:09:22.470 READ FPDMA QUEUED
60 00 10 80 73 00 40 00 27d+02:09:22.470 READ FPDMA QUEUED
60 80 08 80 72 00 40 00 27d+02:09:22.470 READ FPDMA QUEUEDError 52 occurred at disk power-on lifetime: 24252 hours (1010 days + 12 hours)
When the command that caused the error occurred, the device was active or idle.After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 49 b7 d2 01 40 Error: UNC at LBA = 0x0001d2b7 = 119479Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 00 00 d2 01 40 00 26d+22:26:42.152 READ FPDMA QUEUED
60 80 10 80 d8 01 40 00 26d+22:26:39.876 READ FPDMA QUEUED
60 00 08 00 d5 01 40 00 26d+22:26:39.876 READ FPDMA QUEUED
ea 00 00 00 00 00 00 00 26d+22:26:39.788 FLUSH CACHE EXT
60 08 00 68 ee 1d 40 00 26d+22:26:39.773 READ FPDMA QUEUEDError 51 occurred at disk power-on lifetime: 24252 hours (1010 days + 12 hours)
When the command that caused the error occurred, the device was active or idle.After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 49 b7 d2 01 40 Error: UNC at LBA = 0x0001d2b7 = 119479Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 00 00 d2 01 40 00 26d+22:26:39.744 READ FPDMA QUEUED
60 80 18 00 c1 0f 40 00 26d+22:26:37.469 READ FPDMA QUEUED
60 80 10 80 d8 01 40 00 26d+22:26:37.469 READ FPDMA QUEUED
60 00 08 00 d5 01 40 00 26d+22:26:37.469 READ FPDMA QUEUED
60 00 30 80 05 16 40 00 26d+22:26:37.444 READ FPDMA QUEUEDError 50 occurred at disk power-on lifetime: 24244 hours (1010 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 e6 9a 78 00 40 Error: UNC at LBA = 0x0000789a = 30874Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 00 80 77 00 40 00 26d+15:19:27.393 READ FPDMA QUEUED
2f 00 01 10 00 00 00 00 26d+15:19:25.076 READ LOG EXT
2f 00 01 10 00 00 00 00 26d+15:19:25.076 READ LOG EXT
60 00 08 80 77 00 40 00 26d+15:19:22.811 READ FPDMA QUEUED
60 00 00 80 75 00 40 00 26d+15:19:22.811 READ FPDMA QUEUEDSMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed: read failure 90% 24255 119479
# 2 Short offline Completed without error 00% 14732 -
# 3 Extended offline Completed without error 00% 2206 -
# 4 Short offline Completed without error 00% 2045 -SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Hello,
when I logged on one of the petasan nodes and saw in dmesg there were some errors I ran a "smartctl -t short /dev/sdf" command, and below is the output.
Unfortunately, I see that smartctl test is considered 'passed' even if the disk begins to show some errors. I guess that's why Petasan doesn't report any issue in the physical disk list.
One question though, how often does Petasan trigger a smartctl test (if it does) ?
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-4.12.14-28-petasan] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, http://www.smartmontools.org=== START OF INFORMATION SECTION ===
Model Family: HGST Ultrastar He6
Device Model: HGST HUS726060ALA640
Serial Number: <redacted>
LU WWN Device Id: 5 000cca 232e4acae
Firmware Version: AHGNT1EN
User Capacity: 6,001,175,126,016 bytes [6.00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Wed Feb 21 16:52:29 2024 EET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSEDGeneral SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 121) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 57) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: (1100) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0
2 Throughput_Performance 0x0005 094 094 054 Pre-fail Offline - 491
3 Spin_Up_Time 0x0007 205 205 024 Pre-fail Always - 507 (Average 465)
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 53
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 71
7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 130 130 020 Pre-fail Offline - 12
9 Power_On_Hours 0x0012 097 097 000 Old_age Always - 24280
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 53
22 Helium_Level 0x0023 100 100 025 Pre-fail Always - 100
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 1103
193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 1103
194 Temperature_Celsius 0x0002 181 181 000 Old_age Always - 33 (Min/Max 20/44)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 5
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 5
199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0SMART Error Log Version: 1
ATA Error Count: 54 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.Error 54 occurred at disk power-on lifetime: 24255 hours (1010 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 e6 9a 78 00 40 Error: UNC at LBA = 0x0000789a = 30874Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 00 80 77 00 40 00 27d+02:09:27.068 READ FPDMA QUEUED
2f 00 01 10 00 00 00 00 27d+02:09:24.751 READ LOG EXT
2f 00 01 10 00 00 00 00 27d+02:09:24.751 READ LOG EXT
60 00 08 80 77 00 40 00 27d+02:09:22.485 READ FPDMA QUEUED
60 00 00 80 75 00 40 00 27d+02:09:22.485 READ FPDMA QUEUEDError 53 occurred at disk power-on lifetime: 24255 hours (1010 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 e6 9a 78 00 40 Error: UNC at LBA = 0x0000789a = 30874Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 80 77 00 40 00 27d+02:09:24.751 READ FPDMA QUEUED
60 00 00 80 75 00 40 00 27d+02:09:22.485 READ FPDMA QUEUED
60 00 18 80 8e 07 40 00 27d+02:09:22.470 READ FPDMA QUEUED
60 00 10 80 73 00 40 00 27d+02:09:22.470 READ FPDMA QUEUED
60 80 08 80 72 00 40 00 27d+02:09:22.470 READ FPDMA QUEUEDError 52 occurred at disk power-on lifetime: 24252 hours (1010 days + 12 hours)
When the command that caused the error occurred, the device was active or idle.After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 49 b7 d2 01 40 Error: UNC at LBA = 0x0001d2b7 = 119479Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 00 00 d2 01 40 00 26d+22:26:42.152 READ FPDMA QUEUED
60 80 10 80 d8 01 40 00 26d+22:26:39.876 READ FPDMA QUEUED
60 00 08 00 d5 01 40 00 26d+22:26:39.876 READ FPDMA QUEUED
ea 00 00 00 00 00 00 00 26d+22:26:39.788 FLUSH CACHE EXT
60 08 00 68 ee 1d 40 00 26d+22:26:39.773 READ FPDMA QUEUEDError 51 occurred at disk power-on lifetime: 24252 hours (1010 days + 12 hours)
When the command that caused the error occurred, the device was active or idle.After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 49 b7 d2 01 40 Error: UNC at LBA = 0x0001d2b7 = 119479Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 00 00 d2 01 40 00 26d+22:26:39.744 READ FPDMA QUEUED
60 80 18 00 c1 0f 40 00 26d+22:26:37.469 READ FPDMA QUEUED
60 80 10 80 d8 01 40 00 26d+22:26:37.469 READ FPDMA QUEUED
60 00 08 00 d5 01 40 00 26d+22:26:37.469 READ FPDMA QUEUED
60 00 30 80 05 16 40 00 26d+22:26:37.444 READ FPDMA QUEUEDError 50 occurred at disk power-on lifetime: 24244 hours (1010 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 e6 9a 78 00 40 Error: UNC at LBA = 0x0000789a = 30874Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 00 80 77 00 40 00 26d+15:19:27.393 READ FPDMA QUEUED
2f 00 01 10 00 00 00 00 26d+15:19:25.076 READ LOG EXT
2f 00 01 10 00 00 00 00 26d+15:19:25.076 READ LOG EXT
60 00 08 80 77 00 40 00 26d+15:19:22.811 READ FPDMA QUEUED
60 00 00 80 75 00 40 00 26d+15:19:22.811 READ FPDMA QUEUEDSMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed: read failure 90% 24255 119479
# 2 Short offline Completed without error 00% 14732 -
# 3 Extended offline Completed without error 00% 2206 -
# 4 Short offline Completed without error 00% 2045 -SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
admin
2,930 Posts
Quote from admin on February 27, 2024, 12:11 pmYes the problem is that the drive reports itself as passed. Sometimes different vendors, device models sometimes report things differently.
We check drive health if you open/get info on the drive in UI under Physical Disk List. We also check every 10 min in a notification service which sends email notification if you enable it for users.
Yes the problem is that the drive reports itself as passed. Sometimes different vendors, device models sometimes report things differently.
We check drive health if you open/get info on the drive in UI under Physical Disk List. We also check every 10 min in a notification service which sends email notification if you enable it for users.
minimos
4 Posts
Quote from minimos on February 28, 2024, 10:30 amOk thanks. Sorry, I didn't quite get, does the notification service check every 10 minuts only if some disk has reported error (sending a mail), or does also trigger a complete SMART test (which I suppose it would be a short one)?
I'm still not clear if I should configure the smartd service to independently launch SMART tests or not (short test frequently, long tests perhaps monthly).
If Petasan already does it, I'd avoid my own cronjob as it could launch concurrent tests.
Ok thanks. Sorry, I didn't quite get, does the notification service check every 10 minuts only if some disk has reported error (sending a mail), or does also trigger a complete SMART test (which I suppose it would be a short one)?
I'm still not clear if I should configure the smartd service to independently launch SMART tests or not (short test frequently, long tests perhaps monthly).
If Petasan already does it, I'd avoid my own cronjob as it could launch concurrent tests.
admin
2,930 Posts
Quote from admin on February 28, 2024, 1:17 pmthe service checks health of the drives, it does not invoke a test itself. errors from regular operations will be reported.
the service checks health of the drives, it does not invoke a test itself. errors from regular operations will be reported.