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


Recommended Posts

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
Link to post
Share on other sites
Armbian is a community driven open source project. Do you like to contribute your code?

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)
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...