Re: [qubes-users] Re: dom0 update got stuck - now QOS daemon does not start
Qubes666: Hi. Have read several times through the journal, but could not see "mount errors". Well i am surely not an expert at that detail and may just mist it. Would like to send you the file, but how do i get i from dom0 to an usb stick. I am writing this posts from an old computer. Replied off list, check your spam folder if you don't see my email and reply to me there. -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6b5f8b14-09c1-8ddf-0a58-c0c99107a1b6%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: dom0 update got stuck - now QOS daemon does not start
On Thursday, June 6, 2019 at 9:17:49 PM UTC+2, awokd wrote: > 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. Hi. Have read several times through the journal, but could not see "mount errors". Well i am surely not an expert at that detail and may just mist it. Would like to send you the file, but how do i get i from dom0 to an usb stick. I am writing this posts from an old computer. -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/cfc4e073-2f17-422c-bc29-0ab046e43766%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: dom0 update got stuck - now QOS daemon does not start
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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f203-85aa-c088-d1d8-7be7516b4431%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: dom0 update got stuck - now QOS daemon does not start
On Thursday, June 6, 2019 at 7:49:05 PM UTC+2, awokd wrote: > 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: > indigo1...@gmail.com: > > > 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. 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. 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? -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/7f6ffc28-a875-4882-bad3-d04f61ae3688%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: dom0 update got stuck - now QOS daemon does not start
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: indigo1...@gmail.com: 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. 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.
Re: [qubes-users] Re: dom0 update got stuck - now QOS daemon does not start
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: > >> indigo1...@gmail.com: > >> > >>> 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 -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4cb23f5f-382c-4a1e-b311-8aacf76f591e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: dom0 update got stuck - now QOS daemon does not start
Qubes666: Am Mittwoch, 5. Juni 2019 21:58:12 UTC+2 schrieb awokd: indigo1...@gmail.com: 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. -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e576a7fa-882c-b10d-168e-5cfa5700ec5e%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: dom0 update got stuck - now QOS daemon does not start
Am Mittwoch, 5. Juni 2019 21:58:12 UTC+2 schrieb awokd: > indigo1...@gmail.com: > > > 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... -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9d6cc736-5dcc-4348-91a3-d01783c06f0d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: dom0 update got stuck - now QOS daemon does not start
indigo1...@gmail.com: 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. -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/44836887-1275-6975-1cb3-cc32f63a4d45%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: dom0 update got stuck - now QOS daemon does not start
Am Mittwoch, 5. Juni 2019 10:00:36 UTC+2 schrieb qubes666: > Hi, > need really help. Yesterday i started on my Thinkpad dom0 update through the > terminal command. During verification process the program got stuck. I > powered off. Now, the boot process seems to stop after the login. > > Qubes manager, other programs and all VM do no start. (sudo journalctl). > > qubes-prefs output state: error: failed to connect to qubesd service Errno2 > no such file or directory > > new sudo qubes-dom0-update state the same error message. > > Any help is appreciated. Further Info: sudo Hubes-dom0-update also state "UpdateVM not set,exiting" 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... qubes-prefs --help-properties points to the same error. Seems there is a config file missing or empty... "dnf history info" state that qubes-core-dom0 ; qubes-gpg-split-dom0 ; qubes-mgmt-salt-dom0 ; qubes-usb-proxy-dom0 are upgraded, but there is a Scriptlet output : 1 running as unit: run-rb708..service I am still lost. -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9fe2850d-8d81-40e9-b5da-7f93f03ec0b1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: dom0 update got stuck - now QOS daemon does not start
Am Mittwoch, 5. Juni 2019 12:03:38 UTC+2 schrieb Bertrand Lec: > Le mercredi 5 juin 2019 10:00:36 UTC+2, qubes666 a écrit : > > Hi, > > need really help. Yesterday i started on my Thinkpad dom0 update through > > the terminal command. During verification process the program got stuck. I > > powered off. Now, the boot process seems to stop after the login. > > > > Qubes manager, other programs and all VM do no start. (sudo journalctl). > > > > qubes-prefs output state: error: failed to connect to qubesd service Errno2 > > no such file or directory > > > > new sudo qubes-dom0-update state the same error message. > > > > Any help is appreciated. > > I had the same problem. > I did a "sudo dnf reinstall qubes-core-dom0" Hi, thank you. I tried it an got the message: Failed to synchronize cache for repo "qubes-dom0-cached", disabling. Installed package qubes-core-dom0-4.0.43-1.fc25.x86_64 (from) not available. Error: Nothing to do. The last line is kind of ironic, i try to keep my humor, since everything is "locked" in qubesOS. Any other suggestion ? -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4cb9ec8a-cebf-4a46-b7dc-6deb8ab22ce3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: dom0 update got stuck - now QOS daemon does not start
Le mercredi 5 juin 2019 10:00:36 UTC+2, qubes666 a écrit : > Hi, > need really help. Yesterday i started on my Thinkpad dom0 update through the > terminal command. During verification process the program got stuck. I > powered off. Now, the boot process seems to stop after the login. > > Qubes manager, other programs and all VM do no start. (sudo journalctl). > > qubes-prefs output state: error: failed to connect to qubesd service Errno2 > no such file or directory > > new sudo qubes-dom0-update state the same error message. > > Any help is appreciated. I had the same problem. I did a "sudo dnf reinstall qubes-core-dom0" -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ff4bac1d-29d5-41d3-8d65-88c05ea5ab2a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
