** No longer affects: gentoo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/17216
Title:
Hard drive spindown should be configurable
To manage notifications about this bug go to:
https://bugs
** No longer affects: acpi-support (Mandriva)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/17216
Title:
Hard drive spindown should be configurable
To manage notifications about this bug go
** Changed in: acpi-support (Mandriva)
Importance: Unknown => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https://bugs.launchpad.net/bugs/17216
Title:
Hard drive spindown should be configurable
--
ubuntu-bugs mailin
** Changed in: acpi-support (Mandriva)
Status: Invalid => Unknown
--
Hard drive spindown should be configurable
https://bugs.launchpad.net/bugs/17216
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubun
In current Ubuntu releases, acpi-support doesn't touch the disk power
settings at all when transitioning on/off battery power, so I think this
report can be closed as resolved.
** Changed in: acpi-support (Ubuntu)
Status: Fix Committed => Fix Released
--
Hard drive spindown should be conf
Wow -- this is finally getting fixed? :D
--
Hard drive spindown should be configurable
https://bugs.launchpad.net/bugs/17216
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
** Visibility changed to: Private
** This bug has been flagged as a security issue
--
Hard drive spindown should be configurable
https://bugs.launchpad.net/bugs/17216
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailin
** Changed in: acpi-support (Mandriva)
Status: In Progress => Invalid
--
Hard drive spindown should be configurable
https://bugs.launchpad.net/bugs/17216
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
Johnathon wrote on 2007-10-31:
"Added Gentoo to the list as we have had the bug confirmed there. Does anyone
know where the gentoo bug tracker is, and if so, is there already a bug there
about this issue?"
Just google it: http://bugs.gentoo.org/
I didn't find any bug about it there. If you find
For everyone who doesn't know :
The Load_Cycle_Issue bug continues here :
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/59695
--
Hard drive spindown should be configurable
https://bugs.launchpad.net/bugs/17216
You received this bug notification because you are a member of Ubuntu
Bu
Stock Ubuntu Feisty on HP 6715s:
$ sudo smartctl -ad ata /dev/sda |grep Load_Cycle; sleep 300; sudo smartctl -ad
ata /dev/sda |grep Load_Cycle
193 Load_Cycle_Count0x0012 095 095 000Old_age Always
- 58565
193 Load_Cycle_Count0x0012 095 095 000Old_
** Changed in: acpi-support (Mandriva)
Status: Confirmed => In Progress
--
Hard drive spindown should be configurable
https://bugs.launchpad.net/bugs/17216
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing lis
tracker bugs that are possibly relevant :
"[gutsy] trackerd kills disk io"
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/131983
"Tracker should not be enabled by default until it doesn't clobber everything"
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/132741
"the index delay s
a bug regarding laptop_mode :
power.sh: wrong laptop_mode activation
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/89269
more disk activity bugs :
evolution : Heavy disk activity when resizing columns
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/159037
tracker : Tracke
** Changed in: acpi-support (Mandriva)
Status: Unknown => Confirmed
--
Hard drive spindown should be configurable
https://bugs.launchpad.net/bugs/17216
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ub
my suggestion for a name for this Load_Cycle_Count bug :
rapid parking/unparking of harddisk head caused by too aggressive power
management and unnecessary disk activity
--
Hard drive spindown should be configurable
https://bugs.launchpad.net/bugs/17216
You received this bug notification because
> In fact, I think that this issue was inaccurately
> duped onto the "Spindown Configurable" bug
Quite possibly. The bug I reported is nothing to do with spindown or
load cycles since I get the clicking without the drive spinning down or
the load cycle count increasing, but that bug was duped her
* (laptop) harddisk firmwares and (laptop) BIOSes might set too aggressive
power management (operating system independent)
* The operating system and the applications running on it might cause too much
unnecessary disk activity (multiple operating systems are affected. at least a
couple of Linux
btrace howto :
sudo aptitude install blktrace
sudo mount -t debugfs none_debug /sys/kernel/debug
sudo su
echo 1 > /proc/sys/vm/block_dump
exit
sudo /etc/init.d/sysklogd stop
sudo btrace /dev/sda
open a second terminal and keep typing (can't this be done easier?) :
dmesg
once you are done :
sudo
Groover wrote:
>> ubuntu_demon wrote:
>> I would like to see some btrace output from people who are suffering from
>> the fastly increasing Load_Cycle_Count problem.
>
> Indeed, it was interesting! I have had evolution running on another
> workspace, but it had not touched the drive. Instead, it
>ubuntu_demon wrote:
>I would like to see some btrace output from people who are suffering from the
>fastly increasing Load_Cycle_Count problem.
Indeed, it was interesting! I have had evolution running on another
workspace, but it had not touched the drive. Instead, it were kjournald
and pdflush.
Can we rename this bug? "Hard drive spindown should be configurable" is
laughably inaccurate. In fact, I think that this issue was inaccurately
duped onto the "Spindown Configurable" bug, related though they are.
Since the frequent disk access issue is quite active, and if others
agree, I'll rena
another way to fix the issue although I haven't investigated which
parameters are best :
http://www.suselinuxsupport.de/wikka.php?wakka=HowToSaveYourLaptopHD
http://mishameteo.blogspot.com/2007/10/ubuntu-default-acpi-settings-decreases.html
http://bbs.archlinux.org/viewtopic.php?pid=294594#p294594
This Load_Cycle_Count issue on forums of other distributions :
Arch Linux
http://bbs.archlinux.org/viewtopic.php?pid=294929
Mandriva
http://forum.mandriva.com/viewtopic.php?p=393299
Suse
http://forums.suselinuxsupport.de/index.php?showtopic=62262&st=0
--
Hard drive spindown should be configur
to Alex Muntada :
Sometimes the raw value isn't easy to interpret. If you divide your raw
Load_Cycle_Count value by the smallest increment you can find then you
will probably have your real Load_Cycle_Count. You can also track your
WORST (84 right now for you) and calculate when it will reach your
to Chrischan :
Thanks for notifying people about the fact that some harddisks use too
aggressive power management settings. In your case Western Digital uses
it as a selling point for this particular drive.
from http://www.wdc.com/en/products/products.asp?driveid=336 :
"Reduced power consumption
I forgot to include the output of blktrace on:
https://bugs.edge.launchpad.net/ubuntu/+source/acpi-
support/+bug/17216/comments/92
Well, it isn't needed because it traced 0 events.
--
Hard drive spindown should be configurable
https://bugs.launchpad.net/bugs/17216
You received this bug notificat
I have a Sony VAIO VGN-T2XP (ULV processor) and I guess my BIOS is
broken because the Load_Cycle_Count is so extremely huge and grows so
quickly that it can't be true. Maybe other are also broken.
These is the proof of concept:
1. performed an apt-get dist-upgrade in order to be sure that I have
Hi everybody,
I have a VIA Epia board (EX1EG) and a pretty new Western Digital 1
Terabyte WD10EACS drive. I am running Ubuntu 7.04, but I also tested
with 7.10. No laptop mode, no fiddling with ACPI, just standard setup.
Harddrive ACPI is disabled in BIOS. Nevertheless, can hear the drive
load
I wanted to see what was the evolution of that bug between edgy, feisty
and gutsy. So I took my Dell inspiron 9300 and I installed each version
of ubuntu on this laptop to test this. For each ubuntu version, I did
two "smartctl -a /dev/sda", one directly after the installation of
ubuntu, and one 2
hddtemp might cause unnecessary disk activity
https://bugs.launchpad.net/ubuntu/+source/hddtemp/+bug/160621
--
Hard drive spindown should be configurable
https://bugs.launchpad.net/bugs/17216
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber
regarding my previous post about btrace :
https://bugs.launchpad.net/ubuntu/+source/acpi-
support/+bug/17216/comments/87
You need to first do this :
sudo mount -t debugfs none_debug /sys/kernel/debug
--
Hard drive spindown should be configurable
https://bugs.launchpad.net/bugs/17216
You received
I would like to see some btrace output from people who are suffering
from the fastly increasing Load_Cycle_Count problem.
sudo aptitude install blktrace
sudo btrace /dev/sda
When I ran btrace myself I got this : "/sys/kernel/debug does not appear to be
a debug filesystem"
That's probably because
ubuntu_demon napsal(a):
> IMHO we need a solution which can be enabled by default for all laptop
> users at all times (when they are working on battery and when they are
> working on AC). IMHO Ubuntu needs to prevent too much unparking of the
> harddisk head and therefor Ubuntu needs to prevent too
to Bart Samwel :
Thanks for your comment. I linked to it in the two ext3 related bugs I
just reported.
laptop-mode is disabled by default in Ubuntu. AFAIK laptop-mode is only
used when on battery (if it is enabled by the user).
IMHO we need a solution which can be enabled by default for all lapt
probably the same Load_Cycle_Count bug on Red Hat :
https://bugzilla.redhat.com/show_bug.cgi?id=146628
A related discussion on a Fedora forum :
http://fcp.surfsite.org/modules/newbb/viewtopic.php?topic_id=46274&forum=11&post_id=213572
kjournald might be the root cause :
http://ubuntuforums.org/sh
ubuntu_demon wrote:
> Some bug reports about unnecessary disk activity. These bugs are
> possible contributors to the Load_Cycle_Count issue.
>
> * the commit interval for the ext3 filesystem should be higher than 5 seconds
> for laptop users
> https://bugs.launchpad.net/ubuntu/+source/util-linu
More possible unnecessary disk activity :
firefox might cause unnecessary disk activity when going to a new website
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/160513
--
Hard drive spindown should be configurable
https://bugs.launchpad.net/bugs/17216
You received this bug notification
Thank you!
On Tue, 2007-11-06 at 09:26 +, Mantas Kriaučiūnas wrote:
> ** Also affects: acpi-support (Baltix)
>Importance: Undecided
>Status: New
>
--
Hard drive spindown should be configurable
https://bugs.launchpad.net/bugs/17216
You received this bug notification because you ar
Some bug reports about unnecessary disk activity. These bugs are
possible contributors to the Load_Cycle_Count issue.
* the commit interval for the ext3 filesystem should be higher than 5 seconds
for laptop users
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/160448
* ext3 partitions
Follow up
All: I have never heard any hard drive ticking on my laptop.
Merton: Yes, Gutsy Gibbon is prone to this bug. You can check whether
your settings are sane by comparing several outputs of sudo "smartctl -a
/dev/", especially the Load_Cycle_Count increase
rate. Try to run the command now a
** Also affects: acpi-support (Baltix)
Importance: Undecided
Status: New
--
Hard drive spindown should be configurable
https://bugs.launchpad.net/bugs/17216
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing
I love the plan of addressing this from the other side. Specifically
try and stop the spin up, not just the spin down. Ubuntu has been
getting more and more power hungry,
http://www.phoronix.com/scan.php?page=article&item=878&num=1 and this is
one big way to address it. If you could park and slee
to Johnny Jelinek IV:
So you your harddisk is three years old which means that you used it for
roughly 5000 hours per year if your Power_On_Hours of 15100 is correct.
If you have any questions please use this support thread :
http://ubuntuforums.org/showthread.php?t=591503
--
Hard drive spindow
* the output of $sudo smartctl -a /dev/hda
$ sudo smartctl -a /dev/hda
smartctl version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Model Family: Hitachi Travelstar 80GN family
Device Model:
Please don't use the bug tracker for support.
For support you might want to use this thread :
http://ubuntuforums.org/showthread.php?t=591503
--
Hard drive spindown should be configurable
https://bugs.launchpad.net/bugs/17216
You received this bug notification because you are a member of Ubuntu
Noiano:
Unless you are helping in the bugfixing process itself, please use the
forums, and not the bugtracker. I'll respond to your question via
email, though. :-)
On Sat, 2007-11-03 at 19:09 +, Noiano wrote:
> Hello everybody
> I used the 99-hdd-spin-fix.sh method to save my hard drive wh
Hello everybody
I used the 99-hdd-spin-fix.sh method to save my hard drive which had reached
12838 cycles. I also copied 99-hdd-spin-fix.sh into battery.d, added the
"hdparm -B 255 /dev/hda" into /etc/rc.local and commented the evil line «
$HDPARM -B 1 /dev/$drive 2>/dev/null» in /etc/acpi/power
*Some drives use the 255 value for 'disabled'. But 254 is, in all
practical purposes, the same as having power management disabled, and
may even *be* the disabled setting for some disks -- namely, those which
are unaffected by the '255' setting (apparently because they are
following the spec).
Si
Re: Noatime, etc.
..why not just set APM to shut the disk off after two minutes of
inactivity? ..then, even if the disk unparks right after it parks, this
will at least happen few enough times to give 2/3 years of hd life
(assuming it was cycling all the time, which it wouldn't be, and
therefore
I can confirm that everything Claudio just said is true as I did the
same tests and got the same results with Debian/Ubuntu generating huge
load cycle counts compared to Windows running under the very same APM
setting (128). By the way I am running Fedora core 7 now and it does not
suffer from this
I would say the manpage of hdparm is wrong. On one of my laptops 255 doesn't
work (stays at 128) an on the other issuing 'hdparm -B 255 /dev/sda' results in
setting the value to 254.
But I am not sure that it is the right way to set it to anything other than
the default 128 - the temperature of
Same Load_Cycle_Count issue under Suse :
http://www.suseforums.net/index.php?showtopic=41458
--
Hard drive spindown should be configurable
https://bugs.launchpad.net/bugs/17216
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bu
Bruce Allen says that 254 should disable power management while the
behaviour of 255 is unpredictable. Strangely not only hdparm's man page
but also doing the command tells us that you should use 255 to disable
power management :
$ sudo hdparm -B 255 /dev/sda
/dev/sda:
setting Advanced Power Man
Regarding my last posts
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/17216/comments/62
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/17216/comments/63
You can experiment with values between 128 (low power usage) and 254
(best performance) although values below 254 stil
My hard drive (a Fujitsu) on a Dell laptop has default settings of 128 (at
least so hdparm reports) and spins down a lot if I don't alter the settings.
With settings of 254 or 255, it does no longer spin down.
On 11/2/07, ubuntu_demon <[EMAIL PROTECTED]> wrote:
>
> Regarding my last post : https:/
Regarding my last post : https://bugs.launchpad.net/ubuntu/+source/acpi-
support/+bug/17216/comments/62
So maybe Ubuntu should detect whether BIOS or laptop harddrive firmware
have set the drive to a power management setting below 128 and override
this and set it to 128 when on AC.
--
Hard drive
tferero received an email from Bruce Allen. For the whole story read :
http://www.linuxquestions.org/questions/showthread.php?p=2945630#post2945630
[quote=Bruce Allen]
I think that the -B value of 255 is incorrect. You should use 254 for
maximum performance. 255 IS DOCUMENTED AS 'RESERVED' IN THE
> lm-profiler is useless if you look at the disk light / load cycles. It
> does a lot of its own stuff with the disk, so the disk activity you're
> seeing is most probably caused by lm-profiler itself.
No, I was not running lm-profiler the second time around after I closed
kdpf and measured the lo
Christian Vogler wrote:
> Hum. I have noatime enabled, and as I mentioned in my (now disappeared)
> comment on bug 59695, this did not make a difference for me.
>
> Here is my lm-profiler output:
>
> Profiling run started.
> Write accesses at 72/600 in lm-profiler run: kpdf
> Write accesses at 34
Chris Moore napsal(a):
>> I vote for enabling noatime first. :-)
>
> The problem with that is that it disables atime. I find it very useful
> to know when files were most recently accessed. It really shouldn't be
> disabled by default either. I don't see why atime information has to be
> writte
Hum. I have noatime enabled, and as I mentioned in my (now disappeared)
comment on bug 59695, this did not make a difference for me.
Here is my lm-profiler output:
Profiling run started.
Write accesses at 72/600 in lm-profiler run: kpdf
Write accesses at 348/600 in lm-profiler run: kpdf
Read acce
> I vote for enabling noatime first. :-)
The problem with that is that it disables atime. I find it very useful
to know when files were most recently accessed. It really shouldn't be
disabled by default either. I don't see why atime information has to be
written to the disk instantaneously - if
Mark Thomas wrote:
> To Bart Samwel:
>
> If the laptop is idling, with no apps doing anything that requires the
> disk, then I expect the disk to park, then spin down and stay spun down.
> You are correct that dirty pages will get flushed out within 30s, but
> the point is that if the user is not
Mark Thomas napsal(a):
> We should find these daemons and applications (at least the ones in the
> standard ubuntu install) and fix them so they don't access the disk
> unnecessarily. Starter for ten: ACPID.
>
IMO in all Canonical-supported packages - all in main and resticted
repository sectio
To Bart Samwel:
If the laptop is idling, with no apps doing anything that requires the
disk, then I expect the disk to park, then spin down and stay spun down.
You are correct that dirty pages will get flushed out within 30s, but
the point is that if the user is not doing anything (or is doing
som
I made an error in a previous post :
https://bugs.launchpad.net/ubuntu/+source/acpi-
support/+bug/17216/comments/47
http://ubuntuforums.org/showpost.php?p=3671452&postcount=126
225 Load_Cycle_Count 0x0012 001 001 000 Old_age Always - 1387419
I wrote "age : newly aquired". I have now this informati
Brian Visel wrote:
> Any info written to the logs seems to be cached for approximately 30
> seconds, then written to disk. At this point, the disk unparks/spins up
> and then, by hw default, spins down a few seconds later, ostensibly to
> save hd life by keeping the heads off of the platter in cas
thunderbird and liferea also access the disk regularly. I wasn't using
these programs actively while creating this log.
I've used lm-profiler when on AC. I have 2 GB of ram and a swap use of
0.
Profiling run started.
Write accesses at 7/600 in lm-profiler run: thunderbird-bin
Wri
to technomaniac :
Please use this thread for support questions :
http://ubuntuforums.org/showthread.php?t=591503
Please do not reply to the bugreport for support questions.
Please do not use this bug as a forum but use the ubuntuforums thread instad.
--
Hard drive spindown should be configurabl
I get the following outputs
sudo smartctl --all /dev/sda | grep Load_Cycle_Count
193 Load_Cycle_Count0x0032 057 057 000Old_age Always
- 86786
and
sudo smartctl --all /dev/sda | grep Power-Off_Retract_Count
192 Power-Off_Retract_Count 0x0032 100 100 000Old_age
Generally speaking, though, it's better to have your disk never park or
spin down than to park and/or spin down, and unpark and/or spin up every
30 seconds. Increasing the power settings to be more 'performance'
oriented, in this case, would in most cases where this is occurring
drasticly increase
Some data acquired from ubuntuforums. These are just some people who
have recently posted their Load_Cycle_Count information and happen to
have a "WORST" value close to the "THRESHOLD" value. I will send these
people a PM to ask them to reply to this bug report with more
information.
http://ubuntu
I have combined all active threads about the "laptop harddrive
Load_Cycle_Count issue" on the ubuntuforums.
People who have support questions can ask them here :
http://ubuntuforums.org/showthread.php?t=591503
Should I encourage people who seem to be suffering from this problem and
have "WORST" v
Is the drive clicking associated with the drive spinning down? Then
maybe investigate the noatime (and maybe nodiratime) mount options.
I had the opposite problem where my drive wouldn't spin down and found
out that it was apparently because sync runs every few seconds, which
creates a need to wr
Christian Vogler commented in bug 31512 that his ACPID log doesn't seem
to grow but he still gets the bug, so there may be other logging
programs out there too.
I'm using Debian at work at the moment, so I can't write an exact how-
to. You can disable logging entirely by adding "-l /dev/null" to
Is there an easy workaround we can use to try disabling ACPID logging, so that
we can confirm if it is this or not?
(I.e. can you write a quick how-to, so that some of the people here can try it
out?)
--
Hard drive spindown should be configurable
https://bugs.launchpad.net/bugs/17216
You receiv
I've done some investigation, and I think the hard drive "killing" bug
that has been infamous lately is caused by bug 31512. See my comments
there for the rationale, but essentially the problem boils down to a
process writing to the disk once every 15 seconds or so (the actual
interval is probably
"Marki and Guy, thank you very much for all of the info.
I am in the middle of a research project and really do not have time to
look into all of this stuff (more than I already have), so I REALLY
appreciate the help."
No prob. Check if laptop mode is enabled (it most likely is not, unless
you e
Something to bear in mind as well:
smartmon does not always report SMART values as you might think.
Different values are stored in different ways by different
manufacturers.
Namely, if you do the smartctl check, wait for the click, and do it
again immediately after, you may find that the amount h
>>Sébastien, set -B 254 instead.
Thanks!
I will follow the story on ubuntuforums, now...
--
Hard drive spindown should be configurable
https://bugs.launchpad.net/bugs/17216
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
Sébastien, set -B 254 instead.
--
Hard drive spindown should be configurable
https://bugs.launchpad.net/bugs/17216
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubu
ubuntu_demon, sorry! I am new around here and did not know how this
system worked.
I will now head over to the links you provided.
Thank you, and again I appologize!
--
Hard drive spindown should be configurable
https://bugs.launchpad.net/bugs/17216
You received this bug notification because yo
Added Gentoo to the list as we have had the bug confirmed there. Does
anyone know where the gentoo bug tracker is, and if so, is there already
a bug there about this issue?
+1 Brian Visel (although, can you comment on this bug please, as all the
dups & auto-subscribes have been moved to this bug)
I don't get it.
my laptop : Toshiba Satellite SM30X
HDD: SAMSUNG HM160JC
output of
# hdparm -B 255 /dev/sda
/dev/sda:
setting Advanced Power Management level to disabled"
# while (true); do smartctl -a /dev/sda | grep 193; sleep 300; done
"
193 Load_Cycle_Count0x0012 092 092 000
** Also affects: gentoo
Importance: Undecided
Status: New
--
Hard drive spindown should be configurable
https://bugs.launchpad.net/bugs/17216
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bu
to Merton :
Harddrive manufacturers seem to claim most harddrives can handle at
least 600.000 Load_Cycles but this is probably an average under ideal
circumstances. My harddrive started to die slowly when at a
Load_Cycle_Count of 200.000.
Aiming for less than 200.000 Load_Cycles in three years me
On 10/31/07, Guy Van Sanden <[EMAIL PROTECTED]> wrote:
> The fixes in that bug report should work, as would using hdparm.conf
I think several different bugs must have been merged into one here.
hdparm doesn't fix the problem for me. I can use it to stop the disk
spinning down, and also to stop th
Guy, just out of curiously, how does one tell if the BIOS settings are
"sane"? I am just curious, because that would save me all the trouble.
I did notice people in the 59695 thread had ThinkPads and were having
issues, so I am assuming the worst case scenario (where I will have to
edit those few
Marki and Guy, thank you very much for all of the info.
I am in the middle of a research project and really do not have time to
look into all of this stuff (more than I already have), so I REALLY
appreciate the help.
My ThinkPad should be here within the next few weeks, so I am trying to
get ever
"Or does it mainly have to do with Ubuntu's way of managing drive power
on battery?
Concerning 59695:
Will enabling package laptop-mode-tools, and editting
/etc/laptop-mode/laptop-mode.conf, as suggested in the 59695 bug, work?"
Every distro or even OS that does not override the default settings
Verified on my Gentoo install too.
On 10/31/07, Merton <[EMAIL PROTECTED]> wrote:
> So if it is a BIOS setting, is any other distro of linux affected by
> this bug?
>
> Or does it mainly have to do with Ubuntu's way of managing drive power
> on battery?
>
> Concerning 59695:
> Will enabling packag
So if it is a BIOS setting, is any other distro of linux affected by
this bug?
Or does it mainly have to do with Ubuntu's way of managing drive power
on battery?
Concerning 59695:
Will enabling package laptop-mode-tools, and editting
/etc/laptop-mode/laptop-mode.conf, as suggested in the 59695 b
ubuntu_demon wrote:
> * laptop-mode should be less aggressive about power management (in the
> meantime you shouldn’t enable it)
That's not a fix. The problem is the BIOS defaults, not the special case
covered by laptop mode, which is *on battery*.
If you change laptop mode's defaults, you can
I want to make this clear again: There are no confirmed cases in which Ubuntu
caused this to happen.
The issue is that the BIOS has this insanely low setting which Ubuntu does not
modify.
It can be fixed in Ubuntu by overriding the BIOS default.
Again: LAPTOPS WITH A SANE SETTING IN THE BIOS
Opps, I forgot to add that my biggest concern is https://bugs.launchpad.net/bugs/59695";>bug 59695 I tried to
search to see if Ubuntu 7.10 fixed this issue, but had no luck
--
Hard drive spindown should be configurable
https://bugs.launchpad.net/bugs/17216
You received this bug notification beca
After reading a few threads about Ubuntu and all of the laptop hard
drive bugs, I am scared to install it on my brand new ThinkPad T61p.
Does anyone know if any of this has been fixed in the new version of
Ubuntu (7.10)? If not I will probably end up installing Gentoo, even
though I really like Ub
On 10/31/07, Brian Visel <[EMAIL PROTECTED]> wrote:
> > If I ran it every 2 seconds, the clicking stopped altogether.
>
> The clicking would stop in that case due to the hard disk never reaching
> a state of inactivity that was long enough to cause a park. The same
> thing would occur if you had a
> If I ran it every 2 seconds, the clicking stopped altogether.
The clicking would stop in that case due to the hard disk never reaching
a state of inactivity that was long enough to cause a park. The same
thing would occur if you had a script touch a file every 2 seconds, most
likely.
The more
> So, once an error occured, and in 12 minutes it increased by 16! This
does not look that good, doesn’t it?
You're reading that wrong. It doesn't mean "once an error occurred", it
means "once the seek_error_rate" counter contained the digit string
"193".
--
Hard drive spindown should be config
1 - 100 of 116 matches
Mail list logo
