Hello !

Since last armbian update (5.10.16-meson64 #21.02.2 SMP PREEMPT) the quirks option added to the armbianEnv.txt file is not added to the boot command line at boot time

 

 armbianEnv.txt

verbosity=1
console=both
overlay_prefix=meson
rootdev=UUID=722afb48-c000-4b51-a382-ae3a7b132c86
rootfstype=ext4
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u,0x2109:0x0715:u

 

Boot log

Kernel command line: root=UUID=722afb48-c000-4b51-a382-ae3a7b132c86 rootwait rootfstype=ext4 console=ttyAML0,115200n8 console=tty1 loglevel=1  no_console_suspend fsck.repair=yes net.ifnames=0 elevator=noop hdmimode=custombuilt cvbsmode=576cvbs max_freq_a53=1896 max_freq_a73=1800 maxcpus=6 voutmode=hdmi modeline=1920,1080,148500,67500,60,1920,2008,2052,2200,1080,1084,1089,1125,1,1,1 disablehpd=false  cvbscable= overscan=100 consoleblank=0

 

The system uses the UAS driver which causes disk freeze after few minutes of run.

https://forum.armbian.com/topic/5699-how-to-provide-and-interpret-debug-output/

 

armbianmonitor -u

 

We're not psychic. No idea what board / build / u-boot you're using.

Sorry for the lack of information. I think that this kind of issue was not link to the hardware.

I use an Odroid N2 4G. I boot on SD card, the system is on USB SSD disk.

 

I did a workaround by adding the quirks option in the boot.ini file

setenv bootargs "root=${rootdev} rootwait rootfstype=${rootfstype} ${condev} ${amlogic} no_console_suspend fsck.repair=yes net.ifnames=0 elevator=noop hdmimode=${hdmimode} cvbsmode=576cvbs max_freq_a53=${max_freq_a53} max_freq_a73=${max_freq_a73} maxcpus=${maxcpus} voutmode=${voutmode} ${cmode} disablehpd=${disablehpd} ${bootsplash} cvbscable=${cvbscable} overscan=${overscan} consoleblank=0 usb-storage.quirks=0x2109:0x0715:u"

 

Here is the result of armbianmonitor -u  http://ix.io/2RDB

So the boot script is actually provided by the u-boot for your board. And depending on how well your board is supported by the u-boot mainline, there's often many board specific tweaks.

 

In your case, the boot script is unique to your board: https://github.com/armbian/build/blob/master/config/bootscripts/boot-odroid-n2.ini

 

And while there's a generic Meson 64 and N2 Mainline, neither of which is used in the most recent image for your board (21.02), tells me that it's still being worked on.

 

So if you look at the Generic Meson 64 script, your boot script should probably support both "extraargs" and "usbstoragequirks" in /etc/armbianEnv.txt, but currently does not. Not sure if it's an oversight, or some outstanding issue preventing it's use. However, should be pretty easy to add in.

 

Be warned your edits to /etc/boot.ini will certainly be overwritten on the next u-boot update. Best to submit a fix via pull request at https://github.com/armbian/build/pulls, or at least an issue at https://github.com/armbian/build/issues,

 

Also, going forward, the community peer-to-peer board doesn't see a lot of support. The N2 is a supported board and better to post questions in https://forum.armbian.com/forum/16-amlogic-s905x-s922x/ if you still need help. Be sure to include armbianmonitor output, else the replies might be more blunt and less helpful.