Sample Header Ad - 728x90

dm-integrity standalone mapper device lost after reboot

5 votes
3 answers
2817 views
I currently try to use dm-integrity to run in standalone mode. For that I install a plain ubuntu server 20.04 in a virtual box VM. In the next steps I create the dm-integrity device, a ext4 filesystem and mount it: integritysetup format /dev/sdb integritysetup open /dev/sdb hdd-int mkfs.ext4 /dev/mapper/hdd-int mkdir /data mount /dev/mapper/hdd-int /data echo "/dev/mapper/hdd-int /data ext4 defaults 0 0" >> /etc/fstab **NOTE:** For simplification I use /dev/sdb instead of /dev/disk/by-id/. Now I reboot and see, that the device /dev/mapper/hdd-int does not exist and therefore the mount to /data failed. Now my Question: How can I permanently persist the information of the dm-integrity device, so that the mount after a reboot is already there? Should create a line in /etc/fstab? Or is there another config file?
Asked by schlagi123 (153 rep)
Apr 30, 2020, 11:06 AM
Last activity: May 18, 2024, 03:24 AM