Comment 8 for bug 162292

This is not really applicable as it is the installation which is the
problem. I moved away from Ubuntu because of this very bug, unsolved
now every release since the 1st Ubuntu. Installing Ubuntu to an
existing software raid (containing only /home) doesn't work. The grub
installer bombs out, does not accept "trust me" and leaves me with a
broken unbootable system, if only it did continue at the user's
discretion a bootup CD might have done the trick to fix it.
Another reason why I don't use Ubuntu anymore is that the installtion
will bomb out if a package like OpenOffice doesn't install. I mean
WTH?! If the rest of the installation continued I could have done an
apt-get to fix the system.

On 8/29/08, Leann Ogasawara <email address hidden> wrote:
> The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
> upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
> appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
> There are one of two ways you should be able to test:
>
> 1) If you are comfortable installing packages on your own, the linux-
> image-2.6.27-* package is currently available for you to install and
> test.
>
> --or--
>
> 2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer
> 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4.
> Please watch http://www.ubuntu.com/testing for Alpha5 to be announced.
> You should then be able to test via a LiveCD.
>
> Please let us know immediately if this newer 2.6.27 kernel resolves the
> bug reported here or if the issue remains. More importantly, please
> open a new bug report for each new bug/regression introduced by the
> 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please
> specifically note if the issue does or does not appear in the 2.6.26
> kernel. Thanks again, we really appreicate your help and feedback.
>
> ** Tags added: cft-2.6.27
>
> --
> upgrading feisty to gutsy with software raid
> https://bugs.launchpad.net/bugs/162292
> You received this bug notification because you are a direct subscriber
> of the bug.
>