User  |  Syst  |  Libr  |  Device  |  Files  |  Other  |  Admin  |  Head  |

---

   hdparm    ( 8 )

---

---

Ошибки (баги) (Bugs)

As noted above, the -m sectcount and -u 1 options should be used
       with caution at first, preferably on a read-only filesystem.
       Most drives work well with these features, but a few
       drive/controller combinations are not 100% compatible.
       Filesystem corruption may result.  Backup everything before
       experimenting!

       Some options (e.g. -r for SCSI) may not work with old kernels as
       necessary ioctl()´s were not supported.

       Although this utility is intended primarily for use with SATA/IDE
       hard disk devices, several of the options are also valid (and
       permitted) for use with SCSI hard disk devices and MFM/RLL hard
       disks with XT interfaces.

       The Linux kernel up until 2.6.12 (and probably later) doesn´t
       handle the security unlock and disable commands gracefully and
       will segfault and in some cases even panic. The security commands
       however might indeed have been executed by the drive. This poor
       kernel behaviour makes the PIO data security commands rather
       useless at the moment.

       Note that the "security erase" and "security disable" commands
       have been implemented as two consecutive PIO data commands and
       will not succeed on a locked drive because the second command
       will not be issued after the segfault.  See the code for hints
       how patch it to work around this problem. Despite the segfault it
       is often still possible to run two instances of hdparm
       consecutively and issue the two necessary commands that way.

---