Stuck on lvm-luks-format when installing with encryption
Closed this issue · 2 comments
zehkira commented
Setup [1/20]: label
Setup [2/20]: mkpart
Discarding device blocks: done
Creating filesystem with 262144 4k blocks and 65536 inodes
Filesystem UUID: 133ef921-83bf-4d79-9d08-ecba6148016e
Superblock backups stored on blocks:
32768, 98304, 163840, 229376
Allocating group tables: done
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
Setup [3/20]: mkpart
mkfs.fat 4.2 (2021-01-31)
Setup [4/20]: mkpart
Setup [5/20]: mkpart
Setup [6/20]: pvcreate
Setup [7/20]: pvcreate
Setup [8/20]: vgcreate
Setup [9/20]: vgcreate
Setup [10/20]: lvcreate
Setup [11/20]: lvm-format
Discarding device blocks: done
Creating filesystem with 131072 4k blocks and 32768 inodes
Filesystem UUID: cf1c86d6-6178-4bb4-a03c-edb9b613a100
Superblock backups stored on blocks:
32768, 98304
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
Setup [12/20]: lvcreate
Setup [13/20]: lvcreate
Setup [14/20]: make-thin-pool
Setup [15/20]: lvcreate-thin
Setup [16/20]: lvcreate-thin
Setup [17/20]: lvm-format
btrfs-progs v6.6.3
See https://btrfs.readthedocs.io for more information.
Performing full device TRIM /dev/vos-root/root-a (19.00GiB) ...
NOTE: several default settings have changed in version 5.15, please make sure
this does not affect your deployments:
- DUP for metadata (-m dup)
- enabled no-holes (-O no-holes)
- enabled free-space-tree (-R free-space-tree)
Label: (null)
UUID: 093bf450-c884-4cca-8d1a-30ec9ad5d078
Node size: 16384
Sector size: 4096
Filesystem size: 19.00GiB
Block group profiles:
Data: single 8.00MiB
Metadata: DUP 256.00MiB
System: DUP 8.00MiB
SSD detected: no
Zoned device: no
Incompat features: extref, skinny-metadata, no-holes, free-space-tree
Runtime features: free-space-tree
Checksum: crc32c
Number of devices: 1
Devices:
ID SIZE PATH
1 19.00GiB /dev/vos-root/root-a
Setup [18/20]: lvm-format
btrfs-progs v6.6.3
See https://btrfs.readthedocs.io for more information.
Performing full device TRIM /dev/vos-root/root-b (19.00GiB) ...
NOTE: several default settings have changed in version 5.15, please make sure
this does not affect your deployments:
- DUP for metadata (-m dup)
- enabled no-holes (-O no-holes)
- enabled free-space-tree (-R free-space-tree)
Label: (null)
UUID: d8012d3f-ca00-47a3-9208-1f806c594882
Node size: 16384
Sector size: 4096
Filesystem size: 19.00GiB
Block group profiles:
Data: single 8.00MiB
Metadata: DUP 256.00MiB
System: DUP 8.00MiB
SSD detected: no
Zoned device: no
Incompat features: extref, skinny-metadata, no-holes, free-space-tree
Runtime features: free-space-tree
Checksum: crc32c
Number of devices: 1
Devices:
ID SIZE PATH
1 19.00GiB /dev/vos-root/root-b
Setup [19/20]: lvcreate
Setup [20/20]: lvm-luks-format
Installing VanillaOS-2-testing.20240306 (118) with encryption, VM tools and automatic partitions on a 30GB VM. The installation never finishes. I waited for almost 3 hours.
zehkira commented
Tried the same setup but:
- without VM tools: same result
- without encryption:
panic: failed to copy installation files: failed to pull OCI image: writing blob: storing blob to file "/var/tmp/container_images_storage432690568/55": write /var/tmp/container_images_storage432690568/55: no space left on device
goroutine 1 [running]:
main.main()
github.com/vanilla-os/albius/albius.go:32 +0xf4
- without encryption on a 42GB VM: installed successfully
I had to recreate the VM on every attempt due to Vanilla-OS/vanilla-installer#370.
zehkira commented