devmichelcastilho

Turns out it was the time zone... I set my time zone to the correct one and it worked. sudo timedatectl set-timezone <timezone>

OS running from eMMC: Armbian Debian 12 Bookworm Image Armbian_community_25.5.0-trunk.87_Orangepi3-lts_bookworm_current_6.6.72_minimal apt updated and upgraded Docker-engine installation through armbian-config fails. Here's the log: Get:1 http://security.debian.org bookworm-security InRelease [48.0 kB] Get:2 http://deb.debian.org/debian bookworm InRelease [151 kB] Get:3 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB] Get:4 http://deb.debian.org/debian bookworm-backports InRelease [59.4 kB] Ign:5 https://github.armbian.com/configng stable InRelease Get:6 https://download.docker.com/linux/debian bookworm InRelease [43.3 kB] Get:7 http://fi.mirror.armbian.de/beta bookworm InRelease [53.3 kB] Ign:5 https://github.armbian.com/configng stable InRelease Ign:5 https://github.armbian.com/configng stable InRelease Err:5 https://github.armbian.com/configng stable InRelease Certificate verification failed: The certificate is NOT trusted. The certificate chain uses not yet valid certificate. Could not handshake: Error in the certificate verification. [IP: 2606:50c0:8003::153 443] Reading package lists... Done E: Release file for http://security.debian.org/dists/bookworm-security/InRelease is not valid yet (invalid for another 25d 9h 5min 11s). Updates for this repository will not be applied. E: Release file for http://deb.debian.org/debian/dists/bookworm/InRelease is not valid yet (invalid for another 22d 22h 34min 0s). Updates for this repository will not be applied. E: Release file for http://deb.debian.org/debian/dists/bookworm-updates/InRelease is not valid yet (invalid for another 25d 9h 41min 48s). Updates for this repository will not be applied. E: Release file for http://deb.debian.org/debian/dists/bookworm-backports/InRelease is not valid yet (invalid for another 25d 9h 41min 48s). Updates for this repository will not be applied. E: Release file for https://download.docker.com/linux/debian/dists/bookworm/InRelease is not valid yet (invalid for another 11d 0h 1min 59s). Updates for this repository will not be applied. E: Release file for http://beta.armbian.com/dists/bookworm/InRelease is not valid yet (invalid for another 25d 7h 16min 17s). Updates for this repository will not be applied. Reading package lists... Done Building dependency tree... Done Reading state information... Done Package docker-ce is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source Package docker-ce-cli is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'docker-ce' has no installation candidate E: Package 'docker-ce-cli' has no installation candidate E: Unable to locate package containerd.io E: Couldn't find any package by glob 'containerd.io' E: Couldn't find any package by regex 'containerd.io' E: Unable to locate package docker-buildx-plugin E: Unable to locate package docker-compose-plugin Failed to enable unit: Unit file docker.service does not exist. Failed to start docker.service: Unit docker.service not found.

I had installed stuff and slightly increased the system space usage, it's likely it was bigger than the partition created for the system on the eMMC. Since the whole system is copied as is, I assume it tried to copy the whole thing with the additional stuff and went over the available space. After flashing a fresh install into the SD card, I tried it again and it worked first try.

I've overwritten the first few sectors of mmcblk0p2 as suggested, rebooted and tried again, same result. Deleted all partitions, rebooted and tried again, same result and this returned:

Well turns out my eMMC drive is mounted at /dev/mmcblk0p1...but armbian-config tries to install at /dev/mmcblk0p2, which doesn't even exist (Nevermind df command didn't show it but fdisk -l did)

Thank you Werner!! I will try and share the results.

So I'm trying to connect with a UART cable from my PC to the board (OPI3LTS). Here's what I did so far: In desperation, I double checked every connection, to no avail. My devices are powered separately, so only the RX and TX cable are connected, and they are crossed as they should. Set up permissions: sudo chmod 666 /dev/ttyUSB0 Add user to dialout: sudo adduser <user> dialout Install minicom: Set up minicom with the correct address: /dev/ttyUSB0 Set up the correct baud rate (115200 in this case) Turn off flow control Tried connecting via "screen", minicom and putty, all of them just show me a black CLI I can't write in. Help? 🥲

When I check the eMMC from the Disk utility, it shows that it's normal. I can also boot the android distro that came with it normally. Help? 🥲