Here's what I get when trying to boot (data is from my serial adapter):

I2C_WriteByte nack returned
I2C Device Address Write Abitration Error
I2C_WriteByte nack returned
I2C Device Address Write Abitration Error
I2C_WriteByte nack returned
I2C Device Address Write Abitration Error
I2C_WriteByte nack returned
I2C Device Address Write Abitration Error
Wakeup Sub CPU 1234567
CPU Wakeup done! WFI is expected.
CPU0 is Master!

U-Boot 2016.01-armbian (Sep 02 2019 - 08:57:37 +0200)

DRAM:  1 GiB
MMC:   NEXELL DWMMC: 0, NEXELL DWMMC: 1
loaded from SD, getting env from MMC 1
*** Warning - bad CRC, using default environment

MIPI: display.0
HDMI: display.0, preset 0 (1280 *  720)
HDMI: phy ready...
LCD: [HDMI] dp.0.1 1220x680 16bpp FB:0x46000000
In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
** File not found /boot.scr **
## Executing script at 40000000
Wrong image format for "source" command
1277 bytes read in 31 ms (40 KiB/s)
## Executing script at 40000000
Wrong image format for "source" command
Card did not respond to voltage select!
** Bad device mmc 0 **
## Executing script at 40000000
Wrong image format for "source" command
** Bad device mmc 0 **
## Executing script at 40000000
Wrong image format for "source" command
nanoPi#

Here's what gpg and sha256sum output:

% gpg --verify Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img.asc
gpg: assuming signed data in 'Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img'
gpg: Signature made Mon Jan 20 00:04:11 2020 EST
gpg:                using RSA key DF00FAF1C577104B50BF1D0093D6889F9F0E78D5
gpg: Good signature from "Igor Pecovnik <igor@armbian.com>" [unknown]
gpg:                 aka "Igor Pecovnik (Ljubljana, Slovenia) <igor.pecovnik@gmail.com>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: DF00 FAF1 C577 104B 50BF  1D00 93D6 889F 9F0E 78D5
%  sha256sum -c Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img.sha
Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img: OK

Output of mount:

# mount --ro Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img /mnt/usb
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.

dmesg doesn't mention anything about the mounting problems.

Gdisk outputs:

# gdisk -l Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img 
GPT fdisk (gdisk) version 1.0.1

Partition table scan:
  MBR: MBR only
  BSD: not present
  APM: not present
  GPT: not present


***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory. 
***************************************************************


Warning! Secondary partition table overlaps the last partition by
33 blocks!
You will need to delete this partition or resize it in another utility.
Disk Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img: 2957312 sectors, 1.4 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 9FF78C6C-5C9B-4B4D-A4F3-B0B52827C119
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 2957278
Partitions will be aligned on 2048-sector boundaries
Total free space is 8158 sectors (4.0 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            8192         2957311   1.4 GiB     8300  Linux filesystem

The board I'm using is the Nano PI Fire3 LTS. It has worked before, although with a different Micro SD card. I accidentally erased it's SD card and I'm trying to reinstall.

My current Micro SD card is a SanDisk Ultra 32GB rated USH-I, (10), U with a 1 inside, and A1.

I used dd if=IMG of=DEV BS=8192 status=progress to place the image onto the Micro SD card.

I also tried with my original SP Micro SD card without success.

 

If you need anything else, just yell.

Thanks!

Hmmm, I'm having a bigger problem with my main Linux box then just a failed SD boot. Hold still. I'll reboot.

That's odd...I just downloaded the image via https://dl.armbian.com/nanopifire3/Buster_legacy, wrote it to an SD card, and it boots without a problem:

I2C_WriteByte nack returned
I2C Device Address Write Abitration Error
I2C_WriteByte nack returned
I2C Device Address Write Abitration Error
I2C_WriteByte nack returned
I2C Device Address Write Abitration Error
I2C_WriteByte nack returned
I2C Device Address Write Abitration Error
I2C_WriteByte nack returned
I2C Device Address Write Abitration Error
I2C_WriteByte nack returned
I2C Device Address Write Abitration Error
I2C_WriteByte nack returned
I2C Device Address Write Abitration Error
I2C_WriteByte nack returned
I2C Device Address Write Abitration Error
Wakeup Sub CPU 1234567
CPU Wakeup done! WFI is expected.
CPU0 is Master!



U-Boot 2016.01-armbian (Jan 20 2020 - 00:51:40 +0100)

DRAM:  1 GiB
MMC:   NEXELL DWMMC: 0, NEXELL DWMMC: 1
loaded from SD, getting env from MMC 1
*** Warning - bad CRC, using default environment

MIPI: display.0
HDMI: display.0, preset 0 (1280 *  720)
HDMI: phy ready...
LCD: [HDMI] dp.0.1 1220x680 16bpp FB:0x46000000
In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
** File not found /boot.scr **
## Executing script at 40000000
Wrong image format for "source" command
1277 bytes read in 19 ms (65.4 KiB/s)
## Executing script at 40000000
Boot script loaded from SD card 1
142 bytes read in 16 ms (7.8 KiB/s)
48642 bytes read in 27 ms (1.7 MiB/s)
Loading DTB
7764891 bytes read in 357 ms (20.7 MiB/s)
15507464 bytes read in 686 ms (21.6 MiB/s)
## Loading init Ramdisk from Legacy Image at 49000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    7764827 Bytes = 7.4 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 48000000
   Booting using the fdt blob at 0x48000000
   Loading Ramdisk to 7d7f9000, end 7df60b5b ... OK
   Loading Device Tree to 000000007d7ea000, end 000000007d7f8e01 ... OK

Starting kernel ...


Armbian 20.02.0-rc0 Buster ttySAC0

nanopifire3 login:

 

One strange thing I see about your boot log is that the u-boot is pretty old:

 

Quote

U-Boot 2016.01-armbian (Sep 02 2019 - 08:57:37 +0200)

 

The u-boot in the latest image download is just a few days old from today, so it looks like you're booting a corrupted image...?

 

I got it fixed!

As it turns out, I was trying to work on multiple SBCs at the time. One of them, the Firefly RK3399 requires that it's MMC be modified via USB-C using a propriety program that requires root privileges.

In my infinite wisdom, I decided to run it in an apparmor confinement cell -- not a proper totally virtualized machine.

So what happened is that, in spite of being only given a minimal allowance of access, it some how caused my computer to have persistent Micro SD cards (/dev/sdX). Then when I plugged a Micro SD card in it would identify it as /dev/sdX1. There were a few other quirks like this with my Micro SD cards, nothing I really understood or can explain.

 

Now I need to figure out how to run an Xen machine and I have to file a bug about their tool which didn't even do what it was supposed to anyway after wasting half a day pulling my hair out over nothing... Quick, someone tell me they envy my life.