private.img is too big, the file system says its really big but it can not be that big. I guess 4x of the size it should have as I feel it. But I back it up to my big nas and then I say fsck.ext2 just to be sure not to loose a thing.
On Sun, Jan 28, 2018 at 3:08 PM, ludwig jaffe <[email protected]> wrote: > it is qubes 3.2 > > Now I found a way: > I booted kali from usb stick, > then I did > cryptsetup luksOpen /dev/sda3 green > and mount /dev/dm-blabla /mnt/8 > > 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 this a way to repair your cubes without using the idiotic > tools of qubes :-) > > > > On Sun, Jan 28, 2018 at 2:42 PM, awokd <[email protected]> wrote: > >> On Sun, January 28, 2018 5:26 pm, 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. >> >> 4.0? I think the "Qubes way" would be to boot from your install media, >> pick Rescue mode, and get enough free space to be able to boot the full >> system. 3.2 I guess you'd have to use a live image; can't remember if >> there's a rescue mode. >> >> I honestly can't tell you how you'd go about attaching a NIC to dom0. USB >> might be an easier choice, but same there- not something I've ever looked >> into! >> >> > -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAP7JdrKneaZrhfb5safsfgt-YPf6qCP6-JG0Lr25qqZOmpE2hQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
