dom0 update got stuck - now QOS daemon does not start

[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.

[Bertrand Lec]

I had the same problem.
I did a "sudo dnf reinstall qubes-core-dom0"

[indig...@gmail.com]

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 ?

[indig...@gmail.com]

________________________________________________________________________
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.

[awokd]

indig...@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.

[Qubes666]

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...

[awokd]

Qubes666:

"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.

[Qubes666]

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

[awokd]

Qubes666 wrote on 6/6/19 8:39 AM:

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.

[Qubes666]

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?

[awokd]

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.

[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.

[awokd]

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.