On Wednesday 05 November 2008, Allen Weiner wrote: > Thanks very much for your reply. If it performed as intended, the > solution I took from "Knoppix Hacks" installed the GRUB stage 1 from a > Knoppix v5.1.1 live-CD and installed it in Ubuntuu's boot sector on > (hd1,7) AKA hdb8. Under Knoppix I issued sudo grub-install > --root-directory=/mnt/hdb8 /dev/hdb8. GRUB stage 1.5 and stage 2 should > have also been installed by grub-install.. > > The solution seems to partially work. I get a second GRUB menu with a > selection of three Ubuntu kernels. But booting each of these three > kernels hangs in the same place far into the Ubuntu boot, and I have no > idea why.
Well, you mentioned it hung at "Uniform CD-ROM driver Revision 3.20", but that doesn't tell me much; it means that Grub found the kernel and started to boot it, but something goes wrong during bootup. Is the kernel finding the root partition? Hopefully there's some way you can boot up in text mode so that you can see the kernel messages during bootup. But just thinking about this, the next thing to examine is the entries in the GRUB menu. Examine each one of the "kernel=" lines for each one of the menu items in /boot/grub/menu.lst on the partition where Ubuntu is installed, and specifically look at the value for "root=UUID=<long string>". (Ubuntu typically uses a filesystem UUID rather than a hard-coded partition for the "root=" parameter.) If you want to verify the partition's UUID, assuming you used ext2 or ext3, you can check it with 'tune2fs -l <device>'. (Where 'device' is something like '/dev/hda2', '/dev/sda2', etc.) If you used a filesystem other than ext2/3 then there is probably another filesystem-specific tool to check the filesystem's UUID. (For instance, for XFS this can be done with 'xfs_admin -u <device>') If the above isn't the problem, the next suggestion is to boot up with your Knoppix CD, mount Ubuntu's /var (which is probably under the root "/" filesystem), and then to examine /var/log/kern.log which may tell you why the bootup is hanging. Specifically look in the kern.log to see if it's mounting the root filesystem, and check the date/time of the log to make sure that it's for the boot you just tried. > > I'm running GAG now -- for the same reason -- and find it easy to > > install and use. I wasn't thrilled at having to go through two > > boot menus in order to boot Linux at first, but I got used to it. > > Thanks very much for the suggestion. This is worthy of future > consideration. But first, I'd like to try to get a handle on why my > current solution isn't working. > > Actually, I'm surprised you are using a multiboot setup. I thought the > MHVLUG regulars would be using virtual machines (Vmware, KVM). I'm also running virtual machines, but that's for a different purpose. I'm currently running VMs in VirtualBox, but I'm not finding that very useful because getting VirtualBox to allocate an independent LAN IP to each VM is not straightforward. This is something that VMware Workstation did well back when I last used it several years ago. I haven't yet run KVM or Xen to compare this aspect. -- Chris -- Chris Knadle [EMAIL PROTECTED] _______________________________________________ Mid-Hudson Valley Linux Users Group http://mhvlug.org http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug Upcoming Meetings (6pm - 8pm) MHVLS Auditorium Sep 3 - Porkchop - The Areas of My Expertise Oct 1 - Ubikeys Oct 4 - Linux Fest Nov 5 - Releasing Open Source Software Dec 3 - TBD
