Issue while mounting device mapper created by dm-verity

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Issue while mounting device mapper created by dm-verity

1,316 Views
khaleel
Contributor I

Hi

Trying to implement dm-verity for verifying/Authenticating my readonly rootfile system.

Host :

Successfully created hashtree and roothash for my ro rootfile system and verified it with verify command.

Target:(imx8m mini kernel)

Created a mapper /dev/mapper/vroot for the block device which has my readonly rootfile system with the help of hashtree and roothash.

when i try to mount it i'm getting below error.

sh-4.4# mount -o ro /dev/mapper/vroot /mnt/
[ 455.059274] device-mapper: verity: 179:2: data block 0 is corrupted
[ 455.065872] EXT4-fs (dm-0): unable to read superblock
[ 455.073189] device-mapper: verity: 179:2: data block 0 is corrupted
[ 455.079513] EXT4-fs (dm-0): unable to read superblock
[ 455.086139] device-mapper: verity: 179:2: data block 0 is corrupted
[ 455.092485] EXT2-fs (dm-0): error: unable to read superblock
[ 455.100009] device-mapper: verity: 179:2: data block 0 is corrupted
[ 455.106334] SQUASHFS error: squashfs_read_data failed to read block 0x0
[ 455.113001] squashfs: SQUASHFS error: unable to read squashfs_super_block
[ 455.121428] device-mapper: verity: 179:2: data block 0 is corrupted
[ 455.127756] FAT-fs (dm-0): unable to read boot sector
mount: mounting /dev/mapper/vroot on /mnt/ failed: Input/output error

Best Regards,

Khaleel

Labels (1)
0 Kudos
1 Reply

1,308 Views
Zhiming_Liu
NXP TechSupport
NXP TechSupport

Hi

 Please see 3.4 Configurations in Linux/Android platform for security features in i.MX_Android_Security_User's_Guide.pdf

0 Kudos