[BlueOnyx:25685] Re: System fails to start after kernel update last night.

[Ceelie, Arie (VodafoneZiggo)]

Few errors from journalctl -xb:
interface rename errors for eth3 and eth1
/sbin/mdadm -I /dev/sdc failed with exit code 1 (sdc and sdd are backup disks, not OS disks)
dev-sde2.device: job /start timed out (missing USB-disk)

no other errors......

I'm lost here.


________________________________
From: Blueonyx <blueonyx-bounces at mail.blueonyx.it> on behalf of Ceelie, Arie (VodafoneZiggo) <arie.ceelie at vodafoneziggo.com>
Sent: Friday, 11 November 2022 12:39
To: BlueOnyx General Mailing List <blueonyx at mail.blueonyx.it>
Subject: [BlueOnyx:25684] System fails to start after kernel update last night.

Hi all,

this morning the kernel of my almalinux system was updated to vmlinuz-4.18.0-425.3.1. And then it rebooted in rescue mode. I tried both old kernels and still it reboots into rescue mode.
When I use grubby to see the kernel index I also get a grub-editenv: error: cannot rename the file /boot/grub2/grubenv.new to /boot/grub/grubenv (no such file or directory)

  1.  IS this error related to the boot failure?
  2.  What can I do to get the system up and running again?

Until the kernel update it was working fine, even when rebooting.

Cheers,

Arie



C2 VodafoneZiggo Internal


C2 VodafoneZiggo Internal


C2 VodafoneZiggo Internal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.blueonyx.it/pipermail/blueonyx/attachments/20221111/998bcbe1/attachment.html>