Well, "Invalid" appears to be the proper resolution.
** Changed in: hdparm (Ubuntu)
Status: Fix Released => Invalid
--
hdparm apparently not run during boot
https://bugs.launchpad.net/bugs/46414
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
I'm marking this "Fix Released".
If you are running into this, make sure you are not using "sata" drives (i.e.
sd[a-z]); that would be bug 156893.
** Changed in: hdparm (Ubuntu)
Status: Incomplete => Fix Released
--
hdparm apparently not run during boot
https://bugs.launchpad.net/bugs/46
BeSt, any chance you have /dev/sdX drives? Then this may be bug 156893.
Can you please try the patch linked there and report back (over there is
preferred I think), if it solves your problem? You should remove the
hdparm init script before, of course ("sudo update-rc.d hdparm remove").
--
hdparm
On Thu, 2007-10-25 at 00:12 +, dAniel hAhler wrote:
> Is this problem still existent in Gutsy?
As far as I can tell, the problem doesn't seem to exist anymore. The
error messages I previously posted were apparently caused by a failing
disk.
--
Bye,
-Torsten
--
hdparm apparently not run du
I had a problem in Feisty (still present in Gutsy): my /etc/hdparm/hdparm.conf
wasn't executed at startup. I had to do
sudo update-rc.d hdparm defaults
to make /etc/init.d/hdparm be run at each startup. Don't know if it's a bug,
but when there is a file called /etc/hdparm/hdparm.conf, I expect it
Is this problem still existent in Gutsy?
** Changed in: hdparm (Ubuntu)
Status: New => Incomplete
--
hdparm apparently not run during boot
https://bugs.launchpad.net/bugs/46414
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
u
Here's the relevant output of dmesg after a boot which failed to set the
dma flag on /dev/hda. All other settings on hda and all settings on hdb
were applied correctly.
[17179608.932000] hda: dma_timer_expiry: dma status == 0x60
[17179608.932000] hda: DMA timeout retry
[17179608.932000] hda: time
I'm also occasionally seeing this on Edgy. About one out of every 10
boots will result in one (or less often both) of my hard drives not
having DMA turned on (/etc/hdparm.conf had -d1 for both), and very
occasionally one will have multcount set wrong (/etc/hdparm.conf has
-m16).
As with Torsten's
While the above now seems to work ok, I am now seeing another problem.
Sometimes, some settings are not applied. For example, sometimes after
boot, one of my disks doesn't have the dma flag set even though that
setting is listed in hdparm.conf. At other times, one disk has none of
the settings ap
