On 06/09/2011 12:48 PM, Chris Lalancette wrote:
On 06/09/11 - 07:53:55AM, Steven Dake wrote:
> On 06/09/2011 05:18 AM, Chris Lalancette wrote:
>> On 06/08/11 - 09:25:48PM, Steven Dake wrote:
>>> The default 300 second timer is insufficient to install RHEL6.1 on a W510
>>> laptop. When the installation terminates with the 300 second default, the
>>> install.img file is only 70% read from disk on this system.
>> Hm, can you be a bit more clear here? Is this still during the initial
>> anaconda stage where it is reading the install.img from the CD-ROM? If that is
>> the case, I might suggest that instead of increasing the timeout, we also
>> monitor the CD device for activity. That is, if either the diskimage or the
>> CD-ROM has activity, we continue waiting.
> yes it is during the anaconda load of the image. Your proposal makes
> sense - I was going to take a crack at making something like that, but
> didn't really have any idea how to do that :) As is today the value is
> too low though.
Here's the problem with increasing the timeout:
The whole reason I introduced this extra complexity was to reduce the amount
of time people needed to wait on a failed instance (think crashed kernel,
installer, etc). If we bump this timeout to 1000, we've eliminated most of
that usefulness and we might as well just remove the complexity and drop back
to a standard timeout.
Before doing that, though, I think I would like to try watching the CD-ROM for
activity. If that does the trick, I'd much rather go that route than
increasing the timeout.
I'll whip up a patch for you to test tomorrow.
sounds good i'm happy to test it out.