Jump to content

0jay

Members
  • Posts

    45
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Melbourne Australia

Recent Profile Visitors

1314 profile views
  1. Thanks for the reply! I bought used and had no luck at all getting things running (this was some time ago and things are hazy). Have you written up your experience anywhere I could look at? Sent from my iPhone using Tapatalk
  2. I was having some pretty substantial problems with several different builds before developing this hold pattern, Werner
  3. If I hold those packages I don't see any issues at all.
  4. it's a headless unit, Werner. if i can't ssh in then i just use an older build.
  5. bout to try th latest 25.8.2 Edit: still no good – connection refused
  6. may not help you (i'm running the pi4 build) but i find that putting holds on rpi-eeprom, raspi-firmware and raspberrypi-sys-mods from first boot solves this problem
  7. Actually using a zero2w but same image obv as rpi4... unable to login (refused ssh). had to switch back to the 25.2.3 build
  8. Hi bschnei, wondering if you still have one of these units in service? I have a Mochabin box and hoped the espressobin image might be compatible but it sounds a lot like globalscale devices are just a lot of trouble without much success Thanks for your time. Oscar
  9. Freezing kernel upgrades just means you can stay with a stable kernel and an update command will leave your kernel as is (in this case remain on the current edge kernel while updating the rest of the system). It's easy to unfreeze and update when there's a new LTS kernel available.
  10. Hey pdieguez, I've layed out the process in the OMV forum here https://forum.openmediavault.org/index.php?thread/54000-catastrophic-wireguard-install/&postID=403856#post403856
  11. Hi Igor, any developments with these pre-rolled images? Can I request a Renegade OMV image or will I need to wait for an LTS? Thanks for your time, Oscar
  12. Short summary of process to follow: I burn Armbian with Etcher, update etc and install OMV. From here I use armbian-install (or armbian-config) to transfer to the eMMC. This is the only tool I've found that makes the eMMC transfer simple (thank you!). The eMMC system boots and seems fine but OMV is not functional (though it works fine on the SD it was transferred from). As a result I always just transfer the raw Armbian install to eMMC, boot from there and install OMV direct to the eMMC but it would be very handy to be able to transfer from an SD with a working OMV install fully configured as backup.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines