• Content Count

  • Joined

  • Last visited

About Heisath

  • Rank
    Elite member

Profile Information

  • Gender
  • Location

Recent Profile Visitors

1348 profile views
  1. You could figure out what armbian-config does when installing the bootloader and do it manually while changing the relevant paths to your SD card. Or copy the needed files to the new sd card with bootloader. armbian-config source: https://github.com/armbian/config You will find out, that armbian-config uses the nand-sata-install script: https://github.com/armbian/build/blob/master/packages/bsp/common/usr/sbin/nand-sata-install In there you find the call write_uboot_platform "$DIR" "${root_partition_device}" This function comes from the uboot package that you insta
  2. Is there also a status page for the status page? Just to make sure, we know what to do, if the status page is not available
  3. I assume the original thinking of the authors of fancontrol was, that when the programm crashes/unexpectedly get closed, it does not leave the fans at a low speed and possibly endanger the system. The fancontrol does not differentiate between shutdown and exit / kill. And from a system perspective it is much better to have annoying loud fans (but a cool and healthy system) than slowly burning away components while no sound is heard I guess that also answers your second question, if you comment those lines away, the fans wont auto speed up if fancontrol crashes or
  4. You need to assign a fix version. Compare yours https://armbian.atlassian.net/browse/AR-600 with this one from Igor: https://armbian.atlassian.net/browse/AR-630
  5. This has been fixed via a patch to mvebu-current (LK5.10) so should be available via nightly or with the next armbian release : https://github.com/armbian/build/blob/master/patch/kernel/mvebu-current/0001-Revert-block-simplify-set_init_blocksize-to-regain-l.patch It is fixed in LK 5.11 in mainline, but unsure if Armbian will get LK5.11 on mvebu or if we wait until the next LTS kernel version.
  6. You will have to check the home-assistant documentation on how to remove it completely. armbian-config/softy does not have a remove feature build in. See also:
  7. For bootable sd card, I'd just burn a fresh armbian image and rsync the original filesystem in there. This way you have an easy spare. Or you could try to shrink your partition before doing the dd.
  8. Can always use rsync to just copy the files of the root. Theres plenty of tutorials on how to backup your root drive with rsync. I use something like: rsync -aAXh --stats --info=progress2 --delete --exclude={"/dev/*","/proc/*","/sys/*","/tmp/*","/run/*","/mnt/*/*","/media/*","/lost+found"} / <TARGET_DIR>
  9. @Mangix probably not, if he hasn't used it for a few months. @pierre LED 8 is the power led, if nothing else shows (not even LED1 / 2 which are system / error) I'd assume your board is not even starting and your SD card might be corrupt. For further debugging you'll need to attach a computer to the micro usb and listen with some serial terminal to the output (and post it here). Or you could burn another SD card and try with that one. For LED meaning: https://wiki.kobol.io/helios4/hardware/ For Setup (also includes connecting serial terminal): https://w
  10. Maybe find a docker image then with Debian and MariaDB?
  11. This seems to be a OMV specific problem. I just checked my clearfogpro with Armbian (Debian Buster) and it reports MariaDB 10.3: user@cfp-router:~# apt list --installed | grep maria WARNING: apt does not have a stable CLI interface. Use with caution in scripts. libmariadbclient18/now 10.1.41-0+deb9u1 armhf [installed,local] mariadb-backup/stable,now 1:10.3.27-0+deb10u1 armhf [installed] mariadb-client-10.3/stable,now 1:10.3.27-0+deb10u1 armhf [installed,automatic] mariadb-client-core-10.3/stable,now 1:10.3.27-0+deb10u1 armhf [installed,automatic] mariadb-common/stable,now 1:10.3.2
  12. Great that you found & fixed it so quickly. If you add the patch via PR please include a mention (in the patch) about the upstream fixed version, so we can easily identify and remember to remove the patch again once we reach 5.11+
  13. Does this only work on full PRs or also on Draft PR? It should only be included on full PR imho.
  14. This seems like a SD card corruption problem. The UUID was always the long one (check any other clean installed device). And it did not get extended but rather the value in fstab got shortened! Regarding the "(in my sight) the same text" maybe unprintable characters had been added by sd card corruption? This is not the first time something like this has occured, I remember posts about corruption in /boot/armbianEnv.txt for example (recently had this myself when often unplugging power from bananapi w/o shutdown). For reference, my fstab and blkid output: root@####:~#
  15. Is it just me, or did we have the exact same question a few weeks/month ago already? EDIT: Found it!