 |
screenshot Capture.PNG (71,372 bytes) |
 |
The referenced RHBZ now has a comment that says: the workaround is to add a harmless (useless) extra arg to virt-install, like “--extra-args ro” Can you try it and see if that works? |
|
|
Hello. Great.. I've tried those extra args to the virt-install and it went through! perfect, thanks. virt-install command with parameters for the reference: virt-install --name centos8 --ram 4096 --disk path=/dev/zvol/zssd/vm/centos8-disk0,cache=none,bus=virtio --vcpus 1 --os-type linux --os-variant rhel7 --network network=private,model=virtio --location=/var/lib/libvirt/images/CentOS-8-x86_64-1905-dvd1.iso --graphics vnc --extra-args ro |
|
|
I have the same issue on an upgrade from 7.7 to 8. What i found was that the files in the rpm targeted to be copied to the /boot directory are not extracted: [root@centosd51b ~]# rpm -ql kernel-core-4.18.0-147.5.1.el8_1.x86_64.rpm | head -10 /boot/.vmlinuz-4.18.0-147.5.1.el8_1.x86_64.hmac /boot/System.map-4.18.0-147.5.1.el8_1.x86_64 /boot/config-4.18.0-147.5.1.el8_1.x86_64 /boot/initramfs-4.18.0-147.5.1.el8_1.x86_64.img /boot/symvers-4.18.0-147.5.1.el8_1.x86_64.gz <<<<<<<<<<<<<<< /boot/vmlinuz-4.18.0-147.5.1.el8_1.x86_64 When verifying with rpm2cpio you see that these are not listed. [root@centosd51b ~]# rpm2cpio kernel-core-4.18.0-147.5.1.el8_1.x86_64.rpm | cpio -id | head -10 cpio: ./etc/ld.so.conf.d/kernel-4.18.0-147.5.1.el8_1.x86_64.conf not created: newer or same age version exists cpio: ./lib/modules/4.18.0-147.5.1.el8_1.x86_64/.vmlinuz.hmac not created: newer or same age version exists cpio: ./lib/modules/4.18.0-147.5.1.el8_1.x86_64/System.map not created: newer or same age version exists cpio: ./lib/modules/4.18.0-147.5.1.el8_1.x86_64/bls.conf not created: newer or same age version exists cpio: ./lib/modules/4.18.0-147.5.1.el8_1.x86_64/build not created: newer or same age version exists cpio: ./lib/modules/4.18.0-147.5.1.el8_1.x86_64/config not created: newer or same age version exists etc ect.... The extract failure can be verified by manually reinstalling the kernel-core package [root@centosd51b ~]# rpm --reinstall ./kernel-core-4.18.0-147.5.1.el8_1.x86_64.rpm Symvers dump file /boot/symvers-4.18.0-147.5.1.el8_1.x86_64.gz not found <<<<<<<<<<<<<<<<<<< warning: %posttrans(kernel-core-4.18.0-147.5.1.el8_1.x86_64) scriptlet failed, exit status 1 When manually extracting the symvers archive with rpm2cpio I end up with a zero-byte file: I don't know if the rpm was incorrectly build or not: [root@centosd51b ~]# rpm2cpio kernel-core-4.18.0-147.5.1.el8_1.x86_64.rpm | cpio -iv --to-stdout /boot/symvers-4.18.0-147.5.1.el8_1.x86_64.gz > symvers-4.18.0-147.5.1.el8_1.x86_64.gz 54346 blocks [root@centosd51b ~]# ll symvers-4.18.0-147.5.1.el8_1.x86_64.gz -rw-r--r-- 1 root root 0 Feb 19 17:32 symvers-4.18.0-147.5.1.el8_1.x86_64.gz [root@centosd51b ~]# If anyone has any ideas that would be great as I cannot boot into Centos 8 at the moment and I'm worried that the box needs to be reimaged. As I'm 2000 miles away from it that might take a while. :-( thanks for your feedback. |
|
|
I'm trying to debug the same issue. The symvers file is actually in the RPM, it's just in /lib/modules/4.18.0-147.5.1.el8_1.x86_64/symvers.gz. I'm not sure what's supposed to copy it to /boot, though. |
|
|
The RPM process should just unpack the files into the respective directory as shown in the package. So there should be a symvers.gz in the /boot directory. The "post-script" in the rmp should just take care of the housekeeping that is associated with these files. (Running depmod etc...) What I find strange is that the files that should be extracted from the rpm simply doesn't seem to happen. If I create a bogus symvers.gz in the /boot directory I can see the rpm process moving further but obviously still failing later in the install process. The package maintainer should be able to diagnose this. |
|
|
It looks like the issue is resolved and a fixed package has been published. If you do a dnf update it should progress further now. At least it did in my setup. Cheers Erwin |
|
|
I fixed this issue by increasing the /boot partition size to 500MB. |
|
|
Solution : -- Download kernel-core-4.18.0-408.el8.x86_64.rpm and just Execute This commands. # rpm2cpio kernel-core-4.18.0-408.el8.x86_64.rpm | cpio -iv --to-stdout /boot/symvers-4.18.0-408.el8.x86_64.gz > symvers-4.18.0-408.el8.x86_64.gz # cp symvers-4.18.0-408.el8 /boot # rpm --reinstall kernel-core-4.18.0-408.el8.x86_64.rpm -- Verify new kernel installation on /boot |
- Anonymous
