![]() ![]() Paste the content, save with Ctrl+O, and exit nano with Ctrl+X. Now paste the above (last 3 lines are enough) to the same file in chrooted environment. # See man:rvice(8) for details about the supported modes of # different way, replace this symlink by a static file or a different symlink. # Third party programs should typically not access this file directly, but only # Run "resolvectl status" to see details about the uplink DNS servers # internal DNS stub resolver of systemd-resolved. # This is a dynamic nf file for connecting local clients to the # /etc/nf and seeing this text, you have followed the symlink. # This file might be symlinked as /etc/nf. # This is /run/systemd/resolve/nf managed by man:systemd-resolved(8). Open another terminal and copy the file contents: cat /etc/nf So we need to add the contents of /etc/nf from Live media onto the one of the installed OS, else we won’t be able to install grub2-common with the package manager. Pts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0 6 Configure DNS of installed OSīy default, the DNS is not setup and the settings of the Live USB won’t work for the installed OS (they are completely separate entities). Grep: /proc/mounts: input file is also the cat /etc/mtab sudo mount -t proc none sudo mount -t sysfs sys sudo mount -o sysfs sys sudo mount -o bind /dev sudo mount -t devpts pts /mnt/pika/dev/pts 5 chroot into installed OS sudo chroot /mnt/pika/ grep -v rootfs /proc/mounts > /etc/mtab Before that, we need to mount other devices too, under the root mount point (in Linux, any device is just a file/ directory). However, because we don’t have it, the only way is to chroot into that partition and install grub from there. Lib mnt proc tmp 4 Prepare for chroot into installed OSĪt this point we could have just run grub-install to the nvme disk, had Pika OS included the grub2-common/ grub-pc packages (i.e. Home media pika-sources_3.0-99pika18_all.deb.3 sys 3 Mount into installed OS partition sudo mkdir -p sudo mount /dev/nvme0n1p4 ls /mnt/pikaīoot lib64 pika-sources_3.0-99pika18_all.deb run varĭev libx32 pika-sources_3.0-99pika18_all.deb.1 sbinĮtc lost+found pika-sources_3.0-99pika18_all.deb.2 srv The other partitions are p1: EFI boot partition, p2: Windows, p3: a small partition kept just in case for another EFI bootloader. In this case the device is nvme0n1, and partition was nvme0n1p4. 2 Find the device id of the partition of installed OS sudo lsblk In my case even sudo was not working because /dev/pts was not mounted. Here follows: 1 Reboot into the Live USBĪfter installation of the OS, because during that installer session the partitions will be mounted by the installer. So I needed to chroot into the installed OS and fix the bootloader. The SolutionĪnyways, after I got the error message, I restarted into grub-rescue screen, and was left with an unbootable system. It customized the Calamares installer, but forgot to include one of the main things. ![]() However, at the very end when the system is installed and the last step of installing a bootloader was to be done, it threw a really unexpected error of grub-install command not found! So Pika OS in all its wisdom did not bother to include the fundamental package grub2-common (and grub-pc) without which it is impossible to install GRUB bootloader, even if it did not declare it does not support GRUB. I already had a EFI partition on the MBR of the disk, and Pika did pick it up (see what I did there?) for bootloader installation. At the end of selection it asked for a 8 MB partition if system was on GPT partition scheme, but mine was on MBR (which it showed on the disk partitions screen), so I did not bother. The Calamares installer was put to Manual partition mode, because by default Pika OS selected btrfs filesystem whereas I wanted the good old ext4. I wanted to try this one on my old Ryzen PC, which already had Windows. Pika OS is a new kid on the block, in the footsteps of Nobara Linux (a Fedora spinoff by GloriousEggroll of custom Proton editions fame). ![]() So we might need to rescue it after installation when we are stuck with an unbootable machine. However, as I found out, some of the less popular (but not at all lower quality) Linux distributions do not test all the scenarios with GRUB. They are not necessarily dependent on each other, because GRUB also supports EFI etc. As such, computers with legacy BIOS wanting to dual-boot have to put up with a typical no-mans-land nowadays, with the newer EFI BIOS and systemd-boot services. The GRUB bootloader is old but works, and if the computer is about 5+ years old, it is still relevant today. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |