<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>hard-drive</title>
  <link rel="alternate" type="text/html" href="http://tumbleweed.org.za/tags/hard-drive"/>
  <link rel="self" type="application/atom+xml" href="http://tumbleweed.org.za/taxonomy/term/122/atom/feed"/>
  <id>http://tumbleweed.org.za/taxonomy/term/122/atom/feed</id>
  <updated>2008-09-19T07:53:26+00:00</updated>
  <entry>
    <title>An update on Laptop Hard Drives &amp; Linux</title>
    <link rel="alternate" type="text/html" href="http://tumbleweed.org.za/2007/10/27/an-update-on-laptop-hard-drives-linux" />
    <id>http://tumbleweed.org.za/2007/10/27/an-update-on-laptop-hard-drives-linux</id>
    <published>2007-10-27T08:11:31+00:00</published>
    <updated>2008-01-02T19:55:15+00:00</updated>
    <author>
      <name>tumbleweed</name>
    </author>
    <category term="apm" />
    <category term="hard-drive" />
    <category term="hardware" />
    <category term="laptop" />
    <category term="linux" />
    <category term="ubuntu" />
    <summary type="html"><![CDATA[<p>Launchpad <a href="https://bugs.launchpad.net/bugs/59695">bug 59695</a> has been gathering a <em>huge</em> amount of activity since I wrote about this issue. The issue seems to be that the hardware manufacturers (<span class="caps"><span class="caps">BIOS</span></span> and <span class="caps"><span class="caps">HDD</span></span> firmware) set <em>very</em> aggressive values for power management. And every other <span class="caps"><span class="caps">OS</span></span> (Windows <span class="amp">&amp;</span> Mac <span class="caps"><span class="caps">OSX</span></span>) override these values to something more sane. The manufacturers only test their equipment in Windows, so they don&#8217;t see any&nbsp;problems&nbsp;:-)</p>

<p>This kind of thing seems to happen to Linux quite regularly - we all remember the <span class="caps"><span class="caps">ACPI</span></span> debacle caused by manufacturers using Microsoft&#8217;s broken <span class="caps"><span class="caps">ASL</span></span> compiler, which worked in Microsoft&#8217;s broken <span class="caps"><span class="caps">ACPI</span></span> environment (or was overridden with&nbsp;driver&nbsp;updates).</p>

<p>So in my opinion, Ubuntu (and every other distributor) has to step in and override these aggressive settings. And, by the look of the bug report, Gnome Power Manager should provide the user with a slider to set the balance between power savings and&nbsp;hardware&nbsp;lifetime.</p>

<p>There is already the obligatory <a href="http://ubuntuiskillingyourhd.blogspot.com/">ubuntu is killing your Hard Drive blog</a>, and a <a href="http://ubuntuforums.org/showthread.php?t=508576">closed for cooling off Ubuntu forums thread</a>, if you want get involved and start swinging&nbsp;your&nbsp;battle-axe.</p>

<p>Oh, and the workaround I posted last week obviously doesn&#8217;t cover the case of the machine resuming from suspend. You have to use an <span class="caps"><span class="caps">ACPI</span></span> event script&nbsp;for&nbsp;that.</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>Launchpad <a href="https://bugs.launchpad.net/bugs/59695">bug 59695</a> has been gathering a <em>huge</em> amount of activity since I wrote about this issue. The issue seems to be that the hardware manufacturers (<span class="caps">BIOS</span> and <span class="caps">HDD</span> firmware) set <em>very</em> aggressive values for power management. And every other <span class="caps">OS</span> (Windows <span class="amp">&amp;</span> Mac <span class="caps">OSX</span>) override these values to something more sane. The manufacturers only test their equipment in Windows, so they don&#8217;t see any problems&nbsp;:-)</p>

<p>This kind of thing seems to happen to Linux quite regularly - we all remember the <span class="caps">ACPI</span> debacle caused by manufacturers using Microsoft&#8217;s broken <span class="caps">ASL</span> compiler, which worked in Microsoft&#8217;s broken <span class="caps">ACPI</span> environment (or was overridden with driver&nbsp;updates).</p>

<p>So in my opinion, Ubuntu (and every other distributor) has to step in and override these aggressive settings. And, by the look of the bug report, Gnome Power Manager should provide the user with a slider to set the balance between power savings and hardware&nbsp;lifetime.</p>

<p>There is already the obligatory <a href="http://ubuntuiskillingyourhd.blogspot.com/">ubuntu is killing your Hard Drive blog</a>, and a <a href="http://ubuntuforums.org/showthread.php?t=508576">closed for cooling off Ubuntu forums thread</a>, if you want get involved and start swinging your&nbsp;battle-axe.</p>

<p>Oh, and the workaround I posted last week obviously doesn&#8217;t cover the case of the machine resuming from suspend. You have to use an <span class="caps">ACPI</span> event script for&nbsp;that.</p>
    ]]></content>
  </entry>
  <entry>
    <title>A serious warning to Linux Laptop users</title>
    <link rel="alternate" type="text/html" href="http://tumbleweed.org.za/2007/10/23/a-serious-warning-to-linux-laptop-users" />
    <id>http://tumbleweed.org.za/2007/10/23/a-serious-warning-to-linux-laptop-users</id>
    <published>2007-10-22T21:15:22+00:00</published>
    <updated>2008-09-19T07:53:26+00:00</updated>
    <author>
      <name>tumbleweed</name>
    </author>
    <category term="apm" />
    <category term="hard-drive" />
    <category term="hardware" />
    <category term="laptop" />
    <category term="linux" />
    <category term="ubuntu" />
    <summary type="html"><![CDATA[<p>I&#8217;ve just come across a rather scary, and worryingly old <a href="https://bugs.launchpad.net/bugs/59695">launchpad bug</a>, which talks about real hardware damage. There is more on the problem <a href="http://paul.luon.net/journal/hacking/BrokenHDDs.html">here</a>. But basically, by default, Linux is far too optimistic with spinning laptop hard drives down, and you can reach number of spin-up/downs that your drive is rated for over it&#8217;s entire life-time, in a&nbsp;few&nbsp;months.</p>

<p>My laptop (3 months old), is already at 160000 Load/Unloads: Around half it&#8217;s&nbsp;rated&nbsp;life.</p>

<p>The easy&nbsp;solution&nbsp;is</p>

<div class="geshifilter"><div class="text geshifilter-text" style="font-family:monospace;"># hdparm -B 180 /dev/sda</div></div>

<p>Or, the following&nbsp;in&nbsp;/etc/hdparm.conf</p>

<div class="geshifilter"><div class="css geshifilter-css" style="font-family:monospace;">/dev/sda <span class="br0">&#123;</span><br />
&nbsp; &nbsp; apm <span class="sy0">=</span> <span class="nu0">180</span><br />
<span class="br0">&#125;</span></div></div>

<p>Lets hope that this gets resolved soon, or the problem isn&#8217;t as bad as&nbsp;it&nbsp;appears.</p>

<p>I see that Matthew Garrett (the Ubuntu Laptop Tzar) is subscribed to this bug, but doesn&#8217;t seem to have commented on it. I find that a little odd, considering&nbsp;its&nbsp;seriousness.</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>I&#8217;ve just come across a rather scary, and worryingly old <a href="https://bugs.launchpad.net/bugs/59695">launchpad bug</a>, which talks about real hardware damage. There is more on the problem <a href="http://paul.luon.net/journal/hacking/BrokenHDDs.html">here</a>. But basically, by default, Linux is far too optimistic with spinning laptop hard drives down, and you can reach number of spin-up/downs that your drive is rated for over it&#8217;s entire life-time, in a few&nbsp;months.</p>

<p>My laptop (3 months old), is already at 160000 Load/Unloads: Around half it&#8217;s rated&nbsp;life.</p>

<p>The easy solution&nbsp;is</p>

<div class="geshifilter"><div class="text geshifilter-text" style="font-family:monospace;"># hdparm -B 180 /dev/sda</div></div>

<p>Or, the following in&nbsp;/etc/hdparm.conf</p>

<div class="geshifilter"><div class="css geshifilter-css" style="font-family:monospace;">/dev/sda <span class="br0">&#123;</span><br />
&nbsp; &nbsp; apm <span class="sy0">=</span> <span class="nu0">180</span><br />
<span class="br0">&#125;</span></div></div>

<p>Lets hope that this gets resolved soon, or the problem isn&#8217;t as bad as it&nbsp;appears.</p>

<p>I see that Matthew Garrett (the Ubuntu Laptop Tzar) is subscribed to this bug, but doesn&#8217;t seem to have commented on it. I find that a little odd, considering its&nbsp;seriousness.</p>
    ]]></content>
  </entry>
</feed>
