The Armbian community is doing a really great job. I am still grateful for all the help I found here when I had a problem with my Helios64. (Remember that? https://forum.armbian.com/topic/18855-upgrading-to-bullseye-troubleshooting-armbian-21081/?do=findComment&comment=129711 )
Today I'm not coming to ask for help (since my NAS is working perfectly fine!) but to say hi to everyone.
And reading your positive message, Amix73, you even made me want to make a small donation.
QUICK UPDATE: I am NOW looking for ONLY one Helios64 (either full system or just the board).
The reason is, that I got an explanation from Igor, that hardware donations do NOT make sense (they are deprecated) since they are not needed - hardware is the cheapest part of the dev-process, and the devs have enough hardware.
So the ONLY thing what would help the Armbian project would be
a.) person-power, i.e., help for keeping the project going (development, infrastructure, build-server) OR
b.) money donations.
That's why I am NOW looking for ONLY for a single Helios64 (full system or just the board) - when it is located in Europe. It's for my personal use and as a backup.
@planned donation; Since I have neither the time nor the expertise to participate in development - I will make a single donation of 300€ (done) - which was the worth of the hardware.
I will consider a subscription if it is possible to donate anonymously
BUT STILL - if you are located in Europe and have a helio64 you want to sell - please contact me.
Note rootdev=UUID= will be different. You can check your by running
sudo blkid
from the sdcard os.
I believe yours is fine so you could also:
fsck /dev/mmcblk2p1
when booting from sdcard (booting kernel that has the emmc fix only ! your log shows 5.10.63 armbian 22.08.2 so your are fine. But double check before fscking).
Fscking will tell you if the filesystem is fine (readable/mountable by for one u-boot itself to start the kernel).
My mmcblk2p1 boot/armbianEnv.txt content was wrong as I ran fsck when my emmc was unstable (this was a bad idea). Thus u-boot was unable to start the system. Restoring armbianENv.txt fixed my boot.
The red is fine it is color for deb file type.
just a note. The steps were to download from :
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
not 5.10.63 ... but 5.10.63 will be fine too per
ie 21.08.2 has the emmc fix.
On emmc (/dev/mmcblk2p1) you just need to replace the root UUID in /etc/fstab and in /boot/armbianEnv.txt to match the UUID of your emmc (e4e3bcd6-3f03-4362-bbe0-f1654138c5d8). Then reboot without microsd in the slot...
mount your eMMC to some random folder.
code {
font-family: Consolas,"courier new";
color: crimson;
background-color: rgba(0, 0, 0, 0.2);
padding: 2px;
font-size: 105%;
}
mkdir ~/mount && mount /dev/mmcblk2p1 ~/mount && cd ~/mount
If it is empty then you now know why u-boot fails to boot the kernl.
Mine was filled with garbage due to the FS corruption (due to the emmc bug)
Fill the emmc armbianEnv.txt with:
echo 'verbosity=1
bootlogo=false
overlay_prefix=rockchip
rootdev=UUID=e4e3bcd6-3f03-4362-bbe0-f1654138c5d8
rootfstype=ext4
overlays=dwc3-0-host
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u,0x0bc2:0x231a:u' > /mount/boot/armbianEnv.txt
and reboot. You are done !
You should settle the dust down. First check where you mount /dev/mmcblk2p1. Do you:
mount /dev/mmcblk2p1 /mnt
or
mount /dev/mmcblk2p1 /mount
?
Because the content of the emmc will show up in the above command right directory. It will not be in /mount or /mnt if you did not made it so in the mount command.
Second give use the emmc boot/armbianEnv.txt because it could be you set the sdcard armbianEnv.txt to boot with sdcard kernel and "rootdev" (ie boot partition) as emmc. Thus it works but you have to let the sdcard for the boot which is fragile.
It ought ot contains:
verbosity=1
bootlogo=false
overlay_prefix=rockchip
rootdev=UUID=e4e3bcd6-3f03-4362-bbe0-f1654138c5d8
rootfstype=ext4
overlays=dwc3-0-host
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u,0x0bc2:0x231a:u
only. "echo" and "> /mount/boot/armbianEnv.txt" where only there so you could paste the full command and have it write the armbianEnv.txt in /mount/boot for you. If you write them down in armbianEnv.txt it kills boot.
Then feel free to update. I currenty run OMV with buster and armbian up to date on my helios64.
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)