Hello
I have been struggling to get kernel 553 working. The 513 kernel works fine on the same machine. I have noticed in the boot.log that the /boot/efi is not mounting for the 553
but does mount for the 513 kernel.
I presume that the /boot/efi is essential to a system booting properly. Would this explain why my 553 boot goes straight to a black screen? Is there a way to correct this?
Any thoughts are most welcome.
It appears that the initramfs for that kernel is incomplete and needs to be rebuilt. There could be other reasons like partition definitions in fstab defined by device names like sdax instead of by UUID. So assuming my first guess I would suggest reading the man page for the command dracut which is used to generate the initramfs. The basic command needed is:
dracut --kver <kernel-version>
or
dracut --force --kver <kernel-version>
Thank you for your suggestions
Below is the log. The log then goes into an extremely long list of symbols.
The above command does not solve my failed kernel mount of 553 not starting. Can you tell me if there is a log that covers the “handover” between the BIOS and the kernel?
Thank you
dracut: Executing: /usr/bin/dracut -v --force --kver 4.18.0-553.5.1.el8_10.x86_64
dracut: dracut module 'busybox' will not be installed, because command 'busybox' could not be found!
dracut: dracut module 'rngd' will not be installed, because command 'rngd' could not be found!
dracut: dracut module 'network-legacy' will not be installed, because command 'dhclient' could not be found!
dracut: dracut module 'btrfs' will not be installed, because command 'btrfs' could not be found!
dracut: dracut module 'dmraid' will not be installed, because command 'dmraid' could not be found!
dracut: memstrack is available
dracut: dracut module 'busybox' will not be installed, because command 'busybox' could not be found!
dracut: dracut module 'rngd' will not be installed, because command 'rngd' could not be found!
dracut: dracut module 'network-legacy' will not be installed, because command 'dhclient' could not be found!
dracut: dracut module 'btrfs' will not be installed, because command 'btrfs' could not be found!
dracut: dracut module 'dmraid' will not be installed, because command 'dmraid' could not be found!
dracut: *** Including module: bash ***
dracut: *** Including module: systemd ***
dracut: *** Including module: systemd-initrd ***
dracut: *** Including module: nss-softokn ***
dracut: *** Including module: i18n ***
dracut: *** Including module: network-manager ***
dracut: *** Including module: network ***
dracut: *** Including module: ifcfg ***
dracut: *** Including module: drm ***
dracut: *** Including module: plymouth ***
dracut: *** Including module: prefixdevname ***
dracut: *** Including module: dm ***
dracut: Skipping udev rule: 64-device-mapper.rules
dracut: Skipping udev rule: 60-persistent-storage-dm.rules
dracut: Skipping udev rule: 55-dm.rules
dracut: *** Including module: kernel-modules ***
I didn’t see anything wrong with the dracut output. The missing commands are as expected for Rocky.
Journalctl is the command to access all the logs. For the current boot you would use the format:
sudo journalctl -b
For the prior boot:
sudo journalctl -b -1
and so forth.
There are options to refine the search criteria as can be found in the man page.
Did you do the default install for Rocky 8 or did you do custom partitioning?
Might be an answer here on RH customer portal if you subscribe.
It’s basically saying someone might have disabled the FAT (or vfat) file systems as part of “security hardening”.
I don’t have Redhat access. This is a personal machine so if any “hardening” was done, it was by accident … and I have no idea how to do that anyway.
Below is my fstab for the partitioning. I don’t think it is very special.
#
# /etc/fstab
# Created by anaconda on Wed Aug 23 06:35:56 2023
#
# Accessible filesystems, by reference, are maintained under '/dev/disk/'.
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
#
# After editing this file, run 'systemctl daemon-reload' to update systemd
# units generated from this file.
#
/dev/mapper/rl_lowrocky00-root / xfs defaults 0 0
UUID=1b9daae2-f65f-49ac-9de8-7e51676964a0 /boot xfs defaults 0 0
UUID=8B40-5827 /boot/efi vfat umask=0077,shortname=winnt 0 2
/dev/mapper/rl_lowrocky00-home /home xfs defaults 0 0
/dev/mapper/rl_lowrocky00-swap none swap defaults 0 0
/dev/disk/by-uuid/49c57912-2bd6-4f31-a2b7-6df585bc9f40 /mnt/49c57912-2bd6-4f31-a2b7-6df585bc9f40 auto nosuid,nodev,nofail,x-gvfs-show 0 0
I have just downloaded the latest dnf upgrade that was offered to me this morning :
4.18.0-553.8.1.el8_10.x86_64
and now 553 works.
The mount boot/efi fail has disappeared
Within a very long list of updates, I noticed that it installed linux-firmware-20240111-121.gitb that I had never seen before.
Maybe it was this that was broken.
All very strange.
Thank you for all your help.
Just as an added note for others …
If like me, your machine is not keeping the multiple journalctl logs, you can activate the multiple log service by adding
Storage=persistent
SystemMaxUse=500M
SystemMaxFiles=5
to the conf file below.
sudo nano /etc/systemd/journald.conf
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.