Hi All,
I'm new in fedora world and here's my first unsolved problem there.. It's an un-reasoned hang during boot up of a healthy system..
I have installed fedora 18 on a ssd, followed a given process to install required packages of my goal system, and it was working fine before..
Today I powered my system up and it hanged during boot up.. using 'e' key and changing gfxpayload value to text showed me this error: Starting Bluetooth Service... systemd-readahead[416]: Failed to open pack file: Read-only system
I googled it but I could not find the given error..
Actually there is no need for bluetooth service on my system, but I can't figure it out what exactly the error is.
Would someone please give me a hand on this? I would really appreciate that..
Kind regards, takcoder
would anyone please give me any hints? can I disable bluetooth servive from repair mode?
Best Regards, t.a.k
On Wed, Mar 12, 2014 at 2:06 PM, takCoder tak.official@gmail.com wrote:
Hi All,
I'm new in fedora world and here's my first unsolved problem there.. It's an un-reasoned hang during boot up of a healthy system..
I have installed fedora 18 on a ssd, followed a given process to install required packages of my goal system, and it was working fine before..
Today I powered my system up and it hanged during boot up.. using 'e' key and changing gfxpayload value to text showed me this error: Starting Bluetooth Service... systemd-readahead[416]: Failed to open pack file: Read-only system
I googled it but I could not find the given error..
Actually there is no need for bluetooth service on my system, but I can't figure it out what exactly the error is.
Would someone please give me a hand on this? I would really appreciate that..
Kind regards, takcoder
On Wed, 2014-03-12 at 17:57 +0330, takCoder wrote:
would anyone please give me any hints? can I disable bluetooth servive from repair mode?
[Please don't top-post on the Fedora lists. See the Guidelines document referenced at the end of every post.]
F18 is EOL, i.e. no longer supported, however you might try booting in rescue mode, then:
1) chroot /mnt/... (root of the system you're trying to fix) 2) systemctl disable bluetooth.service
I've no idea if this will work.
poc
On Mar 12, 2014, at 4:36 AM, takCoder tak.official@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
For posterity: https://bugzilla.redhat.com/show_bug.cgi?id=696821
It's not exactly the OP's problem, but there appears to be a kernel bug that can cause systemd readahead problems. Anyway I always do a 1/2 dozen reboots with it enabled, checking systemd-analyze each time; and then disable it and reboot and check systemd-analyze again. At least in my configurations, there's no difference so I just leave it disabled.
Chris Murphy
On Mar 12, 2014, at 1:11 PM, Chris Murphy lists@colorremedies.com wrote:
Anyway I always do a 1/2 dozen reboots with it enabled, checking systemd-analyze each time; and then disable it and reboot and check systemd-analyze again.
That is, I do this with each new major version of systemd. Because this readahead code is constantly being tweaked, so eventually it might benefit my use case. There are some tips here:
http://freedesktop.org/wiki/Software/systemd/Optimizations/
Chris Murphy