LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora
User Name
Password
Fedora This forum is for the discussion of the Fedora Project.

Notices

Reply
 
Search this Thread
Old 09-18-2013, 08:41 AM   #1
kaza
Member
 
Registered: Apr 2010
Distribution: FC17
Posts: 132

Rep: Reputation: 1
yum update -> boot fails


Hello,

I performed "yum update" as a preparation
to upgrading my FC17 to FC19 using a "fedup".

The "yum update" process went OK but when I rebooted,
I've been directed into "emergency mode" slightly
after the "filling teardrop" shape stage of the GUI boot.

The updated kernel which got stuck is:

3.9.10-100.fc17.x86_64

I temporary changed the grub.conf to use my
previous kernel

3.8.13-100.hpfs.fc17.x86_64

(recompiled to add HPFS support, I need it for an old OS/2 disk)

but I think I can't run "fedup" unless I'm not at the latest
update (correct me if I wrong).

How can I debug a boot failure? What files to look in?
Any keystrokes during boot to show more information as to in what
stage the problem is?

TIA,
 
Old 09-18-2013, 11:42 AM   #2
business_kid
Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 6,573

Rep: Reputation: 580Reputation: 580Reputation: 580Reputation: 580Reputation: 580Reputation: 580
Try your initrd. man mkinitrd - you can specify the options. The readymade initrd does not work for me ever, and provides huge wads of modules that have nothing to do with your system.

I have only expletives to describe this process. As soon as you are happy with your initrd they will update the kernel again and screw you over. I ran with a slackware kernel which did not need an initrd, and that was fine.
 
Old 09-18-2013, 02:44 PM   #3
John VV
Guru
 
Registered: Aug 2005
Posts: 13,271

Rep: Reputation: 1775Reputation: 1775Reputation: 1775Reputation: 1775Reputation: 1775Reputation: 1775Reputation: 1775Reputation: 1775Reputation: 1775Reputation: 1775Reputation: 1775
i would do a 100% new clean install of fedora 19
fedora moved from "preupgrade" to "fedup"
and introduced a new experimental replacement for "yum" called DNF

a in place upgrade skipping a version has NEVER been a good idea
 
Old 09-19-2013, 03:33 PM   #4
business_kid
Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 6,573

Rep: Reputation: 580Reputation: 580Reputation: 580Reputation: 580Reputation: 580Reputation: 580
That's the trouble with fedora: some of their experiments fail miserably - e.g. installer in F18.
 
Old 09-19-2013, 04:49 PM   #5
John VV
Guru
 
Registered: Aug 2005
Posts: 13,271

Rep: Reputation: 1775Reputation: 1775Reputation: 1775Reputation: 1775Reputation: 1775Reputation: 1775Reputation: 1775Reputation: 1775Reputation: 1775Reputation: 1775Reputation: 1775
well Fedora is "the great experiment"
it is for trying out new things , and sometimes they fail big time
or fail for a single version
remember the pulseaudio issue with fedora 6
 
Old 09-19-2013, 04:53 PM   #6
kaza
Member
 
Registered: Apr 2010
Distribution: FC17
Posts: 132

Original Poster
Rep: Reputation: 1
Thanks for everyone who responded,

I found the solution: after removing the "quiet" option from the "inintrd" line in grub.conf
I saw that the "Welcome to emergency mode" lines start after error messages related
to OS/2 disks (HPFS) and I remembered that before starting the "yum update" I didn't
comment the 3 lines in /etc/fstab which mount the 3 HPFS partitions. Since the new kernel
is without the HPFS support, attempts to mount HPFS partitions fail. After commenting
the above 3 lines, the system booted OK.

OK, I solved it now but how I'll remember in 2 years when I'll repeat this process to
comment HPFS-related lines first? :-)
And it's not going to improve with age... :-)
 
Old 09-27-2013, 06:37 PM   #7
falcomuser
LQ Newbie
 
Registered: Apr 2010
Location: Ecuador
Distribution: Fedora
Posts: 9

Rep: Reputation: 0
men whe you upgrade to 3.11.1-200.fc19.x86_64 kernel version you have a problem when your systems starts (donīt work the gui start)
but is only a troubled with the nvidia drivers!!


Quote:
Originally Posted by kaza View Post
Hello,

I performed "yum update" as a preparation
to upgrading my FC17 to FC19 using a "fedup".

The "yum update" process went OK but when I rebooted,
I've been directed into "emergency mode" slightly
after the "filling teardrop" shape stage of the GUI boot.

The updated kernel which got stuck is:

3.9.10-100.fc17.x86_64

I temporary changed the grub.conf to use my
previous kernel

3.8.13-100.hpfs.fc17.x86_64

(recompiled to add HPFS support, I need it for an old OS/2 disk)

but I think I can't run "fedup" unless I'm not at the latest
update (correct me if I wrong).

How can I debug a boot failure? What files to look in?
Any keystrokes during boot to show more information as to in what
stage the problem is?

TIA,
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Yum Update Fails tanalam Fedora 8 10-06-2010 07:35 AM
yum update fails micmizer Fedora 5 07-21-2009 06:34 PM
yum update fails jnojr Linux - General 2 06-19-2009 02:28 PM
Update YUM Fails sajdutt Linux - Software 7 03-09-2009 11:37 PM
xfs fails after yum update davidwiener Fedora 0 11-22-2006 10:47 AM


All times are GMT -5. The time now is 04:42 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration