Hi,
maxim.courno...@gmail.com writes:
> On a system where:
>
> 1) Each disks comprising the array is fully LUKS encrypted
> 2) Each mapped disk is made part of a Btrfs RAID1 array
>
> When attempting to boot the system after pulling out (in BIOS or using
> the cable) the drive to simulate a compl
Hi,
I'm writing here because I just found a much easier way to trigger this
than by opening the case of my desktop and pulling a drive out with this
QEMU script:
--8<---cut here---start->8---
#!/usr/bin/env bash
devices=(sda sdb sdc)
args=(-enable-kvm -snapsho
Hi Maxim,
I'd "debug" the issue trying to compare my Debian system config with
yours since I'm also using a BTRFS RAID1 filesystem on LUKS.
I've still not unplugged one of the two disks on mine to simulate a
drive failure, Soon™ I'd like to test this condition... but it's a
busy machine so I don'
Hello Giovanni,
Giovanni Biscuolo writes:
> Hello Maxim,
>
> Maxim Cournoyer writes:
>
> [...]
>
>>> On a system where:
>>>
>>> 1) Each disks comprising the array is fully LUKS encrypted
>>> 2) Each mapped disk is made part of a Btrfs RAID1 array
>>>
>>> When attempting to boot the system after
Hello Maxim,
Maxim Cournoyer writes:
[...]
>> On a system where:
>>
>> 1) Each disks comprising the array is fully LUKS encrypted
>> 2) Each mapped disk is made part of a Btrfs RAID1 array
>>
>> When attempting to boot the system after pulling out (in BIOS or using
>> the cable) the drive to si
On a system where:
1) Each disks comprising the array is fully LUKS encrypted
2) Each mapped disk is made part of a Btrfs RAID1 array
When attempting to boot the system after pulling out (in BIOS or using
the cable) the drive to simulate a complete disk failure, GRUB hangs,
prompting for the LUKS
