Dual booting Arch Linux and Ubuntu on separate SSDs

 

Issues

I have Arch Linux on one SSD disk and I installed Ubuntu on a new SSD disk. Upon system restart it booted automatically with the GRUB configuration that Ubuntu had installed, not the GRUB configuration that I had for my Arch Linux - BIOS/EFI prioritized the disk Ubuntu is on (issue A, see below). Also this GRUB configuration had an os-prober-generated grub.cfg “menuentry” to boot into my Arch Linux installation (issue B), which unsurprisingly did not work.

Disk setup

I chose identical setup for both of the SSD’s - and thus an EFI partition in the 2 of them.

[root@arch-pc grub.d]# fdisk -l
Disk /dev/sda: 223.57 GiB, 240057409536 bytes, 468862128 sectors
Disk model: ADATA SP580     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: A1ADEEAF-4A37-4807-9C99-6F4B2AAB79D8

Device        Start       End   Sectors  Size Type
/dev/sda1      2048    534527    532480  260M EFI System
/dev/sda2    534528  42477567  41943040   20G Linux filesystem
/dev/sda3  42477568  46671871   4194304    2G Linux swap
/dev/sda4  46671872 214444031 167772160   80G Linux filesystem


Disk /dev/sdb: 223.57 GiB, 240057409536 bytes, 468862128 sectors
Disk model: ADATA SU650     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 1FBFA320-D304-491E-8AF8-E5965EB695FF

Device         Start       End   Sectors   Size Type
/dev/sdb1       2048    999423    997376   487M EFI System
/dev/sdb2     999424 157249535 156250112  74.5G Linux filesystem
/dev/sdb3  157249536 161155071   3905536   1.9G Linux swap
/dev/sdb4  161155072 468860927 307705856 146.7G Linux filesystem


Disk /dev/mapper/casa: 79.98 GiB, 85882568704 bytes, 167739392 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Issue A

First, the problem is that the Ubuntu drive took priority of the Arch drive. Restart, F12 -> BIOS settings. I’ve changes the boot priority to the disk containing Arch.



Issue B - disabling OS prober, so it does not scan drives for OS’es

I’ve added to /etc/default/grub in both of the OS’es:

GRUB_DISABLE_OS_PROBER=true

Adding a grub.cfg “menuentry” for Ubuntu in ArchLinux

Ubuntu root partition is is on /dev/sdb2

[root@arch-pc coffee]# mount /dev/sdb2 /mnt/astules/

Finding the disk number of the disk on which Ubuntu is and the partition of the / mount. Note the “hd1” and “gpt2” in the output.

[root@arch-pc grub.d]# cat /mnt/astules/boot/grub/grub.cfg | grep "set root" | tail -n1
        set root='hd1,gpt2'

By instruction from https://wiki.archlinux.org/index.php/GRUB#GNU/Linux add to /etc/grub.d/40_custom in the Arch Linux partition:

menuentry "Astules Ubuntu"  {
        insmod part_gpt
        insmod btrfs
        insmod ext2
        set root='hd1,gpt2'
        configfile /boot/grub/grub.cfg
}

Updating grub.cfg

[root@arch-pc grub.d]# grub-mkconfig -o /boot/grub/grub.cfg

Reboot.

Success:



Popular posts from this blog

AWS VPN Client on a guest VM

Image
The AWS VPN Client for Linux ( https://docs.aws.amazon.com/vpn/latest/clientvpn-user/client-vpn-connect-linux.html ) at the time of writing (Nov 26, 2023) is only supported on Ubuntu and the latest Ubuntu version supported is 20.04 LTS. This version of Ubuntu is nearly 4 years old and people have been having problems with the client - there have been numerous complaints on the forums by people trying to get it working on newer Ubuntu versions, for example https://repost.aws/questions/QUNJeF_ja_Suykous7EvfX5Q/aws-client-vpn-on-ubuntu-22-04 . While it is possible to get the VPN client working on Ubuntu 22.04, there is a caveat - the client uses an outdated libssl version (libssl1) and Ubuntu 22.04 comes with a libssl3, which makes the client error out.  The workaround is manual installation of libssl1, replacing libssl3. If one uses another distro or simply does not want to downgrade libssl just for the AWS VPN client, one solution is to run the client on guest installation of Ub...
Read more

Cyberghost Vpn on Arch Linux

  CyberGhost has apps or shell scripts for various Linux distros but not for Arch Linux, at least not at the time of writing this. However, it is very easy to configure it for Arch. Here’s what I did. Steps Logged into  https://my.cyberghostvpn.com/,  “My Download Apps” -> “Other Apps” -> “Routers and other devices” -> “Configure New Device”. Make the selections, for my setup I’ve selected “Open VPN” as the protocol. Download the OpenVPN configuration files. Extract the archive, mv the files to  /etc/openvpn/client . chmod 600 /etc/openvpn/client/* chown openvpn:network /etc/openvpn/client/* Create an auth file that stores the login credentials for this VPN connection /etc/openvpn/client/login.conf with the username on the 1st line and the password on the 2nd line. Change  auth-user-pass  in cyberghost.conf to  auth-user-pass login.conf . sudo systemctl start openvpn-client@cyberghost sudo systemctl enable openvpn-client@cyberghost Check the I...
Read more

Go error handling and stack traces voted as the biggest challenge

Image
The results of Go Developer Survey 2022 Q2 came out and showed that error handling and working with stack traces in Go pose the biggest challenge to respondents: "Error handling remains a challenge. Following the release of generics, respondents' top challenge when working with Go shifted to error handling." The answer distribution is as below (click): In this blog post I would like to focus on error handling and try to explain in detail how, in my view, error handling in Go is or should be done. Ready? Let's begin. Error handling in Go explained A function or a method in Go returns a non-nil error if and only if it encounters an error during execution. The caller checks for the returned error value - if it is not nil, it either handles it or returns an error of its own. I hope this blog post makes Go error handling better understood and appreciated.  
Read more