On 8/5/20 5:40 AM, Kenneth Porter wrote:
Is there some way we could get the initrd rebuild to be more verbose,
so that it doesn't appear to hang? It would be nice to get feedback
that something is happening, especially on an older, slower system
that takes a long time for this step.
While
Am 05.08.20 um 13:44 schrieb Leon Fauster via CentOS:
> Take a look into "top",
> if something like gz or xz is in place occupying your CPU then the
> initrd gets build ... just wait :-)
'journalctl -f' shows the state of the build process.
___
CentOS
Am 05.08.20 um 02:13 schrieb david:
At 05:01 PM 8/4/2020, you wrote:
Am 05.08.20 um 01:27 schrieb david:
At 04:18 PM 8/4/2020, you wrote:
Am 05.08.20 um 01:09 schrieb david:
At 01:54 PM 8/4/2020, you wrote:
On Tue, 04 Aug 2020 13:44:05 -0700
david wrote:
> After all the updates, the system
On 05/08/2020 10:40, Kenneth Porter wrote:
Is there some way we could get the initrd rebuild to be more verbose, so
that it doesn't appear to hang? It would be nice to get feedback that
something is happening, especially on an older, slower system that takes
a long time for this step.
On 8/4/2020 11:20 AM, Jonathan Billings wrote:
Running transaction
Installing : kernel-3.10.0-1127.el7.x86_64 1/1
at which point the process appeared to hang. No further output happened for
five minutes. I opened a different terminal and entered "shutdown -r now".
The result is an
At 05:01 PM 8/4/2020, you wrote:
Am 05.08.20 um 01:27 schrieb david:
At 04:18 PM 8/4/2020, you wrote:
Am 05.08.20 um 01:09 schrieb david:
At 01:54 PM 8/4/2020, you wrote:
On Tue, 04 Aug 2020 13:44:05 -0700
david wrote:
> After all the updates, the system was NOT bootable.
How long did you
Am 05.08.20 um 01:27 schrieb david:
At 04:18 PM 8/4/2020, you wrote:
Am 05.08.20 um 01:09 schrieb david:
At 01:54 PM 8/4/2020, you wrote:
On Tue, 04 Aug 2020 13:44:05 -0700
david wrote:
> After all the updates, the system was NOT bootable.
How long did you wait for it to boot, and what did
At 04:18 PM 8/4/2020, you wrote:
Am 05.08.20 um 01:09 schrieb david:
At 01:54 PM 8/4/2020, you wrote:
On Tue, 04 Aug 2020 13:44:05 -0700
david wrote:
> After all the updates, the system was NOT bootable.
How long did you wait for it to boot, and what
did it do when it failed to boot? What
Am 05.08.20 um 01:09 schrieb david:
At 01:54 PM 8/4/2020, you wrote:
On Tue, 04 Aug 2020 13:44:05 -0700
david wrote:
> After all the updates, the system was NOT bootable.
How long did you wait for it to boot, and what did it do when it
failed to boot? What text messages showed up on the
At 01:54 PM 8/4/2020, you wrote:
On Tue, 04 Aug 2020 13:44:05 -0700
david wrote:
> After all the updates, the system was NOT bootable.
How long did you wait for it to boot, and what did it do when it
failed to boot? What text messages showed up on the console? Any
reported errors when you
On Tue, 04 Aug 2020 13:44:05 -0700
david wrote:
> After all the updates, the system was NOT bootable.
How long did you wait for it to boot, and what did it do when it failed to
boot? What text messages showed up on the console? Any reported errors when
you ran the update or when you rebooted
Your system was most likely rebuilding the initrd, and you interrupted
it leaving you with a broken initrd.
Try booting off a rescue disk and chroot into the install, and run:
dracut -f -v
to regenerate all the initrds.
Also, you don't need to reinstall the kernel but just do a 'yum
On Tue, Aug 04, 2020 at 10:54:50AM -0700, david wrote:
> Yum got up to the point:
>
> Running transaction
> Installing : kernel-3.10.0-1127.el7.x86_64 1/1
>
> at which point the process appeared to hang. No further output happened for
> five minutes. I opened a different terminal and entered
Following the advice on this mailing list, I rebuilt (from scratch)
Centos 7.8. I added the following line into /etc/yum.conf before the
first update:
exclude=grub2* shim* mokutil
The system worked fine. I was able to do general updates
yum -y update
and all was well.
HOWEVER, following
14 matches
Mail list logo
