Yesterday 1 of my 3 NanoPi Neo2 didnt boot complete anymore.
Because I had i the last time - I thought that the internal 2.5" HDD has died and couldnt mounted anymore from /etc/fstab

 

Today I checked the 2.5" HDD externally and its fine
So I connected a TTL-RS232 for the boot-output and did get:
 

Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
done.
Gave up waiting for root file system device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  UUID=47f29e2a-b4bd-451d-88 does not exist.  Dropping to a shell!
(initramfs)

 

The NanoPi Neo2 isnt finding the UUID for the root-filesystem = my sdcard?
I did pu the card in a reader on my other NanoPi Neo2 and used blkid to check the UUID - and did get:
 

/dev/sdb1: UUID="47f29e2a-b4bd-451d-88a9-35998f669cd1" TYPE="ext4" PARTUUID="53e18e13-01"

in /etc/fstab there is
UUID=47f29e2a-b4bd-451d-88

and here at the "remote" system
UUID=47f29e2a-b4bd-451d-88a9-35998f669cd1

 

Why and when has this UUID extended/expanded (and why isnt it booting with the short version?)?

 

So I did put the new/longer UUID for root in the /etc/fstab on the sdcard and put it back in the half-booting NanoPi Neo2.

armbianmonitor -u
System diagnosis information has been uploaded to http://ix.io/2KOz

 

Now this Neo2 is booting fine.
Should I check my other 2 Neo2 and compare blkid to the /etc/fstab ?

 

On my second (512MB) Neo2 I got the same long UUID for root:
UUID=47f29e2a-b4bd-451d-88a9-35998f669cd1 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro
 0 1
/dev/mmcblk0p1: UUID="47f29e2a-b4bd-451d-88a9-35998f669cd1" TYPE="ext4" PARTUUID="53e18e13-01"

but on my third (1GB LTS) Neo2 the UUIDs didnt match and it DOES boot and mount root:
UUID=47f29e2a-b4bd-451d-88a9-35998f669cd1 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1
/dev/mmcblk0p1: UUID="4e972167-ea53-4c61-9d49-a67b1f839f5f" TYPE="ext4" PARTUUID="d2f285f3-01"

[EDIT] edited /etc/fstab to 4e972167-ea53-4c61-9d49-a67b1f839f5f as seen in blkid and it boots
also perfect (maybe a differnt u-boot in "flash"?)

System diagnosis information has been uploaded to http://ix.io/2KON

 

Is it normal that all 3 Neo2 got
47f29e2a-b4bd-451d-88a9-35998f669cd1
as root-UUID? (UUID of the flash image - should this change after resize?)

The 1GB Neo2 does use a Focal-dev-image and the other use a Buster-dev-image.

23 minutes ago, guidol said:

Why and when has this UUID extended/expanded (and why isnt it booting with the short version?)?

That is something new.

 

24 minutes ago, guidol said:

UUID of the flash image - should this change after resize?

Resize only resizes. Its known problem https://armbian.atlassian.net/browse/AR-581

@Igorstrange - got near the same problem this evening with a nanoPi K1 Plus

(after updating to pihole FTL 5.5.1 and reboot  = https://pi-hole.net/2021/01/19/pi-hole-ftl-v5-5-released-update-today#page-content )

The NPI K1 Plus is searching a shorter UUID than shown as blkid

 

The Boot-Error does show

boot-err    971c3757-23ee-42

 

 

So I did put the card of the NPI K1 Plus in my Neo2 (IP24) and monuted it on /mnt/sdb1

 

But with blkid and in /etc/fstab and /boot/armbianEnv.txt I ons could find the long UUID:

boot-err	971c3757-23ee-42
blkid		971c3757-23ee-4281-b0cb-989e7255e3d9
fstab		971c3757-23ee-4281-b0cb-989e7255e3d9
armbianEnv	971c3757-23ee-4281-b0cb-989e7255e3d9

 

Spoiler

[621561.601232] usb 5-1: Product: Transcend
[621561.601241] usb 5-1: Manufacturer: TS-RDF5
[621561.601249] usb 5-1: SerialNumber: 000000000036
[621561.602363] usb-storage 5-1:1.0: USB Mass Storage device detected
[621561.603006] scsi host1: usb-storage 5-1:1.0
[621562.607000] scsi 1:0:0:0: Direct-Access     TS-RDF5  SD  Transcend    TS3A PQ: 0 ANSI: 6
[621562.607853] sd 1:0:0:0: Attached scsi generic sg1 type 0
[621562.963468] sd 1:0:0:0: [sdb] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB)
[621562.964815] sd 1:0:0:0: [sdb] Write Protect is off
[621562.964829] sd 1:0:0:0: [sdb] Mode Sense: 23 00 00 00
[621562.966520] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[621562.996686]  sdb: sdb1
[621563.002129] sd 1:0:0:0: [sdb] Attached SCSI removable disk

root@npi-neo2-24(192.168.6.24):~# blkid
/dev/sdb1: UUID="971c3757-23ee-4281-b0cb-989e7255e3d9" TYPE="ext4" PARTUUID="0b57c95b-01"

root@npi-neo2-24(192.168.6.24):/mnt/sdb1/etc# more /mnt/sdb1/etc/fstab
UUID=971c3757-23ee-4281-b0cb-989e7255e3d9 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1
tmpfs /tmp tmpfs defaults,nosuid 0 0

root@npi-neo2-24(192.168.6.24):/mnt/sdb1/boot# more /mnt/sdb1/boot/armbianEnv.txt
verbosity=1
bootlogo=false
console=both
disp_mode=1920x1080p60
overlay_prefix=sun50i-h5
overlays=analog-codec
rootdev=UUID=971c3757-23ee-4281-b0cb-989e7255e3d9
rootfstype=ext4
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

boot-err    971c3757-23ee-42
blkid        971c3757-23ee-4281-b0cb-989e7255e3d9
fstab        971c3757-23ee-4281-b0cb-989e7255e3d9
armbianEnv    971c3757-23ee-4281-b0cb-989e7255e3d9

 

Everthing seems OK - so because the Neo2 had the problem in /etc/fstab I deleted (the correct one) and replaced it with (in my sight) the same text and did put back the card in the NPI K1 Plus and it worked again ?? just fine  Dont know what happend - while booting- the 4 times before I removed the card...

This is the second time this month with a different device...

 

System diagnosis information has been uploaded to http://ix.io/2MCd

This seems like a SD card corruption problem. The UUID was always the long one (check any other clean installed device). And it did not get extended but rather the value in fstab got shortened!

 

Regarding the "(in my sight) the same text" maybe unprintable characters had been added by sd card corruption? This is not the first time something like this has occured, I remember posts about corruption in /boot/armbianEnv.txt for example (recently had this myself when often unplugging power from bananapi w/o shutdown).

 

For reference, my fstab and blkid output:

root@####:~# cat /etc/fstab
UUID=c4b74654-b71b-44c9-9303-e7f9ca15211d / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1
tmpfs /tmp tmpfs defaults,nosuid 0 0

root@####:~# blkid /dev/sda1
/dev/sda1: UUID="c4b74654-b71b-44c9-9303-e7f9ca15211d" TYPE="ext4" PARTUUID="b122e6b0-01"

 

1 hour ago, Heisath said:

This seems like a SD card corruption problem. The UUID was always the long one (check any other clean installed device). And it did not get extended but rather the value in fstab got shortened!

 

Regarding the "(in my sight) the same text" maybe unprintable characters had been added by sd card corruption? This is not the first time something like this has occured, I remember posts about corruption in /boot/armbianEnv.txt for example (recently had this myself when often unplugging power from bananapi w/o shutdown).

In this second incident with the NPi K1 Plus I did check the sdcard on the Neo2 with fsck - and it tested the filesystem without problems.
I also could see the UUID in the long version (with the right charcters) in /etc/fstab and /boot/armbianEvent.txt

 

OK, it may be an unprintable character - then it would make sense that it doesnt want to start, but its interesting that on both devices the corruption does cut the UUID that the same place.

Corruption due to Power-Outage is possible here in Turkey