Comment 3 for bug 294747

Actually what fixed it was to change the grub boot timeout [not exactly
sure what the actual variable name was] to a pretty large number. Looks
like my old laptop sata drive just wasn't mounting fast enough and
needed some extra time, if I remember right I had to crank the number
pretty high.

Probably not too likely to see that happen in a more modern system. My
lappy was an old 2ghz Pentium 4 with 512 ram and a hard drive from who
knows where, not exactly zippy by any means. I however have got rid of
my old laptop and built a new system and haven't even run into the
problem again.

rage9

kernel-janitor wrote:
> Hi rage9,
>
> This bug was reported a while ago and there hasn't been any activity in
> it recently. We were wondering if this is still an issue? Can you try
> with the latest development release of Ubuntu? ISO CD images are
> available from http://cdimage.ubuntu.com/releases/karmic .
>
> If it remains an issue, could you run the following command from a
> Terminal (Applications->Accessories->Terminal). It will automatically
> gather and attach updated debug information to this report.
>
> apport-collect -p linux 294747
>
> Also, if you could test the latest upstream kernel available that would
> be great. It will allow additional upstream developers to examine the
> issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once
> you've tested the upstream kernel, please remove the 'needs-upstream-
> testing' tag. This can be done by clicking on the yellow pencil icon
> next to the tag located at the bottom of the bug description and
> deleting the 'needs-upstream-testing' text. Please let us know your
> results.
>
> Thanks in advance.
>
> [This is an automated message. Apologies if it has reached you
> inappropriately; please just reply to this message indicating so.]
>
>
> ** Tags added: needs-kernel-logs
>
> ** Tags added: needs-upstream-testing
>
> ** Tags added: kj-triage
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
>