Page MenuHomePureOS Tracker
Create Task
Maniphest T143

Doing an encrypted install of PureOS with Calamares fails on NVMe drive
Closed, DuplicatePublic
Actions

Description

When doing an encrypted install of PureOS through the live usb image using Calamares on the NVMe of a Librem13 v2, I get the following error as soon as the install starts partitioning the disk :

The installer failed to create file system on partition /dev/nvme0n1p1.
===================================================================================
Command: cryptsetup -s 512 --batch-mode --force-password luksFormat /dev/nvme0n1p1
===================================================================================
===================================================================================
Command: cryptsetup open /dev/nvme0n1p1 luks-22f3066-56f4-4cf2-a410-07de5fb19e2e
===================================================================================
===================================================================================
Command: mkfs.ext4 -qF /dev/mapper/nvme0n1p1
===================================================================================

This doesn't happen if I choose not to encrypt the drive.

Event Timeline

francois created this task.Jul 10 2017, 15:10
zlatan.todoric reassigned this task from zlatan.todoric to mak.Jul 29 2017, 20:43
zlatan.todoric added a subscriber: zlatan.todoric.
• qwerty123 added a subscriber: • qwerty123.EditedAug 11 2017, 12:06

I reproduced this installing PureOS via Calamares on a Librem 15v3.

For anyone else who may end up here:
I was able to get around it by booting directly to the installer (not the "graphical" installer) and doing an encrypted install this way.

Installing this way led to a different bug (GRUB not working correctly or some such), that causes SeaBIOS to hang on startup. Got around this by attempting to install the LILO bootloader (which option you can see if you hit the "back" button at the GRUB screen in installer). This fails, but installer subsequently recognized some sort of EFI compatibility issue and suggested installing GRUB to a removable disk directory or some such as well. After installing GRUB this different way, it then boots correctly from SeaBIOS.

mak added a comment.Aug 11 2017, 16:06

This particular bug should be resolved now - please verify!