Upgrade wheezy to jessie and omv 2.x to 3.x

    • OMV 2.x
    • Resolved
    • Update

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

    • Upgrade wheezy to jessie and omv 2.x to 3.x

      Hello everyone,

      first of all, big thanks to the OMV team and all the supporters to make OMV such an awesome system which is running stable for 2 years at my home!

      I just saw that OMV 3 has been released. Since i wanted to upgrade my debian to jessie for quite some time - i'm super excited about this. So i was searching this forum and the omv-wiki for a guide to upgrade wheezy to jessie and OMV 2.x to 3.x. Since i wasn't able to find anything i hope i can get some support here.

      Right now i'm running

      Source Code

      1. ================================================================================
      2. = OS/Debian information
      3. ================================================================================
      4. Distributor ID: debian
      5. Description: Debian GNU/Linux 7 (wheezy)
      6. Release: 7.11
      7. Codename: wheezy
      8. ================================================================================
      9. = openmediavault information
      10. ================================================================================
      11. Release: 2.2.13
      12. Codename: Stone burner
      13. ================================================================================
      14. = System information
      15. ================================================================================
      16. Linux NAS 3.2.0-4-amd64 #1 SMP Debian 3.2.82-1 x86_64 GNU/Linux
      Display All

      Status quo i would do following:

      1. Debian upgrade: howtoforge.com/tutorial/how-to…to-jessie-stable-release/

      2. OMV upgrade: omv-release-upgrade

      Question is, if this is as save as an upgrade can be or if i should to the upgrade in a different way? Basically i would like to upgrade the system with minimum effort of re-configuring everything, try to prevent clean installs.

      Thank you for your help in advance!


      (BTW there is no upgrade label yet for "2 -> 3"?)

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

    • So i've used "omv-release-upgrade" to upgrade the system and rebooted.

      But now the system is always booting into emergency mode and i don't get out there.
      A "systemctl default" after login in to the emergency shell gets me stuck at "INFO: task (plymouth): 1230 blocked for more than 120 seconds."

      I thought the filesystem would be corrupted so i ran a fsck with an rescue usb but it didn't solved my problem.

      Hopefully anyone has a suggestion?

      ------ EDiT -----

      So after 5h of research and trying to fix it, i've found a fix: unix.stackexchange.com/questio…n-plymouth-debian-testing

      basically i removed everything from /etc/fstab except the debian disc. But now i can't mount my raid anymore.

      Does anyone now how to adjust my fstab?

      Source Code

      1. # /etc/fstab: static file system information.
      2. #
      3. # Use 'blkid' to print the universally unique identifier for a
      4. # device; this may be used with UUID= as a more robust way to name devices
      5. # that works even if disks are added and removed. See fstab(5).
      6. #
      7. # <file system> <mount point> <type> <options> <dump> <pass>
      8. # / was on /dev/sda1 during installation
      9. UUID=e7146065-a39c-44ce-9121-640b4926a3b7 / ext4 noatime,nodiratime,discard,noatime,nodiratime,discard,errors=remount-ro 0 1
      10. # swap was on /dev/sda5 during installation
      11. UUID=a693916f-cda3-4111-86a5-99771a662b18 none swap sw 0 0
      12. /dev/sdb1 /media/usb0 auto rw,user,noauto 0 0
      13. # >>> [openmediavault]
      14. UUID=64c8ec70-528a-4817-a69b-096d85b6c0e9 /media/64c8ec70-528a-4817-a69b-096d85b6c0e9 ext4 defaults,nofail,acl,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0 0 2
      15. /media/64c8ec70-528a-4817-a69b-096d85b6c0e9/box/ /export/box none bind 0 0
      16. # <<< [openmediavault]
      17. tmpfs /tmp tmpfs defaults 0 0
      Display All

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

    • I was able to fix everything now by adjusting the fstab like following:

      Source Code

      1. # /etc/fstab: static file system information.
      2. #
      3. # Use 'blkid' to print the universally unique identifier for a
      4. # device; this may be used with UUID= as a more robust way to name devices
      5. # that works even if disks are added and removed. See fstab(5).
      6. #
      7. # <file system> <mount point> <type> <options> <dump> <pass>
      8. # / was on /dev/sda1 during installation
      9. UUID=e7146065-a39c-44ce-9121-640b4926a3b7 / ext4 noatime,nodiratime,discard,noatime,nodiratime,discard,errors=remount-ro 0 1
      10. # swap was on /dev/sda5 during installation
      11. UUID=a693916f-cda3-4111-86a5-99771a662b18 none swap sw 0 0
      12. /dev/sdb1 /media/usb0 auto rw,user,noauto 0 0
      13. # >>> [openmediavault]
      14. UUID=64c8ec70-528a-4817-a69b-096d85b6c0e9 /media/64c8ec70-528a-4817-a69b-096d85b6c0e9 ext4 noauto,nofail,acl,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0 0 2
      15. /media/64c8ec70-528a-4817-a69b-096d85b6c0e9/box/ /export/box none bind 0 0
      16. # <<< [openmediavault]
      17. tmpfs /tmp tmpfs noauto 0 0
      Display All