You are not logged in.
I am not sure if Automatic Acoustic Management (AAM) is even possible; I've read rumours that it is not really implemented, despite what is reported by S.M.A.R.T.
Anyway, in order to possibly reduce the noise from my computer I tried this command:
$ hdparm -M 192 /dev/sda
/dev/sda:
setting acoustic management to 192
HDIO_DRIVE_CMD:ACOUSTIC failed: Bad address
HDIO_DRIVE_CMD(identify) failed: Bad address
$ hdparm -M 128 /dev/sdc
/dev/sdc:
setting acoustic management to 128
HDIO_DRIVE_CMD:ACOUSTIC failed: Bad address
HDIO_DRIVE_CMD(identify) failed: Bad address
$
***
S.M.A.R.T., via 'hdparm -I', recommends the above values for the two disks.
Am I using a bad command, or is there another explanation for the "Bad address" message?
Last edited by whaler (2009-02-02 20:17:50)
Offline
I don't know why you get those messages, but it is the right command, and it does make a difference (less vibrations).
Offline
I don't know why you get those messages, but it is the right command, and it does make a difference (less vibrations).
Thanks. At least I seem to be on the right track... I might add that this is on an AMD Athlon64 system with a Gigabyte MB and what I would consider a vanilla setup - i.e. the disks in question are ordinary PATA disks. Strange.
Edit: I was on the wrong track entirely: I had given the command as user, not as root. Given as root, the response is the following:
bash-3.2# hdparm -M 192 /dev/sda
/dev/sda:
setting acoustic management to 192
acoustic = 192 (128=quiet ... 254=fast)
***
Sorry for this silliness...
Last edited by whaler (2009-02-02 20:16:59)
Offline