[opensuse] Halp! After reboot, simple Leap 15.1 system stalls at grub2 with hd0 error
Something like invalid read or write on (hd0) and something about ramdisk and you need to load kernel first or something. What happened? Some dracut updates or whatever and and I needed to do maintenance on my power supply here, and after the start up of this system it is in this limbo state now. Sigh :( Any helpers? What can I do? I think I have pretty simple swap, / and /home three partitions, thats all. Simple mbr disk. What now? And even more interestingly, WHY oh WHY? :( Is this some known issue with recent boot/disk related updates and patches? I always do zypper ref zypper up Eventually this system got itself a shutdown and now the boot up attempt totally fails :( Thanks for helping. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-09-05 11:04, cagsm wrote:
Something like invalid read or write on (hd0) and something about ramdisk and you need to load kernel first or something.
What happened? Some dracut updates or whatever and and I needed to do maintenance on my power supply here, and after the start up of this system it is in this limbo state now.
Something failed during the last update, perhaps. Can you try boot previous kernel, perhaps? -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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.
What happened? Some dracut updates or whatever and and I needed to do maintenance on my power supply here, and after the start up of this system it is in this limbo state now.
Sigh :( Any helpers? What can I do?
I think I have pretty simple swap, / and /home three partitions, thats all. Simple mbr disk.
What now? And even more interestingly, WHY oh WHY? :(
Is this some known issue with recent boot/disk related updates and patches?
I always do zypper ref zypper up
Eventually this system got itself a shutdown and now the boot up attempt totally fails :(
Thanks for helping. Eh, I guess you mean 15.0 ... It's going to be a while before 15.1 reaches a more stable state.
If it is 15.0, can you boot a previous kernel? Can't you fix it by booting from an install medium, then do some bind mounts, and chroot into the system? It looks like dracut / initrd did not finish properly. -- 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
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. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
On Wed, Sep 5, 2018 at 5:43 PM Knurpht-openSUSE <knurpht@opensuse.org> 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
Le 05/09/2018 à 17:47, cagsm a écrit :
Or are there more steps inside yast, and next to yast that I need to execute?
what I would test would be "zypper up" to try repairing a failed install, and/or yast boot setup, change delay time (to force reinstall) and accept jdd -- http://dodin.org -- 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 <knurpht@opensuse.org> 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 2018-09-05 11:29, cagsm wrote:
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.
<http://download.opensuse.org/distribution/leap/15.0/live/openSUSE-Leap-15.0-Rescue-CD-x86_64-Current.iso> Try that one. Basically, mount your root, bind mount /proc, /dev/ and /sys mount --bind /proc /mnt/proc mount --bind /sys /mnt/sys mount --bind /dev /mnt/dev then "chroot /mnt" and run yast in text mode in that terminal. In yast, go to the boot section and simply change the number of seconds it waits for your input, that forces it to write it all again to disk. Watch out for errors on the road. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas)) -- 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 <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.
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
Hi Am 05.09.2018 um 17:29 schrieb cagsm:
it more precisely said that it were about to read or write outside of hd0, that sounded weird to me.
interesting, i installed a plain new tumbleweed at the last weekend on a second drive of a tumbleweed installation, this one without graphic, (at installer go to custom and then do not add anything) after install i have made a: partprobe -s and i got also a message like yours, something like: "error, try to read/write outside of the drive." the exact message i do not remember, if from interest, i could maybe check at the weekend. -> but my system is booting fine. simoN -- www.becherer.de -- 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 <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.
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
participants (7)
-
cagsm -
Carlos E. R. -
don fisher -
jdd＠dodin.org -
Knurpht-openSUSE -
Per Jessen -
Simon Becherer