nvdias Posted August 1, 2018 Share Posted August 1, 2018 (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 August 1, 2018 by nvdias Link to comment Share on other sites More sharing options...
tkaiser Posted August 1, 2018 Share Posted August 1, 2018 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 comment Share on other sites More sharing options...
zdroyer Posted June 17, 2019 Share Posted June 17, 2019 This issue is also described here: Link to comment Share on other sites More sharing options...
Recommended Posts