Qubes666 wrote on 6/6/19 6:56 PM:
On Thursday, June 6, 2019 at 7:49:05 PM UTC+2, awokd wrote:
Qubes666 wrote on 6/6/19 8:39 AM:
Ok, have made your two screenshots. https://photos.app.goo.gl/YeqmJkc9mchwBR7w6
A) from "sudo systemctl start qubesd" response
B) from "sudo journalctl -b" right after the above command which was Jun 06
10:14:01
It's complaining about not having a driver loaded for your storage
pools. If you boot then look through "sudo journalctl -b", you'll
probably see that's caused by file system or pool corruption. If that's
the case and you have a recent backup, I think your best bet at this
point is to reinstall and restore.
Hi, thank you. I have upload a picture from journalctl -d from what i think
you could mean.
Please have a look. Same link from above.
That's not it. Look for something about mount errors, or copy out the
log file (sudo journalctl -b > logfilename) and attach here or send to
me. Note there may be details in the log file regarding your hardware
configuration and VM names, etc.
i have a 2 month old backup on a external drive. Will be a lesson to to this
more regular, if a new installation is really required.
Is there a option to reinstall only dom0?
Some of the data volumes might be recoverable assuming it is file system
corruption, but you would have to repair that first, then mount the VM
drives individually and copy out the contents. No dom0 only reinstall
option.
--
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/f2222203-85aa-c088-d1d8-7be7516b4431%40danwin1210.me.
For more options, visit https://groups.google.com/d/optout.
