OMV 3.0 after OMV 2.0

    • OMV 3.x

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

    • don't know what to tell you, I did run into grub issue that OP is getting. it was a VirtualBox running on OMV 3.0 that in turn run on Hyper-V VM. :) yeah , a nice nested dolls effect.

      and I could not install OMV 3.0 on that VM until I changed disk type to SCSI.
      it would run through the setup and on reboot go into grub rescue mode.
      when I used SCSI all went as expected and I had an
      OMV 3.0 setup
      ==> running in VitualBox VM,
      ==> running in OMV 3.0 setup
      ==>running in Hyper-V VM
      ==>running on my windows 10 pro workstation.

      how is that for nesting virtualization?
      omv 3.0.56 erasmus | 64 bit | 4.7 backport kernel
      SM-SC846(24 bay)| H8DME-2 |2x AMD Opteron Hex Core 2431 @ 2.4Ghz |49GB RAM
      PSU: Silencer 760 Watt ATX Power Supply
      IPMI |3xSAT2-MV8 PCI-X |4 NIC : 2x Realteck + 1 Intel Pro Dual port PCI-e card
      OS on 2×120 SSD in RAID-1 |
      DATA: 3x3T| 4x2T | 2x1T
    • as far as I understand , it is a VM bug, it is not really related to OMV so much but the way VB presents the drives to the system. the SATA "driver" is broken some how and the bug comes up now and then.
      as I said before, I had no problem setting up OMV 2 on the same VM that gave me issue with OMV 3. when using SATA driver.
      but both versions had no problem installing on SCSI. Same nested VM setup as above.

      something in the VB SATA driver and OMV 3.0 install drivers clash on occasion. since in my case it was just a test rig, I did not care. hence did not research to deeply.
      omv 3.0.56 erasmus | 64 bit | 4.7 backport kernel
      SM-SC846(24 bay)| H8DME-2 |2x AMD Opteron Hex Core 2431 @ 2.4Ghz |49GB RAM
      PSU: Silencer 760 Watt ATX Power Supply
      IPMI |3xSAT2-MV8 PCI-X |4 NIC : 2x Realteck + 1 Intel Pro Dual port PCI-e card
      OS on 2×120 SSD in RAID-1 |
      DATA: 3x3T| 4x2T | 2x1T
    • We'll now I am lost , the only thing I am thinking now is to try a straight debian install to see if it works.

      Sent from my SGH-T889 using Tapatalk
      omv 3.0.56 erasmus | 64 bit | 4.7 backport kernel
      SM-SC846(24 bay)| H8DME-2 |2x AMD Opteron Hex Core 2431 @ 2.4Ghz |49GB RAM
      PSU: Silencer 760 Watt ATX Power Supply
      IPMI |3xSAT2-MV8 PCI-X |4 NIC : 2x Realteck + 1 Intel Pro Dual port PCI-e card
      OS on 2×120 SSD in RAID-1 |
      DATA: 3x3T| 4x2T | 2x1T
    • I guess I am going to have to install Virtualbox somewhere and test this. Never had this problem with multiple Debian and Ubuntu installs on virtualbox.
      omv 4.0.5 arrakis | 64 bit | 4.12 backports kernel | omvextrasorg 4.0.2
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      I guess I am going to have to install Virtualbox somewhere and test this. Never had this problem with multiple Debian and Ubuntu installs on virtualbox.
      I only have it once. myself. and it was on OMV 3.0.20
      I had not tried it with later versions as I do not need it at the moment.

      as per my google research at the time, it is/was bug in VB on Debian 8 only.
      other distros like Ubuntu , Mint, CentOS... did not have it.

      I found the tip to use SCSI instead of SATA on one of the forum google dredged up,
      there were a discussion and someone said that he had no issues with his install, but that he used SCSI hdd, it was said that it worked, so I tried it and sure enough no issue with install. once it worked I was fine form my testing.

      the only similar issue I ever had was with Hyper-V VMs. most often than none if I use Gen2 VM for Linux I have problem either with install(will not install, or even boot from install ISO)
      or with grub boot after install (just like the OP).
      but that is on Hyper-V and only with Gen2 VM. something with Secure Boot implementation
      omv 3.0.56 erasmus | 64 bit | 4.7 backport kernel
      SM-SC846(24 bay)| H8DME-2 |2x AMD Opteron Hex Core 2431 @ 2.4Ghz |49GB RAM
      PSU: Silencer 760 Watt ATX Power Supply
      IPMI |3xSAT2-MV8 PCI-X |4 NIC : 2x Realteck + 1 Intel Pro Dual port PCI-e card
      OS on 2×120 SSD in RAID-1 |
      DATA: 3x3T| 4x2T | 2x1T
    • Using sata on Virtualbox:

      install OMV 2.1 from sourceforge iso

      Shell-Script

      1. omv-update
      2. apt-get clean
      3. update-initramfs -u
      4. update-grub
      5. reboot
      6. touch /etc/apt/apt.conf
      7. omv-release-upgrade
      8. # get normal dbus error
      9. update-initramfs -u
      10. update-grub
      11. reboot
      12. apt-get -f install
      13. # get sed error that still needs to be fixed -purge OMV package to fix but not a good option for upgraders
      14. dpkg -P openmediavault
      15. apt-get install openmediavault
      16. apt-get clean
      17. apt-get autoremove
      18. update-initramfs -u
      19. update-grub
      20. reboot
      Display All

      no grub or booting issues. I think the update-initramfs and update-grub commands are important.
      omv 4.0.5 arrakis | 64 bit | 4.12 backports kernel | omvextrasorg 4.0.2
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • So, i followed your steps....and i again get grub rescue


      Source Code

      1. Updating configuration ...
      2. Failed to get D-Bus connection: Unknown error -1
      3. Failed to get D-Bus connection: Unknown error -1
      4. Failed to get D-Bus connection: Unknown error -1
      5. Clearing symlinks in /etc/ssl/certs...done.
      6. Updating certificates in /etc/ssl/certs... 174 added, 0 removed; done.
      7. Running hooks in /etc/ca-certificates/update.d....done.
      8. Failed to get D-Bus connection: Unknown error -1
      9. dpkg: error processing package openmediavault (--configure):
      10. subprocess installed post-installation script returned error exit status 1
      11. Processing triggers for libc-bin (2.19-18+deb8u6) ...
      12. Processing triggers for systemd (215-17+deb8u5) ...
      13. Processing triggers for resolvconf (1.76.1) ...
      14. Processing triggers for ca-certificates (20141019+deb8u1) ...
      15. Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done.
      16. Running hooks in /etc/ca-certificates/update.d....done.
      17. Processing triggers for initramfs-tools (0.120+deb8u2) ...
      18. update-initramfs: Generating /boot/initrd.img-4.7.1
      19. W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
      20. W: mdadm: no arrays defined in configuration file.
      21. Errors were encountered while processing:
      22. openmediavault
      23. Creating index of upgradeable packages ...
      24. Creating index of openmediavault plugins ...
      25. E: Sub-process /usr/bin/dpkg returned an error code (1)
      26. root@openmediavault:~# update-initramfs -u
      27. update-initramfs: Generating /boot/initrd.img-4.7.1
      28. W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
      29. W: mdadm: no arrays defined in configuration file.
      30. root@openmediavault:~# update-grub
      31. Generating grub configuration file ...
      32. Linux-Abbild gefunden: /boot/vmlinuz-4.7.1
      33. initrd-Abbild gefunden: /boot/initrd.img-4.7.1
      34. Linux-Abbild gefunden: /boot/vmlinuz-4.7.0-rc3-fts-amd64
      35. initrd-Abbild gefunden: /boot/initrd.img-4.7.0-rc3-fts-amd64
      36. Linux-Abbild gefunden: /boot/vmlinuz-3.16.0-4-amd64
      37. initrd-Abbild gefunden: /boot/initrd.img-3.16.0-4-amd64
      38. Linux-Abbild gefunden: /boot/vmlinuz-3.16.0-0.bpo.4-amd64
      39. initrd-Abbild gefunden: /boot/initrd.img-3.16.0-0.bpo.4-amd64
      40. Linux-Abbild gefunden: /boot/vmlinuz-3.2.0-4-amd64
      41. initrd-Abbild gefunden: /boot/initrd.img-3.2.0-4-amd64
      42. erledigt
      43. root@openmediavault:~# reboot
      Display All
      Latest OMV 2 with omv extras removed....
    • You might have to remove those custom kernels but I haven't tried. You won't need those kernels once you are on OMV 3.x since you can install the backports 4.7 kernel.
      omv 4.0.5 arrakis | 64 bit | 4.12 backports kernel | omvextrasorg 4.0.2
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • epicfail wrote:

      Can you tell me how to remove them right?
      I assume you used dpkg -i to install them? Use dpkg -R to purge them.

      epicfail wrote:

      Is this also required on my real Nas?
      No idea. I don't know why you are using those kernels and I haven't tested this situation. So, I really can't answer it. Clone the OS drive and try it.
      omv 4.0.5 arrakis | 64 bit | 4.12 backports kernel | omvextrasorg 4.0.2
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • So, i´ve removed all 4.x kernels with dpkg -r and dpkg --purge

      After that i got the same error as above and again the grub rescue screen.

      So i´ve made a new virtual machine and installed omv 2 from scratch.....problem is i cant enable ssh....get an error something with dirty modules json....or so.

      It´s annoying :D

      EDIT: Fixed the dirtymodules error....and update works with your steps from above.

      So, how to update my real system with keeping the current configuration?

      The post was edited 1 time, last by epicfail ().

    • epicfail wrote:

      how to update my real system with keeping the current configuration?
      I would update the system. If you get the grub rescue screen again, boot the debian jessie netinst iso and boot into rescue mode. Then do a grub-install /dev/sdX (replace sdX with your OS drive), update-grub, then update-initramfs -u. I would imagine that should fix the grub issue.
      omv 4.0.5 arrakis | 64 bit | 4.12 backports kernel | omvextrasorg 4.0.2
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • Most likely. It is possible that it could be different when you boot the debian image. I would look at the output of fdisk -l to make sure. If you install grub on the wrong disk, it won't hurt the disk but it won't fix your problem either.
      omv 4.0.5 arrakis | 64 bit | 4.12 backports kernel | omvextrasorg 4.0.2
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!