From: BitTwister@mouse-potato.com   
      
   On Mon, 23 Jul 2012 09:56:04 -0600, Warren Post wrote:   
   >   
   > and I take it for granted   
   > that on any new distro I'll be tweaking the bootloader and a whole lot   
   > more besides. What does worry me is that my whole strategy of testing   
   > distros without putting my production distro at risk is obviously flawed.   
   > What should I do differently the next time I install a distro for testing?   
      
   Use VirtualBox for testing.  :-D   
      
   I can only guess your new install chain loads the old install's grub.   
   Those do not know about the new partition which might have caused   
   renumbering of partitions.   
      
   If nothing else you should be able to add a Production stanza to the   
   new grub with the correct drive,partition for vmlinuz,initrd.   
      
   Example:   
      
   title Production   
   kernel (hd1,6)/boot/vmlinuz BOOT_IMAGE=mga_2_64 root=LABEL=mga2  nokmsboot    
   vga=794   
   initrd (hd1,6)/boot/initrd.img   
      
   Before chainloading, I used to just mount the Production partition,   
   copy the stanza from /boot/grub/menu.lst and paste it into the new   
   install /boot/grub/menu.lst to get Production to boot.   
   Once there I would clone a chain load stanza and set it to the new   
   install drive,partition, and re-install Production grub to MBR.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)