• Content Count

  • Joined

  • Last visited

Reputation Activity

  1. Like
    PEW got a reaction from gprovost in Helios4 Buster using the older kernel version 4   
    @gprovost I described last year a process to upgrade from omv4 to omv5. (which is doable). I also did a clean install of omv5 after i was having random reboot issues using the newer kernel5. 
    I ended up using the clean built and reconfiguring all the services and dockers. I do not recommend using the newer kernel if you are using dockers. This is where I would have random system reboots. OMV4 was very stable but since omv4 was eol. I decided to upgrade or do a clean install. I did both with the same random reboots using the newer kernel 5. Once i switched back to the older kernel with my config, I was not having the random reboot issues. I understand this would be hard to replica because everyone has different configs. I am just trying to help anyone else that would be in this situation.
  2. Like
    PEW got a reaction from gprovost in Helios4 Support   
    Here is my guide to upgrade omv4to5. Hopefully this will help out others looking to do the same.
    Was able to upgrade omv4 to 5. Here is my posts and the github bash script from the omv site: I downloaded the scripts then changed to executable.
    Steps to reproduce:
    1. Remove incompatible plugins
    2. Switch over to dockers that are incompatible
    3. Download the two bash scripts:
    4. chmod +x the upgrade4to5 chmod +x install
    5. Run the upgrade4to5 as root
    6. omv and plugins will fail. as describes here:
    7. Remove failed packages not purge since we want config files from omv They should print out.
    8. Reinstall openmediavault only
    9. Reboot
    10. Run this command : apt-get purge openmediavault-omvextrasorg resolvconf
    11. Reboot again
    12. Run the install script as root. this will install omv extras.
    13. apt update
    14. apt dist-upgrade
    15. omv-salt deploy run nginx
    16. omv-salt deploy run phpfpm
    17. But remove or move upsschedule-cmd from usr/bin and bin then run  apt-get install usrmerge
    18. apt install docker
    The docker installer uses iptables for nat. Unfortunately Debian uses nftables. You can convert the entries over to nftables or just setup Debian to use the legacy iptables.
    sudo update-alternatives --set iptables /usr/sbin/iptables-legacy
    sudo update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy
    dockerd, should start fine after switching to iptables-legacy.
    sudo service docker start
    20. Switch to 5.4 kernel using armbian-config refer to kobol blog:
    Hopefully this helps others out.