You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know this isn't yet a fully supported storage layout, but it looks like it should work and I am willing to help troubleshoot.
The installer sees the magic labels CLR_[ROOT|SWAP|BOOT] and attempts to install, but fails after prompting for LUKS password+confirm on the console (which seems broken). It seems like it's trying to recreate the encryption:
2022/01/07 21:25:14 [DBG] partprobe /dev/nvme0n1
2022/01/07 21:25:14 [DBG] Using default shellProxy.DefaultGetProxyValue
2022/01/07 21:25:14 [DBG] [Previous line repeated 4 times]
2022/01/07 21:25:14 [DBG] cmd.Env: []
2022/01/07 21:25:18 [DBG] Skipping new file system for nvme0n1p1
2022/01/07 21:25:18 [DBG] Skipping new file system for nvme0n1p3
2022/01/07 21:25:18 [INF] Mapping vg0 partition to an encrypted partition
2022/01/07 21:25:18 [DBG] cryptsetup --batch-mode --hash=sha256 --cipher=aes-xts-plain64 --key-size=512 luksFormat /dev/mapper/vg0 -
2022/01/07 21:25:18 [DBG] Using default shellProxy.DefaultGetProxyValue
2022/01/07 21:25:18 [DBG] [Previous line repeated 4 times]
2022/01/07 21:25:18 [DBG] cmd.Env: []
2022/01/07 21:25:18 [DBG] Device /dev/mapper/vg0 is in use. Cannot proceed with format operation.
root@clr-live/home/clrlinux # clr-installer
Please report this crash using GitHub Issues:
https://github.com/clearlinux/clr-installer/issues
Include the following as attachments to enable diagnosis:
/root/pre-install-clr-installer.yaml
/root/clr-installer.log
You may need to remove any personal data of concern from the attachments.
The Installer will now exit.
exit status 1
Error Trace:
errors.Wrap()
/builddir/build/BUILD/clr-installer-2.7.2/errors/errors.go:85
storage.(*BlockDevice).MapEncrypted()
/builddir/build/BUILD/clr-installer-2.7.2/storage/encrypt.go:86
I have an existing Arch install which I am trying to install alongside:
I know this isn't yet a fully supported storage layout, but it looks like it should work and I am willing to help troubleshoot.
The installer sees the magic labels CLR_[ROOT|SWAP|BOOT] and attempts to install, but fails after prompting for LUKS password+confirm on the console (which seems broken). It seems like it's trying to recreate the encryption:
clr-installer.log
pre-install-clr-installer.yaml.txt
The text was updated successfully, but these errors were encountered: