Hardware⏱️ 3 min read📅 2026-05-29

How to Fix: smartd scheduled short test overloads system & crashes it

Quick Answer: Check the SAS HBA and expander configuration to ensure they are properly configured and not causing any conflicts. Also, verify that the system's power supply unit (PSU) is sufficient for the workload during the short test.

The issue you're experiencing is caused by the smartd service running a scheduled short test that overloads the system and causes it to crash. This can happen when the test collides with other services or when there are issues with file indexing, such as bugged plocate/mlocate/updatedb processes.

⚠️ Common Causes

  • The smartd service is configured to run a short test that exceeds the system's power limits, causing it to crash.
  • The SAS HBAs + expanders are overloaded, leading to excessive power consumption and heat generation.
  • File indexing issues, such as bugged plocate/mlocate/updatedb processes, can cause the system to become unstable and crash during the short test.

🛠️ Step-by-Step Verified Fixes

Method 1: Disable Smartd Short Test

  1. Step 1: Edit the smartd configuration file to disable the short test.
  2. Step 2: Run the command smartctl -d scsi -q run to stop the smartd service.
  3. Step 3: Verify that the short test is no longer scheduled by running the command smartctl -d scsi -q status.

Method 2: Monitor and Manage Power Consumption

  1. Step 1: Install monitoring software, such as smartdmon, to track power consumption and identify potential issues.
  2. Step 2: Adjust the system's power settings to ensure that the SAS HBAs + expanders are not overloaded.

Method 3: Resolve File Indexing Issues

  1. Step 1: Update the plocate/mlocate/updatedb packages to the latest version.
  2. Step 2: Run the command find / -type f -print > /dev/null to identify and clean up any unnecessary files.

💡 Conclusion

By following these steps, you should be able to resolve the issue causing your system to crash during the smartd short test. Remember to monitor your system's power consumption and file indexing to prevent similar issues in the future.

Did this fix your problem?

If not, try searching for specific error codes.

🔍 Search Error Database

❓ Frequently Asked Questions