Fedora 18 not booting after lots of successful boot ups

[Chris Murphy]

On Mar 12, 2014, at 4:36 AM, takCoder <tak.official at gmail.com> wrote:

> systemd-readahead[416]:  Failed to open pack file: Read-only system

I'm not sure the problem is Bluetooth at all. Systemd has a way to optimize boot times with its own read ahead mechanism, and puts the hint for what to read ahead in (I'm guessing) this pack file. I don't know why the file system is read only at this point though, so that seems to be the real problem.

I'd start out by booting single user mode (rescue.target in systemd vernacular). Do this by pressing e at the grub menu to edit the entry, find the linux line, and add to the end of it the word single. Use the mount command to see that all relevant file systems are in fact mounted rw and not ro. If / or /var is ro, then you are slightly better off booting from alternate media like a live desktop image, and running fsck on the problematic volume rather than running it on a mounted ro volume. But if you do run it on the ro volume, immediately reboot after repairs by using reboot -f.

Also while you're at it, use df -h to see if for some reason a volume is full.

If everything file system wise is OK, then you'll need to add some other boot parameters to try to track this down.

Remove both the quiet rhgb options, and add systemd.log_level=debug systemd.log_target=console options. This will produce rather verbose messages on the console but should better pinpoint where the problem is.

It is also possible to just disable the readahead. If you successfully boot single user with a rw mounted file system:

systemctl disable systemd-readahead-collect.service systemd-readahead-drop.service systemd-readahead-replay.service

It's unlikely that it makes much of a difference performance wise anyway. And it's probably not worth spending much time troubleshooting and filing bugs since Fedora 18 is EOL anyway.


Chris Murphy