Failed to read disk ... with lsblk

[mmbrom]

Which ISO version are you using?

2025.01.01

The installation log

Process 61 stopped
* thread #1: tid = 61, 0x00007effaf9f8790, name = 'fhost'
    frame #0:
Process 61 stopped
* thread #8: tid = 61, 0x00007f007d647160 fhost`get(path='/BXYi.log') + 27 at fhost.c:139, name = 'fhost/responder', stop reason = invalid address (fault address: 0x30)
    frame #0: {3:#018x} fhost`get(path='/BXYi.log') + 27 at fhost.c:139
   136   get(SrvContext *ctx, const char *path)
   137   {
   138       StoredObj *obj = ctx->store->query(shurl_debase(path));
-> 139       switch (obj->type) {
   140           case ObjTypeFile:
   141               ctx->serve_file_id(obj->id);
   142               break;
(lldb) q

describe the problem

Installation process crashed about 1 Second after it partitioned the drive. Partitioning config was chosen as "best effort partitioning" on a 256 GB SATA SSD with 1GB FAT32 boot partition and rest as BTRFS root partition.

Left Python Stacktrace, which I unfortunately only partially captured. It ended with:

File "/usr/lib/python3.13/site-packages/archinstall/lib/installer.py", line 256, in _mount_partitio[...]
    self._mount_partition(part_mod)
File "/usr/lib/python3.13/site-packages/archinstall/lib/installer.py", line 321, in _mount_partitio[...]
    disk.device_handler.mount(part_mod.dev_path, target, options=part_mod.mount_options)
File "/usr/lib/python3.13/site-packages/archinstall/lib/device/device_handler.py", line 728[...]
    lsblk_info = get_lsblk_info(dev_path)
File "/usr/lib/python3.13/site-packages/archinstall/lib/device/device_model.py", line 1477 [...]
    infos = _fetch_lsblk_info(dev_path, reverse=reverse, full_dev_path=full_dev_path)
File "/usr/lib/python3.13/site-packages/archinstall/lib/device/device_model.py", line 1464 [...]
    raise DiskError(f'Failed to read disk "{dev_path}" with lsblk')
archinstall.lib.exceptions.DiskError: Failde to read disk "/dev/sda1" with lsblk

Other Hardware was Ryzen 5600 and RTX 3060.

[codefiles]

There are a few issues (#2726, #2769, #2770) with the Process number stopped message in the log. Upon reviewing those, I think the failed lsblk is probably a red herring but I may be wrong.

[svartkanin]

Can you please upload the whole log file

[mmbrom]

This is the whole uploaded log. I used the suggested command of curl -F'file=@/var/log/archinstall/install.log' https://0x0.st, but admittedly failed to manually check the log while the failed system was running. I too was surprised by the short length, but fail to see how I could have mistyped that command such that it resulted in truncated output.

[svartkanin]

There should definitely be more in the log