Can't boot Lucid after upgrade from Karmic

[Tony Pursell]

On 30 May 2010 at 7:48, chris wrote:

> 
> On Sat, 2010-05-29 at 18:08 +0100, Tony Pursell wrote:
> > On 27 May 2010 at 18:06, NoOp wrote:
> > 
> > > 
> > > On 05/27/2010 04:14 PM, Tony Pursell wrote:
> > > > On 27 May 2010 at 13:26, NoOp wrote:
> > > ...
> > > >>  Tony, can you get to the /var/logs/dist-upgrade and post the apt, main,
> > > >>  and terminal logs on pastebin?
> > > >>
> > > >>  http://ubuntu.pastebin.com/
> > > >>  or
> > > >>  http://pastebin.org/
> > > >>
> > > >>  and then post back with the links to the logs?
> > > >>
> > > > 
> > > > Logs are in
> > > > 
> > > > _http://ubuntu.pastebin.com/2Nwhbimx_
> > > > 
> > > > 
> > > > Note that I had a failed dist-upgrade prior to this with this bug (because I had 
> > > > Xubuntu also installed). I can get you the logs for this if you need them, but 
> > > > it won't be until Friday evening.
> > > 
> > > Most of it (as far as I can tell) looks fairly normal. Only bits that
> > > look odd are:
> > > ====
> > > #
> > > Running postrm hook script /sbin/update-grub.
> > > #
> > > Your /etc/kernel-img.conf needs to be updated. Read grub's NEWS.Debian[1]
> > > #
> > > file and follow its instructions.
> > > #
> > > Searching for GRUB installation directory ... found: /boot/grub
> > > #
> > > Searching for default file ... found: /boot/grub/default
> > > #
> > > Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
> > > #
> > > Searching for splash image ...
> > > #
> > > Searching for splash image ... found:
> > > (hd0,5)/boot/grub/splashimages/SunsetOverPontypool.xpm.gz
> > > #
> > > Found kernel: /boot/vmlinuz-2.6.32-21-generic
> > > #
> > > Found kernel: /boot/vmlinuz-2.6.31-21-generic
> > > #
> > > Found kernel: /boot/vmlinuz-2.6.27-11-generic
> > > #
> > > Found kernel: /boot/memtest86+.bin
> > > #
> > > Replacing config file /var/run/grub/menu.lst with new version
> > > #
> > > Updating /boot/grub/menu.lst ...
> > > #
> > > 6.31-20-generic
> > > #
> > > Updating /boot/grub/menu.lst ... done
> > > ====
> > > 
> > > Can you try:
> > > $ sudo update-initramfs -c -k all
> > > $ sudo update-grub
> > > 
> > > and also post on pastebin:
> > > 
> > > $ cat /etc/fstab
> > > $ cat /etc/boot/menu.lst
> > > $ blkid
> > > 
> > > I know that you've done some/most of this before, but having it on
> > > pastebin will be helpful
> > > 
> > 
> > fstab and menu.lst are at http://ubuntu.pastebin.com/mVyacMHN
> > 
> > Did these from the live USB.  Can't get the output from blkid as I 
> > cannot boot at all now, not even with the Karmic kernel. Did the 
> > update-initramfs cause this?  
> > 
> > So it looks likes re-intstall time. So any advice on this would be 
> > welcome.  I will want to rescue my data in /home and probably keep it 
> > in a separate partition.  The rest can go in to a single root partition. 
> > Plus swap, of course.  
> > 
> > On my 200MB drive (/dev/sda), I currently have:
> > 
> > /dev/sda1 Windows XP NTFS 90GB
> > /dev/sda2 Extended partiton
> >   /dev/sda5 swap 1GB
> >   /dev/sda6 / 3GB
> >   /dev/sda7 /tmp 5GB
> >   /dev/sda8 /usr 10GB
> >   /dev/sda9 /var 5GB
> >   /dev/sda10 /home 40GB
> >   unused 
> > /dev/sda3 Windows VFAT 5GB 
> > /dev/sda4 Windows Recovery VFAT 6GB (Recovery data)
> > 
> > This last partiton doesn't ever get mounted.
> > 
> > Tony 
> > 
> > I would suggest that / is too small can you try 8GB as a minimum?
> cheers the kiwi
> > 

With /tmp, /usr, /var and /home in their own partitons, root was only 
half full.  If I re-install with all these combined, I will have at least 
23GB.

Tony