Re: After system-upgrade F26->F27, system startup hangs after Reached target System Initialization

2018-05-18 Thread Ed Greshko
On 05/18/18 13:48, Frédéric wrote:
>> It may have been rebuilding the initramfs if there was a kernel update
>> or an SELinux relabel operation (really common on an upgrade, say from
>> F27->F28). If it happens again and if you have an LED showing disk
>> activity, watch it. If it's blinking like mad or on steadily, that's
>> probably what's going on (I love LEDs...but I also liked front panels
>> on my Imsai, Altair and PDP-11s).
>>
>> The first boot after an upgrade always seems to take a while for me, so
>> when I do it I just take a coffee break for 10 minutes or so. If things
>> aren't working by then, I go into spelunker mode to sort it out.
> Then do you think I should run manually the SElinux relabeling?
> Because I may have stopped it when I turned the computer off?
> What about the initramfs thing?
>
>
Unlike Rick, I have never experienced a SElinux relabel at boot after an 
upgrade. 

All of my boots after upgrade will take more time than usual since I run the 
binary
nVidia drivers and it needs to be built for the new kernel at boot time as they
aren't built during the upgrade process.

-- 
Conjecture is just a conclusion based on incomplete information. It isn't a 
fact.



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/4FHGF33XDA6IE3PWSKNYGHXGW747LPJ7/


Re: After system-upgrade F26->F27, system startup hangs after Reached target System Initialization

2018-05-17 Thread Frédéric
> It may have been rebuilding the initramfs if there was a kernel update
> or an SELinux relabel operation (really common on an upgrade, say from
> F27->F28). If it happens again and if you have an LED showing disk
> activity, watch it. If it's blinking like mad or on steadily, that's
> probably what's going on (I love LEDs...but I also liked front panels
> on my Imsai, Altair and PDP-11s).
>
> The first boot after an upgrade always seems to take a while for me, so
> when I do it I just take a coffee break for 10 minutes or so. If things
> aren't working by then, I go into spelunker mode to sort it out.

Then do you think I should run manually the SElinux relabeling?
Because I may have stopped it when I turned the computer off?
What about the initramfs thing?

F
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/E2R43UGZXAG7DFWH6WHKH6D6RCQSPNZT/


Re: After system-upgrade F26->F27, system startup hangs after Reached target System Initialization

2018-05-17 Thread Rick Stevens
On 05/16/2018 02:43 PM, Frédéric wrote:
>> So I have to force turning off... I do not like that.
> 
> Did that, rebooted. It stopped for a long time at the same place (2-3
> minutes) then showed the login screen!
> 
> Don't know what happened but it seems that it is fine now.

It may have been rebuilding the initramfs if there was a kernel update
or an SELinux relabel operation (really common on an upgrade, say from
F27->F28). If it happens again and if you have an LED showing disk
activity, watch it. If it's blinking like mad or on steadily, that's
probably what's going on (I love LEDs...but I also liked front panels
on my Imsai, Altair and PDP-11s).

The first boot after an upgrade always seems to take a while for me, so
when I do it I just take a coffee break for 10 minutes or so. If things
aren't working by then, I go into spelunker mode to sort it out.
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 -
--
-Admitting you have a problem is the first step toward getting   -
-medicated for it.  -- Jim Evarts (http://www.TopFive.com)   -
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/K227623GTLAK5JNURIKECVEUIRQGNTRE/


Re: After system-upgrade F26->F27, system startup hangs after Reached target System Initialization

2018-05-17 Thread Wolfgang Pfeiffer
On Wed, May 16, 2018 at 11:33:40PM +0200, Frédéric wrote:
> > What should I do? Just try to reboot another time?
> 
> Ctrl+Alt+Suppr did not work.
> Ctrl+Alt+SysReq works only for key S "Emergency Sync complete". All
> other keys in REISUB give "This sysrq operation is disabled.

I never heard that  might be part of the sysrq combo.

Here on an x86 it's 

0: press , keep holding
1: press -, release  -
2: press the magic key, release it
3: release 

But maybe you have most sysrq keys disabled: if you do a 
cat /proc/sys/kernel/sysrq
you might see what currently is set (my guess: 16).

more on the topic:
https://fedoraproject.org/wiki/QA/Sysrq#How_do_I_enable_the_magic_SysRq_key.3F

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/plain/Documentation/sysrq.txt?id=refs/tags/v4.9.5

And careful: hitting 'c' in sysrq will crash your system .. :)

Wolfgang
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/FI3EYNQ7TUSL3AC4MU4U4VA7ZBM74CRM/


Re: After system-upgrade F26->F27, system startup hangs after Reached target System Initialization

2018-05-16 Thread Frédéric
> So I have to force turning off... I do not like that.

Did that, rebooted. It stopped for a long time at the same place (2-3
minutes) then showed the login screen!

Don't know what happened but it seems that it is fine now.

Thanks
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: After system-upgrade F26->F27, system startup hangs after Reached target System Initialization

2018-05-16 Thread Frédéric
> What should I do? Just try to reboot another time?

Ctrl+Alt+Suppr did not work.
Ctrl+Alt+SysReq works only for key S "Emergency Sync complete". All
other keys in REISUB give "This sysrq operation is disabled.
So I have to force turning off... I do not like that.

F
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org