- yes ，i put device in force recovery state in Step 1 to Step 3. I referred to the operation here.Jetson Orin Nano DevKit Disk Encryption Could not stat device /dev/mmcblk0 - No such file or directory - #3 by KevinFFF
- command like this（sudo cp t234/bin/xtest /usr/bin/xtest） is tee’s operation(use luks-srv to unlock disk), i used the function.you can read this for details:tegra/optee-src/nv-optee/optee/atf_and_optee_README.txt
- I tried to encrypt only the UDA partition and the system could run. I also found this sentence in the log:
[ 11.098435] bluetooth hci0: Direct firmware load for rtl_bt/rtl8822cu_fw.bin failed with error -2
[ 11.098439] bluetooth hci0: Falling back to sysfs fallback for: rtl_bt/rtl8822cu_fw.bin
[ 11.861812] ext4 filesystem being mounted at /boot supports timestamps until 2038 (0x7fffffff)
[ 13.472402] Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8822cu_fw.bin not found
[ 13.786353] ext4 filesystem being mounted at /mnt/crypt_UDA supports timestamps until 2038 (0x7fffffff)
[ 14.970904] using random self ethernet address
[ 14.970911] using random host ethernet address
Is there anything I need to pay attention to when encrypting the rootfs partition?