System disk does not boot

  • Hello

    Code
    [x86]SGX disabled by bios
    Timed out waiting for udev queue being empty

    Each time I restart omv7 after a week or when it fails i've got this message. I don't know how to permanently remove this message (and this behaviour).

    I tried Yannubuntu boot-repair (failed to install

    Traceback (most recent call last):

    File "/usr/bin/glade2script-python3", line 48, in <module>

    gi.require_version('Notify', '0.7')

    File "/usr/lib/python3/dist-packages/gi/__init__.py", line 126, in require_version

    raise ValueError('Namespace %s not available' % namespace)

    ValueError: Namespace Notify not available

    /usr/share/boot-sav/bs-cmd.sh: ligne 148 : hash: xhost : non trouv

    ).

    Here are the result of boot disk offline-immediate test

    I'm lost. Thank you for your help

    Edited 4 times, last by gretaM: re-building of the post ().

  • gretaM

    Changed the title of the thread from “System disk boots read-only” to “System disk does not boot”.
  • OK I managed to boot with 6.6.13 but the default linux image prevents me to access omv7


    Can I remove linux-image-6.7.12+bpo-amd64 or deactivate it in order to reboot my system from anywhere if it fails?

    Must I remove linux-headers too?


    Is there another solution or advice you can give me?

    ls -1 /boot/vmlinuz-*

    Code
    /boot/vmlinuz-5.5.0-0.bpo.2-amd64
    /boot/vmlinuz-5.6.0-0.bpo.2-amd64
    /boot/vmlinuz-5.7.0-0.bpo.2-amd64
    /boot/vmlinuz-5.8.0-0.bpo.2-amd64
    /boot/vmlinuz-5.9.0-0.bpo.2-amd64
    /boot/vmlinuz-5.9.0-0.bpo.5-amd64
    /boot/vmlinuz-6.5.0-0.deb12.4-amd64
    /boot/vmlinuz-6.6.13+bpo-amd64
    /boot/vmlinuz-6.7.12+bpo-amd64
  • Here's what I did

    I won't reboot until you tell me it's ok. Must I run sudo apt autoremove?

  • gretaM

    Added the Label resolved
    • Official Post

    I saw you were looking at my thread. Thank you!

    I wasn't quite sure what to tell you but it seemed as if it the original error seemed to be related to hardware and/or BIOS. I have an older server that, on one occasion, had an issue with a Debian 4 backports kernel that caused my CPU fans (dual Xeon's) to run at full speed all the time. I suspected it was related to BIOS or the generation of CPU which (if it was to be corrected) would have to be addressed up stream. As it turned out, an older kernel fixed the problem until a newer kernel version came out.

    With the above in mind, in your case, I was thinking about recommending:
    1. Installing OMV-Extras 
    Note: Before installing the following plugin; use System, Update Management to update OMV and the OS.

    2. Under System Plugins, install the Kernel Plugin This plugin exists in OMV6 and OMV7.

    The Kernel Plugin will allow you to select any available Kernel to boot from and (after a kernel has been selected and booted into) it's possible to remove other kernels. (I would keep at least one old kernel, especially if it worked before. Kernels take up very little space and, sometimes, an old kernel is a fall back that might bail you out.)

    Depending on your hardware, BIOS and Debian kernel upgrades, the Kernel Plugin may be of use to you in the future. The additional one time utilities like Gparted, Clonzilla, or SystemRescue may be useful as well.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!