• Content Count

  • Joined

  • Last visited

Everything posted by PEW

  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
  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 differ
  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: 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)
  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.
  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.