upgraded kernel (was Re: ubuntu boot problem)

[Matthew Carpenter]

On Saturday 08 September 2007, james at jamesmcdonald.id.au wrote:
> > On 9/7/07, Bob Hemus <ol.bob at sisqtel.net> wrote:
> >> On Fri, 2007-09-07 at 19:06 -0700, Lonni J Friedman wrote:
> >> > On 9/7/07, Bob Hemus <ol.bob at sisqtel.net> wrote:
> >> > > Folks, somehow I've bugered up, again.  I've got a couple of other
> >> > > distros on my hda, Winders, Debisn, Ubuntu 7.04, & kbuntu 7.04.  I'm
> >> > > using the Ubuntu 7.04.  When I get to the grub menu and pick Ubuntu
> >> > > 7.04, it begins to load normally, but about half way through it
> >>
> >> jumps to
> >>
> >> > > a text load with this error message, among others:
> >> > >
> >> > > fsck.ext3:unable to resolve
> >> > > uuid=304ff5cc-ed19-4d45-adb2-3ea9480b63e4
> >> > > fsck died with exit status 8
> >> > >
> >> > > Then the instructions say cntl D, and it finishes loading, but then
> >> > > going by 'til I stop it I see:
> >> > >
> >> > > Mount: special device /dev/disk/by-uuid=304ff5cc-ed19-4d45-
> >> > >     adb2-3ea9480b63e4 does not exist
> >> > >
> >> > > Do I need to make a device? or a directory or ?
> >> > > Now that Susan is back, any help from you fine Lady or gentlemen
> >>
> >> will be
> >>
> >> > > greatly appreciated.
> >> >
> >> > That's really horked.  Ubuntu's speial disk UUID sauce appears to have
> >> > blown up.  Did you repartition the disk or something since the last
> >> > time this worked?
> >>
> >> --------------------
> >> Yup, sure did.  Not this partition, though.  Every thing seems to still
> >> work, though?
> >
> > Clearly everything doesn't still work, as you can't boot Ubuntu any
> > longer.  Sorry, I can't help you on this one.  Using UUIDs for
> > partiton IDs seems like a rather short-sighted approach, or at the
> > very least its incredibly fragile.  Some googling did turn up others
> > with this same fate:
> > http://www.linuxforums.org/forum/redhat-fedora-linux-help/60464-uuid-inco
> >rrect-drive-lvm-after-running-fdisk-new-drive.html
> > http://linuxmafia.com/pipermail/sf-lug/2007q1/001208.html
> >
> >
> > What you can try doing is to specify the actual block device name
> > (/dev/hda1, /dev/sdb3, etc) in place of that UUID in /etc/fstab.
>
> I recently upgraded my kernel on Ubuntu on gutsy and found that trying to
> boot an older kernel from it caused the boot sequence to go to one of
> those CTRL D prompts you mentioned. Rebooting however to the new kernl
> worked fine. Have you got several ubuntu kernels and are booting an older
> one?

Sounds like your upgrade possibly didn't build a correct initrd?  Check to see 
if you're using an initrd (in /boot/grub/menu.lst) and then make sure one 
exists for the new gutsy kernel (/boot/initrd.img-****) and then include more 
error messages since many things can cause the CTRL-D prompt.  Typically I 
run into this because I'm running root (or another partition listed 
in /etc/fstab that doesn't have either "noauto" or has a non-zero number in 
the last column) on a filesystem that is not in my initrd.


-- 
Matthew Carpenter
mcarpenter at intelguardians.com
http://www.intelguardians.com

PGP Fingerprint: 
87EB 54A8 FB42 0A0E B8AE CDA7 FF99 2A64 E70F 4466
hkp://wwwkeys.pgp.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mailman.celestial.com/pipermail/linux-users/attachments/20070910/0dd255e8/attachment-0002.bin