Search results

  1. C

    Upgrade from Kernel 1.6.12 to 1.6.13 now causes boot-up error on automatic decrypting and mounting a second disk....

    SOLVED. I upgraded to 6.1.18 this morning, and -- voila! -- /dev/sda1 is back!
  2. C

    Upgrade from Kernel 1.6.12 to 1.6.13 now causes boot-up error on automatic decrypting and mounting a second disk....

    Thanks for the offer. I've ended up changing a line in /etc/fstab so that I can boot up in post 6.1.12: FROM /dev/sda1 /drive2 ext4 defaults 0 3 TO /dev/sda1 /drive2 ext4 noauto 0 3 I can afford not to have /dev/sda recognized for now, so I'll keep working on trying to get later versions of...
  3. C

    Upgrade from Kernel 1.6.12 to 1.6.13 now causes boot-up error on automatic decrypting and mounting a second disk....

    What I'm finding is that /dev/sda1, the encrypted disk, does not appear at all using gparted in either Linux 6.1.13 or Linux 6.1.14, but /dev/sda1 DOES appear in Linux 6.1.12....
  4. C

    Upgrade from Kernel 1.6.12 to 1.6.13 now causes boot-up error on automatic decrypting and mounting a second disk....

    Yep, you're right about the kernel version. I'll wait for the encryption dependencies to show up, will continue to use 6.1.12. Thanks.
  5. C

    Upgrade from Kernel 1.6.12 to 1.6.13 now causes boot-up error on automatic decrypting and mounting a second disk....

    I have two disks in my laptop, one boot disk and one backup disk. I have both disks encrypted with LUKS, and when I boot the system I type in the password for the boot disk. I've set up the second disk, /dev/sda1, to automatically decrypt and mount as /drive2. It's worked fine for several...
Top