Hello there,
VeraCrypt Boot Loader 1.23 (VCBL) doesn't seem to be able to find bootable partitions on other internal drives, does it?
Current working configuration: 1 hard drive, 4 partitions (MBR): Drive: 0, Partition: 1 - VCBL/Win10-boot Drive: 0, Partition: 2 - Win10 (VC encrypted system) Drive: 0, Partition: 3 - /boot (ext4) with grub 2.02 Drive: 0, Partition: 4 - Ubuntu (luks encrypted system)
VCBL is correctly showing bootable partition 1 and 3.
Due to space requirements and hoped-for easier maintenance wanted configuration: 2 hard drives, each with 2 partitons (MBR): Drive: 0, Partition: 1 - VCBL/Win10-boot Drive: 0, Partition: 2 - Win (VC encrypted system) Drive: 1, Partition: 1 - /boot with grub 2.02 Drive: 1, Partition: 2 - Ubuntu (luks encrypted system)
VCBL is showing only bootable partition 1 from drive 0. Drive 1 partition 1 is only bootable with BIOS boot menu.
Strangely bootable USB-Sticks are no problem and shown as bootable drives in VCBL.
Is that behaviour intended, a missing feature or a bug?
Best Regards, Florian Schwarz
Someone with technical insight who can help?
Log in to post a comment.
Hello there,
VeraCrypt Boot Loader 1.23 (VCBL) doesn't seem to be able to find bootable partitions on other internal drives, does it?
Current working configuration:
1 hard drive, 4 partitions (MBR):
Drive: 0, Partition: 1 - VCBL/Win10-boot
Drive: 0, Partition: 2 - Win10 (VC encrypted system)
Drive: 0, Partition: 3 - /boot (ext4) with grub 2.02
Drive: 0, Partition: 4 - Ubuntu (luks encrypted system)
VCBL is correctly showing bootable partition 1 and 3.
Due to space requirements and hoped-for easier maintenance wanted configuration:
2 hard drives, each with 2 partitons (MBR):
Drive: 0, Partition: 1 - VCBL/Win10-boot
Drive: 0, Partition: 2 - Win (VC encrypted system)
Drive: 1, Partition: 1 - /boot with grub 2.02
Drive: 1, Partition: 2 - Ubuntu (luks encrypted system)
VCBL is showing only bootable partition 1 from drive 0. Drive 1 partition 1 is only bootable with BIOS boot menu.
Strangely bootable USB-Sticks are no problem and shown as bootable drives in VCBL.
Is that behaviour intended, a missing feature or a bug?
Best Regards,
Florian Schwarz
Last edit: Florian Schwarz 2019-05-30
Someone with technical insight who can help?