You are not logged in.

#1 2018-09-08 05:02:56

Batou
Member
Registered: 2017-01-03
Posts: 259

Kernel fails to fully boot when a non-bootable disk is missing

Hi all.

I've encountered this issue years ago but it never bothered or affected me too much but it has happened to me again so I'd like to figure out what the root cause of this is. I have several SSDs and HDDs and I've noticed that when one of the non-bootable (my backup/archive) disk is physically disconnected (SATA+power cable pulled), my Arch doesn't fully boot and locks up.

I basically have two entries: one in /etc/cryptab that unlocks it using a key (it's a LUKS encrypted disk) and an entry in /etc/fstab that mounts it.

fstab:

  UUID=<id-here> /run/media/user/backuptb  btrfs  defaults,noatime,nodiratime 0 0

crypttab:

 backuptb        UUID=<id-here> /root/backuptb.key luks

And if I comment these two lines out, it boots fine. But if they're there and the disk is disconnected, it won't boot.

Is there a way to tell the kernel to ignore disks that it cannot find?

Thanks!


Please vote for all the AUR packages you're using. You can mass-vote for all of them by doing: "pacman -Qqm | xargs aurvote -v" (make sure to run "aurvote --configure"  first)

Offline

#2 2018-09-08 05:11:01

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 29,523
Website

Re: Kernel fails to fully boot when a non-bootable disk is missing


"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

Board footer

Powered by FluxBB