Qubes666 wrote on 6/6/19 8:39 AM:
Am Donnerstag, 6. Juni 2019 00:34:13 UTC+2 schrieb awokd:
Qubes666:
Am Mittwoch, 5. Juni 2019 21:58:12 UTC+2 schrieb awokd:
[email protected]:
Tried to start sys-net or sys-firewall with qvm-start, but did not work:
File"usr/lib/python3.5/site-packages/qubesadmin/app.py", line 540, in
qubesd_call client_socket-connect(qubesadmin.config.QUBESD_SOCKET)
FileNotFoundError...
Qubesd service probably not started. Do "sudo systemctl start qubesd".
Confirm with "sudo systemctl status qubesd". See if it gives any errors
(I expect it will). Also check journalctl log for related errors when
you try to start it.
Hi, Thank you.
tried : sudo systemctl start qubesd but failed to start Qubes OS daemon due to
"start limit hit"
Have a picture but don´t see a attache button...
"Start limit hit" is the last error, and doesn't really tell us
anything. Review "sudo journalctl -b" and find the error(s) that occur
immediately after you attempt to start it.
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.
--
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/a6a1c653-fd50-e0e4-e1b0-67ca5475ab4d%40danwin1210.me.
For more options, visit https://groups.google.com/d/optout.
