Skip to content

Commit cce6bf2

Browse files
committed
Acrolinx improvements
1 parent 58806f3 commit cce6bf2

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/virtual-machines/linux/how-to-configure-lvm-raid-on-crypt.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ You'll use the **EncryptFormatAll** option. For more information about this opti
4646

4747
Although you can use this method when you're also encrypting the OS, we're just encrypting data drives here.
4848

49-
The procedures assume that you already reviewed the prerequisites mentioned in [Azure Disk Encryption scenarios on Linux VMs](https://docs.microsoft.com/azure/virtual-machines/linux/disk-encryption-linux) and in [Quickstart: Create and encrypt a Linux VM with the Azure CLI](https://docs.microsoft.com/azure/virtual-machines/linux/disk-encryption-cli-quickstart).
49+
The procedures assume that you already reviewed the prerequisites in [Azure Disk Encryption scenarios on Linux VMs](https://docs.microsoft.com/azure/virtual-machines/linux/disk-encryption-linux) and in [Quickstart: Create and encrypt a Linux VM with the Azure CLI](https://docs.microsoft.com/azure/virtual-machines/linux/disk-encryption-cli-quickstart).
5050

5151
The Azure Disk Encryption dual-pass version is on a deprecation path and should no longer be used on new encryptions.
5252

@@ -250,7 +250,7 @@ The extension will add the file systems to /var/lib/azure_disk_encryption_config
250250
251251
This file will take care of activating these disks during the boot process so that LVM or RAID can use them later.
252252

253-
Don't worry about the mount points on this file. Azure Disk Encryption will lose the ability to get the disks mounted as a normal file system after we create a physical volume or a RAID device on top of those encrypted devices. (This will get rid of the file system format that we used during the preparation process.)
253+
Don't worry about the mount points on this file. Azure Disk Encryption will lose the ability to get the disks mounted as a normal file system after we create a physical volume or a RAID device on top of those encrypted devices. (This will remove the file system format that we used during the preparation process.)
254254

255255
### Remove the temporary folders and temporary fstab entries
256256
You unmount the file systems on the disks that will be used as part of LVM.
@@ -277,7 +277,7 @@ cat /etc/fstab
277277
![Verification that temporary fstab entries are removed](./media/disk-encryption/lvm-raid-on-crypt/013-lvm-raid-verify-fstab-temp-removed.png)
278278

279279
## Steps for LVM-on-crypt
280-
Now that the underlying disks are encrypted, you can proceed to create the LVM structures.
280+
Now that the underlying disks are encrypted, you can create the LVM structures.
281281

282282
Instead of using the device name, use the /dev/mapper paths for each of the disks to create a physical volume (on the crypt layer on top of the disk, not on the disk itself).
283283

0 commit comments

Comments
 (0)