On Mon, Feb 1, 2010 at 15:09, Debian Bug Tracking System
<owner@bugs.debian.org> wrote:
This is an automatic notification regarding your Bug report
which was filed against the linux-2.6 package:
#516968: base: SATA drive is resumed at boot, even if not used
It has been closed by maximilian attems <max@stro.at>.
Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact maximilian attems <max@stro.at> by
replying to this email.
--
516968: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516968
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
---------- Forwarded message ----------
From: maximilian attems <max@stro.at>
To: 516968-done@bugs.debian.org
Date: Mon, 1 Feb 2010 14:55:38 +0100
Subject: Re: SATA drive usage
just add your small hdparam snipped in /etc/rc.local
anyway not a kernel bug, but just a userspace policy,
thus closing.
/etc/rc.local is executed AFTER kernel spins-up the disk. i don't want to put disk to sleep every boot. it is already in 'start in sleep mode' but someway kernel spins-up the disk even if it is not to be mounted. this is kernel thing i think so, or sata_nv kernel module.
normally, all disks are spinned-up in BIOS's post stage. but when disk has set option 'start in sleep mode' post stage skips the disk. the same kernel should do.
---------- Forwarded message ----------
From: Mark Poks <markpoks@wp.pl>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Date: Tue, 24 Feb 2009 20:17:00 +0100
Subject: base: SATA drive is resumed at boot, even if not used
Package: base
Severity: important
i have extra SATA disk which i use rarely. so to reduce some power consumption
and noise - i put the disk to 'start in sleep state'. i've done it with
hdparam -s /dev/sdX. obviously i have removed all links in fstab to that drive.
to prevent any auto mount.
motor of the disk is no longer starting when bios is booting-up the
machine, but unfortunetly it does when system starts INIT section (after initrd
finishes it's job).
i cannot discover what exactly makes disk to start it's motor but it's possibly
sata_nv driver - motor begins to work near logs from this driver.
i would like to start my extra disks on demand - when they are needed, but as
for now i can't do that.
Mark
-- System Information:
Debian Release: 5.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash