mount: [...] fsconfig() failed: /dev/sda1: Can't lookup blockdev. #146
Description
I just installed WoeUSB from Gentoo's repositories and tried flashing a Windows 11 ISO to both my USB drives. Both of them had the exact same error at the Mounting target filesystem step.
Here's the full output of my command:
$ doas woeusb --device Win11_25H2_English_x64.iso /dev/sda --verbose
WoeUSB v0.2.12
==============================
Info: Target device is /dev/sda
Info: Target partition is /dev/sda1
Mounting source filesystem...
Warning: File /media/woeusb_source_1762668399_11550/sources/install.wim in source image has exceed the FAT32 Filesystem 4GiB Single File Size Limitation, swiching to NTFS filesystem.
Refer: https://github.com/slacka/WoeUSB/wiki/Limitations#fat32-filesystem-4gib-single-file-size-limitation for more info.
Wiping all existing partition table and filesystem signatures in /dev/sda
/dev/sda: 2 bytes were erased at offset 0x000001fe (dos): 55 aa
/dev/sda: calling ioctl to re-read partition table: Success
Ensure that /dev/sda is really wiped...
Creating new partition table on /dev/sda...
Creating target partition...
Making system realize that partition table has changed...
Wait 3 seconds for block device nodes to populate...
Failed to access '/dev/sda1': No such file or directory
The device doesn't exist; did you specify it correctly?
Mounting target filesystem...
mount: /media/woeusb_target_1762668399_11550: fsconfig() failed: /dev/sda1: Can't lookup blockdev.
dmesg(1) may have more information after failed mount system call.
Error: Unable to mount target media
Error: Unable to mount target filesystem
Unmounting and removing /media/woeusb_source_1762668399_11550...
You may now safely detach the target device
I don't think the problem is on my drives as I've tested them before using and they were working just fine.
I also suspected there was something missing on my kernel configuration as the script wouldn't work at all with my previous setup, so I tried to adapt it and enabled loop device and NTFS support. No difference between having the latter enabled and disabled, however.
So what could it be? Is is just mount's fault at this point?