Ask Your Question
0

Fedora 19 fails to start [closed]

asked 2013-10-16 00:56:02 -0600

Bharat gravatar image

updated 2014-02-13 13:52:22 -0600

mether gravatar image

I had updated fedora 17 to fedora 19 (kernel 3.10.11-200) on my laptop using fedup a ~2-3 weeks back. Everything was fine until yesterday night. All of a sudden while shutting down I got some recurring kernel error message. I couldn't note it down and I powered off the system forcibly. The next morning when I started the system the login screen fails to start. I am just able to see kernel messages. I get this message:

failed to start wait for plymouth boot screen to quit

When I start terminal with Ctrl+Alt+F2 i get this message when I log in:

login: write lastlog failed: No space left on device

yum updatedoesn't work and fails with this message:

error: db5 error(11) from dbenv->open: Resource temporarily unavailable
error: cannot open Packages index using db5 - Resource temporarily unavailable (11)
error: cannot open Packages in /var/lib/rpm
CRITICAL:yum.main:

Error: rpmdb open failed

I have around 50 GB for the root partition. Can't understand how can all this space run out. The disk is LVM partitioned. Is there any way to rescue the system without losing files on /home.

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by Akshay
close date 2013-10-27 10:58:24.000808

2 Answers

Sort by » oldest newest most voted
1

answered 2013-10-22 14:50:09 -0600

zbyszek gravatar image

updated 2013-10-22 14:53:00 -0600

There are probably three unrelated issues:

  1. "failed to start wait for plymouth ..." → This is probably bug https://bugzilla.redhat.com/show_bug.cgi?id=967521. As a work-around, you can press ESC during bootup.

  2. lack of disk space. Try

    du -ax | sort -g | less

This will give a list of stuff on the root partition, sorted by size. You'll probably find something to nuke in there. E.g. /var/log/messages* or /var/log/journal// might be good options, assuming you don't need the logs.

  1. rpm errors... Here alexfinn's suggestion is good. Just make some free space beforehand.
edit flag offensive delete link more

Comments

Thanks for the suggestions. I was too impatient then and I just reinstalled fedora. I should have checked what is taking up that much of space. Quite probable that it must have been something in /var/log/messages because during the last shutdown there was a torrent of messages.

Bharat gravatar imageBharat ( 2013-10-28 00:50:16 -0600 )edit
0

answered 2013-10-16 01:42:46 -0600

alexfinn gravatar image

Try

rm -f /var/lib/rpm/__db*

and

rpm --rebuilddb
edit flag offensive delete link more

Comments

I did try that but it didnt work. Perhaps because of lack of space.

Bharat gravatar imageBharat ( 2013-10-28 00:51:04 -0600 )edit

Question Tools

Stats

Asked: 2013-10-16 00:56:02 -0600

Seen: 1,412 times

Last updated: Oct 22 '13