Use dm-verity with or without permanent on-disk superblock.

Specifies the hash version type. Format type 0 is original Chrome OS version. Format type 1 is modern version.

Used block size for the data device. (Note kernel supports only page-size as maximum here; Multiples of 512 bytes.)

Used block size for the hash device. (Note kernel supports only page-size as maximum here; Multiples of 512 bytes.)

Number of blocks of data device used in verification. If not specified, the whole device is used.

Offset of hash area/superblock on "hash-device". (Multiples of 512 bytes.)

Salt used for format or verification. Format is a hexadecimal string; 256 bytes long maximum; "-"is the special value for empty.

Use the provided UUID for format command instead of generating new one. The UUID must be provided in standard UUID format, e.g. 12345678-1234-1234-1234-123456789abc.

Defines what to do if a data verity problem is detected (data corruption). Without these options kernel fails the IO operation with I/O error. With "--ignore-corruption" option the corruption is only logged. With "--restart-on-corruption" or "--panic-on-corruption" the kernel is restarted (panicked) immediately. (You have to provide way how to avoid restart loops.)

Instruct kernel to not verify blocks that are expected to contain zeroes and always directly return zeroes instead. WARNING: Use this option only in very specific cases. This option is available since Linux kernel version 4.5.

Instruct kernel to verify blocks only the first time they are read from the data device, rather than every time. WARNING: It provides a reduced level of security because only offline tampering of the data device's content will be detected, not online tampering. This option is available since Linux kernel version 4.17.

Hash algorithm for dm-verity. This should be the name of the algorithm, like "sha1". For default see veritysetup --help.

Use forward error correction (FEC) to recover from corruption if hash verification fails. Use encoding data from the specified device. The fec device argument can be block device or file image. For format, if fec device path doesn't exist, it will be created as file. Note: block sizes for data and hash devices must match. Also, if the verity data_device is encrypted the fec_device should be too.

This is the offset, in bytes, from the start of the FEC device to the beginning of the encoding data. (Aligned on 512 bytes.)

Number of generator roots. This equals to the number of parity bytes in the encoding data. In RS(M, N) encoding, the number of roots is M-N. M is 255 and M-N is between 2 and 24 (including).

A base64 string encoding the root hash signature prefixed by "base64:" or a path to roothash signature file used to verify the root hash (in kernel). This feature requires Linux kernel version 5.4 or more recent.

Marks this veritysetup device as requiring network. It will be started after the network is available, similarly to systemd.mount(5) units marked with _netdev. The service unit to set up this device will be ordered between remote-fs-pre.target and remote-veritysetup.target, instead of veritysetup-pre.target and veritysetup.target.

Hint: if this device is used for a mount point that is specified in fstab(5), the _netdev option should also be used for the mount point. Otherwise, a dependency loop might be created where the mount point will be pulled in by local-fs.target, while the service to configure the network is usually only started after the local file system has been mounted.

This device will not be added to veritysetup.target. This means that it will not be automatically enabled on boot, unless something else pulls it in. In particular, if the device is used for a mount point, it'll be enabled automatically during boot, unless the mount point itself is also disabled with noauto.

This device will not be a hard dependency of veritysetup.target. It'll still be pulled in and started, but the system will not wait for the device to show up and be enabled, and boot will not fail if this is unsuccessful. Note that other units that depend on the enabled device may still fail. In particular, if the device is used for a mount point, the mount point itself also needs to have the nofail option, or the boot will fail if the device is not enabled successfully.

Setup this verity protected block device in the initrd, similarly to systemd.mount(5) units marked with x-initrd.mount.

Although it's not necessary to mark the mount entry for the root file system with x-initrd.mount, x-initrd.attach is still recommended with the verity protected block device containing the root file system as otherwise systemd will attempt to detach the device during the regular system shutdown while it's still in use. With this option the device will still be detached but later after the root file system is unmounted.

All other verity protected block devices that contain file systems mounted in the initrd should use this option.