Clean install openmediavault_3.0.36-i386 with following updates -> kernel panic with 3.16.0-6-686-pae and above

    • OMV 3.x
    • Update

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Clean install openmediavault_3.0.36-i386 with following updates -> kernel panic with 3.16.0-6-686-pae and above

      I am trying to prepare a new system on a virtual machine (virtual box, 32-bit, 1 GB RAM) based on the 3.0.36. I assume, this is the most recent 32-bit Openmediavault-ISO available.

      The initial setup runs smooth, however, updating this through the web-gui with all available updates, the underlying 3.16.0-4-686-pae is updated as well to 3.16.0-6.686-pae, which causes a kernel panic during reboot. The exit code is 0x0000000b, however I am not sure, if this helps a lot. By switching back to the initial kernel in the advanced options of grub, I can start the system as expected.

      Any ideas? For the 2.x this approach of setting up a test bench used to work.
    • locu wrote:

      I assume, this is the most recent 32-bit Openmediavault-ISO available.
      You can always install Debian and then OMV on top of that.
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Of course, however I assumed the other way would be the more direct and easy approach.

      In general I am confused, that an update within the Openmediavault-environment is actually breaking a running system and would have thought, that all packages updated within this environment are somehow harmonized.
    • locu wrote:

      I assumed the other way would be the more direct and easy approach.
      The 3.0.36 is an early release. So, I would actually think installing Debian would be better and less error prone.

      locu wrote:

      In general I am confused, that an update within the Openmediavault-environment is actually breaking a running system and would have thought, that all packages updated within this environment are somehow harmonized.
      OMV doesn't create the packages that are failing. Those are all Debian images. Generally Debian is very stable.
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!