TDCroPower

  • Posts

    36
  • Joined

  • Last visited

Everything posted by TDCroPower

  1. Use instead of jumper 11 the jumper 10, so you should be able to see and write your emmc in running mode. See also here how...
  2. It worked, I have my eMMC system back! Here are all the steps in case someone else has the problem and wants to repair his eMMC image... 1. download a previous Helios64 image from here... https://wiki.kobol.io/download/ 2. install the image on a microSD e.g. for Windows and macOS there is Etcher... https://www.balena.io/etcher/ 3a. boot your Helios64 with the microSD and Jumper 10, see here... https://wiki.kobol.io/helios64/troubleshoot/#how-to-force-boot-from-microsd 3b. Alternative: from the serial console press a key on the keyboard while u-boot start. You will get the u-boot prompt. From this prompt write and press enter. Helios64 will boot from SD... (thx @prahal) run bootcmd_mmc1 4. if you are logged in as root user (normal users must put a sudo in front of the commands) execute the following commands... root@helios64:~# mkdir -p /mnt/system root@helios64:~# mount /dev/mmcblk2p1 /mnt/system root@helios64:~# cd /mnt/system/ 5. The contents of the /mnt/system directory should now be filled with the contents of your eMMC.... root@helios64:/mnt/system# ll total 80 lrwxrwxrwx 1 root root 7 Aug 30 2020 bin -> usr/bin drwxr-xr-x 3 root root 4096 Sep 1 03:01 boot drwxr-xr-x 2 root root 4096 Oct 15 2020 dev drwxr-xr-x 110 root root 12288 Sep 1 03:01 etc drwxr-xr-x 2 root root 4096 Sep 22 2020 export drwxr-xr-x 5 root root 4096 Jun 10 04:12 home lrwxrwxrwx 1 root root 7 Aug 30 2020 lib -> usr/lib drwx------ 5 root root 4096 Oct 5 2020 lost+found drwxr-xr-x 4 root root 4096 Oct 15 2020 media drwxr-xr-x 2 root root 4096 Feb 9 2021 mnt drwxr-xr-x 4 root root 4096 Dec 2 2020 opt dr-xr-xr-x 2 root root 4096 Oct 15 2020 proc drwx------ 7 root root 4096 Aug 31 23:36 root drwxr-xr-x 2 root root 4096 Oct 15 2020 run lrwxrwxrwx 1 root root 8 Aug 30 2020 sbin -> usr/sbin drwxrwxr-x 2 root root 4096 Oct 5 2020 selinux drwxr-xr-x 6 root root 4096 Jun 10 03:18 srv dr-xr-xr-x 2 root root 4096 Oct 15 2020 sys lrwxrwxrwx 1 root root 42 Sep 1 03:01 thermal_zone0 -> /sys/devices/virtual/thermal/thermal_zone0 drwxrwxrwt 2 root root 4096 Oct 15 2020 tmp drwxr-xr-x 12 root root 4096 Nov 27 2020 usr drwxr-xr-x 14 root root 4096 Oct 6 2020 var 6. now download the 3 old packages... root@helios64:/mnt/system# wget http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.43-rockchip64/linux-dtb-current-rockchip64_21.05.4_arm64.deb root@helios64:/mnt/system# wget http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.43-rockchip64/linux-headers-current-rockchip64_21.05.4_arm64.deb root@helios64:/mnt/system# wget http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.43-rockchip64/linux-image-current-rockchip64_21.05.4_arm64.deb 7. now changes the root directory... root@helios64:/mnt/system# chroot /mnt/system root@helios64:/# pwd / root@helios64:/# ll total 50996 lrwxrwxrwx 1 root root 7 Aug 30 2020 bin -> usr/bin drwxr-xr-x 3 root root 4096 Sep 1 14:56 boot drwxr-xr-x 2 root root 4096 Sep 1 16:15 dev drwxr-xr-x 110 root root 12288 Sep 1 03:01 etc drwxr-xr-x 2 root root 4096 Sep 22 2020 export drwxr-xr-x 5 root root 4096 Jun 10 04:12 home lrwxrwxrwx 1 root root 7 Aug 30 2020 lib -> usr/lib -rw-r--r-- 1 root root 314304 Jul 8 19:32 linux-dtb-current-rockchip64_21.05.4_arm64.deb -rw-r--r-- 1 root root 11527696 Jul 8 19:32 linux-headers-current-rockchip64_21.05.4_arm64.deb -rw-r--r-- 1 root root 40290884 Jul 8 19:33 linux-image-current-rockchip64_21.05.4_arm64.deb drwx------ 5 root root 4096 Oct 5 2020 lost+found drwxr-xr-x 4 root root 4096 Oct 15 2020 media drwxr-xr-x 2 root root 4096 Feb 9 2021 mnt drwxr-xr-x 4 root root 4096 Dec 2 2020 opt dr-xr-xr-x 2 root root 4096 Oct 15 2020 proc drwx------ 7 root root 4096 Aug 31 23:36 root drwxr-xr-x 2 root root 4096 Oct 15 2020 run lrwxrwxrwx 1 root root 8 Aug 30 2020 sbin -> usr/sbin drwxrwxr-x 2 root root 4096 Oct 5 2020 selinux drwxr-xr-x 6 root root 4096 Jun 10 03:18 srv dr-xr-xr-x 2 root root 4096 Oct 15 2020 sys lrwxrwxrwx 1 root root 42 Sep 1 03:01 thermal_zone0 -> /sys/devices/virtual/thermal/thermal_zone0 drwxrwxrwt 2 root root 4096 Oct 15 2020 tmp drwxr-xr-x 12 root root 4096 Nov 27 2020 usr drwxr-xr-x 14 root root 4096 Oct 6 2020 var 8. now installs the downloaded packages... root@helios64:/# dpkg -i *.deb dpkg: warning: downgrading linux-dtb-current-rockchip64 from 21.08.1 to 21.05.4 (Reading database ... 62558 files and directories currently installed.) Preparing to unpack linux-dtb-current-rockchip64_21.05.4_arm64.deb ... Unpacking linux-dtb-current-rockchip64 (21.05.4) over (21.08.1) ... Selecting previously unselected package linux-headers-current-rockchip64. Preparing to unpack linux-headers-current-rockchip64_21.05.4_arm64.deb ... Unpacking linux-headers-current-rockchip64 (21.05.4) ... dpkg: warning: downgrading linux-image-current-rockchip64 from 21.08.1 to 21.05.4 Preparing to unpack linux-image-current-rockchip64_21.05.4_arm64.deb ... update-initramfs: Deleting /boot/initrd.img-5.10.60-rockchip64 Removing obsolete file uInitrd-5.10.60-rockchip64 stat: cannot stat '/proc/1/root/.': No such file or directory Unpacking linux-image-current-rockchip64 (21.05.4) over (21.08.1) ... Setting up linux-dtb-current-rockchip64 (21.05.4) ... Setting up linux-headers-current-rockchip64 (21.05.4) ... Compiling headers - please wait ... grep: /proc/cpuinfo: No such file or directory grep: /proc/cpuinfo: No such file or directory Setting up linux-image-current-rockchip64 (21.05.4) ... update-initramfs: Generating /boot/initrd.img-5.10.43-rockchip64 W: Couldn't identify type of root file system for fsck hook update-initramfs: Converting to u-boot format 9. reset the root change with exit and restart your helios64 with reboot... root@helios64:/# exit exit root@helios64:/mnt/system# reboot 10. after a reboot you should now boot from the eMMC again... root@192.168.180.5's password: _ _ _ _ __ _ _ | | | | ___| (_) ___ ___ / /_ | || | | |_| |/ _ \ | |/ _ \/ __| '_ \| || |_ | _ | __/ | | (_) \__ \ (_) |__ _| |_| |_|\___|_|_|\___/|___/\___/ |_| Welcome to Armbian 21.08.1 Buster with Linux 5.10.43-rockchip64 No end-user support: built from trunk System load: 74% Up time: 3 min Memory usage: 34% of 3.77G IP: 172.18.0.1 172.19.0.1 172.20.0.1 172.17.0.1 192.168.180.5 CPU temp: 66°C Usage of /: 87% of 15G [ 0 security updates available, 3 updates total: apt upgrade ] Last check: 2021-09-01 16:38 [ General system configuration (beta): armbian-config ] Last login: Wed Sep 1 16:26:23 2021 root@helios64:~# root@helios64:~# uname -a Linux helios64 5.10.43-rockchip64 #21.05.4 SMP PREEMPT Wed Jun 16 08:02:12 UTC 2021 aarch64 GNU/Linux root@helios64:~# 11. if the eMMC was used you can see with mount... root@helios64:~# mount | grep /dev/mmc /dev/mmcblk2p1 on / type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600) /dev/mmcblk2p1 on /var/folder2ram/var/log type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600) /dev/mmcblk2p1 on /var/folder2ram/var/tmp type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600) /dev/mmcblk2p1 on /var/folder2ram/var/lib/openmediavault/rrd type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600) /dev/mmcblk2p1 on /var/folder2ram/var/spool type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600) /dev/mmcblk2p1 on /var/folder2ram/var/lib/rrdcached type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600) /dev/mmcblk2p1 on /var/folder2ram/var/lib/monit type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600) /dev/mmcblk2p1 on /var/folder2ram/var/cache/samba type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600)
  3. ok i got a little further. I wrote the armbian image 21.02.3 with 5.10.21-rockchip64 on a SD and triggered the boot from microSD via jumper 10... https://wiki.kobol.io/helios64/troubleshoot/#how-to-force-boot-from-microsd i am back on the box and was able to mount the emmc under /dev/mmcblk2p1... root@helios64:~# ll /mnt/ total 0 root@helios64:~# mkdir -p /mnt/system root@helios64:~# mount /dev/mmcblk2p1 /mnt/system root@helios64:~# cd /mnt/system/ root@helios64:/mnt/system# ll total 80 lrwxrwxrwx 1 root root 7 Aug 30 2020 bin -> usr/bin drwxr-xr-x 3 root root 4096 Sep 1 03:01 boot drwxr-xr-x 2 root root 4096 Oct 15 2020 dev drwxr-xr-x 110 root root 12288 Sep 1 03:01 etc drwxr-xr-x 2 root root 4096 Sep 22 2020 export drwxr-xr-x 5 root root 4096 Jun 10 04:12 home lrwxrwxrwx 1 root root 7 Aug 30 2020 lib -> usr/lib drwx------ 5 root root 4096 Oct 5 2020 lost+found drwxr-xr-x 4 root root 4096 Oct 15 2020 media drwxr-xr-x 2 root root 4096 Feb 9 2021 mnt drwxr-xr-x 4 root root 4096 Dec 2 2020 opt dr-xr-xr-x 2 root root 4096 Oct 15 2020 proc drwx------ 7 root root 4096 Aug 31 23:36 root drwxr-xr-x 2 root root 4096 Oct 15 2020 run lrwxrwxrwx 1 root root 8 Aug 30 2020 sbin -> usr/sbin drwxrwxr-x 2 root root 4096 Oct 5 2020 selinux drwxr-xr-x 6 root root 4096 Jun 10 03:18 srv dr-xr-xr-x 2 root root 4096 Oct 15 2020 sys lrwxrwxrwx 1 root root 42 Sep 1 03:01 thermal_zone0 -> /sys/devices/virtual/thermal/thermal_zone0 drwxrwxrwt 2 root root 4096 Oct 15 2020 tmp drwxr-xr-x 12 root root 4096 Nov 27 2020 usr drwxr-xr-x 14 root root 4096 Oct 6 2020 var root@helios64:/mnt/system# remains only the question how/where I install the packages that were described here... https://forum.armbian.com/topic/18855-upgrading-to-bullseye/?tab=comments#comment-128189 maybe it has something to do with the boot/ directory.... root@helios64:/mnt/system# ll boot/ total 64696 -rw-r--r-- 1 root root 166 Sep 1 03:01 armbianEnv.txt -rw-r--r-- 1 root root 1536 Oct 15 2020 armbian_first_run.txt.template -rw-r--r-- 1 root root 38518 Oct 15 2020 boot.bmp -rw-r--r-- 1 root root 3113 Oct 15 2020 boot.cmd -rw-r--r-- 1 root root 3185 Oct 15 2020 boot.scr -rw-r--r-- 1 root root 221489 Aug 25 20:56 config-5.10.60-rockchip64 lrwxrwxrwx 1 root root 22 Sep 1 02:31 dtb -> dtb-5.10.60-rockchip64 drwxr-xr-x 6 root root 4096 Sep 1 02:30 dtb-5.10.60-rockchip64 lrwxrwxrwx 1 root root 26 Sep 1 02:31 Image -> vmlinuz-5.10.60-rockchip64 -rw-r--r-- 1 root root 15767106 Sep 1 02:32 initrd.img-5.10.60-rockchip64 -rw-r--r-- 1 root root 5839373 Aug 25 20:56 System.map-5.10.60-rockchip64 lrwxrwxrwx 1 root root 26 Sep 1 02:32 uInitrd -> uInitrd-5.10.60-rockchip64 -rw-r--r-- 1 root root 15767170 Sep 1 02:32 uInitrd-5.10.60-rockchip64 -rw-r--r-- 1 root root 28580352 Aug 25 20:56 vmlinuz-5.10.60-rockchip64 root@helios64:/mnt/system#
  4. I don't have a clean backup of the eMMC unfortunately, will probably have to introduce in the future to have a backup for such a step. I found the following tutorial to clone the system from the emmc to a connected media.... https://averagelinuxuser.com/backup-and-restore-your-linux-system-with-rsync/ After that I would have to somehow downgrade my emmc backup on the media? Does anyone have a tip which files have to be replaced? After that I should clone from the fixed medium to a new SD and boot from it, now I should see my system again or? And then in the armbian-config with... System&security -> Install to -> system on emmc, boot from emmc ... to clone the image again on the emmc... https://wiki.kobol.io/helios64/install/transfer/
  5. I unfortunately ran fsck last night as mentioned by you, which probably does not boot cleanly or I no longer have ssh access. Maybe I have to connect it to the monitor and check what I see in the bootlog. If someone could offer a step by step guide on how to recover I would be very grateful!
  6. Can you explain how you got your system back? Unfortunately, I also updated to 21.08.01 tonight and urgently need a downgrade to get the system back. Would be very grateful to you!
  7. My upgrade is done. Before... root@192.168.180.5's password: _ _ _ _ __ _ _ | | | | ___| (_) ___ ___ / /_ | || | | |_| |/ _ \ | |/ _ \/ __| '_ \| || |_ | _ | __/ | | (_) \__ \ (_) |__ _| |_| |_|\___|_|_|\___/|___/\___/ |_| Welcome to Armbian 20.08.21 Buster with Linux 5.8.17-rockchip64 No end-user support: work in progress System load: 8% Up time: 16 days 6:46 Memory usage: 77% of 3.71G IP: 172.18.0.1 192.168.180.5 CPU temp: 47°C Usage of /: 60% of 15G [ General system configuration (beta): armbian-config ] Last login: Fri Nov 27 02:53:45 2020 from 192.168.180.83 root@helios64:~# After... root@192.168.180.5's password: _ _ _ _ __ _ _ | | | | ___| (_) ___ ___ / /_ | || | | |_| |/ _ \ | |/ _ \/ __| '_ \| || |_ | _ | __/ | | (_) \__ \ (_) |__ _| |_| |_|\___|_|_|\___/|___/\___/ |_| Welcome to Armbian 20.11 Buster with Linux 5.9.10-rockchip64 No end-user support: work in progress System load: 53% Up time: 0 min Memory usage: 8% of 3.71G IP: 192.168.180.5 CPU temp: 43°C Usage of /: 60% of 15G [ General system configuration (beta): armbian-config ] Last login: Fri Nov 27 03:42:24 2020 from 192.168.180.83 root@helios64:~#
  8. After the official release of Armbian 20.11 today I would like to collect feedback if and how the firmware runs on the Helios64. Is it possible to upgrade already or should we Helios64 owners wait? apt-get lists these already... armbian-config/buster,buster 20.11 all [upgradable from: 20.08.22] armbian-firmware/buster,buster 20.11 all [upgradable from: 20.08.22] libgssapi-krb5-2/stable,stable 1.17-3+deb10u1 arm64 [upgradable from: 1.17-3] libk5crypto3/stable,stable 1.17-3+deb10u1 arm64 [upgradable from: 1.17-3] libkrb5-3/stable,stable 1.17-3+deb10u1 arm64 [upgradable from: 1.17-3] libkrb5support0/stable,stable 1.17-3+deb10u1 arm64 [upgradable from: 1.17-3] libldap-2.4-2/stable,stable 2.4.47+dfsg-3+deb10u4 arm64 [upgradable from: 2.4.47+dfsg-3+deb10u3] libldap-common/stable,stable,stable,stable 2.4.47+dfsg-3+deb10u4 all [upgradable from: 2.4.47+dfsg-3+deb10u3] linux-buster-root-current-helios64/buster 20.11 arm64 [upgradable from: 20.08.21] linux-dtb-current-rockchip64/buster 20.11 arm64 [upgradable from: 20.08.21] linux-image-current-rockchip64/buster 20.11 arm64 [upgradable from: 20.08.21] linux-u-boot-helios64-current/buster 20.11 arm64 [upgradable from: 20.08.21] openmediavault/usul,usul,usul,usul 5.5.17-3 all [upgradable from: 5.5.16-1] The changelog is here... https://www.armbian.com/newsflash/armbian-20-11-tamandua/
  9. you can use the boot mode jumper to switch between eMMC (P10) and microSD (P11) boot, see the Helios wiki... https://wiki.kobol.io/helios64/jumper/ @Helios Team... what is the current image status? Is it now possible to upgrade from 20.08.10 to the current version? By now we are already at 20.08.22... armbian-config/buster,buster 20.08.22 all [upgradable from: 20.08.10] armbian-firmware/buster,buster 20.08.22 all [upgradable from: 20.08.10] libfreetype6/stable,stable 2.9.1-3+deb10u2 arm64 [upgradable from: 2.9.1-3+deb10u1] libldap-2.4-2/stable,stable 2.4.47+dfsg-3+deb10u3 arm64 [upgradable from: 2.4.47+dfsg-3+deb10u2] libldap-common/stable,stable,stable,stable 2.4.47+dfsg-3+deb10u3 all [upgradable from: 2.4.47+dfsg-3+deb10u2] linux-buster-root-current-helios64/buster 20.08.21 arm64 [upgradable from: 20.08.10] linux-dtb-current-rockchip64/buster 20.08.21 arm64 [upgradable from: 20.08.10] linux-image-current-rockchip64/buster 20.08.21 arm64 [upgradable from: 20.08.10] linux-libc-dev/stable,stable 4.19.152-1 arm64 [upgradable from: 4.19.146-1] linux-u-boot-helios64-current/buster 20.08.21 arm64 [upgradable from: 20.08.10] openmediavault-omvextrasorg/buster,buster 5.4.2 all [upgradable from: 5.4.1] openmediavault/usul,usul,usul,usul 5.5.16-1 all [upgradable from: 5.5.12-1] salt-common/usul,usul,usul,usul 3002.1+ds-1 all [upgradable from: 3001.1+ds-1] salt-minion/usul,usul,usul,usul 3002.1+ds-1 all [upgradable from: 3001.1+ds-1] tzdata/stable-updates,stable-updates 2020d-0+deb10u1 all [upgradable from: 2020a-0+deb10u1]
  10. use the command df -h to show from which storage the system was loaded. If it says /dev/mmcblk1p1 it is the eMMC and if it says /dev/mmcblk0p1 it is still your microSD. You can also tell from the memory size whether it is the eMMC (has 15GB) or your microSD. root@helios64:~# df -h Filesystem Size Used Avail Use% Mounted on udev 1.8G 0 1.8G 0% /dev tmpfs 381M 37M 344M 10% /run /dev/mmcblk1p1 15G 7.8G 5.7G 59% / tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup tmpfs 1.9G 4.0K 1.9G 1% /tmp
  11. Soldering? No problem here ! I can help users from Germany to fix their helios board once the solution is released.
  12. how did you display this ingenious output? I currently have a consumption of 88-90% on my Helios64 and suspect that a container is at fault. edit: ok with docker stats I got a similar output, but yours is even more "neat". CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS 7b42ac796d6f pihole 0.13% 18.92MiB / 3.711GiB 0.50% 0B / 0B 2.87GB / 621MB 21 3d3d14ccf50d unifi-controller 3.85% 938.7MiB / 3.711GiB 24.70% 0B / 0B 6.22GB / 8.44GB 124 711e02b8f517 iobroker 15.94% 977.9MiB / 3.711GiB 25.73% 0B / 0B 4.79GB / 59.5GB 144 ae4aba42dce4 embyserver 2.94% 928MiB / 3.711GiB 24.42% 0B / 0B 13.2GB / 423MB 39 0150a9f8edfb portainer-ce 0.66% 14.87MiB / 3.711GiB 0.39% 5.95MB / 9.88MB 741MB / 136MB 15
  13. @aprayoga was once again very active, so we can look forward to further optimizations in the next armbian releases ... https://github.com/armbian/build/commit/079b467342fffa7678f903793c589e9fe9fb8b69 https://github.com/armbian/build/commit/5e62c071f0c4bafd1d25ef5f5259bb485935a77e
  14. @Bethlehem my Helios64 installation with 3x WD Red 4TB, OMV und Docker nativ -> Containers: Portainer, pihole, iobroker, emby, unifi controller, netdata... runs at 45°C Welcome to Armbian 20.08.10 Buster with Linux 5.8.14-rockchip64 No end-user support: work in progress System load: 20% Up time: 1 day 9:02 Memory usage: 61% of 3.71G IP: 172.18.0.1 192.168.180.5 CPU temp: 45°C Usage of /: 59% of 15G [ General system configuration (beta): armbian-config ] Last login: Sun Oct 18 03:35:55 2020 from 192.168.180.83 root@helios64:~# note that the change to eMMC is not necessarily only about speed, mainly about the stability an eMMC has compared to a microSD. A microSD will most likely die faster than an eMMC. Especially if you want to run your system in the background in continuous operation at some point, a microSD in continuous operation is not pleasant.
  15. After several weeks of testing and trying I finally put my Helios64 into production. With the 20.08.10 and the possibility to run the firmware over the eMMC I can finally sleep more calmly again. The front view mounted: The back view connected: And to prevent my wife from killing me because there is a lighting party going on in the hallway I taped the front LEDs with insulating tape... And for all who have problems with the included USB-C cable at the USB-C port of the Helios64. You have to remove the plastic so that the connector looks like this... The black plastic of the USB-C cable must NOT touch the backside of the Helios64, this ensures that the Cable is 100% plugged in.
  16. yes I have. I started it via armbian-config >>> System >>> Install >>> "2 Boot from eMMC - system on eMMC", but it is the same script that is behind it. Before that I installed OMV and Docker natively on the system and pihole, unifi controller, iobroker and emby server as container. @antsu you are probably right, because under /srv I cant't find my OMV -> SMB Shared Folders... root@helios64:~# ll /srv/ total 0 root@helios64:~# i try to boot from the microSD again to save the 2 directories. You should tell the armbian team or the dev of the nand-sata-install script. I think you can do this via their Jira ticket system? edit: unfortunately I did not manage to boot from the microSD again. Does anyone know how to switch from eMMC boot to microSD boot? Solution: with this mount command... mount /dev/mmcblk0p1 /mnt ... you can have access to the microsd files under /mnt... root@helios64:~# ll /mnt/ total 96 lrwxrwxrwx 1 root root 7 Aug 30 20:55 bin -> usr/bin drwxr-xr-x 3 root root 4096 Oct 15 16:47 boot drwxr-xr-x 2 root root 4096 Oct 5 16:04 dev drwxr-xr-x 108 root root 12288 Oct 15 16:49 etc drwxr-xr-x 2 root root 4096 Sep 22 02:38 export drwxr-xr-x 3 root root 4096 Oct 6 02:24 home lrwxrwxrwx 1 root root 7 Aug 30 20:55 lib -> usr/lib drwx------ 2 root root 16384 Oct 5 16:17 lost+found drwxr-xr-x 2 root root 4096 Aug 30 20:55 media drwxr-xr-x 4 root root 4096 Oct 15 16:48 mnt drwxr-xr-x 4 root root 4096 Oct 14 01:18 opt drwxr-xr-x 2 root root 4096 Jul 10 23:04 proc drwx------ 5 root root 4096 Oct 14 01:39 root drwxr-xr-x 2 root root 4096 Oct 5 16:13 run lrwxrwxrwx 1 root root 8 Aug 30 20:55 sbin -> usr/sbin drwxrwxr-x 2 root root 4096 Oct 5 16:05 selinux drwxr-xr-x 2 root root 4096 Sep 22 02:38 sharedfolders drwxr-xr-x 6 root root 4096 Oct 15 16:39 srv drwxr-xr-x 2 root root 4096 Jul 10 23:04 sys drwxrwxrwt 2 root root 4096 Oct 5 16:17 tmp drwxr-xr-x 11 root root 4096 Oct 6 03:22 usr drwxr-xr-x 14 root root 4096 Oct 6 03:12 var root@helios64:~# and to copy the two directories back into the /srv directory just use the following two commands... cp -r /mnt/srv/pillar /srv cp -r /mnt/srv/salt /srv ... and after an reboot its back... root@helios64:~# ll /srv/ total 16 drwxr-xr-x 10 root root 4096 Oct 15 16:40 dev-disk-by-label-nas drwxr-xr-x 2 ftp nogroup 4096 Oct 6 03:06 ftp drwxr-xr-x 3 root root 4096 Oct 6 03:05 pillar drwxr-xr-x 5 root root 4096 Oct 6 03:05 salt root@helios64:~#
  17. The new firmware 20.08.10 is finally available via apt-get... root@helios64:~# apt list --upgradable Listing... Done armbian-config/buster,buster 20.08.10 all [upgradable from: 20.08.8] armbian-firmware/buster,buster 20.08.10 all [upgradable from: 20.08.8] linux-buster-root-current-helios64/buster 20.08.10 arm64 [upgradable from: 20.08.8] linux-dtb-current-rockchip64/buster 20.08.10 arm64 [upgradable from: 20.08.8] linux-image-current-rockchip64/buster 20.08.10 arm64 [upgradable from: 20.08.8] linux-u-boot-helios64-current/buster 20.08.10 arm64 [upgradable from: 20.08.8] openmediavault-omvextrasorg/buster,buster 5.4.1 all [upgradable from: 5.4] root@helios64:~# As soon as my copy of my backup to my new RAID5 is finished I will update and test the part with the eMMC right away! edit: Perfect, the update went through cleanly and installing/booting from eMMC now works without problems. _ _ _ _ __ _ _ | | | | ___| (_) ___ ___ / /_ | || | | |_| |/ _ \ | |/ _ \/ __| '_ \| || |_ | _ | __/ | | (_) \__ \ (_) |__ _| |_| |_|\___|_|_|\___/|___/\___/ |_| Welcome to Armbian 20.08.10 Buster with Linux 5.8.14-rockchip64 No end-user support: work in progress System load: 28% Up time: 1 min Memory usage: 8% of 3.71G IP: 192.168.180.5 CPU temp: 41°C Usage of /: 45% of 15G Last login: Thu Oct 15 16:47:49 2020 from 192.168.180.83 root@helios64:~# df -h Filesystem Size Used Avail Use% Mounted on udev 1.8G 0 1.8G 0% /dev tmpfs 381M 11M 370M 3% /run /dev/mmcblk1p1 15G 6.1G 7.4G 45% / tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup tmpfs 1.9G 4.0K 1.9G 1% /tmp folder2ram 1.9G 11M 1.9G 1% /var/log folder2ram 1.9G 0 1.9G 0% /var/tmp folder2ram 1.9G 268K 1.9G 1% /var/lib/openmediavault/rrd folder2ram 1.9G 724K 1.9G 1% /var/spool folder2ram 1.9G 14M 1.9G 1% /var/lib/rrdcached folder2ram 1.9G 12K 1.9G 1% /var/lib/monit folder2ram 1.9G 1.3M 1.9G 1% /var/cache/samba tmpfs 381M 0 381M 0% /run/user/0 root@helios64:~#
  18. thanks for the feedback. Will be available again after about 24h via apt-get. Currently the 20.08.9 is still offered... root@helios64:~# apt list --upgradable Listing... Done armbian-config/buster,buster 20.08.9 all [upgradable from: 20.08.8] armbian-firmware/buster,buster 20.08.9 all [upgradable from: 20.08.8] linux-buster-root-current-helios64/buster 20.08.9 arm64 [upgradable from: 20.08.8] root@helios64:~# edit: the new wikis are even already online ... https://wiki.kobol.io/helios64/install/emmc/
  19. Cool, very good news! Is a fresh install from "20.08.8" also urgently necessary or can we also upgrade to "20.08.10" with an apt-get upgrade?
  20. i checked today and saw a new 20.08.9 in the updates. Has anything new been implemented or fixed in the new 20.08.9 that might interest us as Helios64 owners? root@helios64:~# apt list --upgradable Listing... Done armbian-config/buster,buster 20.08.9 all [upgradable from: 20.08.8] armbian-firmware/buster,buster 20.08.9 all [upgradable from: 20.08.8] linux-buster-root-current-helios64/buster 20.08.9 arm64 [upgradable from: 20.08.8] root@helios64:~# edit1: I have found 2 commits from aprayoga, have they perhaps already been implemented in 20.08.9? If so, the first one should be seen as fix for the eMMC problem, right? https://github.com/armbian/build/commit/d909a4ea723f5e3e1d1b3e7bb07a2215793725b1 (Verified) https://github.com/armbian/build/commit/bc66f9d835cb8303eb65ea55ac02da69920284f7 (???) edit2: Unfortunately there is nothing to find in the changelog about 20.08.9 yet. Is it perhaps still so fresh? https://docs.armbian.com/Release_Changelog/
  21. I had the same problem on my Mac. But with Windows and PuTTY it works perfectly.
  22. very good, just these 2 features are for many probably the most important to be able to set it up quickly and neatly.
  23. because my first microSD has a satisfying image i got a second microSD today to test it. I will try to reproduce my steps to copy + boot from the eMMC. I have here still the 20.08.4 image for reference. Tomorrow I have to set up my test setup to test more effective/faster and give feedback again. @aprayoga is it true what @gprovost has written here that you have already fixed the eMMC problem and are working on a suitable Wiki? If that's true then theoretically I can save myself the test run and just wait for your update. Unless you would like to get further feedback on it.
  24. @aprayoga Oh sorry I think there is an understanding problem. The system can always boot from the microSD! When i install everything on the eMMC with nand-sata-install and reboot it has booted from the eMMC... the microSD stays plugged in! If I shut down the system, removed the microSD and rebooted it did not boot anymore. When I plugged in the microSD and booted it again it showed me that it has mounted from the eMMC. See my post early Topic 2