You are not logged in.
I've probably assembled 50 or more systems over the past few years and have never run into this situation.
I have a main drive drive that boots perfectly on its own. When I add a second drive to the system, it fails to find /dev/sda2 which holds the OS. But when I connect the second drive via a USB port, it all works perfectly.
Here are the results of blkid:
/dev/sda1: UUID="9933-92E2" TYPE="vfat" PARTUUID="24a92c8a-ce59-4afb-836f-39343b945637"
/dev/sda2: UUID="a681a973-8346-4340-8cf8-71ecc118e747" TYPE="ext4" PARTUUID="87f10e05-d02a-4ced-819a-6a583a485c57"
/dev/sdb1: UUID="dd6a6de5-29e2-43f3-a922-83453aee33d7" TYPE="ext4" PARTUUID="000bf16b-01"
Here is my fstab:
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda2
UUID=a681a973-8346-4340-8cf8-71ecc118e747 / ext4 $
# /dev/sda1
UUID=9933-92E2 /boot vfat rw,relatime,fmask=0022,$
# /dev/sdb1 (/music)
UUID=dd6a6de5-29e2-43f3-a922-83453aee33d7 /music ext4 $
Again, when I connect the second drive (/dev/sdb) via SATA, the system won't boot and fails waiting for /dev/sda2. When I hook up the same second drive via USB, it boots perfectly.
Any ideas on what might cause this would be greatly appreciated.
- Jim
Last edited by jsalk (2018-02-08 20:25:55)
Offline
Your boot loader/manager config is the relevant file here. If you aren't using persistent names/labels there, that would explain your issue.
Moving to NC...
Offline
The contents of /boot/loader.loader.conf are:
default arch
timeout 3
editor 0
The contents of /boot/loader/entries/arch.conf are:
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=/dev/sda2 rw
Note that I also have an exactly identical setup that does not have this issue.
- Jim
Offline
If you aren't using persistent names/labels there, that would explain your issue.
Offline
That was the solution. Switched to PARTUUID for /sda2 and that did the trick. Thanks.
- Jim
Offline