tychobrouwer
commented
7 months ago I fixed this by creating a new GPT table with fdisk
Open Compizfox opened 8 months ago
tychobrouwer
commented
7 months ago I fixed this by creating a new GPT table with fdisk
codefiles
commented
7 months ago The Chosen configuration section of the log shows the manual partitioning option is being used to install to the device /dev/nvme0n1 adding a root and boot partition.
-- Chosen configuration --
{
...
"disk_config": {
"config_type": "manual_partitioning",
"device_modifications": [
{
"device": "/dev/nvme0n1",
"partitions": [
{
...
"flags": [
"Boot",
"ESP"
],
"fs_type": "fat32",
"mount_options": [],
"mountpoint": "/boot",
...
},
{
...
"flags": [],
"fs_type": "xfs",
"mount_options": [],
"mountpoint": "/",
...
}
],
"wipe": false
}
]
},
...
}Examining the Disk states before installing section of the log, the device you are installing to is set up as a partitionless disk.
Disk states before installing: [
...
{
...
"fstype": "xfs",
...
"path": "/dev/nvme0n1",
...
"pttype": null,
...
"type": "disk",
...
}
]It is not possible to add partitions without there being a partition table.
What happens is a parted.Partition is created for the boot partition and partition.setFlag() is called to add the boot flag to that partition. This raises the exception since the disk.type has a value of loop in this scenario rather than a partition table value like gpt or msdos.
Compizfox
commented
7 months ago IIRC I tried to create an empty GPT table at some point. Or maybe not; I'm not a 100% sure since this was some weeks ago (in the end I just installed Arch manually). I did try some stuff, but all without getting Archinstall to run successfully.
In any case, shouldn't Archinstall just create a GPT table when partitioning a disk in the case one does not already exist on a disk?
codefiles
commented
7 months ago IIRC I tried to create an empty GPT table at some point. Or maybe not; I'm not a 100% sure since this was some weeks ago (in the end I just installed Arch manually). I did try some stuff, but all without getting Archinstall to run successfully.
My conclusion is based on the log. In the Disk states before installing section of the log the fstype of the device would have been null and the pttype would have been gpt if you had created a GUID Partition Table. Instead the log shows the fstype is xfs and the pttype is null.
I have also verified my conclusion in reproducing the issue.
In any case, shouldn't Archinstall just create a GPT table when partitioning a disk in the case one does not already exist on a disk?
I think this scenario should be handled while warning the user that a file system signature was detected and it will be removed.
@svartkanin, would you mind reopening the issue? Thank you.
JoaquinDecima
commented
3 months ago I have the same error, I am trying to automate it, should I create the partition table before running the archinstall with the configuration?
Hardware model detected: QEMU Standard PC (Q35 + ICH9, 2009); UEFI mode: True
Processor model detected: AMD Ryzen 5 5600 6-Core Processor
Memory statistics: 3055156 available out of 3989264 total installed
Virtualization detected: kvm; is VM: True
Graphics devices detected: dict_keys(['Red Hat, Inc. Virtio 1.0 GPU (rev 01)'])
Disk states before installing: [
{
"children": [],
"fsavail": 0,
"fsroots": [
"."
],
"fstype": "squashfs",
"fsuse_percentage": "100%",
"fsver": "4.0",
"log_sec": 512,
"mountpoint": "/run/archiso/airootfs",
"mountpoints": [
"/run/archiso/airootfs"
],
"name": "loop0",
"partn": null,
"parttype": null,
"partuuid": null,
"path": "/dev/loop0",
"pkname": null,
"pttype": null,
"ptuuid": null,
"rota": true,
"size": "1589 MiB",
"tran": null,
"type": "loop",
"uuid": null
},
{
"children": [],
"fsavail": 0,
"fsroots": [
"."
],
"fstype": "iso9660",
"fsuse_percentage": "100%",
"fsver": "Joliet Extension",
"log_sec": 2048,
"mountpoint": "/run/archiso/bootmnt",
"mountpoints": [
"/run/archiso/bootmnt"
],
"name": "sr0",
"partn": null,
"parttype": null,
"partuuid": null,
"path": "/dev/sr0",
"pkname": null,
"pttype": "dos",
"ptuuid": "ec462901",
"rota": true,
"size": "1896 MiB",
"tran": "sata",
"type": "rom",
"uuid": "2024-06-20-02-48-59-00"
},
{
"children": [],
"fsavail": null,
"fsroots": [],
"fstype": "vfat",
"fsuse_percentage": null,
"fsver": "FAT32",
"log_sec": 512,
"mountpoint": null,
"mountpoints": [],
"name": "vda",
"partn": null,
"parttype": null,
"partuuid": null,
"path": "/dev/vda",
"pkname": null,
"pttype": null,
"ptuuid": null,
"rota": true,
"size": "20480 MiB",
"tran": "virtio",
"type": "disk",
"uuid": "EC97-0ED2"
}
]
Checking version...
Failed determine pacman version: ['/usr/bin/pacman', '-Qu', 'archinstall'] exited with abnormal exit code [1]:
Unmounting all existing partitions: /dev/vda
Unmounting: /dev/vda
Use existing device: /dev/vda
Creating partitions: /dev/vda
Traceback (most recent call last):
File "/usr/lib/python3.12/site-packages/archinstall/__init__.py", line 332, in run_as_a_module
main()
File "/usr/lib/python3.12/site-packages/archinstall/__init__.py", line 327, in main
importlib.import_module(mod_name)
File "/usr/lib/python3.12/importlib/__init__.py", line 90, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 995, in exec_module
File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
File "/usr/lib/python3.12/site-packages/archinstall/scripts/guided.py", line 245, in <module>
fs_handler.perform_filesystem_operations()
File "/usr/lib/python3.12/site-packages/archinstall/lib/disk/filesystem.py", line 54, in perform_filesystem_operations
device_handler.partition(mod, partition_table=partition_table)
File "/usr/lib/python3.12/site-packages/archinstall/lib/disk/device_handler.py", line 521, in partition
self._setup_partition(part_mod, modification.device, disk, requires_delete=requires_delete)
File "/usr/lib/python3.12/site-packages/archinstall/lib/disk/device_handler.py", line 374, in _setup_partition
partition.setFlag(flag.value)
File "/usr/lib/python3.12/site-packages/parted/decorators.py", line 28, in new
ret = fn(*args, **kwds)
^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.12/site-packages/parted/partition.py", line 214, in setFlag
return self.__partition.set_flag(flag, 1)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
_ped.PartitionException: The flag 'boot' is not available for loop disk labels.
Archinstall experienced the above error. If you think this is a bug, please report it to
https://github.com/archlinux/archinstall and include the log file "/var/log/archinstall/install.log".
Hint: To extract the log from a live ISO
curl -F'file=@/var/log/archinstall/install.log' https://0x0.stConfig
{
"additional-repositories": [
"multilib"
],
"archinstall-language": "English",
"audio_config": {
"audio": "pipewire"
},
"bootloader": "Grub",
"config_version": "2.8.0",
"debug": false,
"disk_config": {
"config_type": "default_layout",
"device_modifications": [
{
"device": "/dev/vda",
"partitions": [
{
"btrfs": [],
"dev_path": "/dev/vda1",
"flags": [
"Boot"
],
"fs_type": "ext4",
"mount_options": [],
"mountpoint": "/boot",
"obj_id": "",
"size": {
"sector_size": {
"unit": "MB",
"value": 512
},
"unit": "MB",
"value": 512
},
"start": {
"sector_size": {
"unit": "MB",
"value": 0
},
"unit": "MB",
"value": 0
},
"status": "create",
"type": "primary"
},
{
"btrfs": [],
"dev_path": "/dev/vda2",
"flags": [],
"fs_type": "ext4",
"mount_options": [],
"mountpoint": "/",
"obj_id": "",
"size": {
"sector_size": {
"unit": "MB",
"value": 15872
},
"unit": "MB",
"value": 15872
},
"start": {
"sector_size": {
"unit": "MB",
"value": 512
},
"unit": "MB",
"value": 512
},
"status": "create",
"type": "primary"
},
{
"btrfs": [],
"dev_path": "/dev/vda3",
"flags": [],
"fs_type": "ext4",
"mount_options": [],
"mountpoint": "swap",
"obj_id": "",
"size": {
"sector_size": {
"unit": "MB",
"value": 4096
},
"unit": "MB",
"value": 4096
},
"start": {
"sector_size": {
"unit": "MB",
"value": 16384
},
"unit": "MB",
"value": 16384
},
"status": "create",
"type": "primary"
}
],
"wipe": true
}
]
},
"hostname": "archlinux",
"kernels": [
"linux"
],
"locale_config": {
"kb_layout": "us",
"sys_enc": "UTF-8",
"sys_lang": "en_US"
},
"mirror_config": {
"custom_mirrors": [],
"mirror_regions": {
"Sweden": [
"https://mirror.osbeck.com/archlinux/$repo/os/$arch",
"https://mirror.bahnhof.net/pub/archlinux/$repo/os/$arch",
"https://ftp.myrveln.se/pub/linux/archlinux/$repo/os/$arch",
"https://ftp.lysator.liu.se/pub/archlinux/$repo/os/$arch",
"https://ftp.ludd.ltu.se/mirrors/archlinux/$repo/os/$arch",
"https://ftp.acc.umu.se/mirror/archlinux/$repo/os/$arch",
"http://mirror.bahnhof.net/pub/archlinux/$repo/os/$arch",
"http://ftpmirror.infania.net/mirror/archlinux/$repo/os/$arch",
"http://ftp.myrveln.se/pub/linux/archlinux/$repo/os/$arch",
"http://ftp.lysator.liu.se/pub/archlinux/$repo/os/$arch",
"http://ftp.acc.umu.se/mirror/archlinux/$repo/os/$arch"
]
}
},
"network_config": null,
"no_pkg_lookups": false,
"ntp": true,
"offline": false,
"packages": [],
"parallel downloads": 10,
"profile_config": null,
"save_config": null,
"script": "guided",
"separator": null,
"silent": true,
"skip_ntp": false,
"skip_version_check": false,
"swap": true,
"timezone": "America/Argentina/Buenos_Aires",
"version": "2.8.0"
}
svartkanin
commented
3 months ago Could you please try the master branch as this may be fixed by now
When trying to install, I get the following error when the install script is partitioning my NVMe SSD:
Complete log: