SolusVM KVM VPS boots with "not bootable device" in noVNC console: Kernel panic - not syncing

Have more questions? Submit a request

Applicable to:

  • SolusVM

Symptoms

  • SolusVM KVM VPS boots with "not bootable device" in noVNC console.

  • The following is shown at the end of SolusVM > Virtual Servers > VPS > Build Log:

    CONFIG_TEXT: ...
    [ 1.755629] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
    ...

  • Unable to list packages on the KVM Node where the affected VPS was created:

    # rpm -qa
    error: rpmdb: BDB0113 Thread/process 99506/140546427115584 failed: BDB1507 Thread died in Berkeley DB library
    error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
    error: cannot open Packages index using db5 - (-30973)
    error: cannot open Packages database in /var/lib/rpm
    error: rpmdb: BDB0113 Thread/process 99506/140546427115584 failed: BDB1507 Thread died in Berkeley DB library
    error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
    error: cannot open Packages database in /var/lib/rpm

Cause

Failure libguestfs utilites due to corrupted rpm database.

Resolution

  1. Access the affected SolusVM KVM node over SSH.

  2. Rebuild the rpm database:

    # mkdir ./backup/
    # cp -a /var/lib/rpm/__db* ./backup/
    # rm -f /var/lib/rpm/__db.[0-9][0-9]*
    # rpm --quiet -qa
    # rpm --rebuilddb
    # yum clean all

Articles in this section

Was this article helpful?
0 out of 0 found this helpful
Share

Comments

0 comments

Please sign in to leave a comment.