This problem is still there under ubuntu Hardy 8.04 (LTS... but with present settings, my HD will not last 3 years!).
I've a brand new HDD, a WD scorpio 320Gb. Hardy hdparm -B defaults to 128 even on AC power, leading this drive to have heads parked/unparked every minutes. 600000 minutes average lifetime is about 1 year.
Please fix this. Note that I reinstalled from live-CD. previously I was running Dapper (6.06) and never experimented such behaviour.
There is a lot of duplicates of this bug since more than one year now, which is currently read by in charge teams?
The result is we can expect a lot of HDD starting to dead now and furious users that will never run ubuntu or even Linux anymore. So why such a poor reactivity for this critical problem? Having them coming back in mass to Redmond? Shit...
Please also note that common fixes (99* shell scripts in various /etc/acpi/*.d) does not survive restoring from a suspend to ram: acpid seems to override scripts settings after script execution (or do not execute them at all?). This is the behaviour of current 2.6.24 hardy kernel.
A small Heron being "hardy"... I should have been careful. Next is "intrepid" ibex? Holly shit, what must be expected from this "intrepid" one? Machine burning after install?
This problem is still there under ubuntu Hardy 8.04 (LTS... but with present settings, my HD will not last 3 years!).
I've a brand new HDD, a WD scorpio 320Gb. Hardy hdparm -B defaults to 128 even on AC power, leading this drive to have heads parked/unparked every minutes. 600000 minutes average lifetime is about 1 year.
Please fix this. Note that I reinstalled from live-CD. previously I was running Dapper (6.06) and never experimented such behaviour.
There is a lot of duplicates of this bug since more than one year now, which is currently read by in charge teams?
The result is we can expect a lot of HDD starting to dead now and furious users that will never run ubuntu or even Linux anymore. So why such a poor reactivity for this critical problem? Having them coming back in mass to Redmond? Shit...
Please also note that common fixes (99* shell scripts in various /etc/acpi/*.d) does not survive restoring from a suspend to ram: acpid seems to override scripts settings after script execution (or do not execute them at all?). This is the behaviour of current 2.6.24 hardy kernel.
A small Heron being "hardy"... I should have been careful. Next is "intrepid" ibex? Holly shit, what must be expected from this "intrepid" one? Machine burning after install?
Regards