Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #174547 > unrolled thread

Does hdparm not run at startup anymore?

Back to article view | Back to linux.debian.user

Contents

  Does hdparm not run at startup anymore? Rainer Dorsch <ml@bokomoko.de> - 2016-11-11 23:20 +0100
    Re: Does hdparm not run at startup anymore? Rainer Dorsch <ml@bokomoko.de> - 2016-11-12 08:40 +0100
      Re: Does hdparm not run at startup anymore? Alex Mestiashvili <alex@biotec.tu-dresden.de> - 2016-11-12 17:00 +0100
        Re: Does hdparm not run at startup anymore? Rainer Dorsch <ml@bokomoko.de> - 2016-11-12 21:20 +0100
          Re: Does hdparm not run at startup anymore? Cindy-Sue Causey <butterflybytes@gmail.com> - 2016-11-14 15:50 +0100
          Re: Does hdparm not run at startup anymore? Alex Mestiashvili <alex@biotec.tu-dresden.de> - 2016-11-16 13:30 +0100
    Re: Does hdparm not run at startup anymore? Mirko Parthey <mirko.parthey@web.de> - 2016-11-13 14:10 +0100

#174547 — Does hdparm not run at startup anymore?

[Multipart message — attachments visible in raw view] — view raw

Hi,

I configure sdb in /etc/hdparm.conf to apm=64, but when I start the system, apm does not change. Interesting enough a /etc/init.d/hdparm restart fixes the problem:


root@Silberkiste:~# cat /etc/hdparm.conf
## This is the default configuration for hdparm for Debian.  It is a 
## rather simple script, so please follow the following guidelines :)
## Any line that begins with a comment is ignored - add as many as you 
## like.  Note that an in-line comment is not supported.  If a line 
## consists of whitespace only (tabs, spaces, carriage return), it will be
## ignored, so you can space control fields as you like.  ANYTHING ELSE
## IS PARSED!!  This means that lines with stray characters or lines that 
## use non # comment characters will be interpreted by the initscript.  
## This has probably minor, but potentially serious, side effects for your 
## hard drives, so please follow the guidelines.  Patches to improve 
## flexibilty welcome.  Please read /usr/share/doc/hdparm/README.Debian for 
## notes about known issues, especially if you have an MD array.
##
## Note that if the init script causes boot problems, you can pass 'nohdparm' 
## on the kernel command line, and the script will not be run.
##
## Uncommenting the options below will cause them to be added to the DEFAULT
## string which is prepended to options listed in the blocks below.
##
## If an option is listed twice, the second instance replaces the first.
##
## /sbin/hdparm is not run unless a block of the form:
##      DEV {
##         option
##         option
##         ...
##      }
## exists.  This blocks will cause /sbin/hdparm OPTIONS DEV to be run.
## Where OPTIONS is the concatenation of all options previously defined
## outside of a block and all options defined with in the block.

# -q be quiet
quiet 
# -a sector count for filesystem read-ahead
#read_ahead_sect = 12
# -A disable/enable the IDE drive's read-lookahead feature
#lookahead = on
# -b bus state
#bus = on
# -B apm setting
#apm = 255
# -B apm setting when on battery
#apm_battery = 127
# -c enable (E)IDE 32-bit I/O support - can be any of 0,1,3
#io32_support = 1
# -d disable/enable the "using_dma" flag for this drive
#dma = off
# -D enable/disable the on-drive defect management
#defect_mana = off
# -E cdrom speed
#cd_speed = 16
# -k disable/enable the "keep_settings_over_reset" flag for this drive
#keep_settings_over_reset = off
# -K disable/enable the drive's "keep_features_over_reset" flag
#keep_features_over_reset = on
# -m sector count for multiple sector I/O
#mult_sect_io = 32
# -P maximum sector count for the drive's internal prefetch mechanism
#prefetch_sect = 12
# -r read-only flag for device
#read_only = off
# -s Turn on/off power on in standby mode
# poweron_standby = off
# -S standby (spindown) timeout for the drive
#spindown_time = 24
# -u interrupt-unmask flag for the drive
#interrupt_unmask = on
# -W Disable/enable the IDE drive's write-caching feature
#write_cache = off
# -X IDE transfer mode for newer (E)IDE/ATA2 drives
#transfer_mode = 34
# -y force to immediately enter the standby mode
#standby
# -Y force to immediately enter the sleep mode
#sleep
# -Z Disable the power-saving function of certain Seagate drives
#disable_seagate
# -M Set the acoustic management properties of a drive
#acoustic_management
# -p Set the chipset PIO mode
# chipset_pio_mode
# --security-freeze Freeze the drive's security status
# security_freeze
# --security-unlock Unlock the drive's security
# security_unlock = PWD
# --security-set-pass Set security password
# security_pass = password
# --security-disable Disable drive locking
# security_disable
# --user-master Select password to use
# user-master = u
# --security-mode Set the security mode
# security_mode = h

# Root file systems.  Please see README.Debian for details
# ROOTFS = /dev/hda

## New note - you can use straight hdparm commands in this config file 
## as well - the set up is ugly, but it keeps backwards compatibility
## Additionally, it should be noted that any blocks that begin with 
## the keyword 'command_line' are not run until after the root filesystem
## is mounted.  This is done to avoid running blocks twice.  If you need 
## to run hdparm to set parameters for your root disk, please use the 
## standard format.

#Samples follow:
#First three are good for devfs systems, fourth one for systems that do 
#not use devfs.  The fifth example uses straight hdparm command line
#syntax.  Any of the blocks that use command line syntax must begin with
#the keyword 'command_line', and no attempt is made to validate syntax.  
#It is provided for those more comfortable with hdparm syntax. 

#/dev/discs/disc0/disc {
#       mult_sect_io = 16
#       write_cache = off
#       spindown_time = 240
#}

#/dev/discs/disc1/disc {
#       mult_sect_io = 32
#       spindown_time = 36
#       write_cache = off
#}

#/dev/cdroms/cdrom0 {
#       dma = on                   
#       interrupt_unmask = on
#       io32_support = 0
#}

#/dev/hda {
#       mult_sect_io = 16
#       write_cache = off
#       dma = on
#}

/dev/sdb {
         apm = 64
         spindown_time = 5
}

root@Silberkiste:~# hdparm -I /dev/sdb|grep level
        Advanced power management level: 254
root@Silberkiste:~# /etc/init.d/hdparm restart
[ ok ] Restarting hdparm (via systemctl): hdparm.service.
root@Silberkiste:~# hdparm -I /dev/sdb|grep level
        Advanced power management level: 64
root@Silberkiste:~#


Any insight, why I need the /etc/init.d/hdparm restart is very welcome.

Thanks
Rainer

-- 
Rainer Dorsch
http://bokomoko.de/

[toc] | [next] | [standalone]

#174570

[Multipart message — attachments visible in raw view] — view raw

+ Alexandre, hdparm maintainer

On Friday 11 November 2016 23:11:24 Rainer Dorsch wrote:
> Hi,
> 
> I configure sdb in /etc/hdparm.conf to apm=64, but when I start the system, apm does not change. Interesting enough a /etc/init.d/hdparm restart fixes the problem:
> 
> 
> root@Silberkiste:~# cat /etc/hdparm.conf
> ## This is the default configuration for hdparm for Debian.  It is a 
> ## rather simple script, so please follow the following guidelines :)
> ## Any line that begins with a comment is ignored - add as many as you 
> ## like.  Note that an in-line comment is not supported.  If a line 
> ## consists of whitespace only (tabs, spaces, carriage return), it will be
> ## ignored, so you can space control fields as you like.  ANYTHING ELSE
> ## IS PARSED!!  This means that lines with stray characters or lines that 
> ## use non # comment characters will be interpreted by the initscript.  
> ## This has probably minor, but potentially serious, side effects for your 
> ## hard drives, so please follow the guidelines.  Patches to improve 
> ## flexibilty welcome.  Please read /usr/share/doc/hdparm/README.Debian for 
> ## notes about known issues, especially if you have an MD array.
> ##
> ## Note that if the init script causes boot problems, you can pass 'nohdparm' 
> ## on the kernel command line, and the script will not be run.
> ##
> ## Uncommenting the options below will cause them to be added to the DEFAULT
> ## string which is prepended to options listed in the blocks below.
> ##
> ## If an option is listed twice, the second instance replaces the first.
> ##
> ## /sbin/hdparm is not run unless a block of the form:
> ##      DEV {
> ##         option
> ##         option
> ##         ...
> ##      }
> ## exists.  This blocks will cause /sbin/hdparm OPTIONS DEV to be run.
> ## Where OPTIONS is the concatenation of all options previously defined
> ## outside of a block and all options defined with in the block.
> 
> # -q be quiet
> quiet 
> # -a sector count for filesystem read-ahead
> #read_ahead_sect = 12
> # -A disable/enable the IDE drive's read-lookahead feature
> #lookahead = on
> # -b bus state
> #bus = on
> # -B apm setting
> #apm = 255
> # -B apm setting when on battery
> #apm_battery = 127
> # -c enable (E)IDE 32-bit I/O support - can be any of 0,1,3
> #io32_support = 1
> # -d disable/enable the "using_dma" flag for this drive
> #dma = off
> # -D enable/disable the on-drive defect management
> #defect_mana = off
> # -E cdrom speed
> #cd_speed = 16
> # -k disable/enable the "keep_settings_over_reset" flag for this drive
> #keep_settings_over_reset = off
> # -K disable/enable the drive's "keep_features_over_reset" flag
> #keep_features_over_reset = on
> # -m sector count for multiple sector I/O
> #mult_sect_io = 32
> # -P maximum sector count for the drive's internal prefetch mechanism
> #prefetch_sect = 12
> # -r read-only flag for device
> #read_only = off
> # -s Turn on/off power on in standby mode
> # poweron_standby = off
> # -S standby (spindown) timeout for the drive
> #spindown_time = 24
> # -u interrupt-unmask flag for the drive
> #interrupt_unmask = on
> # -W Disable/enable the IDE drive's write-caching feature
> #write_cache = off
> # -X IDE transfer mode for newer (E)IDE/ATA2 drives
> #transfer_mode = 34
> # -y force to immediately enter the standby mode
> #standby
> # -Y force to immediately enter the sleep mode
> #sleep
> # -Z Disable the power-saving function of certain Seagate drives
> #disable_seagate
> # -M Set the acoustic management properties of a drive
> #acoustic_management
> # -p Set the chipset PIO mode
> # chipset_pio_mode
> # --security-freeze Freeze the drive's security status
> # security_freeze
> # --security-unlock Unlock the drive's security
> # security_unlock = PWD
> # --security-set-pass Set security password
> # security_pass = password
> # --security-disable Disable drive locking
> # security_disable
> # --user-master Select password to use
> # user-master = u
> # --security-mode Set the security mode
> # security_mode = h
> 
> # Root file systems.  Please see README.Debian for details
> # ROOTFS = /dev/hda
> 
> ## New note - you can use straight hdparm commands in this config file 
> ## as well - the set up is ugly, but it keeps backwards compatibility
> ## Additionally, it should be noted that any blocks that begin with 
> ## the keyword 'command_line' are not run until after the root filesystem
> ## is mounted.  This is done to avoid running blocks twice.  If you need 
> ## to run hdparm to set parameters for your root disk, please use the 
> ## standard format.
> 
> #Samples follow:
> #First three are good for devfs systems, fourth one for systems that do 
> #not use devfs.  The fifth example uses straight hdparm command line
> #syntax.  Any of the blocks that use command line syntax must begin with
> #the keyword 'command_line', and no attempt is made to validate syntax.  
> #It is provided for those more comfortable with hdparm syntax. 
> 
> #/dev/discs/disc0/disc {
> #       mult_sect_io = 16
> #       write_cache = off
> #       spindown_time = 240
> #}
> 
> #/dev/discs/disc1/disc {
> #       mult_sect_io = 32
> #       spindown_time = 36
> #       write_cache = off
> #}
> 
> #/dev/cdroms/cdrom0 {
> #       dma = on                   
> #       interrupt_unmask = on
> #       io32_support = 0
> #}
> 
> #/dev/hda {
> #       mult_sect_io = 16
> #       write_cache = off
> #       dma = on
> #}
> 
> /dev/sdb {
>          apm = 64
>          spindown_time = 5
> }
> 
> root@Silberkiste:~# hdparm -I /dev/sdb|grep level
>         Advanced power management level: 254
> root@Silberkiste:~# /etc/init.d/hdparm restart
> [ ok ] Restarting hdparm (via systemctl): hdparm.service.
> root@Silberkiste:~# hdparm -I /dev/sdb|grep level
>         Advanced power management level: 64
> root@Silberkiste:~#
> 
> 
> Any insight, why I need the /etc/init.d/hdparm restart is very welcome.
> 
> Thanks
> Rainer
> 
> 

-- 
Rainer Dorsch
http://bokomoko.de/

[toc] | [prev] | [next] | [standalone]

#174587

On 11/12/2016 08:37 AM, Rainer Dorsch wrote:
> + Alexandre, hdparm maintainer
>
> On Friday 11 November 2016 23:11:24 Rainer Dorsch wrote:
>> Hi,
>>
>> I configure sdb in /etc/hdparm.conf to apm=64, but when I start the system, apm does not change. Interesting enough a /etc/init.d/hdparm restart fixes the problem:
>>
>>
>> root@Silberkiste:~# cat /etc/hdparm.conf
<skip>
>> /dev/sdb {
>>          apm = 64
>>          spindown_time = 5
>> }
>>
>> root@Silberkiste:~# hdparm -I /dev/sdb|grep level
>>         Advanced power management level: 254
>> root@Silberkiste:~# /etc/init.d/hdparm restart
>> [ ok ] Restarting hdparm (via systemctl): hdparm.service.
>> root@Silberkiste:~# hdparm -I /dev/sdb|grep level
>>         Advanced power management level: 64
>> root@Silberkiste:~#
>>
>>
>> Any insight, why I need the /etc/init.d/hdparm restart is very welcome.
>>
>> Thanks
>> Rainer
>>
>>
Hi Rainer,
I can not reproduce this problem on my machine:

lsb_release -c
Codename:    jessie

hdparm -V
hdparm v9.43

egrep -v "^$|^#" /etc/hdparm.conf
/dev/sdc {
         apm = 64
         acoustic_management = 250
}
/dev/sdd {
         apm = 128
}
/dev/sdf {
         apm = 48
}


for disk in sdc sdd sdf; do echo $disk; hdparm -I /dev/$disk | egrep
"level:|acoustic"; done
sdc
    Advanced power management level: 64
    Recommended acoustic management value: 254, current value: 250
sdd
    Advanced power management level: disabled
    Recommended acoustic management value: 128, current value: 128
sdf
    Advanced power management level: 48
    Recommended acoustic management value: 208, current value: 0

The values are set after reboot or after init script restart.

Best,
Alex

[toc] | [prev] | [next] | [standalone]

#174607

[Multipart message — attachments visible in raw view] — view raw

Hi Alex,

thank you for your reply and your testing.

On Saturday 12 November 2016 16:40:40 Alex Mestiashvili wrote:
> On 11/12/2016 08:37 AM, Rainer Dorsch wrote:
> > + Alexandre, hdparm maintainer
> >
> > On Friday 11 November 2016 23:11:24 Rainer Dorsch wrote:
> >> Hi,
> >>
> >> I configure sdb in /etc/hdparm.conf to apm=64, but when I start the system, apm does not change. Interesting enough a /etc/init.d/hdparm restart fixes the problem:
> >>
> >>
> >> root@Silberkiste:~# cat /etc/hdparm.conf
> <skip>
> >> /dev/sdb {
> >>          apm = 64
> >>          spindown_time = 5
> >> }
> >>
> >> root@Silberkiste:~# hdparm -I /dev/sdb|grep level
> >>         Advanced power management level: 254
> >> root@Silberkiste:~# /etc/init.d/hdparm restart
> >> [ ok ] Restarting hdparm (via systemctl): hdparm.service.
> >> root@Silberkiste:~# hdparm -I /dev/sdb|grep level
> >>         Advanced power management level: 64
> >> root@Silberkiste:~#
> >>
> >>
> >> Any insight, why I need the /etc/init.d/hdparm restart is very welcome.
> >>
> >> Thanks
> >> Rainer
> >>
> >>
> Hi Rainer,
> I can not reproduce this problem on my machine:
> 
> lsb_release -c
> Codename:    jessie
> 
> hdparm -V
> hdparm v9.43
> 
> egrep -v "^$|^#" /etc/hdparm.conf
> /dev/sdc {
>          apm = 64
>          acoustic_management = 250
> }
> /dev/sdd {
>          apm = 128
> }
> /dev/sdf {
>          apm = 48
> }
> 
> 
> for disk in sdc sdd sdf; do echo $disk; hdparm -I /dev/$disk | egrep
> "level:|acoustic"; done
> sdc
>     Advanced power management level: 64
>     Recommended acoustic management value: 254, current value: 250
> sdd
>     Advanced power management level: disabled
>     Recommended acoustic management value: 128, current value: 128
> sdf
>     Advanced power management level: 48
>     Recommended acoustic management value: 208, current value: 0
> 
> The values are set after reboot or after init script restart.
> 

Hmm...since hdparm works for me if I do a 

# /etc/init.d/hdparm restart

after boot (or even in /etc/rc.local, is it possible that hdparm runs for my system for whatever reason too early (though it is not special setup, all SATA SSDs and HDDs)?

Rainer


-- 
Rainer Dorsch
http://bokomoko.de/

[toc] | [prev] | [next] | [standalone]

#174698

On 11/12/16, Rainer Dorsch <ml@bokomoko.de> wrote:
>
> On Saturday 12 November 2016 16:40:40 Alex Mestiashvili wrote:
>> On 11/12/2016 08:37 AM, Rainer Dorsch wrote:
>> > + Alexandre, hdparm maintainer
>> >
>> > On Friday 11 November 2016 23:11:24 Rainer Dorsch wrote:
>> >> Hi,
>> >>
>> >> I configure sdb in /etc/hdparm.conf to apm=64, but when I start the
>> >> system, apm does not change. Interesting enough a /etc/init.d/hdparm
>> >> restart fixes the problem:
>> >>
>> >> < snipped for brevity >
>> >> root@Silberkiste:~# hdparm -I /dev/sdb|grep level
>> >>         Advanced power management level: 254
>> >> root@Silberkiste:~# /etc/init.d/hdparm restart
>> >> [ ok ] Restarting hdparm (via systemctl): hdparm.service.
>> >> root@Silberkiste:~# hdparm -I /dev/sdb|grep level
>> >>         Advanced power management level: 64
>> >> root@Silberkiste:~#
>> >>
>> >>
>> >> Any insight, why I need the /etc/init.d/hdparm restart is very
>> >> welcome.
>> >>
>> >>
>> Hi Rainer,
>> I can not reproduce this problem on my machine:
>>
>> lsb_release -c
>> Codename:    jessie
>>
>> hdparm -V
>> hdparm v9.43
>>
>> < snipped for brevity >
>
> Hmm...since hdparm works for me if I do a
>
> # /etc/init.d/hdparm restart
>
> after boot (or even in /etc/rc.local, is it possible that hdparm runs for my
> system for whatever reason too early (though it is not special setup, all
> SATA SSDs and HDDs)?


Hi.. Have CC'd those recently brought into the loop (because it seemed
the proper thing to do)..

What I'm sharing is "similarly different". It's only one of the
problems I'm having with (STILL) attempting to get wireless/Bluetooth
to function, but this thread right here is one of the things I'm
facing, too.

It's been a few days since I... attempted it so I've forgotten which
[package] this worked for, but one function that WAS working needed a
manual restart after reboots. Whichever [package] it was, that package
would be "failed" (or similar error) for a "systemctl status" command
issuance. It would then function fine (based on systemctl status query
feedback) after a "systemctl restart" terminal command line restart.
Again, this was all immediately after a fresh reboot where things
become reset.

Been a couple threads recently where my instance seemed to potentially
apply, as well, actually. Like maybe it's hinting at something more
universal involved beyond singular packages. I'm on Sid Unstable
(attempting a Stretch debootstrap in just a few).

Cindy :)

-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* Ya gotta find your crochet-t-t-t-t!!! *

[toc] | [prev] | [next] | [standalone]

#174794

On 11/12/2016 09:14 PM, Rainer Dorsch wrote:
> Hi Alex,
> 
> thank you for your reply and your testing.
> 
> On Saturday 12 November 2016 16:40:40 Alex Mestiashvili wrote:
>> On 11/12/2016 08:37 AM, Rainer Dorsch wrote:
>>> + Alexandre, hdparm maintainer
>>>
>>> On Friday 11 November 2016 23:11:24 Rainer Dorsch wrote:
>>>> Hi,
>>>>
>>>> I configure sdb in /etc/hdparm.conf to apm=64, but when I start the system, apm does not change. Interesting enough a /etc/init.d/hdparm restart fixes the problem:
>>>>
>>>>
>>>> root@Silberkiste:~# cat /etc/hdparm.conf
>> <skip>
>>>> /dev/sdb {
>>>>          apm = 64
>>>>          spindown_time = 5
>>>> }
>>>>
>>>> root@Silberkiste:~# hdparm -I /dev/sdb|grep level
>>>>         Advanced power management level: 254
>>>> root@Silberkiste:~# /etc/init.d/hdparm restart
>>>> [ ok ] Restarting hdparm (via systemctl): hdparm.service.
>>>> root@Silberkiste:~# hdparm -I /dev/sdb|grep level
>>>>         Advanced power management level: 64
>>>> root@Silberkiste:~#
>>>>
>>>>
>>>> Any insight, why I need the /etc/init.d/hdparm restart is very welcome.
>>>>
>>>> Thanks
>>>> Rainer
>>>>
>>>>
>> Hi Rainer,
>> I can not reproduce this problem on my machine:
>>
>> lsb_release -c
>> Codename:    jessie
>>
>> hdparm -V
>> hdparm v9.43
>>
>> egrep -v "^$|^#" /etc/hdparm.conf
>> /dev/sdc {
>>          apm = 64
>>          acoustic_management = 250
>> }
>> /dev/sdd {
>>          apm = 128
>> }
>> /dev/sdf {
>>          apm = 48
>> }
>>
>>
>> for disk in sdc sdd sdf; do echo $disk; hdparm -I /dev/$disk | egrep
>> "level:|acoustic"; done
>> sdc
>>     Advanced power management level: 64
>>     Recommended acoustic management value: 254, current value: 250
>> sdd
>>     Advanced power management level: disabled
>>     Recommended acoustic management value: 128, current value: 128
>> sdf
>>     Advanced power management level: 48
>>     Recommended acoustic management value: 208, current value: 0
>>
>> The values are set after reboot or after init script restart.
>>
> 
> Hmm...since hdparm works for me if I do a 
> 
> # /etc/init.d/hdparm restart
> 
> after boot (or even in /etc/rc.local, is it possible that hdparm runs for my system for whatever reason too early (though it is not special setup, all SATA SSDs and HDDs)?
> 
> Rainer
> 
> 

Hi Rainer,

you can try to tweak the init script to see what is really happening,
for example by echoing more information or redirecting the command
outputs to a logfile.
Alternatively you can give hdparm link a higher Start number in
/etc/rc3.d/ to see if it helps.

Best,
Alex

[toc] | [prev] | [next] | [standalone]

#174647

On Fri, Nov 11, 2016 at 11:11:24PM +0100, Rainer Dorsch wrote:
> I configure sdb in /etc/hdparm.conf to apm=64, but when I start the system, apm
> does not change. Interesting enough a /etc/init.d/hdparm restart fixes the
> problem:

There are two config options available: "apm" and "apm_battery".
Which one takes effect depends on your machine's power status:
connected to external power or running on battery.
Does this help you?
If not, please run these commands as root and show us their output:

  find /etc/rc* \( -name "*hdparm" -o -lname "*hdparm" \) -ls
  ls -l /sbin/init
  systemctl status hdparm

Regards
Mirko

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web