PEW

  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

PEW's Achievements

  1. @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. Thx
  2. @gprovost I went the upgrade path where i went from debian 9 to debian 10 so i could upgrade from omv4 to 5 using the omv upgrade script. After having random reboots after the upgrade, I did a clean install of debian 10 buster with omv5. I had no issues with reboots for about 20 days until i updated and reboot since then I am having random reboot after about 3 days. If the watchdog service is off, i will get hard lockups with a powercycle reboot so i kept the watchdog service on. It points to the orion watchdog service. Since omv5 has changed a couple things are different now: kernel, urbackup service is now a docker, cockpit, and portainer. i stopped the urbackup docker.. still had random reboots ~3 days. i decided to switch to the older 4.19.159 kernel now. I will see how it works. Other notes about armbian 20.11 @gprovost I have not had issues with going to the kernel 4.19.159 or greater @Igor The armbian-apt-updates located here: /usr/lib/armbian this bash script does not work on a clean build(it will not create the temp file needed for updates). I switched to the python script version from debian 9 so it will download updates. (Not sure why it switched) Also, the file in /etc/update-motd.d 30-armbian-sysinfo always gets changes when armbian is updated and i have to switch the STORAGE= variable to the correct storage i am using. Thanks Patrick
  3. @gprovost I rebuilt my helios4 with a clean buster build on another sd card and configured the dockers,services, etc. It seems to be a running better now. I would say to do not do a upgrade from omv4 to 5 even thou it is doable. The watchdog service will reboot a hardware watchdog for orion because it will crash somehow. My suggestion is for upgrade process is get another sd card and rebuilt using the old configs for the original sd card. Thanks
  4. @gprovost I will limp along until helios64 has second batch out.
  5. @gprovost I agree with you but I just had the system freeze and had to do a hard reboot(pull power plug/reinsert). I turned watchdog service back on to auto recover.
  6. @gprovost Yes. I did. i was also fixing other issues as well. Please read: https://forum.openmediavault.org/index.php?thread/31517-log2ram/&postID=250089#post250172 Trying to determine armbian issues vs. omv5 with cron and armbian scripts. Thanks
  7. Yes. It is running. I will disable. watchdog.service - watchdog daemon Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-09-09 09:24:25 EDT; 1 day 1h ago Process: 3723 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ "${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module (co Process: 3726 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec /usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS) Main PID: 3737 (watchdog) Tasks: 1 (limit: 4503) Memory: 752.0K CGroup: /system.slice/watchdog.service └─3737 /usr/sbin/watchdog Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. patrick@helios4-PW:~$ sudo systemctl status watchdog.service | more ● watchdog.service - watchdog daemon Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-09-09 09:24:25 EDT; 1 day 1h ago Process: 3723 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ "${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module (co de=exited, status=0/SUCCESS) Process: 3726 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec /usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS) Main PID: 3737 (watchdog) Tasks: 1 (limit: 4503) Memory: 752.0K CGroup: /system.slice/watchdog.service └─3737 /usr/sbin/watchdog Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
  8. I recently upgraded from omv4 to omv5 and after about two weeks into the upgrade i noticed the helios was rebooting randomly. It has been doing this since late June. I decided to replaced the hard disks due to the smartctl showing up red and replaced all 4 with good drives. During the raid rebuild process, I was getting random reboots as well until the final drive. I did run a fschk on the raid volume and fixed the file system. Random reboot are still happening. I looked at all the logs and could not find anything. I have not tried any stress tests or io tests. i was wondering if this has been an issue with others or is it best to revert to the legacy kernel(4.19). I am noticing a ERROR in u-boot in reserving fdt memory region failed (addr=2040000 size=6c000) then loading device tree ... OK then starting kernel. Any other ideas? Thanks
  9. 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. https://forum.openmediavault.org/index.php?thread/27909-omv-5-0-finally-out/&pageNo=2 https://forum.openmediavault.org/index.php?thread/27909-omv-5-0-finally-out/&pageNo=22 https://github.com/OpenMediaVault-Plugin-Developers/installScript/blob/master/upgrade4to5 https://forum.openmediavault.org/index.php?thread/33219-upgrade-to-5-x-failure/&pageNo=1 Steps to reproduce: 1. Remove incompatible plugins 2. Switch over to dockers that are incompatible 3. Download the two bash scripts: wget https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/upgrade4to5 wget https://github.com/OpenMediaVault-Plugin-Developers/packages/raw/master/install 4. chmod +x the upgrade4to5 chmod +x install 5. Run the upgrade4to5 as root 6. omv and plugins will fail. as describes here: https://forum.openmediavault.org/index.php?thread/33219-upgrade-to-5-x-failure/&pageNo=1 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 19. https://forums.docker.com/t/fa…te-nat-chain-docker/78269 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: https://blog.kobol.io/2020/03/13/armbian-new-release/ Hopefully this helps others out. Thanks