On Sunday, January 28, 2018 at 12:26:44 PM UTC-5, ludwig jaffe wrote:
> Hi some systems got too big and now my dom0 is full.
>
> data panic (disc full) / want to mount nas with nfs and backup all in
> /var/lib/cubes
>
> In a normal system I would setup an insulated air gap network and take a big
> nas server mount nfs to the root-fs of dom0 and say as root cp -a
> /var/lib/cubes /net/nas/bck.
> And then I would clean up and remove some VMs with rm -rf as I could undo it
> when I got the VMs booted and cleaned of all the shit that got downloaded.
>
> Now I can not connect the dom0 to a nic.
> Is there a trick to do it?
> booting a rescue linux from a stick would be a way but I first want to try
> using qubes-os and changing a thing in the configs.
>
> Thanks for your help.
Now I fixed nearly all.
I did as follows:
boot kali-linux (or some other linux with enough tools -> Kali)
from usb stick
cryptsetup luksOpen /dev/sda3 green sda was the disk with the system and
sda3 holds the encrypted qubes-os installation.
and mount /dev/dm-blabla /mnt/8 (I have always mount points /mnt/{0-9} ready)
also I mounted my nas to nfs (no file security) in air gapped network
mount 192.0.123:/bigsasdrives/bakup /net/nas
and copied /var/lib/cubes to it
cp -av /var/lib/qubes /net/nas
this is running.
The disk to full problem is found:
I went to
/var/lib/qubes/personal
said file private.img
and file was so nice to tell me that private.img needs fsck.
but as there is important data on this private.img,
I first copy it to the nas and then say e2fsck private.img
so after back-up of the important stuff, i said e2fsck -f private.img
for all the app-vms and service-vms in the directory structure of
/var/lib/qubes/
then I went to the vms like
cd /var/lib/qubes/appvms/banking1
said
mount -o loop,ro,noatime private.img /mnt/9
and I copied the important stuff here to the encrypted nas
in /var/lib/qubes/appvms/personal
I also copied the important stuff to the encrypted nas, and then I
deleted all the bloody videos I downloaded from the private.img in
personal and there is now room on the disk.
Videos are to be watched from nas from now on :-)
--
Only one Problem remains:
The Qubes-VM-Manager only shows running VMs and not all the VMs that are
there, but from the menue button one can start the shells of these VMs,
which causes the vms to be started.
Also I can not change the disk size of private.img in the shutdown
personal vm. And maybe others.
How to fix qubes vm manager?!
--
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/7b384e53-bdbb-429b-91b1-5a79b737bafd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
