User talk:Altercation/Bullet Proof Arch Install

From ArchWiki


Just wanted to say those partitioning tables are pretty cool. And their source is readable at that! Cheers -- Alad (talk) 09:22, 2 December 2016 (UTC)Reply[reply]

Thanks User:Alad, they took me a while! Still some cleanup to do, but I felt that there needed to be a visual to make things clear. Appreciate the feedback. -Ethan


Hm, install works fine but I can't boot. Could you add an EFI boot section? I tried with efibootmgr and systed-boot but somehow I don't know how to properly get my root partition. Dreivier (talk) 15:00, 2 January 2017 (UTC)Reply[reply]

--> solved it and will post my solution latern on Dreivier (talk) 08:00, 10 January 2017 (UTC) --> here it is:[reply]

System partition type shows 8200 Linux Swap should this be 8300 Linux filesystem ?

sgdisk --zap-all /dev/sda

sgdisk --clear \

      --new=1:0:+550MiB --typecode=1:ef00 --change-name=1:EFI \
      --new=2:0:+12GiB  --typecode=2:8200 --change-name=2:swap \
      --new=3:0:0       --typecode=2:8200 --change-name=3:system \


sgdisk --zap-all /dev/sda

sgdisk --clear \

      --new=1:0:+550MiB --typecode=1:ef00 --change-name=1:EFI \
      --new=2:0:+12GiB  --typecode=2:8200 --change-name=2:swap \
      --new=3:0:0       --typecode=2:8300 --change-name=3:system \

It's repeated as that through out the document would have to change in multiple locations if not correct.

Seems to be missing in the write up mkdir /mnt/boot for efi also missing in the command review at the end.

—This unsigned comment is by NonaSuomy (talk) 20:39, 14 June 2017‎. Please sign your posts with ~~~~!

Error with boot partition labeled as EFI

I'm just posting this to prevent future errors,

apparently is wide common having a boot partition labeled as EFI, so last day I had a windows installed in an USB ssd that "hijacked" my boot partition and was mounted instead the real one; after updating and regenerating mkinitcpio that created a huge mess. Maybe it would be usefull label boot partition as another name to prevent this.

—This unsigned comment is by Thongil (talk) 13:09, 31 December 2018‎. Please sign your posts with ~~~~!

Mounting btrfs root subvolume

Using my laptop to mount the root subvolume with the mount -t btrfs -o subvol=root,$o_btrfs LABEL=system /mnt command returns this error: [ 3545.459506 ] BTRFS error(device dm-0): open_ctree failed

mount: /mnt: wrong fs type, bad option, bad superblock on /dev/mapper/system, missing codepage or helper program or other error.

I did everything as described here apart from the swap partition and the home subvolume, as I want that on another disk.

EDIT: I rebooted my machine and it went on flawlessly without errors the second time.

—This unsigned comment is by Lorecast162 (talk) 12:41, 13 January 2020‎. Please sign your posts with ~~~~!

Fix (workaround) for systemd-nspawn "Login incorrect" error

Just going through this setup again as an exercise as a newbie, each time I got to this point in the setup, where instead of arch-chrooting into the new system it's suggested to use "systemd-nspawn," this has always gotten my tty instance stuck and unable to login or exit the prompt. Today I just had an idea how to fix this while stuck here again and the solution is simple:

Open another tty (alt-f2 in my case) and use "arch-chroot /mnt" to chroot into the new system. Then, as root, set a password by typing "passwd" hitting enter and creating the new password. Now exit chroot go back to your original tty and try to login again with the root password you just created. Viola! Works for me. I hope this may help someone else as well. Also it's my first time editing and I am on my phone so I hope the formatting isn't too bad, apologies if so.
Nisma (talk) 19:27, 22 September 2020 (UTC)Reply[reply]

July 2021 and I'm running through these instructions on a fresh machine, I am unable to sign in as root using the guide, nor by adding entries to /mnt/etc/securetty, nor by deleting /mnt/etc/securetty and /mnt/usr/share/factory/etc/securetty.

I was able to sign-in using the described method in the Arch Wiki article for systemd-nspawn

Teknobilly (talk) 17:13, 3 July 2021 (UTC)Reply[reply]

This guide is over 5 years old now, with some intermediate bug fixes by users. Curious why people are still following it. -- Alad (talk) 09:08, 4 July 2021 (UTC)Reply[reply]
This guide is generally still up to date Madscience (talk) 14:33, 4 November 2023 (UTC)Reply[reply]