failed to list mountpoints

[a-joyes]

Hello, I have this message when come the installation :
Setup [1/24]: vgremove
Setup [2/24]: pvremove
Setup [3/24]: pvremove
Setup [4/24]: label
panic : failed to run setup operation label: label: failed to unmount partition /dev/sda1: failed to list mountpoints for /dev/sda1: lsblk: /dev/sda1: not a block device

Can you help me please ?
Thx

[Novemberheks]

Hi, I think I've got the same issue. I'm trying to run setup with encryption on an old laptop with a previous install from another distro on it.

Log:

Setup [1/21]: label
panic: failed to run setup operation label: label: failed to unmount partition /dev/sda7: failed to list mountpoints for /dev/sda7: not a block device

goroutine 1 [running]:
main.main()
github.com/vanilla-os/albius/albius.go
:22 +0x106

I managed to locate the partition through settings -> search -> custom locations -> + Add Location (this starts the file manager). Then right click on any volume in the select location area and choose 'properties'. In properties, choose 'Open in Disks'. In Disks, /dev/sda7 is a swap partition. Apparently there is a problem with swap, perhaps in relation to encryption (I think I read that somewhere, not sure).

Thanks.

[Novemberheks]

Ok, I was able to remove all partitions from the previous Linux install and restart the installer through apps in the settings. I chose manual partioning instead of selecting to use the entire disk. Then I repartitioned with gparted which is available from there, using the suggestions given. It all seems to be installing fine now, with encryption enabled.

Edit:
When using encryption, you may need to follow this instruction to be able to boot into your system:
Vanilla-OS/vanilla-installer#464 (comment)

Can this be confirmed as a solution for now?

[taukakao]

@Novemberheks
I tested installing with a swap partition and it worked fine so that doesn't seem to be the issue.
But it's definitely related to the existing partitions so manually removing them should always be a valid workaround for this issue.

Of course if the swap partition is currently active then it will cause an issue but it produces a different error message. But that should never be an issue anyway since swap partitions aren't activated by default.