Transferring the data got me back in action, so I'm quite happy I had the
old system running and didn't have to muck about to regain access to the
files
I've normally had good enough luck with the qubes backup and restore, but
it does seem like Qubes from older systems might run into incompatibili
My current problem is this error (triggerable by running `lvm lvchange -ay
-v qubes_dom0/vm-vault-personal-docs-private`)
It happens with some other affected vms.
Activating logical volume qubes_dom0/vm-vault-personal-docs-private
exclusively.
activation/volume_list configuration setti
Oh, forgive me, no not all vms are present in lvs.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To view this discuss
Thanks Chris for your response!
On Mon, 29 Jul 2019, 4:25 pm Chris Laprise, wrote:
> On 7/29/19 10:19 AM, thomas.ke...@gmail.com wrote:
> > Thanks for your response.
> >
> > I have some which don't show as active - it's looking like some data
> loss..
> >
> > Something I am getting when I run
>
Sorry, didn't send to list. See my response to Chris.
-- Forwarded message -
From: Thomas Kerin
Date: Mon, 29 Jul 2019, 3:40 pm
Subject: Re: [qubes-users] fixing LVM corruption, question about LVM
locking type in Qubes
To: Chris Laprise
Hi Chris,
Yes, I think I tried
Thanks for your response.
I have some which don't show as active - it's looking like some data loss..
Something I am getting when I run
Lvconvert --repair qubes_dom0/pool00
WARNING: Sum of all thin volume sizes (2.67TiB) exceeds the size of thin pools
and the size of whole volume group (931.0
I've just encountered this issue, and I thought my problems were over once I
found this post..
Fyi, previously lvscan on my system shown root, pool00, and every volume but
swap as inactive
I followed your instructions, but the system still fails to boot. I've run
'vgchange -ay' and o saw the
I wanted to ask about including a feature in Qubes to create storage volumes on
disk which can then be assigned to a VM.
Presently, I'm writing an ISO to a USB, by downloading it in one VM, and
writing it to disk in another. Instead of copying the data, I'd rather write it
directly to a volume
I reinstalled Qubes R4.0.1, and during the reboot-and-setup phase I left
all options unchecked. Qubes installed some template VM's, but didn't add
sys-net/sys-usb/sys-firewall as desired.
This time I started with a small number of VM's and it worked - I am trying
more and I don't get the original
I installed a new SSD in my laptop, so I created a backup of my old one and
tried to restore it into a fresh install of Qubes R4.0.1 (the old system was
Qubes R4.0).
I'm receiving errors when I try to restore from the backup - 'Error restoring
VM: empty response from qubesd - check journalctl f
Hi all,
Sorry for this one, I somehow have made the mouse cursor become twice as
large whenever its moved over a dom0 window (Qubes Manager, system
settings, etc).
I've explored the settings menu and found some likely settings, but no luck.
Is there a place I can safely nuke to get back to the
11 matches
Mail list logo