You are not logged in.
Hello, first of all I'm a newbie. I have been following a online course about the installation process of Arch Linux but I'm stuck.
I want to have a triple boot setup on my Lenovo Laptop (Windows, Ubuntu and Arch Linux), but when trying to boot from my USB flash drive, it takes me to the boot loader menu and I select Arch Linux install medium.
After a few seconds I get the following error:
https://imgur.com/a/IzVKJFs
I show a screenshot of Disks Ubuntu program where appears my SSD and USB flash drive partitions.
https://imgur.com/a/yEFxsxw
Why is trying to search the boot folder from the bootable USB in the SSD, it doesnt have sense for me.
I also tried to follow the installation guide from the Arch Linux wiki, and on the section 1.4 Boot the live environment it says that the ISO uses syslinux boot loader for BIOS booting, and that using Tab i could enter the boot parameters, and i figured that maybe i could change something there that solve my problem but pressing tab doesnt do anything.
Arch Linux Installation guide
Next i show an image from my BIOS.
https://imgur.com/a/shUg5xR
Last edited by MiguelDonado (2024-05-17 14:05:18)
Offline
The "arch linux install medium" is trying to find the iso to continue booting but doesn't find it where it expects it.
It then tries all drives present in the system just in case it may be in an unexpected location, but fails.
Unless your lenovo laptop is older then approx 10 years , it uses Uefi to boot, not bios .
Most likely cause of the issue is that the usb stick was created wrong.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
If the USB drive was created correctly and it still can't find the device, try setting the rootdelay= kernel parameter. The default is 2 seconds, so try e.g.:
rootdelay=5
Offline
Yes, first thank you for your time, as you mentioned my laptop uses UEFI instead of BIOS (because of the old-fashioned interface i thought it was BIOS).
Regarding the USB and the installation, it still doesnt work, since your reply I tried many ways (rufus, isoimagewriter, etcher) and the next command line:
cat ../home/miguel/Downloads/archlinux-2024.05.01-x86_64\(1\).iso > /dev/disk/by-id/usb-General_UDisk-0\:0
I also used
wipefs --all /dev/disk/by-id/usb-General_UDisk-0\:0
after each try, but it doesnt work.
I dont know exactly what im doing wrong.
Offline
Don't use etcher, https://wiki.archlinux.org/title/USB_fl … ing_etcher
rufus is known to cause this unless using the DD mode but the other two methods sshould work.
https://imgur.com/a/yEFxsxw looks like the proper LABEL is there, try to increase the rootdelay or just use rootwait to wait indefinitely
Offline
rootwait won't work since the archiso hooks don't use it.
If rootdelay= doesn't help, when you get dumped to the rootfs shell, run:
# blkid
# ls -l /dev/disk/by-uuid/
and post the output (or a image of it).
Offline
Thank you for your time Lone_Wolf, nl6720, seth.
Rootdelay did the trick, I've been a week or so stuck, I wanted to try different ways before posting on the forum.
Offline
Which is the smallest rootdelay value that works for you? I could increase the default.
Offline
I only tried rootdelay=20 and it works.
Offline
If you have the time, I'd appreciate if you could test which is the lowest value that works for you.
Offline
By all means:
rootdelay=3 (doesnt work)
rootdelay=From 4 onwards (work)
Offline
Thanks! I created a merge request archlinux/mkinitcpio/mkinitcpio-archiso!53 to increase the default (targeting July's ISO).
Offline