Op woensdag 5 september 2018 17:29:30 CEST schreef cagsm:
On Wed, Sep 5, 2018 at 5:24 PM Knurpht-openSUSE <knurpht@opensuse.org> wrote:
Op woensdag 5 september 2018 17:04:52 CEST schreef cagsm:
Something like invalid read or write on (hd0) and something about ramdisk and you need to load kernel first or something.
it more precisely said that it were about to read or write outside of hd0, that sounded weird to me.
and yes you are right of course, it is opensuse leap 15.0
I have no other kernels I guess, as I tend to remove them once the systems work fine with the latest kernel. there were no kernel updates today that got applied on that system. only some buch of kde stuff or something.
it is running on some auto onlineupdate means via yast settings, daily interval.
systems had been up several days running nicely. last kernel had been some days or week(s) ago?
I think I need to take some bootable usb media to the machine with leap 15.0 iso and try to rescue mode and repair? chroot and mounting all the usual stuff? and then repair boot/mbr/grub how exactly? any hints? been long ago that I needed to repair stuff like this.
hope it is not disk error, s.m.a.r.t. didnt show trouble lately cant remember any troubles.
thanks. Let's say your rootfs is on /dev/sda1 ( you have to replace sda1 with the actual / mounted partition ), boot from an install medium, wait until the installer shows up, then hit Ctrl-Alt-F2. Next do: mount /dev/sda1 /mnt mount --bind /dev /mnt/dev mount --bind /proc /mnt/proc mount --bind /sys /mnt/sys chroot /mnt yast
Furthermore I strongly suggest not to remove all old kernels, they're your insurance against issues like you're having now. FWIW it's not just kernels that run dracut/initrd. Updates to f.e. ucode, udev, dracut itself trigger a rebuild of the initrd as well. -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org