Arch Linux does not boot after plugging in a secondary drive

jazznuts · 2020-11-04 21:06:25

Hello,

The other day I added a secondary ssd to my machine and now it will not boot. I have an LVM on LUKS setup on my main drive, but my EFI partition is unencrypted. I know that it has something to do with block devices switching names when I plug the new drive in, but I don't know where to add UUIDs and PARTUUIDs to my config files so that I can boot successfully.

My /etc/default/grub looks like this:

   41 # GRUB boot loader configuration
   40
   39 GRUB_DEFAULT=0
   38 GRUB_TIMEOUT=5
   37 GRUB_DISTRIBUTOR="Arch"
   36 GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 cryptdevice=PARTUUID=e222408-b100-b14f-b88a-9db1fd4f537f:volgroup0:allow-discards"
   35 GRUB_CMDLINE_LINUX=""
   34
   33 # Preload both GPT and MBR modules so that they are not missed
   32 GRUB_PRELOAD_MODULES="part_gpt part_msdos"
   31
   30 # Uncomment to enable booting from LUKS encrypted devices
   29 GRUB_ENABLE_CRYPTODISK=y
   28
   27 # Set to 'countdown' or 'hidden' to change timeout behavior,
   26 # press ESC key to display menu.
   25 GRUB_TIMEOUT_STYLE=menu
   24
   23 # Uncomment to use basic console
   22 GRUB_TERMINAL_INPUT=console
   21
   20 # Uncomment to disable graphical terminal
   19 #GRUB_TERMINAL_OUTPUT=console
   18
   17 # The resolution used on graphical terminal
   16 # note that you can use only modes which your graphic card supports via VBE
   15 # you can see them in real GRUB with the command `vbeinfo'
   14 GRUB_GFXMODE=auto
   13
   12 # Uncomment to allow the kernel use the same resolution used by grub
   11 GRUB_GFXPAYLOAD_LINUX=keep
   10
    9 # Uncomment if you want GRUB to pass to the Linux kernel the old parameter
    8 # format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
    7 #GRUB_DISABLE_LINUX_UUID=true
    6
    5 # Uncomment to disable generation of recovery mode menu entries
    4 GRUB_DISABLE_RECOVERY=true
    3
    2 # Uncomment and set to the desired menu colors.  Used by normal and wallpaper
    1 # modes only.  Entries specified as foreground/background.
  42  #GRUB_COLOR_NORMAL="light-blue/black"
    1 #GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
    2
    3 # Uncomment one of them for the gfx desired, a image background or a gfxtheme
    4 #GRUB_BACKGROUND="/path/to/wallpaper"
    5 #GRUB_THEME="/path/to/gfxtheme"
    6
    7 # Uncomment to get a beep at GRUB start
    8 #GRUB_INIT_TUNE="480 440 1"
    9
   10 # Uncomment to make GRUB remember the last selection. This requires
   11 # setting 'GRUB_DEFAULT=saved' above.
   12 #GRUB_SAVEDEFAULT="true"

fstab looks like this:

  1   # /dev/mapper/volgroup0-lv_root
    1 UUID=a1f0c9c0-8cc0-4c3c-ac0a-c29300a0e76a /           ext4        rw,relatime 0 1
    2
    3 # /dev/mapper/volgroup0-lv_home
    4 UUID=a4134a2f-ed0a-41ab-81e3-c42d4a384a78 /home       ext4        rw,relatime 0 2
    5
    6 # /dev/sdb2
    7 UUID=8a7513cf-1c53-4e99-b604-3ad7665a796a /boot       ext4        rw,relatime 0 2
    8
    9 /swapfile none swap sw 0 0

Here are some of the outputs of blkid:

/dev/sdb1: UUID="9BF5-7B43" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="4e7753cc-64ef-2941-a70e-63e235982977"

/dev/sdb3: UUID="3f9a7323-cc79-4bc7-a188-c3782e6e3ec3" TYPE="crypto_LUKS" PARTUUID="ce222408-b100-b14f-b88a-9db1fd4f537f"

/dev/mapper/volgroup0: UUID="uB6Fbi-of1K-wtVq-fmRz-plcQ-BEaS-saOs0F" TYPE="LVM2_member"

/dev/mapper/volgroup0: UUID="uB6Fbi-of1K-wtVq-fmRz-plcQ-BEaS-saOs0F" TYPE="LVM2_member"

Here is the output of fdisk -l so that you can get a general understanding of the layout of my system:

Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10EZEX-00B
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 14AC6272-9D09-11E4-82AE-448A5B266E0E

Device     Start        End    Sectors   Size Type
/dev/sda1   2048 1953525134 1953523087 931.5G Linux home


Disk /dev/sdb: 223.57 GiB, 240057409536 bytes, 468862128 sectors
Disk model: KINGSTON SA400S3
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: 0AF86022-F31D-6A47-ACA1-8395AC8D84CC

Device       Start       End   Sectors   Size Type
/dev/sdb1     2048   1026047   1024000   500M EFI System
/dev/sdb2  1026048   2050047   1024000   500M Linux filesystem
/dev/sdb3  2050048 468862094 466812047 222.6G Linux LVM


Disk /dev/mapper/volgroup0: 222.58 GiB, 238990990848 bytes, 466779279 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


Disk /dev/mapper/volgroup0-lv_root: 30 GiB, 32212254720 bytes, 62914560 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


Disk /dev/mapper/volgroup0-lv_home: 192.57 GiB, 206774992896 bytes, 403857408 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

/dev/sda is not the problematic drive, it is another extra drive but it has not caused me any trouble.

Please let me know if there is any more information I can provide. I wish I could provide more details about whats going wrong during the boot but I don't know how to increase the verbosity and where the logs are saved. For now I can say that it crashes just after it says "starting version 246.6-1-arch" after selecting arch in the grub boot menu. If there is a way to increase the verbosity of this let me know how and I'll report it here. Thank you in advance for helping!

nicholas · 2020-11-05 13:38:23

It's unclear to me at the moment if you are making it into the Linux system or if you're stuck at GRUB.
Could you post either the full grub.cfg or the relevant lines to the entry you're booting?
If you are looking for better kernel logging, you can set the loglevel=6 (INFO) in /etc/default/grub's GRUB_CMDLINE_LINUX, as described better here

My first guess is that something is trying to boot via `/dev/sda1` style parameters and is properly handing off to the wrong device, but the grub.cfg would clarify if that's a reasonable guess.

natervance · 2020-11-05 13:52:06

It doesn't appear to me that you have all of the necessary components on your bootloader setup, though I'm using dracut so my config looks a bit different. I assume you used the relevant wiki page (https://wiki.archlinux.org/index.php/Dm … VM_on_LUKS) when initially setting up. I notice that the setup there differs from your configuration by including a root=/dev/MyVolGroup/root stanza. Also, it uses a cryptdevice=UUID and not PARTUUID. I'd just recommend revisiting that and making sure that all the components are in place.

jazznuts · 2020-11-05 17:42:26

Thank you nicolas and natervance! Adding the /dev/root/MyVolGroup/root stanza and regenerating grub.cfg did the trick. I also changed the PARTUUID to UUID and regenerated lvm2.conf.

nicholas · 2020-11-06 16:45:44

Great to hear

Per the Code of Conduct please edit your first post to say '[SOLVED]' at the beginning.

Arch Linux

#1 2020-11-04 21:06:25

Arch Linux does not boot after plugging in a secondary drive

#2 2020-11-05 13:38:23

Re: Arch Linux does not boot after plugging in a secondary drive

#3 2020-11-05 13:52:06

Re: Arch Linux does not boot after plugging in a secondary drive

#4 2020-11-05 17:42:26

Re: Arch Linux does not boot after plugging in a secondary drive

#5 2020-11-06 16:45:44

Re: Arch Linux does not boot after plugging in a secondary drive

Board footer