Archinstall encounters Error when starting - "/dev/sda3: not a block device"

[SlenLen]

exited with abnormal exit code [32]: lsblk: /dev/sda3: not a block device

When I start archinstall, it exists after a few seconds with the mentioned error. I tried the newest package from the Arch Repos, and I tried the scripts from the master branch, but regardless this error occurrs.

Running lsblk shows that sda doesn't have a 3rd partition which puzzles me. sda isn't even relevant I what I was going to do. I want to install Arch on a different device. Is there any way to make archinstall ignore this or is temporarily removing the drive the only solution?

[svartkanin]

@fabianmuehlberger this isn't related. @SlenLen I'm aware that it's quite a while already, but any chance you have the log file still available, under /var/log/archinstall/install.log

[svartkanin]

@SlenLen archinstall is reading all available disks at startup, that's to be able to display all possible options to the user what devices they can choose from. It isn't possible to filter them away. I'd say that the error isn't related to archinstall as lsblk has issues reading the device all together which could indicate that there is some issue with it. A restart might help to resolve it. In any case to debug this more info would be required

[rearrangement]

exited with abnormal exit code [32]: lsblk: /dev/sda3: not a block device

When I start archinstall, it exists after a few seconds with the mentioned error. I tried the newest package from the Arch Repos, and I tried the scripts from the master branch, but regardless this error occurrs.

Running lsblk shows that sda doesn't have a 3rd partition which puzzles me. sda isn't even relevant I what I was going to do. I want to install Arch on a different device. Is there any way to make archinstall ignore this or is temporarily removing the drive the only solution?

By chance, are you trying to install Hyprland? And are you clearing / wiping all disks before installation, because in my case, there was an invalid configuration, and that seemed to fix it. If you are wiping all disks, try NOT doing that and just re-running the installation, because that also worked in my case.

[codefiles]

This bug is still present though the code has changed a little so it looks slightly different in the latest reports of it.

A DiskError is raised like the following:

archinstall.lib.exceptions.DiskError: Failed to read disk "/dev/sda1" with lsblk

This will appear in the log as:

Error calling lsblk: lsblk: /dev/sda1: not a block device
{
   "blockdevices": [

   ]
}

I can't reproduce the bug but I have seen logs for other issues where this is present, for example #2540 and #2563. In those cases the logs show that the partitions that lsblk failed for are valid as their lsblk information is listed later in the logs under Disk states before installing.

[rearrangement]

This bug is still present though the code has changed a little so it looks slightly different in the latest reports of it.

A DiskError is raised like the following:

archinstall.lib.exceptions.DiskError: Failed to read disk "/dev/sda1" with lsblk

This will appear in the log as:

Error calling lsblk: lsblk: /dev/sda1: not a block device
{
   "blockdevices": [

   ]
}

I can't reproduce the bug but I have seen logs for other issues where this is present, for example #2540 and #2563. In those cases the logs show that the partitions that lsblk failed for are valid as their lsblk information is listed later in the logs under Disk states before installing.

correct, the way to reproduce this (atleast from my understanding) is by having a config that creates problems with another part of something that you picked