Lexingtonian

This got me going again today after I over-wrote my armbianEnv.txt. Thank you!

For anyone that runs into this. I too went back to 5.9.14. My process to fix was to download Armbian focal with 5.9.14. Write Armbian focal to SD Card/USB Stick. Boot from SD Card/USB Stick (hold the boot button on the NanoPC). Log in as root, mount the /dev/mmcblk2p1 (this is the emmc) to /mnt/mmc. Copy (cp -rv /boot/* /mnt/mmc/boot/ ) everything in /boot to /mnt/mmc/boot. BUT! Do not overwrite your armbianEnv.txt. Rename it or move it to keep it from being overwritten. In my case I'm booting from EMMC but my rootdev is on my NVME. I made the mistake of writing over the armbianEnv.txt which is why I share the warning. If you do, you'll get a missing rootdev error on boot (and you'll hear a sad horn sound in your mind). Reboot into the SD Card Armbian again, mount /dev/mmcblk2p1 as before and edit armbianEnv.txt as root. My root partition on my NVME is /dev/nvme0n1p1. Comment out the existing rootdev (which is actually the rootdev of your SD card - Doh!) and replace it like this: #rootdev=UUID=e3841b02-afff-4f2d-9b88-990f1e858c10 rootdev=/dev/nvme0n1p1 Should get you going again. keep in mind, this will get you booted. Services that depend on or compiled for your kernel headers (like Docker) will fail. You'll need to fix your kernel branch using armbian-config > System > Other (Other Kernels) as well. I'd also recommend you freeze your kernel from future kernel updates with armbian-config > System > Freeze

Same happened to me after an apt-get upgrade. Ouch! Surprise! Thanks for the post @Viper!

That thought occurred to me. Being very familiar with raspbian. It’s a Tinkerboard though and I naturally thought since it had an armbianENV that it was Armbian. So the mystery remains... where’d my /boot go? *shrugs* Thanks again for the reply’s!

@martinayotte Thanks for the quick reply! Below is my partition table on /dev/sda (the Armbian SD Card) pi@raspberrypi:/media/pi/$ sudo fdisk -lu /dev/sda Disk /dev/sda: 14.6 GiB, 15615393792 bytes, 30498816 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xc38eda6e Device Boot Start End Sectors Size Id Type /dev/sda1 8192 93596 85405 41.7M c W95 FAT32 (LBA) /dev/sda2 94208 30498815 30404608 14.5G 83 Linux Both partitions are mounted on Rasbian as: /dev/sda2 on /media/pi/722a97e6-d105-48fe-b8a2-1920fdf3e04a type ext4 /dev/sda1 on /media/pi/boot2 type vfat Weird thing is... here's the directory listing of /media/pi/boot2 (/dev/sda1) which looks nothing like what my /boot looked like when running Armbian.. pi@raspberrypi:/media/pi/boot2 $ ls -la total 22161 drwx------ 3 pi pi 2560 Dec 31 1969 . drwxr-x---+ 8 root root 4096 Dec 6 07:47 .. -rw-r--r-- 1 pi pi 23315 Dec 4 11:12 bcm2708-rpi-0-w.dtb -rw-r--r-- 1 pi pi 22812 Dec 4 11:12 bcm2708-rpi-b.dtb -rw-r--r-- 1 pi pi 23071 Dec 4 11:12 bcm2708-rpi-b-plus.dtb -rw-r--r-- 1 pi pi 22589 Dec 4 11:12 bcm2708-rpi-cm.dtb -rw-r--r-- 1 pi pi 24115 Dec 4 11:12 bcm2709-rpi-2-b.dtb -rw-r--r-- 1 pi pi 25311 Dec 4 11:12 bcm2710-rpi-3-b.dtb -rw-r--r-- 1 pi pi 25914 Dec 4 11:12 bcm2710-rpi-3-b-plus.dtb -rw-r--r-- 1 pi pi 24087 Dec 4 11:12 bcm2710-rpi-cm3.dtb -rw-r--r-- 1 pi pi 52116 Dec 4 11:12 bootcode.bin -rw-r--r-- 1 pi pi 187 Dec 4 11:21 cmdline.txt -rw-r--r-- 1 pi pi 1590 Jul 5 2017 config.txt -rw-r--r-- 1 pi pi 18693 Aug 21 2015 COPYING.linux -rw-r--r-- 1 pi pi 41 Dec 4 11:12 .firmware_revision -rw-r--r-- 1 pi pi 2622 Dec 4 11:12 fixup_cd.dat -rw-r--r-- 1 pi pi 6695 Dec 4 11:12 fixup.dat -rw-r--r-- 1 pi pi 9905 Dec 4 11:12 fixup_db.dat -rw-r--r-- 1 pi pi 9899 Dec 4 11:12 fixup_x.dat -rw-r--r-- 1 pi pi 145 Jul 5 2017 issue.txt -rw-r--r-- 1 pi pi 4936888 Dec 4 11:12 kernel7.img -rw-r--r-- 1 pi pi 4688704 Dec 4 11:12 kernel.img -rw-r--r-- 1 pi pi 1494 Nov 18 2015 LICENCE.broadcom -rw-r--r-- 1 pi pi 18974 Jul 5 2017 LICENSE.oracle drwx------ 2 pi pi 12800 Dec 4 11:12 overlays -rw-r--r-- 1 pi pi 678372 Dec 4 11:11 start_cd.elf -rw-r--r-- 1 pi pi 5122820 Dec 4 11:11 start_db.elf -rw-r--r-- 1 pi pi 2864164 Dec 4 11:12 start.elf -rw-r--r-- 1 pi pi 4059716 Dec 4 11:12 start_x.elf Here's what /boot looks like on the main partition. (/dev/sda2). It's empty. All I did was make one edit of /boot/armbianENV.txt with nano and saved it then rebooted. pi@raspberrypi:/media/pi/722a97e6-d105-48fe-b8a2-1920fdf3e04a/boot $ ls -la total 8 drwxr-xr-x 2 root root 4096 Dec 31 1969 . drwxr-xr-x 23 root root 4096 Oct 17 2017 .. Is there another place to find the /boot used by u-boot? Confused as heck.

Noob question - Forgive me here, I'm quite new to u-boot. I made a change in my /boot/armbianENV.txt and my Tinkerboard won't boot. I know exactly what to fix, except I'm not accustomed to not being able to find the file. I've mounted the SD Card on another Linux OS and can see/mount all my partitions, I have them mounted but none of the /boot directories are what is typically there when armbian is booted. I'm assuming u-boot is an image and /boot gets dynamically created. Done some searching but not making much sense of what I'm seeing. How/Where do I find the /boot/armbianENV.txt file with the SD Card mounted to another machine? Thanks in advance.