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
Mounting /dev/sda1: mount /dev/sda1 /mnt/arch_btrfsPartition /dev/sda1 is currently mounted at: ['/mnt/arch_btrfs']Unmounting mountpoint: /mnt/arch_btrfsMounting /dev/sdb1: mount /dev/sdb1 /mnt/arch_btrfsPartition /dev/sdb1 is currently mounted at: ['/mnt/arch_btrfs']Unmounting mountpoint: /mnt/arch_btrfsMounting /dev/sdc1: mount /dev/sdc1 /mnt/arch_btrfsPartition /dev/sdc1 is currently mounted at: ['/mnt/arch_btrfs']Unmounting mountpoint: /mnt/arch_btrfsMounting /dev/sdd1: mount /dev/sdd1 /mnt/arch_btrfsPartition /dev/sdd1 is currently mounted at: ['/mnt/arch_btrfs']Unmounting mountpoint: /mnt/arch_btrfsCould not determine the filesystem: NoneError calling lsblk: lsblk: /dev/nvme0n1p1: not a block device
{
"blockdevices": [
]
}
describe the problem
Description of the issue
When running archinstall in the live Arch iso image, the following error happens:
It appears that archinstall has trouble running lsblk on /dev/nvme0n1p1 which is the boot partition of my existing Arch installation.
However, running lsblk manually lists the affected block device just fine:
nvme0n1 259:2 0 931,5G 0 disk
├─nvme0n1p1 259:3 0 1G 0 part /boot
├─nvme0n1p2 259:4 0 865G 0 part /var/cache/pacman/pkg
│ /var/log
│ /home
│ /
Which ISO version are you using?
archlinux-2024.11.01-x86_64.iso
The installation log
describe the problem
Description of the issue
When running
archinstall
in the live Arch iso image, the following error happens:It appears that archinstall has trouble running lsblk on
/dev/nvme0n1p1
which is the boot partition of my existing Arch installation.However, running
lsblk
manually lists the affected block device just fine:CPU: AMD Ryzen 7 5700G with Radeon Graphics
Memory: 32GB
GPU: AMD Radeon RX 7800 XT
Mainboard: MSI B550-A-PRO
Drive: Samsung 980 PRO 1TB SSD
The text was updated successfully, but these errors were encountered: