On Thursday, 19 April 2018 20:20:48 UTC+10, cooloutac wrote:
>
> sorry for being confused. but are you saying it fails to restore, or just
> don't like the method it uses?
I'm saying it fails.
Often BECAUSE of the method it uses.
Sometimes because of other things it does because it doesn't c
On Wednesday, April 18, 2018 at 9:25:05 PM UTC-4, Drew White wrote:
> I also have a machine that I have just built that is the following..
>
> MMCBLK is /boot and /
> 16 GB SDCard.
> Can be set as Read Only as it will not change (but r/w at the moment until I
> know for sure.)
>
> Log folder set
I also have a machine that I have just built that is the following..
MMCBLK is /boot and /
16 GB SDCard.
Can be set as Read Only as it will not change (but r/w at the moment until I
know for sure.)
Log folder set on HDD.
HDD is set as (technically) /var/lib/qubes
But I doubt that that will have
I have my disk set up as the following...
sda1 /boot
sda2 /
sda3 /var/lib/qubes
I also have
sda1 /boot
sda2 /
sdb1 /var/lib/qubes
Thing is, I used to be able to restore them and all, BEFORE I updated the
manager.
The only difference between 2 PCs is the version of the manager.
Why do
> This is completely unacceptable that you still have not resolved these bugs I
> mentioned in Qubes version 2. Please fix!
Quick question, were the VMs backed up from a Qubes install with multiple
storage pools, by chance?
I am about to create an issue about that as soon as I can grab proper
