Tag Info

New answers tagged

0

If all you want to change is the hash, there is no need to re-encrypt. You still have to build a new LUKS header though. Same cipher, same master key, same offset, different hash. You can try this for yourself. First we set up a LUKS device with standard settings and lousy iter counts: # truncate -s 8M /dev/shm/foobar # cryptsetup --iter-time=42 luksFormat ...


1

dd if=/dev/mapper/storage2-crypto bs=16 count=1 2>/dev/null | od -t c -t x1 0000000 L U K S 272 276 \0 001 a e s \0 \0 \0 \0 \0 4c 55 4b 53 ba be 00 01 61 65 73 00 00 00 00 00 That's what it looks like on my system. See http://wiki.cryptsetup.googlecode.com/git/LUKS-standard/on-disk-format.pdf (page 6) The ...


0

Reason may be a few: A calculation way - base of prefixes (1000 vs. 1024) 334*1024*1024*1024/(1000*1000*1000) = 358.63 You can check disk and partitions size by: fdisk -l /dev/sdc Linux file systems reserving (by default) 5% (mkfs.ext4 -m PERCENT) free space accessed only by root (partition overflow protection) File system structures have some size ...


3

Hmm ... apparently this line was the clue: grub-install: warning: Attempting to install GRUB to a disk with multiple partition labels. This is not supported yet.. Previously I had installed btrfs directly on /dev/sda and /dev/sdb. That's why both of them had a FSTYPE and LABEL attached (as shown in lsblk). Solution: I have now wiped both /dev/sda and ...



Top 50 recent answers are included