{"id":916,"date":"2014-06-23T21:00:57","date_gmt":"2014-06-23T19:00:57","guid":{"rendered":"https:\/\/www.fanjoe.be\/?p=916"},"modified":"2014-07-18T23:26:34","modified_gmt":"2014-07-18T21:26:34","slug":"raspberry-mise-en-veille-du-disque-dur-avec-hdparm","status":"publish","type":"post","link":"https:\/\/www.fanjoe.be\/?p=916","title":{"rendered":"Raspberry Pi : Mise en veille du disque dur avec hdparm"},"content":{"rendered":"

\"hdparm-01\"<\/a><\/p>\n

Depuis quelques temps, j’ai remarqu\u00e9 que le disque dur raccord\u00e9 en USB \u00e0 mon Raspberry Pi ne se mettait jamais en veille. M\u00eame lorsqu’il n’\u00e9tait pas sollicit\u00e9 durant plusieurs heures.<\/p>\n

C’est peut-\u00eatre parce que c’est une disque IDE ? Le premier disque sur lequel j’effectuais mes backups \u00e9tait un SATA et je crois qu’il se mettait en veille tout seul, comme un grand. Mais je n’en suis pas certain.<\/p>\n

Donc, pour lui \u00e9viter une mort trop pr\u00e9coce, je me suis tourn\u00e9 vers hdparm<\/strong><\/a> qui est un service qui va g\u00e9rer le mode veille des disques durs support\u00e9s par le pilote de p\u00e9riph\u00e9rique Linux ATA\/IDE.
\n
\nPour l’installation, c’est tr\u00e8s facile. Comme d’habitude, on va commencer par faire une petite mise \u00e0 jour :<\/p>\n

$ sudo apt-get update && sudo apt-get upgrade<\/pre>\n
Puis on installe hdparm<\/strong> :<\/p>\n
$ sudo apt-get install hdparm<\/pre>\n
On va ensuite d\u00e9terminer comment s\u2019appelle le disque :<\/p>\n
$ sudo fdisk -l<\/pre>\n
Ce qui devrait nous retourner quelque chose comme \u00e7a :<\/p>\n
Disk \/dev\/sdb<\/span>: 250.1 GB, 250059350016 bytes\r\n69 heads, 63 sectors\/track, 112352 cylinders, total 488397168 sectors\r\nUnits = sectors of 1 * 512 = 512 bytes\r\nSector size (logical\/physical): 512 bytes \/ 512 bytes\r\nI\/O size (minimum\/optimal): 512 bytes \/ 512 bytes\r\nDisk identifier: 0x829c39c2\r\n\r\n\u00a0\u00a0 Device Boot\u00a0\u00a0\u00a0\u00a0\u00a0 Start\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 End\u00a0\u00a0\u00a0\u00a0\u00a0 Blocks\u00a0\u00a0 Id\u00a0 System\r\n\/dev\/sdb<\/span>1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 2048\u00a0\u00a0 488397167\u00a0\u00a0 244197560\u00a0\u00a0 83\u00a0 Linux<\/pre>\n
Le disque dur de 250 Gb qui nous int\u00e9resse s’appelle donc : \/dev\/sdb<\/code>. Mais ce pourrait \u00eatre sda<\/code>, sdc<\/code><\/code>, …<\/p>\n
On va maintenant tester si le HD supporte la fonctionnalit\u00e9 de gestion d’\u00e9nergie (APM pour Advanced Power Management<\/em>) :
\nCette proc\u00e9dure est document\u00e9e ici : http:\/\/doc.ubuntu-fr.org\/hdparm#gestion_d_energie<\/a><\/p>\n
$ sudo hdparm -I \/dev\/sd[X] | grep level<\/pre>\n
(o\u00f9 [X] est une lettre (entre a et z) repr\u00e9sentant votre disque dur).<\/p>\n
S’il le disque le supporte, vous obtiendrez un nombre (254 par d\u00e9faut), et vous pourrez continuer.<\/p>\n
On va alors essayer de le mettre en veille au bout de 5 secondes :<\/p>\n
$ sudo hdparm -S 1 \/dev\/sd[X]<\/pre>\n
Puis, consulter son \u00e9tat courant :<\/p>\n
$ sudo hdparm -C \/dev\/sd[X]<\/pre>\n
Sinon, il est seulement possible de le mettre en veille (arr\u00eat de la rotation des plateaux : spin down) une fois et il se relancera d\u00e8s qu’il sera sollicit\u00e9 :<\/p>\n
$ sudo hdparm -y \/dev\/sd[X]<\/pre>\n
Avec mon disque, la commande sudo hdparm -C \/dev\/sdb<\/code> me retourne unknown<\/code> et pourtant, hdparm<\/strong> fonctionne tr\u00e8s bien :<\/p>\n
\/dev\/sdb:\r\n\u00a0drive state is:\u00a0 unknown<\/pre>\n
Jusqu’ici, nous avons utilis\u00e9 hdparm<\/strong> en mode console<\/strong>, mais il est pr\u00e9f\u00e9rable de d\u00e9terminer toute les options dans le fichier \/etc\/hdparm.conf<\/code>.<\/p>\n
Vous trouverez ici la liste des fonctions<\/a> expliqu\u00e9es.<\/p>\n
Pour \u00e9diter \/etc\/hdparm.conf<\/code>, on va utiliser la commande suivante :<\/p>\n
$ sudo nano \/etc\/hdparm.conf<\/pre>\n
Puis rechercher, d\u00e9commenter et modifier la ligne suivante :<\/p>\n
# -S standby (spindown) timeout for the drive\r\nspindown_time = 60<\/pre>\n
O\u00f9 chaque unit\u00e9 \u00e9quivaut \u00e0 5 secondes. 60 = 300 secondes = 5 minutes.<\/p>\n
J’ai lu (par exemple ici<\/a>) que, parfois, les param\u00e8tres du fichier conf<\/em> n’\u00e9taient pas toujours pris en compte.
\nPour r\u00e9soudre ce probl\u00e8me, il semble utile d’ajouter la ligne suivante au fichier \/etc\/rc.local<\/code>.<\/p>\n
On \u00e9dite le fichier :<\/p>\n
$ sudo nano \/etc\/rc.local<\/pre>\n
On ajoute la ligne avant<\/strong> la derni\u00e8re ligne : exit 0<\/code><\/p>\n
sudo hdparm -S 60 \/dev\/sd[X]<\/pre>\n
Perso, au lieu d’une commande dans \/etc\/rc.local<\/code>, j’ai opt\u00e9 pour une commande dans le cron<\/strong> :<\/p>\n
$ sudo crontab -e<\/pre>\n
Et on ajoute la ligne suivante :<\/p>\n
@reboot sudo hdparm -S 60 \/dev\/disk\/by-uuid\/<\/code>d7a9f26c-2f98-4c7f-a33f-53e0fe959d13 2>&1<\/pre>\n
Le @reboot<\/code> indique \u00e0 cron<\/strong> d’ex\u00e9cuter la commande une seule fois au moment du boot. Et l’utilisation de l’uuid<\/strong> \u00e9vite les confusions de disques qui peuvent changer de nom : sda, sdb, sdc, …<\/p>\n
Quelques commandes de cron<\/strong> disponibles ici : http:\/\/doc.ubuntu-fr.org\/cron<\/a><\/p>\n
On obtient l’uuid<\/strong> du disque avec :<\/p>\n
$ sudo blkid<\/pre>\n
Et pour terminer, juste pour le plaisir, on va afficher les propri\u00e9t\u00e9s du disque dur :<\/p>\n
$ sudo hdparm -I \/dev\/sd[X] | more<\/pre>\n
\/dev\/sdb:\r\n\r\nATA device, with non-removable media\r\n\u00a0\u00a0 \u00a0Model Number:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 WDC WD2500BEVE-00WZT0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\r\n\u00a0\u00a0 \u00a0Serial Number:\u00a0\u00a0\u00a0\u00a0\u00a0 WD-WXEZ07320965\r\n\u00a0\u00a0 \u00a0Firmware Revision:\u00a0 01.01A01\r\nStandards:\r\n\u00a0\u00a0 \u00a0Supported: 8 7 6 5 \r\n\u00a0\u00a0 \u00a0Likely used: 8\r\nConfiguration:\r\n\u00a0\u00a0 \u00a0Logical\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0max\u00a0\u00a0 \u00a0current\r\n\u00a0\u00a0 \u00a0cylinders\u00a0\u00a0 \u00a016383\u00a0\u00a0 \u00a016383\r\n\u00a0\u00a0 \u00a0heads\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a016\u00a0\u00a0 \u00a016\r\n\u00a0\u00a0 \u00a0sectors\/track\u00a0\u00a0 \u00a063\u00a0\u00a0 \u00a063\r\n\u00a0\u00a0 \u00a0--\r\n\u00a0\u00a0 \u00a0CHS current addressable sectors:\u00a0\u00a0 16514064\r\n\u00a0\u00a0 \u00a0LBA\u00a0\u00a0\u00a0 user addressable sectors:\u00a0 268435455\r\n\u00a0\u00a0 \u00a0LBA48\u00a0 user addressable sectors:\u00a0 488397168\r\n\u00a0\u00a0 \u00a0Logical\/Physical Sector size:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 512 bytes\r\n\u00a0\u00a0 \u00a0device size with M = 1024*1024:\u00a0\u00a0\u00a0\u00a0\u00a0 238475 MBytes\r\n\u00a0\u00a0 \u00a0device size with M = 1000*1000:\u00a0\u00a0\u00a0\u00a0\u00a0 250059 MBytes (250 GB)\r\n\u00a0\u00a0 \u00a0cache\/buffer size\u00a0 = 8192 KBytes\r\nCapabilities:\r\n\u00a0\u00a0 \u00a0LBA, IORDY(can be disabled)\r\n\u00a0\u00a0 \u00a0Standby timer values: spec'd by Standard, with device specific minimum\r\n\u00a0\u00a0 \u00a0R\/W multiple sector transfer: Max = 16\u00a0\u00a0 \u00a0Current = 0\r\n\u00a0\u00a0 \u00a0Advanced power management level: 128\r\n\u00a0\u00a0 \u00a0Recommended acoustic management value: 128, current value: 254\r\n\u00a0\u00a0 \u00a0DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 \r\n\u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0 Cycle time: min=120ns recommended=120ns\r\n\u00a0\u00a0 \u00a0PIO: pio0 pio1 pio2 pio3 pio4 \r\n\u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0 Cycle time: no flow control=120ns\u00a0 IORDY flow control=120ns\r\nCommands\/features:\r\n\u00a0\u00a0 \u00a0Enabled\u00a0\u00a0 \u00a0Supported:\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 *\u00a0\u00a0 \u00a0SMART feature set\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0Security Mode feature set\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 *\u00a0\u00a0 \u00a0Power Management feature set\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 *\u00a0\u00a0 \u00a0Write cache\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 *\u00a0\u00a0 \u00a0Look-ahead\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 *\u00a0\u00a0 \u00a0Host Protected Area feature set\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 *\u00a0\u00a0 \u00a0WRITE_BUFFER command\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 *\u00a0\u00a0 \u00a0READ_BUFFER command\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 *\u00a0\u00a0 \u00a0NOP cmd\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 *\u00a0\u00a0 \u00a0DOWNLOAD_MICROCODE\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 *\u00a0\u00a0 \u00a0Advanced Power Management feature set\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0SET_MAX security extension\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0Automatic Acoustic Management feature set\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 *\u00a0\u00a0 \u00a048-bit Address feature set\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 *\u00a0\u00a0 \u00a0Device Configuration Overlay feature set\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 *\u00a0\u00a0 \u00a0Mandatory FLUSH_CACHE\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 *\u00a0\u00a0 \u00a0FLUSH_CACHE_EXT\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 *\u00a0\u00a0 \u00a0SMART error logging\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 *\u00a0\u00a0 \u00a0SMART self-test\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 *\u00a0\u00a0 \u00a0General Purpose Logging feature set\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 *\u00a0\u00a0 \u00a064-bit World wide name\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 *\u00a0\u00a0 \u00a0IDLE_IMMEDIATE with UNLOAD\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 *\u00a0\u00a0 \u00a0Segmented DOWNLOAD_MICROCODE\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 *\u00a0\u00a0 \u00a0SMART Command Transport (SCT) feature set\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 *\u00a0\u00a0 \u00a0SCT Long Sector Access (AC1)\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 *\u00a0\u00a0 \u00a0SCT LBA Segment Access (AC2)\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 *\u00a0\u00a0 \u00a0SCT Error Recovery Control (AC3)\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 *\u00a0\u00a0 \u00a0SCT Features Control (AC4)\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 *\u00a0\u00a0 \u00a0SCT Data Tables (AC5)\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0unknown 206[13] (vendor specific)\r\nSecurity: \r\n\u00a0\u00a0 \u00a0Master password revision code = 65534\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0supported\r\n\u00a0\u00a0 \u00a0not\u00a0\u00a0 \u00a0enabled\r\n\u00a0\u00a0 \u00a0not\u00a0\u00a0 \u00a0locked\r\n\u00a0\u00a0 \u00a0not\u00a0\u00a0 \u00a0frozen\r\n\u00a0\u00a0 \u00a0not\u00a0\u00a0 \u00a0expired: security count\r\n\u00a0\u00a0 \u00a0not\u00a0\u00a0 \u00a0supported: enhanced erase\r\n\u00a0\u00a0 \u00a084min for SECURITY ERASE UNIT. \r\nLogical Unit WWN Device Identifier: 50014ee2563ff8e4\r\n\u00a0\u00a0 \u00a0NAA\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0: 5\r\n\u00a0\u00a0 \u00a0IEEE OUI\u00a0\u00a0 \u00a0: 0014ee\r\n\u00a0\u00a0 \u00a0Unique ID\u00a0\u00a0 \u00a0: 2563ff8e4\r\nHW reset results:\r\n\u00a0\u00a0 \u00a0CBLID- above Vih\r\n\u00a0\u00a0 \u00a0Device num = 0 determined by the jumper\r\nChecksum: correct\r\n<\/pre>\n
Edit 5 juillet 2014<\/strong><\/p>\n
\"hdparm-02\"<\/a>J’utilise un disque dur 2,5 pouces avec une alimentation s\u00e9par\u00e9e sur laquelle j’ai raccord\u00e9 un transfo 5V 1A.<\/p>\n
Avec le temps, je me suis aper\u00e7u que l’ordre de branchement du disque dur au Raspberry Pi \u00e9tait important.<\/p>\n
En effet, lors de toute connexion\/d\u00e9connexion physique du disque dur, il convient de d\u00e9brancher tous les c\u00e2bles (usb et alim), puis de reconnecter d’abord<\/strong> l’alimentation, puis<\/strong>, l’USB.<\/p>\n
Dans le cas contraire, lors de sa sortie de veille, le HD va \u00ab\u00a0oublier\u00a0\u00bb qu’il est aliment\u00e9 par un transfo et essayer de ne tirer son alimentation que de la prise USB. Il en r\u00e9sulte alors un cliquetis incessant qui va occuper toutes les ressources processeur et, au final, faire crasher Raspbian.<\/p>\n","protected":false},"excerpt":{"rendered":"
<\/a><\/p>\n
Depuis quelques temps, j’ai remarqu\u00e9 que le disque dur raccord\u00e9 en USB \u00e0 mon Raspberry Pi ne se…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","jetpack_post_was_ever_published":false},"categories":[10,3,12],"tags":[96,94,97,95],"class_list":["post-916","post","type-post","status-publish","format-standard","hentry","category-geek","category-informatique","category-raspberrypi","tag-hd","tag-hdparm","tag-ide","tag-veille","end"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/www.fanjoe.be\/index.php?rest_route=\/wp\/v2\/posts\/916","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.fanjoe.be\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.fanjoe.be\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.fanjoe.be\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.fanjoe.be\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=916"}],"version-history":[{"count":0,"href":"https:\/\/www.fanjoe.be\/index.php?rest_route=\/wp\/v2\/posts\/916\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.fanjoe.be\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=916"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.fanjoe.be\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=916"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.fanjoe.be\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=916"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}