Package: hdparm Version: 6.9-1 Severity: normal Hi,
There is a problem with the boot order. Lets take a look at it: 1. udev calls hdparm script even on coldplug 2. init.d script itself runs 3. hal will start and take a look at the disks You may think: what's wrong? Well, the "suspend" and "sleep" configuration items are pretty much incompatible with that: 1. udev spits errors because the drive goes to sleep under it and probably misses some information 2. init.d script puts the drive to sleep again but MUST make sure that the sleep/suspend commands are issued at the last ones! 3. hal requests info from the drive and wakes it up Result: a drive that is not put to sleep. Besides that, it may not be healthy. Requested solution items: - do not run at coldplug (if that's possible) to keep udev happy and be nicer to the drive - coordinate with hal, so either start after it (at least for the suspend/sleep rules) - when speciying security-freeze globally and sleep as an additional for one drive, the sleep should be the last command Currently, it is somewhat easier to set it manually without /etc/hdparm.conf. I guess that is not the point of the file, isn't it? Have fun... HS -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18.6 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages hdparm depends on: ii libc6 2.3.6.ds1-8 GNU C Library: Shared libraries ii lsb-base 3.1-22 Linux Standard Base 3.1 init scrip hdparm recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
