hdparm 5.3-r2 The /etc/init.d/hdparm should skip ataraid discs, as these are RAID arrays. I.E. on my machine, hdparm init scripts tries to apply settings on these discs: ls -l /dev/discs/ total 0 ... disc0 -> ../ide/host2/bus0/target0/lun0 ... disc1 -> ../ide/host2/bus1/target0/lun0 ... disc2 -> ../ataraid/disc0 hdparm init script fails on disc2. I guess it could be easy to add a grep for ataraid in the function checkconfig(). Thanks, -- Arno. Reproducible: Always Steps to Reproduce: 1. 2. 3.
nagash you wanna pick this one up and run with it?
Yeh sure. Sorry for my tardiness. I kept asking you on IRC. :>
Created attachment 9193 [details] /etc/init.d/hdparm -- ATARAID changes. Works fine, maybe some aesthetic issues seth, I'll leave that for you to decide. (It says "Skipping cdrom1..." if $all_args is specified OR $cdrom1_args is specified.) I thought it might be a good idea to let the user know that hdparm isn't being run on that drive, otherwise people might assume it is (when using $all_args)
OK, this is in 5.3-r2
oops. OK, why doesn't the hdparm script just scan for "ide" in the /dev/discs/ directory rather than scanning for "scsi" and *not* handling those?
No reason I guess, besides I just didnt think of it :)
I'll change it and upload tomorrow.
Created attachment 10051 [details] hdparm rc-script -- grep ide (changes proposed by drobbins) All done, works fine on my machine.
Created attachment 10362 [details] hdparm rc-script v2 -- changes proposed by drobbins Another version, this one uses an ewarn to inform the user that hdparm will not be a run on a device (when it is found not to be an IDE device) Eg. v1 Output.. * Starting hdparm... * Running hdparm on disc0... [ ok ] * Running hdparm on disc1... [ ok ] v2 Output.. * Starting hdparm... * Skipping cdrom0, hdparm only supports IDE devices! * Running hdparm on disc0... [ ok ] * Running hdparm on disc1... [ ok ] No other changes from v1.
Created attachment 10500 [details] hdparm rc-script v3.. more changes asked for by drobbins :> IMHO this one looks like an ugly hack :> I'm not a bash genius, so I'm sure theres many easier ways to do it, but ah well, here it is.
Created attachment 10534 [details] v4.. Sorry, v3 had a small error =\
can you take a look at bug 37755 if that fixes your problem
fixed with bug #37755