[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#516968: marked as done (base: SATA drive is resumed at boot, even if not used)

Your message dated Mon, 1 Feb 2010 14:55:38 +0100
with message-id <20100201135538.GO9849@stro.at>
and subject line Re: SATA drive usage
has caused the Debian Bug report #516968,
regarding base: SATA drive is resumed at boot, even if not 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 owner@bugs.debian.org
immediately.)


-- 
516968: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516968
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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

--- End Message ---
--- Begin Message --- 
just add your small hdparam snipped in /etc/rc.local

anyway not a kernel bug, but just a userspace policy,
thus closing.

--- End Message ---
Reply to: