Ticket #88 (closed defect: fixed)

Opened 6 years ago

Last modified 6 years ago

The bug called "Laptop Hardrive Killer Bug" seems to exist in Parsix 1.0

Reported by: ali.tarihi@… Owned by: parsix-devel@…
Priority: highest Component: Installer System
Version: 1.0 (ramon) Severity: critical
Keywords: Cc:

Description

I use Ubuntu 7.10 till now. In ubuntu there is a bug called "Laptop Hardrive Killer Bug" mentioned in https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/59695. It seems to exist in Parisix too. I used (http://ubuntudemon.wordpress.com/2007/10/28/laptop-hardrive-killer-bug-how-to-discover-whether-you-are-affected/_ as a guide and in less than 2 mins, the counter increased by 3. (Also I can hear the ticking sound of my disk!)
BTW I'm testing the solution given there.

Change History

comment:1 Changed 6 years ago by alan@…

Only some Hitachi and Samsung hard drives are affected.

vim /etc/default/hdparm, add the following lines:

harddisks="/dev/sda"
hdparm_opts="-B 254"

Restart hdparm service and make sure that's started every time on boot (Ramon starts hdparm by default). Change /dev/sda line to meet your needs.

comment:2 Changed 6 years ago by ali.tarihi@…

  • Status changed from new to closed
  • Resolution set to fixed

It worked, thx. I wonder if a script could be written to do the job. I mean the detection & fix.
My idea is this:
1) smartctl will be added to the default packages of Ramon
2) The Load_Cycle_Count is tested initially. The after a reasonable time it is tested agaian. If the difference is more than a value. The fix would be applied.

comment:3 Changed 6 years ago by ali.tarihi@…

  • Status changed from closed to reopened
  • Resolution fixed deleted

The fix seems to work with normal boot...

But after Suspend/Hibernate? the bug appears again. I think hdparm must be set again after hibernate/suspend.

comment:4 Changed 6 years ago by alan@…

  • Status changed from reopened to closed
  • Resolution set to fixed

I believe that this bug has been fixed in parsix-installer 0.82.1.0 package. If you think the problem still exists, feel free to reopen this bug.

comment:5 Changed 6 years ago by ali.tarihi@…

I've tested Voila r0& r1 for a month and can confirm that this bug has been perfectly fixed.
Thx

Note: See TracTickets for help on using tickets.