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 PROTECTED]> 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. > -- upgrading feisty to gutsy with software raid https://bugs.launchpad.net/bugs/162292 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
