Can't start virtualbox on omv3

    • Resolved
    • OMV 3.x
    • Maybe grub wasn't updated?? I don't know. What is the output of: update-grub and dpkg -l | grep linux-image
      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!
    • ryecoaaron wrote:

      Maybe grub wasn't updated?? I don't know. What is the output of: update-grub and dpkg -l | grep linux-image
      siulman@omv:/$ sudo update-grub
      [sudo] password for siulman:
      Generating grub configuration file ...
      Found linux image: /boot/vmlinuz-4.9.0-0.bpo.4-amd64
      Found initrd image: /boot/initrd.img-4.9.0-0.bpo.4-amd64
      done
      siulman@omv:/$ dpkg -l | grep linux-image
      ii linux-image-4.9.0-0.bpo.4-amd64 4.9.51-1~bpo8+1 amd64 Linux 4.9 for 64-bit PCs
      ii linux-image-amd64 4.9+80+deb9u2~bpo8+1 amd64 Linux for 64-bit PCs (meta-package)
      siulman@omv:/$



      [IMG:https://image.ibb.co/ibvLHw/image.png]
    • Your system definitely doesn't have the 3.2 kernel installed. I would guess update-grub is either finding kernels on other disks that are still bootable or your system is booting from a different disk than grub is writing to.
      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!
    • ryecoaaron wrote:

      Your system definitely doesn't have the 3.2 kernel installed. I would guess update-grub is either finding kernels on other disks that are still bootable or your system is booting from a different disk than grub is writing to.

      Well that's weird as:

      1) My system was installed from scratch yesterday so it's a brand new fresh OMV3 and not coming from an upgrade....
      2) Only one HDD is plugged into my system with an OS on it.

      So where is this coming from !?!? :-S
    • siulman wrote:

      So where is this coming from
      Well, it doesn't hurt anything but what is the output of: ls -al /boot/
      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!
    • ryecoaaron wrote:

      siulman wrote:

      So where is this coming from
      Well, it doesn't hurt anything but what is the output of: ls -al /boot/


      siulman@omv:/$ ls -al /boot/
      total 474548
      drwxr-xr-x 3 root root 4096 Dec 6 19:06 .
      drwxr-xr-x 23 root root 4096 Dec 6 19:41 ..
      -rw-rw-rw- 1 root root 170917888 Feb 17 2015 clonezilla-live-2.3.2-22-i686-pae.iso
      -rw-r--r-- 1 root root 186397 Oct 25 20:06 config-4.9.0-0.bpo.4-amd64
      -rw-rw-rw- 1 root root 282066944 Oct 20 2016 gparted-live-0.27.0-1-i686.iso
      drwxr-xr-x 5 root root 4096 Dec 6 19:46 grub
      -rw-r--r-- 1 root root 25514184 Dec 6 19:06 initrd.img-4.9.0-0.bpo.4-amd64
      -rw-r--r-- 1 root root 3184817 Oct 25 20:06 System.map-4.9.0-0.bpo.4-amd64
      -rw-r--r-- 1 root root 4039648 Oct 25 20:03 vmlinuz-4.9.0-0.bpo.4-amd64
      siulman@omv:/$
    • ryecoaaron wrote:

      Hmmm... What is the output of:

      df -h
      find / -name "vmlinuz-3.2*"

      siulman@omv:/$ df -h
      Filesystem Size Used Avail Use% Mounted on
      udev 10M 0 10M 0% /dev
      tmpfs 1.2G 15M 1.2G 2% /run
      /dev/sdd1 135G 2.5G 126G 2% /
      tmpfs 2.9G 4.0K 2.9G 1% /dev/shm
      tmpfs 5.0M 0 5.0M 0% /run/lock
      tmpfs 2.9G 0 2.9G 0% /sys/fs/cgroup
      tmpfs 2.9G 1.7M 2.9G 1% /tmp
      /dev/sda1 59G 39G 21G 66% /srv/dev-disk-by-label-VM
      /dev/sde1 1.8T 524G 1.3T 29% /srv/dev-disk-by-label-Backup
      /dev/sdb1 2.7T 375G 2.4T 14% /srv/dev-disk-by-label-Data
      /dev/sdc1 2.7T 780G 2.0T 29% /srv/dev-disk-by-label-Media



      siulman@omv:/$ sudo find / -name "vmlinuz-3.2*"
      [sudo] password for siulman:
      siulman@omv:/$



      Nothing...
    • siulman wrote:

      Nothing...
      I posted this on your other thread but I noticed you have your usb stick (/dev/sda) plugged in. That is where the 3.2 kernel entry is coming from.
      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!
    • ryecoaaron wrote:

      siulman wrote:

      Should I remove the 3.2.0 kernel that is still on my install? If yes how should I do it?
      According to your dpkg output above, the 3.2 kernel and headers are not installed on your system.

      Nop... the /dev/sda in an SSD drive plugged in my first sata slot just used as a “shared folder” dedicated to virtualbox VMs to take benefict from the quick disk.... it’s not an usb stick with an OS on it...
    • ssd or usb stick doesnt matter. Has it ever been used as a linux/omv boot drive? grub says the other kernel is on sda1 and that is what the ssd is.
      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!
    • ryecoaaron wrote:

      ssd or usb stick doesnt matter. Has it ever been used as a linux/omv boot drive? grub says the other kernel is on sda1 and that is what the ssd is.
      Indeed!
      The SSD was my OMV drive before migrating to the HDD 2.5. I just decided to keep the SSD for virtualbox to optimize the performance of my VMs but I did wipe it before !!! How is it possible it kept the grub? How can I wipe this without wiping my virtualbox VMs now? :)
    • Whatever wipe you did must have skipped the mbr. So update-grub is still picking up the old info. I wouldnt worry about it. doing something wrong would cause a lot
      more problems.
      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!
    • ryecoaaron wrote:

      Whatever wipe you did must have skipped the mbr. So update-grub is still picking up the old info. I wouldnt worry about it. doing something wrong would cause a lot
      more problems.
      Understood, so my primary system is clean, it’s just the MBR of my /dev/sda SSD. That’s curious....

      Maybe I can copy the content (virtualbox VMs) to a temporary folder of another hard drive, re-wipe it, and then re-copy the VMs? I am obssessed by having it clean... lol
    • siulman wrote:

      ryecoaaron wrote:

      Whatever wipe you did must have skipped the mbr. So update-grub is still picking up the old info. I wouldnt worry about it. doing something wrong would cause a lot
      more problems.
      Understood, so my primary system is clean, it’s just the MBR of my /dev/sda SSD. That’s curious....
      Maybe I can copy the content (virtualbox VMs) to a temporary folder of another hard drive, re-wipe it, and then re-copy the VMs? I am obssessed by having it clean... lol

      Quoting myself @ryecoaaron,

      I tried to wipe the MBR and the whole SDA1 disk but it didn't work. Then I even tried to physical disconnect the disk from the server and the "3.2.0" was still being showed up on the grub menu. I give up... I don't know where that thing comes from.