m4rt1n
April 2, 2025, 12:57pm
13
Broo!! @dalto I got it installed man!!.
I followed this comment
opened 05:35PM - 02 Nov 20 UTC
closed 02:42PM - 02 Nov 21 UTC
Distribution lubuntu 20.04, but, as far as I can tell, this is a Calamares issue… .
Calamares 3.2.20.
Before running Calamares, I have a luks-encrypted lvm partition opened
```
lsblk
...
└─sda5 8:5 0 186G 0 part
└─cryptvol 253:0 0 186G 0 crypt
├─cryptvg-swap 253:1 0 16G 0 lvm
└─cryptvg-linux 253:2 0 160G 0 lvm
```
I start Calamares, select manual partitioning, tell it that the root partition is to go /dev/cryptvg/linux (btrfs), get to the end of the procedure, it asks for confirmation to "Install Lubuntu on btrfs system partition /dev/cryptvg/linux", I say, Yes, please.
It crashes, complaining as follows:
```
Command '['btrfs', 'subvolume', 'create', '/tmp/calamares-root-2_q1ieog/@']' returned non-zero exit status 1.
None
Traceback:
File "/usr/lib/x86_64-linux-gnu/calamares/modules/mount/main.py", line 166, in run
mount_partition(root_mount_point, partition, partitions)
File "/usr/lib/x86_64-linux-gnu/calamares/modules/mount/main.py", line 94, in mount_partition
subprocess.check_call(['btrfs', 'subvolume', 'create',
File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
```
From the log, it is "successfully" sabotaging itself by closing the device before it tries to write to it:
```
ClearTempMountsJob finished. Here's what was done:
""
08:50:48 [8]: [JOBQUEUE]: Progress for Job[ 1 ]: 0 % completed
08:50:48 [8]: [JOBQUEUE]: Progress Overall: 2.32558 % (accumulated) + 0 % (this job) = 2.32558 % (total)
08:50:48 [6]: virtual void Calamares::JobThread::run()
Starting job "Clear mounts for partitioning operations on /dev/sda" (there are 32 left)
08:50:48 [6]: QStringList getPartitionsForDevice(const QString&)
Reading from "/proc/partitions"
08:50:49 [6]: virtual Calamares::JobResult ClearMountsJob::exec()
ClearMountsJob finished. Here's what was done:
"Successfully closed mapper device /dev/mapper/cryptvg-linux.\nSuccessfully closed mapper device /dev/mapper/cryptvg-swap.\nSuccessfully closed mapper device /dev/mapper/cryptvol."
```
For me, this installer is broken. Is there any workaround, or must I get another distribution which does not use the Calamares installer?
while true; sleep 0.1; do sudo vgchange -ay; done
I executed it right before hitting install & it went just smoothly as intended. I guess it did not allow the calamares to disable the volume group. Other things I just did normally as I was doing before.
I am so happy Man! I am really thankful to you for your prompt replies and assistance.
3 Likes