upgrading feisty to gutsy with software raid

Bug #162292 reported by Iwan on 2007-11-12
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Undecided
Unassigned

Bug Description

Installed Feisty on a software raid. I upgraded it using /cdromupgrade to Gutsy. Like in the previous 3 releases which I did not bother to report, the OS did not want to boot afterwards.
I have /dev/sda1 300G
/dev/sdb and c 80G in software raid
/dev/hda which is a CDROM
/dev/hdb which is a IDE disk.

If I install without disconnecting all but the RAID disks, I have trouble booting the system.
My /boot is on /dev/sdb1

I tried various boot disks to boot from in the BIOS, I tried various root configs in GRUB.

Let me know if there is more information I can provide.

Albert Damen (albrt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but a direct upgrade to gutsy is only supported from feisty, as is stated on http://www.ubuntu.com/getubuntu/upgrading
Therefore this does not appear to be a valid bug report and subsequently we are closing it. Feel free to submit any future bugs you may find.

Hi
I believe I got the names confused, but I ran the latest release
before Gutsy and upgraded it to Gutsy. I did not skip any distribution
upgrade in between, I therefore was running Feisty. The problem occurs
between all distribution upgrades for the last 4, 6 month cycles.

On 12/5/07, albert <email address hidden> wrote:
> Thank you for taking the time to report this bug and helping to make Ubuntu
> better. We appreciate the difficulties you are facing, but a direct upgrade
> to gutsy is only supported from feisty, as is stated on
> http://www.ubuntu.com/getubuntu/upgrading
> Therefore this does not appear to be a valid bug report and subsequently we
> are closing it. Feel free to submit any future bugs you may find.
>
> ** Changed in: ubuntu
> Status: New => Invalid
>
> --
> upgrading edgy 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.
>

Albert Damen (albrt) wrote :

OK, that explains. I have updated the title and description to read feisty instead of edgy.

description: updated
Brian Murray (brian-murray) wrote :

As I understand it your system was booting fine with GRUB installed to the mbr and then you upgraded to Gutsy using the cdromupgrade and your system would no longer boot. Is that correct?

If you are using grub as your bootloader - could you please add the contents of your '/boot/grub/menu.lst' file as an attachment? It might also be quite helpful if you have a copy of the one the cdromupgrade process made. Thanks in advance.

Changed in linux-source-2.6.22:
assignee: nobody → brian-murray
status: New → Incomplete

Hi
I don't have that broken list anymore, as I reinstalled a clean
system. What I remember from the menu.lst is that pointing it to the
correct drive root=whatever did not solve the problem. I think the
problem may be grub's menu.lst but it may also be related to initrd
not loading the raid module drivers. Am working in a new job now and I
haven't really tinkered with Linux since Slackware days, but at that
time it looked like a grub error. I think the best way to test it is
to setup a raid with the older Ubuntu and then to cdromupgrade it.

On 1/9/08, Brian Murray <email address hidden> wrote:
> As I understand it your system was booting fine with GRUB installed to
> the mbr and then you upgraded to Gutsy using the cdromupgrade and your
> system would no longer boot. Is that correct?
>
> If you are using grub as your bootloader - could you please add the
> contents of your '/boot/grub/menu.lst' file as an attachment? It might
> also be quite helpful if you have a copy of the one the cdromupgrade
> process made. Thanks in advance.
>
> ** Changed in: linux-source-2.6.22 (Ubuntu)
> Assignee: (unassigned) => Brian Murray (brian-murray)
> Status: New => Incomplete
>
> --
> 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.
>

Changed in linux-source-2.6.22:
assignee: brian-murray → nobody

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

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.

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.
>

Michele Mangili (mangilimic) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers