After upgrading my F15 netbook today, it failed to boot again. It
refused to give me a login prompt and nothing happened after at least 20
minutes after sitting at this[1] screen. In this state, the only way to
get any response was to hard-reset the machine. Ctrl+Alt+{Fn,Delete} did
nothing. Going into init 1 (via grub menu editing) got me a shell, but
trying systemctl default or ^D put it in the same state as before. After
so much of this, it seems as though something on /boot became unhappy
(it was uncleanly unmounted every time) as the keyboard behaved weird
('1' inserted a 't' and everything else seemed to be just spaces) so I
was locked out of init 1 as well. I tried doing a fresh F15 minimal
netinst install and I am at the same state. I'm hesitant to do too much
without some guidance because of the chance that /boot gets corrupted
again and needing another reinstall.
>From what I can recall and hints from Bodhi, (at least) the following
were upgraded on the original install:
Other things may have also been installed, but I can't recall. The
previous kernel upgrade was 2.6.38.1-$unsure to give a lower bound on
packages that may have changed. I have a list of what was installed
(after an attempted yum history undo from one of the init 1 instances to
fix things, unfortunately partial due to packages being deleted from the
repos), but it's on the netbook yet (saved in /home).
--Ben
[1]http://i.imgur.com/odjeA.jpg
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
04-01-2011, 07:08 AM
Matthias Runge
Failure to boot new F15 minimal netinst install
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/04/11 09:00, Ben Boeckel wrote:
> Hi,
>
> After upgrading my F15 netbook today, it failed to boot again. It
there are (at least) two known bugs regarding systemd-21 and booting.
You may try to boot with enforcing=0 appended on kernel command line in
grub.
> refused to give me a login prompt and nothing happened after at least 20
> minutes after sitting at this[1] screen. In this state, the only way to
> get any response was to hard-reset the machine. Ctrl+Alt+{Fn,Delete} did
> nothing. Going into init 1 (via grub menu editing) got me a shell, but
> trying systemctl default or ^D put it in the same state as before. After
> so much of this, it seems as though something on /boot became unhappy
> (it was uncleanly unmounted every time) as the keyboard behaved weird
> ('1' inserted a 't' and everything else seemed to be just spaces) so I
> was locked out of init 1 as well. I tried doing a fresh F15 minimal
> netinst install and I am at the same state. I'm hesitant to do too much
> without some guidance because of the chance that /boot gets corrupted
> again and needing another reinstall.
>
>>From what I can recall and hints from Bodhi, (at least) the following
> were upgraded on the original install:
>
> - kernel-PAE-2.6.28.2-8
> - systemd-21
> - udev-167-$unsure
>
> Other things may have also been installed, but I can't recall. The
> previous kernel upgrade was 2.6.38.1-$unsure to give a lower bound on
> packages that may have changed. I have a list of what was installed
> (after an attempted yum history undo from one of the init 1 instances to
> fix things, unfortunately partial due to packages being deleted from the
> repos), but it's on the netbook yet (saved in /home).
>
> --Ben
>
> [1]http://i.imgur.com/odjeA.jpg
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
On 04/01/2011 09:08 AM, Matthias Runge wrote:
> On 01/04/11 09:00, Ben Boeckel wrote:
>> Hi,
>
>> After upgrading my F15 netbook today, it failed to boot again. It
>
> there are (at least) two known bugs regarding systemd-21 and booting.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=692573
> https://bugzilla.redhat.com/show_bug.cgi?id=692602
>
> You may try to boot with enforcing=0 appended on kernel command line in
> grub.
>
I had the same problem, and managed to boot with both selinux=0 and
enforcing=0 -- switched to the latter since the former might cause a
relabeling to be necessary; interestingly, no such thing happens (is the
auto-relabeling trigger broken?)
With enforcing=0, I was hoping I could find out setroubleshootd would
tell me what's causing the boot failure, but it spews out 51 alerts
touching various components. Is that because I need to relabel, or is
everyone else seeing that too?
If the latter, it might well be a systemd problem.
Regards,
- --
Michel Alexandre Salim
() ascii ribbon campaign - against html e-mail
/ www.asciiribbon.org - against proprietary attachments
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
04-01-2011, 03:17 PM
Ben Boeckel
Failure to boot new F15 minimal netinst install
Matthias Runge <mrunge@matthias-runge.de> wrote:
>> After upgrading my F15 netbook today, it failed to boot again. It
>
> there are (at least) two known bugs regarding systemd-21 and booting.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=692573
> https://bugzilla.redhat.com/show_bug.cgi?id=692602
CC'd myself.
> You may try to boot with enforcing=0 appended on kernel command line in
> grub.
That worked, thanks.
--Ben
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Failure to boot new F15 minimal netinst install
