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
{{ message }}
This repository has been archived by the owner on Apr 9, 2022. It is now read-only.
So I'm not 100% sure what the problem is with this but I got a new notebook with an NVMe(Samsung Evo960) and trying to install Anarchy on the NVMe will fail, as long as I create a swap partition.
Full disk setup when failing is UEFI boot partition, then LVM(encrypted) with swap and root("encrypted LVM" option from menu). When I use the "encrypted LVM" option but say no when the installer asks if I want to create a swap partition, everything works out fine.
What I did notice is the disk returning no data when creating a swap partition and then using dd with a bs of 512. With 4k blocksize everything works fine and I can see the LVM meta data when piping this to a hexdump - this is where the bootloader later chokes on after rebooting. Even during setup when the installer is copying data to the mounted partitions for some weird reason neither the LVM nor the partitions show up in fdisk/gdisk.
Since I need that notebook atm I can't really do a lot of testing but if needed I could do a backup and reinstall once or twice in maybe a month or two if noone else can reproduce this behaviour.
The text was updated successfully, but these errors were encountered:
So I'm not 100% sure what the problem is with this but I got a new notebook with an NVMe(Samsung Evo960) and trying to install Anarchy on the NVMe will fail, as long as I create a swap partition.
Full disk setup when failing is UEFI boot partition, then LVM(encrypted) with swap and root("encrypted LVM" option from menu). When I use the "encrypted LVM" option but say no when the installer asks if I want to create a swap partition, everything works out fine.
What I did notice is the disk returning no data when creating a swap partition and then using
dd
with a bs of 512. With 4k blocksize everything works fine and I can see the LVM meta data when piping this to a hexdump - this is where the bootloader later chokes on after rebooting. Even during setup when the installer is copying data to the mounted partitions for some weird reason neither the LVM nor the partitions show up infdisk
/gdisk
.Since I need that notebook atm I can't really do a lot of testing but if needed I could do a backup and reinstall once or twice in maybe a month or two if noone else can reproduce this behaviour.
The text was updated successfully, but these errors were encountered: