Al - can you append the entries for the kernel update from "/var/log/messages" when your kernel update actually took place - see the discussion with MCB as to what we are looking for...

You could try "yum downgrade kernel && yum update kernel". You may need to use kernel* instead of kernel. Or perhaps do "yum reinstall kernel*"

Tony Ellis wrote:

Al

my log partition of 8gb was completely full

Separate partition just for logs? (/var/log/messages), for var? or in fact was this really the root partition? Please clarify - "df -Th"

Here is a log file (messages) filtered to dracut. It appears there were issues.

Thanks for any suggestions.

Tony Ellis wrote:

Al

my log partition of 8gb was completely full

Separate partition just for logs? (/var/log/messages), for var? or in fact was this really the root partition? Please clarify - "df -Th"

I have a separate partition just for logs. See image.

It appears that a reboot happened in the middle of dracut installing the initramfs file, which caused the file to not be created. We were having hardware issues at the time, which resulted in replacing the main board. The system was down for a week.

What is the procedure for reinstalling updates?

Yes - that's nothing more than just the yum.log - what we want is the content from /var/log/messages for the kernel install at about that time...
here's what was found here to illustrate. Sorry if wasn't clear - "check the others for anything during that same time-frame" meant check the other logs in /var/log for entries about that same time that the kernel was installed.

/var/log/yum.log

Mar 28 15:24:41 Installed: kernel-3.10.0-514.10.2.v7.x86_64



/var/log/messages

Mar 28 15:24:41 alex kernel: blk_update_request: I/O error, dev fd0, sector 0

Mar 28 15:24:41 alex yum[20555]: Installed: kernel-3.10.0-514.10.2.v7.x86_64

Mar 28 15:24:45 alex dracut: dracut-

Mar 28 15:24:45 alex dracut: Executing: /sbin/dracut -f /boot/initramfs-3.10.0-514.10.2.v7.x86_64.img 3.10.0-514.10.2.v7.x86_64

Mar 28 15:24:46 alex dracut: dracut module 'busybox' will not be installed, because command 'busybox' could not be found!

Mar 28 15:24:46 alex dracut: dracut module 'multipath' will not be installed, because command 'multipath' could not be found!

Mar 28 15:24:47 alex dracut: dracut module 'iscsi' will not be installed, because command 'iscsistart' could not be found!

Mar 28 15:24:47 alex dracut: dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found!

Mar 28 15:24:47 alex dracut: 95nfs: Could not find any command of 'rpcbind portmap'!

Mar 28 15:24:47 alex dracut: dracut module 'busybox' will not be installed, because command 'busybox' could not be found!

Mar 28 15:24:48 alex dracut: dracut module 'multipath' will not be installed, because command 'multipath' could not be found!

Mar 28 15:24:48 alex dracut: dracut module 'iscsi' will not be installed, because command 'iscsistart' could not be found!

Mar 28 15:24:48 alex dracut: dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found!

Mar 28 15:24:48 alex dracut: 95nfs: Could not find any command of 'rpcbind portmap'!

Mar 28 15:24:48 alex dracut: *** Including module: bash ***

Mar 28 15:24:48 alex dracut: *** Including module: nss-softokn ***

Mar 28 15:24:48 alex dracut: *** Including module: i18n ***

Mar 28 15:24:49 alex dracut: *** Including module: network ***

Mar 28 15:24:52 alex dracut: *** Including module: ifcfg ***

Mar 28 15:24:52 alex dracut: *** Including module: drm ***

Mar 28 15:24:55 alex dracut: *** Including module: plymouth ***

Mar 28 15:24:57 alex dracut: *** Including module: kernel-modules ***

Mar 28 15:25:20 alex dracut: *** Including module: resume ***

Mar 28 15:25:20 alex dracut: *** Including module: rootfs-block ***

Mar 28 15:25:21 alex dracut: *** Including module: terminfo ***

Mar 28 15:25:21 alex dracut: *** Including module: udev-rules ***

Mar 28 15:25:24 alex dracut: Skipping udev rule: 91-permissions.rules

Mar 28 15:25:24 alex dracut: *** Including module: biosdevname ***

Mar 28 15:25:24 alex dracut: *** Including module: systemd ***

Mar 28 15:25:26 alex dracut: *** Including module: usrmount ***

Mar 28 15:25:26 alex dracut: *** Including module: base ***

Mar 28 15:25:26 alex dracut: *** Including module: fs-lib ***

Mar 28 15:25:26 alex dracut: *** Including module: shutdown ***

Mar 28 15:25:26 alex dracut: *** Including modules done ***

Mar 28 15:25:26 alex dracut: *** Installing kernel module dependencies and firmware ***

Mar 28 15:25:27 alex dracut: *** Installing kernel module dependencies and firmware done ***

Mar 28 15:25:27 alex dracut: *** Resolving executable dependencies ***

Mar 28 15:25:31 alex dracut: *** Resolving executable dependencies done***

Mar 28 15:25:31 alex dracut: *** Hardlinking files ***

Mar 28 15:25:31 alex dracut: *** Hardlinking files done ***

Mar 28 15:25:31 alex dracut: *** Stripping files ***

Mar 28 15:25:32 alex dracut: *** Stripping files done ***

Mar 28 15:25:32 alex dracut: *** Generating early-microcode cpio image contents ***

Mar 28 15:25:32 alex dracut: *** Constructing AuthenticAMD.bin ****

Mar 28 15:25:32 alex dracut: *** Store current command line parameters ***

Mar 28 15:25:32 alex dracut: *** Creating image file ***

Mar 28 15:25:32 alex dracut: *** Creating microcode section ***

Mar 28 15:25:32 alex dracut: *** Created microcode section ***

Mar 28 15:25:58 alex dracut: *** Creating image file done ***

Mar 28 15:26:23 alex dracut: *** Creating initramfs image file '/boot/initramfs-3.10.0-514.10.2.v7.x86_64.img' done ***

As you can see - the last item was the initramfs created by dracut

Now what is in yours???

Mar 16 02:35:41 Updated: clearsdn-intrusion-protection-6.1-20170315.1100.noarch
Mar 16 05:43:51 Updated: kernel-tools-libs-3.10.0-514.10.2.v7.x86_64
Mar 16 05:43:52 Updated: kernel-tools-3.10.0-514.10.2.v7.x86_64
Mar 16 05:43:54 Updated: 1:app-base-core-2.3.30-1.v7.noarch
Mar 16 05:43:54 Updated: 1:app-base-2.3.30-1.v7.noarch
Mar 16 05:44:09 Installed: kernel-devel-3.10.0-514.10.2.v7.x86_64
Mar 16 05:44:18 Installed: kernel-3.10.0-514.10.2.v7.x86_64
Mar 16 05:44:19 Updated: python-perf-3.10.0-514.10.2.v7.x86_64
Mar 16 05:44:19 Updated: kernel-headers-3.10.0-514.10.2.v7.x86_64
Mar 18 01:53:45 Updated: 1:app-reports-database-core-2.3.1-1.v7.noarch
Mar 18 01:53:45 Updated: 1:app-proxy-report-core-2.3.1-1.v7.noarch
Mar 18 01:53:46 Updated: 1:app-software-updates-core-2.3.23-1.v7.noarch
Mar 18 01:53:46 Updated: 1:app-software-updates-2.3.23-1.v7.noarch
Mar 18 01:53:46 Updated: 1:app-proxy-report-2.3.1-1.v7.noarch
Mar 24 23:18:22 Updated: 1:app-network-core-2.3.24-1.v7.noarch
Mar 24 23:18:22 Updated: 1:app-flexshare-core-2.3.2-1.v7.noarch
Mar 24 23:18:22 Updated: 1:app-flexshare-2.3.2-1.v7.noarch
Mar 24 23:18:23 Updated: 1:app-network-2.3.24-1.v7.noarch

Al

my log partition of 8gb was completely full

Separate partition just for logs? (/var/log/messages), for var? or in fact was this really the root partition? Please clarify - "df -Th"

Hmm... would have just rebooted into an older kernel first and simply used yum to reinstall the new kernel...

Currently running kernel 3.10.0-514.2.2.v7.x86_64. Just now used yum to install the newer kernel - but not yet rebooted - have tests running don't want to disrupt..
However looks good- all five files are there - Community Edition btw

[root@alex boot]# ls -ladh /boot/* | grep '3.10.0-514.10.2.v7' 

-rw-r--r--  1 root root 135K Mar 11 02:14 /boot/config-3.10.0-514.10.2.v7.x86_64

-rw-------  1 root root  17M Mar 28 15:26 /boot/initramfs-3.10.0-514.10.2.v7.x86_64.img

-rw-r--r--  1 root root 272K Mar 11 02:18 /boot/symvers-3.10.0-514.10.2.v7.x86_64.gz

-rw-------  1 root root 3.0M Mar 11 02:14 /boot/System.map-3.10.0-514.10.2.v7.x86_64

-rwxr-xr-x  1 root root 5.2M Mar 11 02:14 /boot/vmlinuz-3.10.0-514.10.2.v7.x86_64

Small section of /etc/grub2.cfg

... clipped

### BEGIN /etc/grub.d/10_linux ###

menuentry 'ClearOS (3.10.0-514.10.2.v7.x86_64) 7 (Final)'  ... rest of line clipped

        load_video

        set gfxpayload=keep

        insmod gzio

... clipped

So like Nick should have no problems...
Here's an idea of the total space used - now 3 kernels - was 2

Before

Filesystem         Type      Size  Used Avail Use% Mounted on

/dev/sda1          xfs      1014M  140M  875M  14% /boot



After

Filesystem         Type      Size  Used Avail Use% Mounted on

/dev/sda1          xfs      1014M  165M  850M  17% /boot

It would appear that your install aborted for some reason - did you check if there was there any indication in the logs at the time of install of a failure? /var/log/yum.log will show when it was installed so you can check the others for anything during that same time-frame...

MCB wrote:

Attempts to boot with the latest kernel (3.10.0-514.10.2.v7.x86_64) that was automatically updated for 7.3 resulted in a kernel panic. After scratching our head/beating our head against a wall, we finally determined that the cause was a missing initramfs img file in /boot and a missing initrd entry in /boot/grub2/grub.cfg. We used dracut to generate the initramfs file and added the missing line in the grub.cfg file. All is now well.

Any chance that this will happen again after the next auto update of the kernel?

I think I ran into this today as well... did not have auto updates turned on and updated a ton today. I am guessing this was to the latest version. After I rebooted, the server did not come back online so when I got back to it, it was in a panic. I rebooted and was prompted to select the version I wanted to boot to. I selected the latest 3.10.0-514.10.2.v7.x86_64 and same thing... it hung and did not proceed to post. I selected the next latest version and it booted right up.

Another thing, my log partition of 8gb was completely full so I wiped it down to 30% 2.4gb to free up some space to prevent any issues.

Can someone please let me know what I need to do to make the server boot without fail if it is trying to automatically boot to the 3.10.0-514.10.2.v7.x86_64?

I am running a paid version of Home.

Thanks for any help!

/dev/mapper/clearos-root 456G 4.7G 452G 2% /
devtmpfs 3.9G 0 3.9G 0% /dev
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 3.9G 57M 3.9G 2% /run
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/sda1 497M 234M 264M 47% /boot
tmpfs 799M 0 799M 0% /run/user/991
tmpfs 799M 0 799M 0% /run/user/0

It should not happen and did not with mine - I rebooted a week or so ago. How much free space do you have in /boot?