Jump to content

wolf7250

Members
  • Posts

    18
  • Joined

  • Last visited

  1. Hi @Igor, I'm attempting to update from OMV6 --> OMV7 and initially got the NO_PUBKEY error which I was able to resolve following the link that @Werner provided 🙂. I'm now getting the same unknown compression error as @binkerd dpkg-deb: error: archive '/var/cache/apt/archives/armbian-config_25.2.0-trunk.47.1118.163006_all.deb' uses unknown compression for member 'control.tar.zst', giving up dpkg: error processing archive /var/cache/apt/archives/armbian-config_25.2.0-trunk.47.1118.163006_all.deb (--unpack): dpkg-deb --control subprocess returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/armbian-config_25.2.0-trunk.47.1118.163006_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) I followed your link to the stack exchange post, but I'm not sure what to do to fix the problem? Do I need to edit the apt/sources.list/ and apt/sources.list.d/? Thanks!
  2. OK. Now this is actually solved. The issue was I was unknowingly using a legacy Buster armbian image. As soon as I tried it with a current Buster armbian image the bootloader picked it up and it installed and booted armbian.
  3. Also, if someone could please assist, I was unable to create this topic without a tag as it's a required field. But it wouldn't let me enter anything except for "solved" as the tag, which this definitely is not.
  4. First off, could someone please help. I did not seem to be able to create this topic without a tag and the only tag it would accept was "solved". Wondering if somebody could remove the "solved" tag and add in "odroidhc4"? I purchased a brand new odroid hc4 board with the intention of installing armbian and then subsequently OMV. My intention was/is to install Armbian on a MicroSD card. On the downloader page I read that in order to clean boot Armbian the incompatible Petit bootloader needs to be removed. I tried the bootloader bypass (preferred) method and that didn't seem to work for me. The board still seemed to go to the petitboot UI. I then tried the Petitboot Console method and ran the following commands as detailed on the download page: # flash_eraseall /dev/mtd0 # flash_eraseall /dev/mtd1 # flash_eraseall /dev/mtd2 # flash_eraseall /dev/mtd3 These all seemed to run/complete without issue. I then rebooted the board and now absolutely nothing happens. It doesn't boot to the Petitboot UI/Console and it doesn't boot to Armbian either.... Does anybody have any suggestions or wisdom that can help resolve this? Thanks 🙂
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines