The current example under verify encryption results in an error, as
ENCRYPTED is an unknown column
```
lsblk -o NAME,MOUNTPOINT,TYPE,SIZE,FSUSED,FSTYPE,ENCRYPTED
lsblk: unknown column: ENCRYPTED
```
- https://fleetdm.slack.com/archives/C09JAPRM1EJ/p1777467446591059
- Noted that Fleet generates a new encryption key and the original one
does still remain under step #3 after a customer noted inconsistencies
in our docs.
- The statement was taken from our enforce-disk-encryption article.
Gray Williams