Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Secondary storage: work around 4k incompatibility, drop unnecessary luksFormat arguments #1443

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Secondary storage: work around 4k incompatibility, drop unnecessary luksFormat arguments #1443

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
cc00196
luksFormat: add --sector-size=512 argument
rustybird Dec 20, 2024
4fb0f0c
luksFormat: drop arguments that are already the default
rustybird Dec 20, 2024
65e0511
luksFormat: drop --hash=sha512 argument
rustybird Dec 20, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion user/advanced-topics/secondary-storage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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):

```
sudo cryptsetup luksFormat --hash=sha512 --key-size=512 --cipher=aes-xts-plain64 --verify-passphrase /dev/sdb
sudo cryptsetup luksFormat --sector-size=512 /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:

```
Expand Down