Hi Milan Just to update on this... I was able to get the DM-Crypt and Dm-Verity to work together. There was some issue with the rootfs. I just built it again, encrypted it and generated the hashtree. Then it simply worked. Regards, Vidyesh -----Original Message----- From: Milan Broz <gmazyland@xxxxxxxxx> Sent: Monday, June 18, 2018 10:42 AM To: Nabar, Vidyesh <Vidyesh.Nabar@xxxxxxxxxx>; dm-crypt@xxxxxxxx Subject: Re: [EXTERNAL] Re: DM-Verity + DM-Crypt error On 06/15/2018 06:09 PM, Nabar, Vidyesh wrote: > # cryptsetup 1.6.7 processing "veritysetup create vroot /dev/mmcblk0p13 /dev/mmcblk0p14 aa70f8669af0ea1bea2e3e672a2715a7f1d97ee1077f5885f1af8871af724f36 --debug" > # Running command create. > # Allocating crypt device /dev/mmcblk0p14 context. > # Trying to open and read device /dev/mmcblk0p14 w [ 1.013479] device-mapper: verity: 179:13: metadata block 1 is corrupted ^^^ so, here you have some kernel error ... (dmesg command doesn't work?) > ith direct-io. > # Initialising device-mapper backend library. > # Trying to load VERITY crypt type from device /dev/mmcblk0p14. > # Crypto backend (OpenSSL 1.0.2j 26 Sep 2016) initialized. > # Detected kernel Linux 4.1.15 armv7l. These are really old versions, if you can, please use recent kernel and and cryptsetup (at least 1.7.5). Even if you need to use old kernel series, the latest released longterm in this series is 4.1.52... Milan _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx https://www.saout.de/mailman/listinfo/dm-crypt
