rigacci.org

User Tools

Site Tools

Trace:
doc:appunti:hardware:raspberrypi_nas_smart_hard_disk

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
doc:appunti:hardware:raspberrypi_nas_smart_hard_disk [2021/03/11 10:39] – [smartctl] niccolodoc:appunti:hardware:raspberrypi_nas_smart_hard_disk [2025/10/10 11:24] (current) – [udisks2.service] niccolo
Line 1: Line 1:
 ====== Raspberry Pi NAS: Hard disk management ====== ====== Raspberry Pi NAS: Hard disk management ======
 +
 +This page is about configuring the **hard disk power management** on a Raspberry Pi, to be used as NAS and mediacenter. The hard disk is connected via a **[[raspberrypi_nas_x835_sata_board|SupTronics X835 shield]]**. See the main index at **[[raspberrypi_nas]]**. The operating system is **RaspiOS** based on **Debian 11 Bullseye**.
  
 There are two tools to manage SATA disks in GNU/Linux. **smartctl** is designed to interact with the **[[wp>S.M.A.R.T.]]** capabilities of a disk. **hdparm** is a command line interface to the Linux kernel SATA subsystem, including Advanced Power Management. There are two tools to manage SATA disks in GNU/Linux. **smartctl** is designed to interact with the **[[wp>S.M.A.R.T.]]** capabilities of a disk. **hdparm** is a command line interface to the Linux kernel SATA subsystem, including Advanced Power Management.
Line 18: Line 20:
 # Disable DEVICESCAN, which does not work in our environment. # Disable DEVICESCAN, which does not work in our environment.
 #DEVICESCAN -d removable -n standby -m root -M exec /usr/share/smartmontools/smartd-runner #DEVICESCAN -d removable -n standby -m root -M exec /usr/share/smartmontools/smartd-runner
- 
-# Send an email test to <root@localhost> on daemon start. 
-/dev/sda -d sat -m root@localhost -M test 
  
 # Use the suggedested subset of checks, instead of the '-a'. # Use the suggedested subset of checks, instead of the '-a'.
 +# NOTICE: We are running smartd with option --interval=3600 instead of the
 +# 1800 default, i.e. device polling occurs every 1 our instead of 30 minutes.
 +# The number of skipped checks (option -n) must be multipled by that value
 +# to obtain the maximum time that checks will be skipped:
 +# 336 * 3600 seconds = 14 days.
 /dev/sda -d sat \ /dev/sda -d sat \
     -H \                # Check the health with the SMART RETURN STATUS command     -H \                # Check the health with the SMART RETURN STATUS command
Line 31: Line 35:
     -W 0,50,60 \        # Temperature (SMART att. 194): WARN=50 (log), CRIT=60 (mail)     -W 0,50,60 \        # Temperature (SMART att. 194): WARN=50 (log), CRIT=60 (mail)
     -s S/../../1/23 \   # Schedule a short Self-Test at 23:00 of every monday.     -s S/../../1/23 \   # Schedule a short Self-Test at 23:00 of every monday.
 +    -s O/../.././21 \   # Schedule an Offline Immediate Test every day at 21:00.
     -m root@localhost \ # Send a warning email on failures and errors     -m root@localhost \ # Send a warning email on failures and errors
     -M daily \          # Repeat email warnings daily     -M daily \          # Repeat email warnings daily
Line 65: Line 70:
   * **Long Self-Test**: like short test, but with no time restriction and Read/Verify spans the entire disk. It requires tens of minutes to several hours to complete, can be given during normal system operation.   * **Long Self-Test**: like short test, but with no time restriction and Read/Verify spans the entire disk. It requires tens of minutes to several hours to complete, can be given during normal system operation.
   * **Conveyance Test** (ATA only): a few minutes to check for damages incurred during transporting of the device. It requires a few minutes to complete.   * **Conveyance Test** (ATA only): a few minutes to check for damages incurred during transporting of the device. It requires a few minutes to complete.
-  * **Offline Immediate  Test**: The results of this immediate offline testing (data collection) are reflected in the values of the SMART Attributes. Thus, if problems or errors are detected, the values of these Attributes will go below  their failure thresholds; some types of errors may also appear in the SMART error log. These are visible with the '-A' and '-l error' options respectively.+  * **Offline Immediate  Test**: The results of this test is actually the data collection reflected in the values of the SMART Attributes. Thus, if problems or errors are detected, the values of these Attributes will go below their failure thresholds; some types of errors may also appear in the SMART error log. These are visible with the ''-A'' and ''-l error'' options respectively.
  
 If you want to display the log e.g. of self-test executed, run: If you want to display the log e.g. of self-test executed, run:
Line 88: Line 93:
 ===== hdparm ===== ===== hdparm =====
  
-To set the **Advanced Power Management** level use the **%%-B%%** option, the maximum performance level which **permits spin-down** of the drive is 127:+To set the **Advanced Power Management** level use the **%%-B%%** option. A low value means aggressive power management, an high value means better performance. The maximum performance level which **permits spin-down** of the drive is 127:
  
 <code> <code>
Line 94: Line 99:
 </code> </code>
  
-Regardless of the APM level, we can set the hard disk **Standby timer** (spindown) after 30 minutes of inactivity. See **man hdparm** for explanation of the number following the **%%-S%%** option (it seems that there is not way to know the timeout once you have set it):+Regardless of the APM level, we can set the hard disk **Standby timer** (spindown) after 30 minutes of inactivity. See **man hdparm** for explanation of the number following the **%%-S%%** option (the granularity of the timer up to 20 minutes is 5 seconds, above that threshold it is 30 minutes). It seems that there is not way to know the timeout once you have set it.
  
 <code> <code>
Line 108: Line 113:
 </code> </code>
  
-Debian provides the file **/etc/hdparm.conf** which is handled by the **udev** on system start to set the required parameters. You can set something like this:+Debian provides the file **/etc/hdparm.conf** which is handled by the **udev** on **system start** to set the required parameters. You can set something like this:
  
 <file> <file>
Line 114: Line 119:
 # It is advisable to disable write cache in this case. # It is advisable to disable write cache in this case.
 # See man hdparm(8), -S and -W options. # See man hdparm(8), -S and -W options.
 +# The granularity of the spindown_time up to 20 minutes is 5
 +# seconds, above that threshold it is 30 minutes.
 /dev/sda { /dev/sda {
         write_cache = off         write_cache = off
Line 153: Line 160:
  
   * **updatedb** - Execute by the **/etc/cron.daily/mlocate** cronjob, will update the database of files stored on hard disk. Add the directory to be skipped into **/etc/updatedb.conf**.   * **updatedb** - Execute by the **/etc/cron.daily/mlocate** cronjob, will update the database of files stored on hard disk. Add the directory to be skipped into **/etc/updatedb.conf**.
-  * **smartctl** - Reading SMART attributes (e.g. disk temperature, errors log) awake the disk. Hou may have periodic checks executed by **snmpd**, etc.+  * **smartctl** - Reading SMART attributes (e.g. disk temperature, errors log) awake the disk. You may have periodic checks executed by **snmpd**, etc. 
 + 
 +===== udisks2.service ===== 
 + 
 +It seems that the **udisks2.service** may interfere with the hard disk spin-down feature. The ''man 8 udisks'' refers to setting APT options (//StandbyTimeout//, //APMLevel//, ...) via ATA commands. 
 + 
 +It is likely that the hdparm options set by **udev** on system start are overridden by udisks2. In a [[..:software:kodi_installation_raspios_13|system based on RaspiOS 13 Trixie]] I had to remove the **udisks2** package to allow the hard drive to go into standby mode as epxlained above. 
 + 
 +Some useful udisks2 commands: 
 + 
 +<code> 
 +udisksctl info -b /dev/sda3 
 +</code> 
  
 ===== Web References ===== ===== Web References =====
  
   * **[[https://www.thomas-krenn.com/en/wiki/SMART_tests_with_smartctl|SMART tests with smartctl]]**   * **[[https://www.thomas-krenn.com/en/wiki/SMART_tests_with_smartctl|SMART tests with smartctl]]**
 +  * **[[https://serverfault.com/questions/275364/get-drive-power-state-without-waking-it-up/|Get drive power state without waking it up]]** 
 +  * **[[https://unix.stackexchange.com/questions/366438/hard-disk-not-going-to-standby-automatically|Hard disk not going to standby automatically]]** 
 +  * **[[https://serverfault.com/questions/305847/how-to-determine-disc-spindown-time|How to determine disc spindown time]]**
  
doc/appunti/hardware/raspberrypi_nas_smart_hard_disk.1615455557.txt.gz · Last modified: by niccolo