Stephen Gran <sg...@debian.org> writes:
> This one time, at band camp, Goswin von Brederlow said:
>> In my case I have a SATA Port Multiplier, last one I ever buy :), and
>> it seems that takes a while to work after a boot. Sometimes its disks
>> just aren't there fast enough during boot and for example the fsck run
>> fails. I'm guessing the hdparm script fails too and then the raid
>> speed remains at 0.
s/fails/failed/
> Instead of guessing, would it be possible for you to debug this?
>
> Cheers,
Oh I did test it after boot by adding another entry that doesn't exist
and starting the script again. It exits prematurely. I'm only guessing
that, at the point the hdparm script did run during boot, the devices
weren't yet discovered by the kernel.
The last thing that happens is:
+ hdparm -S 120 /dev/sdl
/dev/sdl: No such file or directory
The problem seems to be in line 382 and the fix could be something like
this:
--- /etc/init.d/hdparm~ 2010-05-26 02:37:59.000000000 +0200
+++ /etc/init.d/hdparm 2010-05-26 02:46:12.000000000 +0200
@@ -15,7 +15,7 @@
@@ -379,9 +379,11 @@
;;
esac
else
- $KEY $SEP $VALUE
+ $KEY $SEP $VALUE || ret=$?
NEXT_LINE=no-go
WAS_RUN=1
+ log_progress_msg " $DISC"
+ log_end_msg $ret || true
fi
done
MfG
Goswin
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
