On Wed, Apr 29, 2020 at 03:10:48PM -0300, Franz wrote:
> I tried fsck on dom0, but got the enclosed terror screen.
it would have helped if you had tried to fsck the right filesystem:
fsck /dev/qubes_dom0/vm-per-dec-private
and if it is asking for repair a bazillion times, perhaps with -y -f
(and i would keep running it with "-y -f" until at least one run
is completely clean...)
"how to repair a filesystem" is basic system management.
the only mildly qubes-specific part about it is that the fsck needs to
be done while the filesystem is not mounted, which in most cases means
the vm is not running.
> and for the future I'll avoid to chenge size of a running VM. I understand
> it can theoretically be done, but it does not work for me. On the other
> hand, it works if the VM is not running.
you will run into exactly the same problems if you try to resize
a damaged filesystem while the vm is not running.
actualy for some constellations of resize and system, an offline
resize is _more_ likely to go wrong.
(it will do the resize on next vm startup, and if the resize takes
longer than the vm-startup-timeout... ouch)
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/20200429182711.GL935%40priv-mua.
