https://bugzilla.suse.com/show_bug.cgi?id=1223609 https://bugzilla.suse.com/show_bug.cgi?id=1223609#c1 --- Comment #1 from andreas bittner --- being at the machine, physically, I can select from the grub2 menu at boot, apparently the older suse leap 15.5 kernels, although the lines show as leap 15.6 but with those 5.something kernels. i can boot the .52 kernel at the end, that was the last one this then-15.5 machine has gotten (i think some .59 kernel for 15.5 came out yesterday or so I remember), just fine with 15.6 apparently. i took the machine off from the network and it sits now standalone on the desk. I guess I could extract some zypper log files or something if anyone points me to? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1223609 https://bugzilla.suse.com/show_bug.cgi?id=1223609#c3 --- Comment #3 from andreas bittner --- using usb install media with 15.6 RC .iso file, booting up into upgrade mode and letting it upgrade, selects 8 packages only and about 200megabytes or such and installs along at the end when saving settings and bootloader stuff, it fails apparently with the same errors as in zypper logs given, that it cannot complete suse mkinitrd or something methinks. something like that. this didnt help. dunno whats wrong here the 15.5 was working a long time fine also kernel updates and opensuse patches via zypper up and all. maybe i try a fresh 15.5 and upgrade that to 15.6rc on this hardware? cant be that buggy? p.s. i have had 15.6rc installing normally fresh into a virtualbox simple setup though. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1223609 https://bugzilla.suse.com/show_bug.cgi?id=1223609#c5 --- Comment #5 from andreas bittner --- today I have tried to fix this machine via the 15.6rc media rescue bootentry, mounting / and /boot and adding sys dev proc and run and then chroot into the system I have tried to look into grub , grub_installdevice and those parts and it looks fine, the disk UUID and names and partitions etc all exist and make sense and are correct. inside chroot: firing up the yast on the commandline and making it re-install the boot setting rewrite MBR or bootstuff into the whole disk and the partition of /boot and all finishes without erros being shown from inside yast. the system doesnt boot after this either. rescue once again and then mkinitrd installs kind of multiple big blocks worth of kernel stuff (with log output) and at the end with the 6.4.0 kernel entry it seems to fail at the dracut step and prints the error to the screen, and this error seems to be in the log files I have provided as an attachment earlier. -------------- zypp-history-log-0000.txt-# dracut[E]: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.7LMEwP/initramfs -N ^i2o_scsi$ --kerneldir /lib/modules/5.14.21-150500.55.49-default/ -m pata_atiixp ahci ata_generic sata_nv pata_amd fan amd74xx ide_pci_generic reiserfs edd zypp-history-log-0000.txt:# dracut[F]: installkernel failed in module suse-initrd zypp-history-log-0000.txt-# warning: %postun(kernel-default-extra-5.14.21-150500.55.49.1.x86_64) scriptlet failed, exit status 1 --------------- it seems that I can not make this hosed system to boot any more even after repair attempts with the 6.4.x kernel entry thanks. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1223609 https://bugzilla.suse.com/show_bug.cgi?id=1223609#c8 --- Comment #8 from andreas bittner --- was curious about /etc/sysconfig/kernel file and on my test from scratch 15.5 and upgrade to 15.6rc there isnt even such a file at all any more thanks. -- You are receiving this mail because: You are on the CC list for the bug.