On Wed, Sep 5, 2018 at 5:24 PM Knurpht-openSUSE 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. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Wed, Sep 5, 2018 at 5:43 PM Knurpht-openSUSE wrote:

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

Thanks for these steps, I basically remembered them roughly. But what do I do then afterwards inside yast. Yast doesnt magically repair boot problems, or is there a module to fix or recreate a simple boot config for a simple setup like mine? Or are there more steps inside yast, and next to yast that I need to execute? Thanks. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

cagsm wrote:

On Wed, Sep 5, 2018 at 5:43 PM Knurpht-openSUSE wrote:

...

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

Thanks for these steps, I basically remembered them roughly. But what do I do then afterwards inside yast. Yast doesnt magically repair boot problems, or is there a module to fix or recreate a simple boot config for a simple setup like mine?

Or are there more steps inside yast, and next to yast that I need to execute?

I don't know if yast can help you, I would recreate the initrd - mkinitrd -k <kernel> -i initrd and then reboot. -- Per Jessen, Zürich (23.3°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 09/05/2018 08:29 AM, cagsm wrote:

On Wed, Sep 5, 2018 at 5:24 PM Knurpht-openSUSE 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.

Look at bug 1105583. I cannot tell from your description if you are hitting the same thing I did. I have to use an older kernel until this is fixed, if ever. No response since posting on 8-27-2018, even though I requested updates. Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 09/05/2018 08:29 AM, cagsm wrote:

On Wed, Sep 5, 2018 at 5:24 PM Knurpht-openSUSE 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.

An experiment you could try is to set acpi=off on boot command line. That allowed my system to boot, but at reduced capability. Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org