Ask Your Question

DNF update failed "[Errno 30] Read-only file system"

asked 2018-11-14 06:05:59 -0500

rzbyn gravatar image

Fedora 29 stuck on Fedora logo on boot after DNF update is aborted because of lights off.
After removing rhgb quiet from grub found out it is stuck because Failed to load SELinux policy. Freezing.

I have tried to follow some articles I found on google such as this or this but always failed because any dnf commands are failed due toConfig error: [Errno 30] Read-only file system: '/var/log/*': '/var/log/*'
Running chmod or fsck from live USB also doesn't solve the read-only file system problem.

Any help are appreciated!

edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted

answered 2018-11-14 22:29:40 -0500

sideburns gravatar image

The reason that chmod hasn't worked is because you're doing it from a LiveUSB, and the directory you need to work with is on the computer's drive. Mounting that drive, finding the right directory and correcting the permissions issue may be what you need, On my laptop, they're drwxr-xr-x. if that's any help.

edit flag offensive delete link more


That what was I'm trying to do. Mounting my / from live USB as rw and fix the problem but even it is mounted as rw it keeps on returning Read-only file system:.

$ ls -l
drwxr-xr-x   19 root root  4140 Nov 15 11:50 dev
drwxr-xr-x. 149 root root 12288 Nov 15 11:49 etc
drwxr-xr-x.  24 root root  4096 Nov  8 22:52 var

Another update I found this from dmesg:

Aborting journal on device sda3-8.
EXT4-fs error (device sda3): ext4_journal_check_start:61: Detected aborted journal
EXT4-fs (sda3): Remounting filesystem read-only

I think this why it keep on ro

rzbyn gravatar imagerzbyn ( 2018-11-15 00:58:54 -0500 )edit

OK, it's not a permissions as such, which is exactly what I was afraid of. You may have to unmount the partition and run fsck to clean everything up, unless some other reader has a better idea.

sideburns gravatar imagesideburns ( 2018-11-15 01:32:03 -0500 )edit

answered 2018-11-14 20:26:51 -0500

ed209 gravatar image

The read only fs is due to the fact that your root partition / is somehow damaged. What is the answer of e2fsck on / device?

edit flag offensive delete link more


Thanks for the response!

running e2fsck from live USB

$ sudo e2fsck /dev/sda3
e2fsck 1.44.3 (10-July-2018)
/dev/sda3: clean, 277759/6553600 files, 4777569/26214400 blocks
rzbyn gravatar imagerzbyn ( 2018-11-14 22:06:05 -0500 )edit

Hm, a tricky one. Let's start with rebuilding the database. As root do:

cd /var/lib/
rm __db*
rpm --rebuilddb
ed209 gravatar imageed209 ( 2018-11-15 14:41:53 -0500 )edit

Here you go:

[/var/lib]$ rm __db*
rm: cannot remove '__db*': No such file or directory
[/var/lib]$ rpm --rebuilddb 
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Permission denied)
[/var/lib]$ sudo rpm --rebuilddb

After doing this I don't see any __db* files on my /var/lib

rzbyn gravatar imagerzbyn ( 2018-11-15 16:00:03 -0500 )edit

Sorry, I dropped the rpm. The correct path is /var/lib/rpm/ . Before erasing and recreating check whether __db.001, .002, .003 are present.

ed209 gravatar imageed209 ( 2018-11-15 17:26:01 -0500 )edit

Question Tools

1 follower


Asked: 2018-11-14 06:05:59 -0500

Seen: 866 times

Last updated: Nov 14 '18