Hi Tom,
> This looks like a show-stopper bug to me.
> The system should never be able to corrupt a critical file like that due to
> disk-full.
This problem could be averted by pulling dom0 out of tpool. Also, using "df" to
check how full your partition is, will not necessarily say how much data
On Friday, 8 December 2017 01:05:32 CET Patrick wrote:
> I found the problem! My /var/lib/qubes/qubes.xml file was corrupted, so
> it could not be parsed correctly by qubesd. I restored a previous version
> from /var/lib/qubes/backup and now I am back in business! Thanks anyway
> for checking out
I found the problem! :-D My /var/lib/qubes/qubes.xml file was corrupted, so it
could not be parsed correctly by qubesd. I restored a previous version from
/var/lib/qubes/backup and now I am back in business! Thanks anyway for checking
out my problem. :-)
Best regards,
Patrick
--
You rece
Correction: the last line is not actually part of the error message! (my
mistake...)
> FileNotFoundError: [Errno 2] No such file or directory
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving ema
Hi Tom,
> I would hope qubesd logs somewhere else as well, as these files show nothing
> of use. Just that it failed.
>
> Try
> qvm-run -p -u root ‘ls /usr/log’
> and similar commands to check if there are more logs.
These commands (almost?) all depend on qubesd it seems, therefore not v
On Thursday, 7 December 2017 01:53:40 CET Patrick wrote:
> However... I immediatelyy found out VM's still did not start on my system.
> After looking in journalctl and systemctl, I found out qubesd would not
> start: "failed to start Qubes OS daemon". I attached text files of the
> error outputs fr
