Jump to content

Corrupted armbianEnv.txt in OPZ, fails to access expansion board


Recommended Posts

Posted (edited)

Just a quick note to help other users that may have the same problem:

 

Recently I've added the 2 USB expansion board to my Orange Pi Zero running Armbian.

As the new USB ports did not get listed by lsusb, I've looked into /boot/armbianEnv.txt:

It started with samba configuration (?) and a bunch of NUL characters (!).

 

I assume it was corrupted by some wrong power outage.

Anyway, recovering the armbianEnv.txt file from original armbian image solved the issue.

 

For reference, this is my current WORKING armbianEnv.txt file contents:

 

verbosity=1
logo=disabled
console=both
disp_mode=1920x1080p60
overlay_prefix=sun8i-h3
overlays=usbhost2 usbhost3
rootdev=UUID=a2c25aee-d15d-4aa7-8f41-ab6bb511776f
rootfstype=ext4
 

 

Edited by nvdias
Posted
4 hours ago, nvdias said:

I've looked into /boot/armbianEnv.txt:

It started with samba configuration (?) and a bunch of NUL characters

 

That's filesystem corruption. Just restoring one file might be not sufficient (and your UUID used anywhere else will prevent booting anyway). I would strongly recommend to do ASAP

  • a filesystem check (fsck)
  • verify package integrity (sudo armbianmonitor -v)
Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines