[Bug 631795] Re: [MAVERICK] fails to boot after install on dmraid set
update: After a couple of 'recovery - repair broken packages - reboot' sessions I have the system booting reasonably well, most of the time. So I'm changing the bug title from 'fails to boot' to 'does not boot reliably'. I still see errors from udevd about not being able to find dm-6. Also Grub-pc refusing to find my dmraid partitions blocks me from finishing installing updates to the kernel of adding any new kernel. cheers Tom ** Summary changed: - [MAVERICK] fails to boot after install on dmraid set + [MAVERICK] does not boot reliably after install on dmraid set -- [MAVERICK] does not boot reliably after install on dmraid set https://bugs.launchpad.net/bugs/631795 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 631795] Re: [MAVERICK] fails to boot after install on dmraid set
hi Jeremy, Got the latest mainline kernels and tried installing them. Unfortunately I running into a bug with Grub that prevents me to update it. See LP 634840. So I cannot test new kernels until I get Grub to boot off them. Sorry. cheers Tom -- [MAVERICK] fails to boot after install on dmraid set https://bugs.launchpad.net/bugs/631795 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 631795] Re: [MAVERICK] fails to boot after install on dmraid set
OK, here's what I did. Managed to get the system running by doing a rescue from the alternate install CD. Dropped into a root session, installed as much packages from ubuntu-desktop by hand (several attempts) and rebooted. At first I got the same errors, but to my surprise when I left it standing for a while, it got on with a reasonably normal boot and a X/Gnome login. Had to go back to the CD and re-add myself as user. Could log on then, but with no sudo or other rights. Back to the CD and added myself to sudoers and admin group. This was all on kernel 2.6.35.19. Yesterday I saw kernel 2.6.35.20. arrive. Updated, rebooted and found that it wouldn't boot. Lots of errors on udev and the kernel disagreeing about devices called dm-5, dm-2 etc ,then busibox from initramfs. So rebooted with 2.6.35.19 which worked. This morning there was an update to udev, which rang a bell with this bug (I thought). Installed it, rebooted 2.6.25.19, all fine. Decided to reinstall 2.6.35.20, in order to force update-initramfs on that kernel as well. Install didn't really work out without errors, but could boot kernel 2.6.35.20. In fact running it right now. Apart from the kernel install failing partly, update-grub starts complaining now as well about not being able to find its devices: tho...@tomdesktop:~$ sudo update-grub [sudo] password for thomas: Generating grub.cfg ... /usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/mapper/pdc_jcchiiab5. Check your device.map. I can not really reproduce this error, and I'm not sure whether it's the kernel, udev, dmraid or grub that's not working well, or all of them not playing nice. I do know however that booting off a dmraid set has been very broken since 10.04 (which is a LTS). I'll be checking on this whenever I feel I see something relevant, and do my updates twice a day. I'll try the latest kernel some time next weekend and report on that. If there's anything else, like more log files, let me know. cheers Tom -- [MAVERICK] fails to boot after install on dmraid set https://bugs.launchpad.net/bugs/631795 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 631795] Re: [MAVERICK] fails to boot after install on dmraid set
apport information ** Tags added: apport-collected ** Description changed: Binary package hint: dmraid hi After *a lot* of troubles with Gparted and Grub / Grub-install, I managed to install Maverick Beta from an Alternative CD (iso image dated 05 sept 2010). This is a system with Promise Fasttrack fakeraid, booting off 2 disks in striped mode. It's dual boot with XP. When booting I see a lot of error messages that indicate a mismatch in the naming of partitions between dmraid and the kernel. It seems one is using the /dev/mapper/pdc_jcchiiab5 convention, while the other uses dm-5. After a while it does boot, but as it does not mount /home on /dev/mapper/pdc_jcchiiab6, I can not log on. I tried going into recovery mode, dropping into a root session on the right partition, mounting /home and then doing an update-initramfs -u to see if that would restore the right device names for my / and /home. It did not work, so I'm not enjoying Maverick yet :-( I'm linking this bug to the package linux as well, since I believe it is an issue between dmraid and the kernel. If there is more information I should collect, please tell me what you need, and give me some hints on how to get them. My CLI and debug skills are limited. cheers Tom + --- + Architecture: i386 + DistroRelease: Ubuntu 10.10 + Frequency: Once a day. + InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100905) + Package: linux 2.6.35.20.21 + PackageArchitecture: i386 + ProcEnviron: + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4 + Regression: Yes + Reproducible: No + Tags: maverick kernel-config regression-potential needs-upstream-testing + Uname: Linux 2.6.35-20-generic i686 + UserGroups: admin lpadmin ** Attachment added: "Dependencies.txt" https://bugs.edge.launchpad.net/bugs/631795/+attachment/1561969/+files/Dependencies.txt ** Description changed: Binary package hint: dmraid hi After *a lot* of troubles with Gparted and Grub / Grub-install, I managed to install Maverick Beta from an Alternative CD (iso image dated 05 sept 2010). This is a system with Promise Fasttrack fakeraid, booting off 2 disks in striped mode. It's dual boot with XP. When booting I see a lot of error messages that indicate a mismatch in the naming of partitions between dmraid and the kernel. It seems one is using the /dev/mapper/pdc_jcchiiab5 convention, while the other uses dm-5. After a while it does boot, but as it does not mount /home on /dev/mapper/pdc_jcchiiab6, I can not log on. I tried going into recovery mode, dropping into a root session on the right partition, mounting /home and then doing an update-initramfs -u to see if that would restore the right device names for my / and /home. It did not work, so I'm not enjoying Maverick yet :-( I'm linking this bug to the package linux as well, since I believe it is an issue between dmraid and the kernel. If there is more information I should collect, please tell me what you need, and give me some hints on how to get them. My CLI and debug skills are limited. cheers Tom --- Architecture: i386 DistroRelease: Ubuntu 10.10 Frequency: Once a day. InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100905) Package: linux 2.6.35.20.21 PackageArchitecture: i386 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4 Regression: Yes Reproducible: No Tags: maverick kernel-config regression-potential needs-upstream-testing Uname: Linux 2.6.35-20-generic i686 UserGroups: admin lpadmin + + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. + Architecture: i386 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: thomas 1440 F pulseaudio + CRDA: Error: [Errno 2] No such file or directory + Card0.Amixer.info: + Card hw:0 'V8233Pre'/'VIA 8233-Pre with ALC200,200P at 0xd400, irq 11' +Mixer name : 'Realtek ALC200,200P rev 0' +Components : 'AC97a:414c4710' +Controls : 44 +Simple ctrls : 26 + DistroRelease: Ubuntu 10.10 + Frequency: Once a day. + HibernationDevice: RESUME=UUID=b17395f5-231b-44d2-b86d-3c2f867ac46c + InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100905) + IwConfig: + lono wireless extensions. + + eth0 no wireless extensions. + MachineType: MSI MS-6380 + Package: linux 2.6.35.20.21 + PackageArchitecture: i386 + ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-20-generic root=UUID=6fbcfa16-341a-4ad0-939f-7ff9933cfe3f ro quiet splash + ProcEnviron: + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4 + Regression: Yes + RelatedPackageVersions: linux-firmware 1.38 + Reproducible: No + RfKill: + + Tags: maverick kernel-config regression-potential needs-upstream-te
[Bug 631795] Re: [MAVERICK] fails to boot after install on dmraid set
Hi Tom, Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . If the issue remains, please 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 631795 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 -- [MAVERICK] fails to boot after install on dmraid set https://bugs.launchpad.net/bugs/631795 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
