Suggestions for live/installer


Hi Master-team!

I hope this is the right place to post this!?

I ran into problems with grub and thought the easiest way was to reboot from install-image and chroot.
To be sure I was using chroot right I read arch-wiki about chroot. In chroot I got stuck though! Could not update grub config or reinstall grub to mbr (I have a the old type of machine!) The reason was “could not find device for / . Is /dev mounted”. Searched for this problem on arch-wiki but couldn’t find anything that helped me.
Then I thought that maybe I could update grub through the installer? I tried to do that by choosing to install as little as possible. Did not work well . The system started but hang and had to “hard-shutdown”!
The only solution I could come up with after this was to reinstall. (A bit dissappointing because I had made a lot of personal configurations!)

(I apologize for this boring rant!)

Live-image could have tools for fixing troubles with boot and a helper for chrooting into the installed system.



I know reinstalling s piss someone some times, been there often on my side ! lol

Wonder if it has to do with the newer way to install on AL or Linux as such here.

While at it, this has saved my but several times in the past, wonder if it can help on newer installs & hardware.Hope it can do it on your install, never know what can happen.


Interesting! Downloading nog!




No problem mate, hope it can do the job, let us know if it works.


Will do!



@womp , cool !


I’ve never used rescatux but I’ve heard some horror stories, use with caution.


@anon37345411 , never had any bad stories with it, might be because I was lucky ! Used alot back then while on Linux in the early years.


Did you (bind) mount the API filesystems before using chroot? The error message suggests that you did not.

The arch-chroot command will mount everything up automagically (once directed to the root filesystem) so that might be better.

It should be possible to re-install and re-configure GRUB from outside the chroot by using:

mount /dev/sdXY /mnt
grub-install --target=i386-pc --boot-directory=/mnt/boot /dev/sdX
grub-mkconfig -o /mnt/boot/grub/grub.cfg

Replace /dev/sdXY with the partition containing the root filesystem but do not add a partition number to the grub-install command.

You can also back up your MBR with:

dd if=/dev/sda of=mbr.bak bs=512 count=1

And restore the mbr.bak file with:

dd if=mbr.bak of=/dev/sda

This won’t work for disks using a GUID partition table or UEFI booting though!


My lack of knowledge made my mess! I could not find arch-chroot in archlabs and therefore I thought that chroot was the same command (but in archlabs)! I will save your reply, I will probably need it sooner or later!

I still think itś a good idea and good use of the live-system to have utils for boot problems (and maybe other problems)



Ah, I see, this command would have told you the package name:

pacman -Fys arch-chroot

and this would have installed it in the live system:

pacman -Sy arch-install-scripts

Please note though that the above command is not safe to use in an installed system: the -u flag should always be used together with -Sy to avoid a partial upgrade.


I thank you for tolerance and understanding!
This has been valuable for me!



Hi there,

It could be nice to enable or disable os-prober when installing grub, I always disable it for 2 main reasons

  1. it take a long time to detect others OS (15min last time I checked)
  2. I end up with trouble booting others OSs (Windows10, Fedora, Manajro, Arch) . It doesn’t happen every time but when it does it’s pretty messy .
    Last experience with it, well it deleted all my ESP partition without even install its own grub ^^

I am aware that not every body share this situation but I think os-prober doesn’t like hardware like nvme0, seems still too recent stuff for it.
In the end when I install a distribution I always remove os-prober or disable it by adding that line in /etc/default/grub:

Other than that I really like the work you did whit that AL-installer!
Fast no GUI and so convenient you guys rock!


Much work has gone into it, particularly by @natemaia and is now refined to damn near perfection (imho).

Curious, how many systems have you installed? I only have AL here but back when I did have multiple systems, I never experienced os-prober taking more than a few seconds.


Sorry for the delay mate been busy, I have 4 systems for now and only 3 soon .
TBH that’s the first time os-prober delete my EFI partition, I already had bad experiences with it but not that bad, may be a bug or something.
Anyway that is just a bad “souvenir” now :wink:


Firstly, os-prober is just a script and nowhere in that script does it contain any commands that might delete anything on any partition or remove any partition so you must be mistaken about that.

I can prove this by running the command as my normal user:

empty@shinken:~ $ os-prober                                                                                                                                                                                        
unshare failed: Operation not permitted
mkdir: cannot create directory ‘/var/lib/os-prober/mount’: Permission denied
mkdir: cannot create directory ‘/var/lib/os-prober/mount’: Permission denied
mkdir: cannot create directory ‘/var/lib/os-prober/mount’: Permission denied
mkdir: cannot create directory ‘/var/lib/os-prober/mount’: Permission denied
mkdir: cannot create directory ‘/var/lib/os-prober/mount’: Permission denied
mkdir: cannot create directory ‘/var/lib/os-prober/mount’: Permission denied
mkdir: cannot create directory ‘/var/lib/os-prober/mount’: Permission denied
mkdir: cannot create directory ‘/var/lib/os-prober/mount’: Permission denied
mkdir: cannot create directory ‘/var/lib/os-prober/mount’: Permission denied
mkdir: cannot create directory ‘/var/lib/os-prober/mount’: Permission denied
mkdir: cannot create directory ‘/var/lib/os-prober/mount’: Permission denied
empty@shinken:~ $

^ As you can see, all it tries to do is unshare (create it’s own namespace in which to run) and make some directories in /var, neither of which will change anything on the ESP.

Secondly, os-prober is not supposed to “install its own grub”, it’s just a tool to allow grub-mkconfig (which also does not “install its own grub”) to pick up other operating systems.

Thirdly, if os-prober is disabled by default how are users supposed to be able to multiboot with ArchLabs?


They’re just errors in the installer, not ‘bugs’ or issues with grub/os-prober.