From aed1a6389b563b6d3aa5aab318b9f7c65a68b4c3 Mon Sep 17 00:00:00 2001 From: Marco Martinez Date: Tue, 2 Oct 2018 16:21:04 -0700 Subject: [PATCH] Update dd command call in "Backup & Restore" When following this guide, I ran into an issue where running the following command in "Backup & Restore" zeroed the entire block device: > dd if=/dev/zero of=/dev/sdX bs=128 count=1 I updated the command to: > dd conv=notrunc if=/dev/zero of=/dev/sdX bs=128 count=1 Using the updated command, only the header portion of the device is zeroed out and can be successfully restored from backup in the rest of the example. --- docs/security/encrypt-data-disk-with-dm-crypt/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/security/encrypt-data-disk-with-dm-crypt/index.md b/docs/security/encrypt-data-disk-with-dm-crypt/index.md index a2ffcf17df4..c12f009b7f9 100644 --- a/docs/security/encrypt-data-disk-with-dm-crypt/index.md +++ b/docs/security/encrypt-data-disk-with-dm-crypt/index.md @@ -170,7 +170,7 @@ Follow these steps very carefully. 2. Test a scenario where the LUKS header is accidentally overwritten: - dd if=/dev/zero of=/dev/sdX bs=128 count=1 + dd conv=notrunc if=/dev/zero of=/dev/sdX bs=128 count=1 3. Trying to open your container will now return an error: