Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-05-05 16:25:11 -04:00
Code Issues Projects Releases Packages Wiki Activity

luksFormat: add --sector-size=512 argument

Browse source
This commit is contained in:
Rusty Bird 2024-12-20 19:29:36 +00:00
parent 01165e5f82
commit cc00196539
No known key found for this signature in database
GPG key ID: 469D78F47AAF2ADF
1 changed files with 3 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

4
user/advanced-topics/secondary-storage.md
View file

@ -65,10 +65,12 @@ In theory, you can still use file-based disk images ("file" pool driver), but it
Assuming the secondary hard disk is at /dev/sdb (it will be completely erased), you can set it up for encryption by doing in a dom0 terminal (use the same passphrase as the main Qubes disk to avoid a second password prompt at boot): Assuming the secondary hard disk is at /dev/sdb (it will be completely erased), you can set it up for encryption by doing in a dom0 terminal (use the same passphrase as the main Qubes disk to avoid a second password prompt at boot):
``` ```
sudo cryptsetup luksFormat --hash=sha512 --key-size=512 --cipher=aes-xts-plain64 --verify-passphrase /dev/sdb sudo cryptsetup luksFormat --sector-size=512 --hash=sha512 --key-size=512 --cipher=aes-xts-plain64 --verify-passphrase /dev/sdb
sudo blkid /dev/sdb sudo blkid /dev/sdb
``` ```
(The `--sector-size=512` argument can sometimes work around an incompatibility of storage hardware with LVM thin pools on Qubes. If this does not apply to your hardware, the argument will make no difference.)
Note the device's UUID (in this example "b209..."), we will use it as its luks name for auto-mounting at boot, by doing: Note the device's UUID (in this example "b209..."), we will use it as its luks name for auto-mounting at boot, by doing:
``` ```