Hi,
I'm running Fedora 21 Workstation on a desktop and a laptop, and on both machines I am experiencing problems trying to boot them.
The problem is that when I boot either of the computers, it gets stuck during the Plymouth splash screen, when the Fedora logo is being filled up. It can be stuck there for tens of minutes until I lose patience and do a hard reset on the computer. About 1/5 of the boot attempts succeed and are very snappy, while the other 4/5 get stuck and require a hard reset.
However, I think I have solved it on the laptop by disabling `nfs-client.target` with `$ sudo systemctl disable nfs-client.target`, and I suspect that it might be related to https://bugzilla.redhat.com/show_bug.cgi?id=1183321.
I tried doing the same on my desktop, but it does not seem to have made any difference. It still requires quite a few boot attempts before it reaches the login screen.
What I need help with is how I am supposed to proceed with debugging and locating the cause of the problem. As far as I know a journalctl entry is not created in `$ journalctl --list-boots` if I do a hard reset during the startup process. And `$ systemd-analyze` does not show any strange things because I am of course only able to execute it after a successful boot, for example on my laptop:
Startup finished in 1.454s (kernel) + 1.412s (initrd) + 2.608s (userspace) = 5.475s
Do you have any suggestions for how I am supposed to proceed with the matter?
Best regards, Daniel Jonsson
On 03/06/2015 05:28 AM, Daniel Jonsson wrote:
The problem is that when I boot either of the computers, it gets stuck during the Plymouth splash screen, when the Fedora logo is being filled up. It can be stuck there for tens of minutes until I lose patience and do a hard reset on the computer. About 1/5 of the boot attempts succeed and are very snappy, while the other 4/5 get stuck and require a hard reset.
That same symptom has happened to me, and it always happened after I changed partitions, as in what fstab has in it is wrong & one of the partitions is not mountable. once I take out all extra partition info, assuming / & /home are mountable, it boots...
On Friday 06 March 2015 06:20:48 Paul Cartwright wrote:
On 03/06/2015 05:28 AM, Daniel Jonsson wrote:
The problem is that when I boot either of the computers, it gets stuck during the Plymouth splash screen, when the Fedora logo is being filled up. It can be stuck there for tens of minutes until I lose patience and do a hard reset on the computer. About 1/5 of the boot attempts succeed and are very snappy, while the other 4/5 get stuck and require a hard reset.
That same symptom has happened to me, and it always happened after I changed partitions, as in what fstab has in it is wrong & one of the partitions is not mountable. once I take out all extra partition info, assuming / & /home are mountable, it boots...
Have you tried hitting <escape> whilst waiting for the plymouth boot screen (to view the current boot dialog)? This will allow you to at least see where the boot process is hanging. Regards Andy
On Fri, Mar 06, 2015 at 06:20:48AM -0500, Paul Cartwright wrote:
That same symptom has happened to me, and it always happened after I changed partitions, as in what fstab has in it is wrong & one of the partitions is not mountable. once I take out all extra partition info, assuming / & /home are mountable, it boots...
On my laptop, which I am currently on, I have only one drive with the partitions /, /boot, /home and swap. And it boots fine after disabling `nfs-client.target`.
I think my setup is more or less the same on my desktop with regards to its main drive. However, I know that I have added at least one additional partition to fstab that resides on a secondary drive. If I recall correctly I have added two partitions, one being ext4 and one being ntfs. I will check when I get home. Thanks for the suggestion.
On 03/06/2015 07:11 AM, Daniel Jonsson wrote:
On Fri, Mar 06, 2015 at 06:20:48AM -0500, Paul Cartwright wrote:
That same symptom has happened to me, and it always happened after I changed partitions, as in what fstab has in it is wrong & one of the partitions is not mountable. once I take out all extra partition info, assuming / & /home are mountable, it boots...
On my laptop, which I am currently on, I have only one drive with the partitions /, /boot, /home and swap. And it boots fine after disabling `nfs-client.target`.
can it get to that ntfs-client?? you may need to start that manually after boot..
I think my setup is more or less the same on my desktop with regards to its main drive. However, I know that I have added at least one additional partition to fstab that resides on a secondary drive. If I recall correctly I have added two partitions, one being ext4 and one being ntfs. I will check when I get home. Thanks for the suggestion.
On Fri, Mar 06, 2015 at 08:22:04AM -0500, Paul Cartwright wrote:
On 03/06/2015 07:11 AM, Daniel Jonsson wrote:
On my laptop, which I am currently on, I have only one drive with the partitions /, /boot, /home and swap. And it boots fine after disabling `nfs-client.target`.
can it get to that ntfs-client?? you may need to start that manually after boot..
What do you mean? I am not using NFS, so disabling nfs-client.target should not cause any problems, I assume at least. NTFS is a file system and not related to systemd.
On 03/06/2015 09:46 AM, Daniel Jonsson wrote:
`nfs-client.target`.
can it get to that ntfs-client?? you may need to start that manually after boot..
What do you mean? I am not using NFS, so disabling nfs-client.target should not cause any problems, I assume at least. NTFS is a file system and not related to systemd.
ack, sorry, I mis-read that... NFS not NTFS.. yes, disable NFS...
On Fri, Mar 06, 2015 at 10:20:14AM -0500, Paul Cartwright wrote:
ack, sorry, I mis-read that... NFS not NTFS.. yes, disable NFS...
I only had one extra ext4 partition in my fstab file which I commented out. However, it did not make any difference with regards to be able to boot up successfully.
It would be nice if there was a way to see the log entries after a hard reset during the boot process. Then I assume it would be trivial to locate the problem.
On Fri, Mar 06, 2015 at 12:02:19PM +0000, Andrew R Paterson wrote:
Have you tried hitting <escape> whilst waiting for the plymouth boot screen (to view the current boot dialog)? This will allow you to at least see where the boot process is hanging. Regards Andy
First the GRUB screen is shown with 3 different kernel versions. When selecting one of them, the text "Ignoring BGRT: invalid status 0 (expected 1)" is displayed for a brief moment. It then switches to the Plymouth Fedora logo. If I hit escape during its process of filling up the Plymouth Fedora logo, it shows the same error.
-
Andy Paterson -
Daniel Jonsson -
Paul Cartwright