Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: Can't boot after installing Artix (Read 2339 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Can't boot after installing Artix

Hi all,

I'm new to Artix, and these past few days I've been trying to use Artix, but I can't boot into the system.
I can install it without any problems, I tried these 2 images so far:

  • artix-lxde-dinit-20240823-x86_64.iso
  • artix-lxde-runit-20240823-x86_64.iso

And both images install without problems, I always opt for Erasing the full disk, enable disk encription and BRTFS file system.

When I try to boot my computer, after typing my encription password, it shows the GRUB menu.
When I press Enter (or leave it to automatically enter for me), it shows this error:

Code: [Select]
Booting 'Artix Linux'

Loading Linux linux ...
Loading initial ramdisk ...
error: start_image() returned 0x8000000000000001

  Failed to boot both default and fallback entries.

Press any key to continue ...

I tried installing using the offline mode, online mode, but it always gives me this error when booting after install.

Re: Can't boot after installing Artix

Reply #1 –
I think calamares breaks with brtfs. It did with me.

Re: Can't boot after installing Artix

Reply #2 –
Quote from: n00b – on
I think calamares breaks with brtfs. It did with me.


Hmm thanks for letting me know, I only tried with BTRFS, I'll try EXT4 and I'll update here.

Re: Can't boot after installing Artix

Reply #3 –
Indeed the problem was BTRFS, I tried with EXT4 and everything worked flawlessly.

Re: Can't boot after installing Artix

Reply #4 –
I have had the same problem when trying to install with btrfs.

Re: Can't boot after installing Artix

Reply #5 –
i guess someone should tell calamares?

Re: Can't boot after installing Artix

Reply #6 –
Quote from: n00b – on
i guess someone should tell calamares?

I don't think the problem is with calamares as I successfully installed archcraft distro with btrfs using calamares to test that.  It seems the problem is with Artix? Just my guess, I am no expert!

Re: Can't boot after installing Artix

Reply #7 –
Even though this topic is marked as solved, I just recently faced the same problem with the latest stable iso 20250407 when trying to install Artix-dinit-xfce on an unencrypted btrfs partition as root. I even got a screen like the one on this other post: https://forum.artixlinux.org/index.php/topic,8243.msg49269.html at one point. But eventually managed to fix it so, since this is the first result that came up on my search, I'm leaving this here so other people can try and see if it works for them.

So, after trying with the usual stuff, which included testing the weekly iso, reinstalling grub, tinkering with fstab and mkinit; none of which worked; I managed to boot normally through grub2disk, which confirmed grub was pointing to the right subvolume (created by Artix installer) for root, so the problem was somewhere else.

Then I came across this old post (https://forum.endeavouros.com/t/boot-issue-grub-when-transitioning-into-initrd-initramfs-img-error-start-image-returned-0x8000000000000001/54238), which suggests editing or adding the next line on ´/etc/default/grub´ :

Code: [Select]
GRUB_EARLY_INITRD_LINUX_STOCK=''

After which I rebuilt mkinit and ran ´update-grub´ and... it worked.

So... the problem seems to be AMD microcode and it seems to trigger on (some?) AMD processors. Curiously enough I remember installing Artix on an Intel machine last year without problems. Perhaps someone with more knowledge can look further into it.

Re: Can't boot after installing Artix

Reply #8 –
Quote from: lact500 – on
Even though this topic is marked as solved, I just recently faced the same problem with the latest stable iso 20250407 when trying to install Artix-dinit-xfce on an unencrypted btrfs partition as root. I even got a screen like the one on this other post: https://forum.artixlinux.org/index.php/topic,8243.msg49269.html at one point. But eventually managed to fix it so, since this is the first result that came up on my search, I'm leaving this here so other people can try and see if it works for them.

So, after trying with the usual stuff, which included testing the weekly iso, reinstalling grub, tinkering with fstab and mkinit; none of which worked; I managed to boot normally through grub2disk, which confirmed grub was pointing to the right subvolume (created by Artix installer) for root, so the problem was somewhere else.

Then I came across this old post (https://forum.endeavouros.com/t/boot-issue-grub-when-transitioning-into-initrd-initramfs-img-error-start-image-returned-0x8000000000000001/54238), which suggests editing or adding the next line on ´/etc/default/grub´ :



I doesn't sound o me like they have any idea what they are doing or saying in this foreign thread. 

Quote
In that thread you linked, the problem turned out to be the AMD microcode was getting double-loaded. It was bundled into the image by dracut, and then Grub was also loading it a second time which was causing the issue. You can prevent Grub from doing this by setting this option in /etc/default/grub:…

This COULD be true but it has zero to do with Luks or BRTFs and a gig of space for efi is really large.  If and binrary is dragcut into the vmlinuz image and then you are telling grub to include it again, then this would be a problem with all the installations and have a pattern of trouble with BRTFS (and luks)