Re: System broken after upgrade to kernel-3.3.2-1.fc16.i686

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

On Mon, 2012-04-23 at 09:39 +0100, Andrew Gray wrote:
> On Sun, 2012-04-22 at 16:49 -0700, Jonathan Ryshpan wrote:
> > I have just upgraded two systems to kernel-3.3.2-1.  One system
> > (x86_64 hardware) upgraded flawlessly.  The other (i686 hardware) now
> > won't boot.  The grub menu comes up allowing me to choose between: 
> >     kernel-3.3.2-1.f16.i686   -- which fails (see below)
> >     kernel-3.3.0-0.f16.i686   -- which works
> > When I choose kernel-3.3.2-1, there is what seems like an
> > exceptionally long pause, the system briefly displays some garbage,
> > and then these messages appear:
> > 
> >         dracut warning no root device
> >         "block:/dev/disk/by-uuid/2d...af"  found
> >         
> >         dracut warning no root device
> >         "block:/dev/disk/by-uuid/2d...af"  found
> >         
> >         dropping to debug shell
> >         
> >         sh: 0 can't access tty:  job control turned off
> >         
> >         dracut:/#
> > 
> > In fact, as blkid shows the device (partition) that the system appears
> > to be looking for is not there.  However all the partitions that
> > should be on the system are there, including the partition that is
> > normally mounted on /boot.  Which must be so, since the previous
> > kernel starts OK.
> > 
> > Questions: 
> >      1. What's going on here? 
> >      2. How can I fix it? 
> >      3. How can I prevent this in the future?
> > 
> > Many thanks - jon
> > 
> > 

> On your failing I686
> Note I show you the file names as on my x86_64 F16 
> 
> I suggest you look at /boot and the sizes of the *.img files for the
> kernels. If the initramfs-3.3.2-1.fc16.x86_64.img is smaller than the 
> initramfs-3.3.1-5.fc16.x86_64.img it kernel 3.3.2-1 didn't install
> properly. 
File sizes look OK.  The latest kernel is slightly larger than the last one.
> I had this a kernel upgrade earlier and fixed it with by reinstalling 
> the kernel it get it to create a proper initramfs file
> 
> yum reinstall kernel-3.3.2-1.fc16.i686 
I have done this.  Unfortunately not change in system behavior.  It's
broken in the same way as before.

Thanks - jon



-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org



Photo 4 Less

[Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Find Someone Special]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Yosemite Photos]     [Linux Apps]     [Maemo Users]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

Add to Google Powered by Linux