You are not logged in.
Hello,
I just wanted to install Arch on a new laptop, so I pulled the latest ISO and put it on a stick, however I do get the following error:
Waiting 10 seconds for device /dev/disk/by-uuid/2026-07-01-16-36-20-00 ...
ERROR: Device '2026-07-01-16-36-20-00' not found
sh: can't access tty; job control turned offIt has nothing to do with the laptop as I tried a different laptop (where arch runs fine) and got the same error.
I also ran it with an older version of the arch install iso from 2024 with the same result.
I formatted the USB via RUFUS and like this:
dd if=archlinux-2026.07.01-x86_64.iso of=/dev/sdb2Anybody got an clue what it could be?
Offline
dd if=archlinux-2026.07.01-x86_64.iso of=/dev/sdb2
You're supposed to write in onto the disk, not some partition.
https://wiki.archlinux.org/title/USB_fl … _utilities
Online
dd if=archlinux-2026.07.01-x86_64.iso of=/dev/sdb2
You're supposed to write in onto the disk, not some partition.
https://wiki.archlinux.org/title/USB_fl … _utilities
That is what I did. I typed the command from memory sorry for the confussion
Last edited by Stefan_xyz (2026-07-27 17:06:29)
Offline
Plug the usb key into a linux system and post the output of "lsblk -f"
Can you boot it on some other host than that notebook?
Online
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda iso9660 Joliet Extension ARCH_202607 2026-07-01-16-36-20-00
├─sda1 iso9660 Joliet Extension ARCH_202607 2026-07-01-16-36-20-00
└─sda2 vfat FAT32 ARCHISO_EFI 6A45-4204As already stated in my original post I get the same error when I plug it into another Laptop.
Offline
So various hosts can boot various iterations of the install iso but then not find the root partition?
How/when did you install arch on the other laptop? Booting an iso or replacing an existing system?
Have you tried to replug the usb key while the kernel is waiting for the FS?
You can add "rootwait" to the kernel parameters to wait indefinitely for it to show up.
Online
seth: I had the same issue yesterday. I can confirm that re-plugging the usb stick helped - I did it once I saw first usb related errors in console. Thanks a lot!
rootwait did nothing for me.
What may be the cause of this behavior? Any ideas?
Offline
rootwait was rather meant to give you all the time in the world to deal with the USB superstate ![]()
It might be related to how the USB is handed off to the OS - do you have a bios setting for that?
This should™ be HW specific (I just remembered that some netbook did that like 15 years ago) - it might be interesting to correlate the involved systems.
Online