Jump to content

fscii

Members
  • Posts

    3
  • Joined

  • Last visited

  1. Looks like its fixed, giving it another shot now. Meanwhile I have to ask you, from armbian commandline does "reboot" command work and reboot for you? For me it just powers off and I need to power cycle it. I used to use a cron job in omv to reboot once a week but now I can't even do it from the command line. Nevermind, figured it out. And the script fix got OMV6 operational!
  2. It is not limited to Armbian. I tried ODROID's version of debian 11 (See report here: https://forum.odroid.com/viewtopic.php?f=203&t=45228&p=355103#p355103 ). I was able to actually get into omv, configure it (I didn't touch eth0 sadly) and upon reboot = DOA. Also there's an open issue now on github omv (Armbian flavor) https://github.com/OpenMediaVault-Plugin-Developers/installScript/issues/106
  3. I do not have petitboot installed. I ran the Armbian buster with OMV5 for over a year. I decided to make a clean install and booted Armbian bullseye 11. I changed hostname and rebooted (curiously reboot doesn't reboot the hc4, why?). I used armbian-config to install OMV. Installation completed, brought me back to armbian-config and prompted to reboot. I hit reboot (then was forced to power cycle as hc4 won't come back to life after a soft-boot?). Note that I was able to power cycle and get a good boot BEFORE omv installed but not after. At that point Odroid hc4 never comes back online. I've been through this 3 times today. I gave it as long as 30 minutes but doesn't respond even to pings. It does get the blue led blinking denoting successful kernel load. How do I get past this?! (I've tried with and without armbian-config's update upgrade with firmware, the full firmware option etc) Nothing is working. Any and all help is greatly appreciated.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines