Calamares finishes its install process and when I reboot it fails . It gets past grub and then starts the kernel but then crashes to the cli with the error:
ERROR ’ ’ device did not show up after 30 seconds …
Calamares finishes its install process and when I reboot it fails . It gets past grub and then starts the kernel but then crashes to the cli with the error:
ERROR ’ ’ device did not show up after 30 seconds …
The initramfs can not find the disk device on which the kernel was installed.
Are You installing to a normal internal disk?
I have 2 session logs but I can’t put them in here they are too large.
one of them I created the partitions and the other I chose the alongside option in calamares and I got the same result both times.
After looking at what is on the created drive the fstab file has nothing in it . Not sure if that is an issue but I assume it is.
You need fstab. Can you boot an USB iso and then show what lsblk says. It should show the USB and your SSD info. What distro you’re installing?
How did that happen? The installer should have made an fstab file.
Can you mount the created filesystem from another linux, then make an /etc/fstab file with an editor?
You could probably copy the fstab from another linux, then alter the UUID’s for each filesystem to those of your new partitions.
To get UUID’s use blkid … you may have to install it.
As @ihasama said, use ‘lsblk’ to identify all your partitions.
Google AI suggests the following
" Recovery Steps
If you encounter an empty /etc/fstab, consider the following steps:
fstab.pacorig in the /etc directory. If it contains the correct entries, you can rename it to fstab.fstab:genfstab -U /mnt > /mnt/etc/fstab
Verify Mount Points: Ensure that all necessary partitions (like root, boot, and home) are mounted before generating the fstab file."
I find that suggestion rather confusing. It omits details.
I would rather just make a new fstab file by hand.
Apparently this is a known issue with Calamares, especially if you dont get the filesystem mounts correct.
Another suggestion: Use Artix instead of Arch. That may avoid the problem.