Your message dated Mon, 1 Jul 2019 14:31:40 +0200 with message-id <[email protected]> and subject line hdparm.conf settings fail if mult_sect_io option is used. has caused the Debian Bug report #775605, regarding hdparm.conf settings fail if mult_sect_io option is used. to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 775605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775605 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: hdparm Version: 9.43-1.1 Severity: normal Dear Maintainer, After attempting to persist some hdparm setttings using the hdparm.conf file I noticed that (none of) the settings were being applied at boot. each boot resulted in the following in /var/log/sysconfig: Jan 17 19:39:21 debian hdparm[206]: Setting parameters of disc: /dev/sda failed! Jan 17 19:39:21 debian hdparm[206]: /dev/sdb failed! Jan 17 19:39:21 debian hdparm[206]: /dev/sdc failed! Jan 17 19:39:21 debian hdparm[206]: /dev/sdd failed! The alterations to my hdparm.conf file were: mult_sect_io = 16 and a block at the end of the file: /dev/sda { write_cache = on } /dev/sdb { write_cache = on } /dev/sdc { write_cache = on } /dev/sdd { write_cache = on } I *can* set these options manually: # hdparm -m16 --yes-i-know-what-i-am-doing /dev/sda /dev/sda: setting multcount to 16 multcount = 16 (on) # hdparm -W1 /dev/sda /dev/sda: setting drive write-caching to 1 (on) write-caching = 1 (on) If I remove the "mult_sect_io = 16" option from the hdparm.conf file, (and leave the block dealing with the write_cache) then the settings are applied correctly when the machine boots and I get the expected confirmation of this in /var/log/sysconfig, e.g.: Jan 17 20:30:20 debian hdparm[207]: Setting parameters of disc: /dev/sda. Jan 17 20:30:20 debian hdparm[207]: /dev/sdb. Jan 17 20:30:20 debian hdparm[207]: /dev/sdc. Jan 17 20:30:20 debian hdparm[207]: /dev/sdd. I *suspect* that the problem relates to the fact that you can't use the -m option on the command line without the --yes-i-know-what-i-am-doing switch, (this is just a guess but I can't see any sign of this switch in the init script, there is also no mention of needing this switch in the man page.) Regards, Craig -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages hdparm depends on: ii libc6 2.19-13 ii lsb-base 4.1+Debian13+nmu1 Versions of packages hdparm recommends: ii powermgmt-base 1.31+nmu1 Versions of packages hdparm suggests: pn apmd <none> -- Configuration Files: /etc/hdparm.conf changed [not included] -- no debconf information
--- End Message ---
--- Begin Message ---tags: wontfix Closing. hdparm refuses to apply potentially dangerous settings on boot.
--- End Message ---
