Re: [qubes-users] Qubes 4 starts, but no VMs will load.

2020-01-07 Thread 'awokd' via qubes-users 
aisteruannano...@gmail.com:
> Dear Fellows,
> 
> I can boot into Qubes normally, except I get some scary looking boot 
> messages (see boot.log contents below.) No VMs will start. After some 
> digging in logs, I found that there was a syntax error on trying to load 
> /usr/lib/tmpfiles.d/qubes.conf. The file seemed to be corrupted, so I 
> renamed it and made a new qubes.conf based on what I found on a working 
> qubes install (I typed it line-by-line, no intentional alterations.) This 
> seems to have fixed the syntax error, but I still can't get qubesd to load, 
> and so can't start any VMs or even start a backup.

I think I've seen that before when someone interrupted a dom0 update
halfway through and/or did a hard poweroff without shutting down Qubes
which resulted in a bunch of files getting corrupted. Probably safest
bet is to reinstall and restore your qubes from a backup. You should be
able to mount the volumes if needed to pull data from them if you
haven't backed up in a while.

-- 
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/1ad08c7a-c59c-8a57-adc3-21345408974c%40danwin1210.me.

[qubes-users] Qubes 4 starts, but no VMs will load.

2020-01-06 Thread aisteruannanorna 
Dear Fellows,

I can boot into Qubes normally, except I get some scary looking boot 
messages (see boot.log contents below.) No VMs will start. After some 
digging in logs, I found that there was a syntax error on trying to load 
/usr/lib/tmpfiles.d/qubes.conf. The file seemed to be corrupted, so I 
renamed it and made a new qubes.conf based on what I found on a working 
qubes install (I typed it line-by-line, no intentional alterations.) This 
seems to have fixed the syntax error, but I still can't get qubesd to load, 
and so can't start any VMs or even start a backup.

I'm not sure what to try next. I strongly suspect more corrupt files are to 
blame. 

As always, any help will be appreciated.

Thanks in advance,


  T. S. P. Capehart



 %G %G %G[ [0;32m  OK   [0m] Started Cryptography Setup for 
luks-e79f0b60-d59c-4caa-b422-fbca72c62f31.
[ [0;32m  OK   [0m] Found device 
/dev/mapper/luks-e79f0b60-d59c-4caa-b422-fbca72c62f31.
[ [0;32m  OK   [0m] Reached target Encrypted Volumes.
[ [0;32m  OK   [0m] Reached target System Initialization.
[ [0;32m  OK   [0m] Reached target Basic System.
[ [0;32m  OK   [0m] Found device /dev/mapper/qubes_dom0-root.
[ [0;32m  OK   [0m] Reached target Initrd Root Device.
[ [0;32m  OK   [0m] Started dracut initqueue hook.
 Starting File System Check on /dev/mapper/qubes_dom0-root...
[ [0;32m  OK   [0m] Reached target Remote File Systems (Pre).
[ [0;32m  OK   [0m] Reached target Remote File Systems.
[ [0;32m  OK   [0m] Started File System Check on 
/dev/mapper/qubes_dom0-root.
 Mounting /sysroot...
[ [0;32m  OK   [0m] Mounted /sysroot.
[ [0;32m  OK   [0m] Reached target Initrd Root File System.
 Starting Reload Configuration from the Real Root...
[ [0;32m  OK   [0m] Started Reload Configuration from the Real Root.
[ [0;32m  OK   [0m] Reached target Initrd File Systems.
[ [0;32m  OK   [0m] Reached target Initrd Default Target.
 Starting Cleaning Up and Shutting Down Daemons...
 Starting Plymouth switch root service...
[ [0;32m  OK   [0m] Stopped target Timers.
 Stopping Forward Password Requests to Plymouth...
[ [0;32m  OK   [0m] Stopped target Remote File Systems.
[ [0;32m  OK   [0m] Stopped target Remote File Systems (Pre).
[ [0;32m  OK   [0m] Stopped dracut initqueue hook.
[ [0;32m  OK   [0m] Stopped dracut cmdline hook.
[ [0;32m  OK   [0m] Stopped Forward Password Requests to Plymouth.
[ [0;32m  OK   [0m] Stopped Cleaning Up and Shutting Down Daemons.
[ [0;32m  OK   [0m] Stopped target Initrd Default Target.
[ [0;32m  OK   [0m] Stopped target Basic System.
[ [0;32m  OK   [0m] Stopped target Sockets.
[ [0;32m  OK   [0m] Stopped target System Initialization.
[ [0;32m  OK   [0m] Stopped Create Volatile Files and Directories.
[ [0;32m  OK   [0m] Stopped Apply Kernel Variables.
[ [0;32m  OK   [0m] Stopped target Local File Systems.
[ [0;32m  OK   [0m] Stopped Load Kernel Modules.
[ [0;32m  OK   [0m] Stopped target Encrypted Volumes.
 Stopping udev Kernel Device Manager...
[ [0;32m  OK   [0m] Stopped udev Coldplug all Devices.
[ [0;32m  OK   [0m] Stopped target Swap.
[ [0;32m  OK   [0m] Stopped target Slices.
[ [0;32m  OK   [0m] Stopped target Paths.
[ [0;32m  OK   [0m] Stopped target Initrd Root Device.
[ [0;32m  OK   [0m] Started Plymouth switch root service.
[ [0;32m  OK   [0m] Stopped udev Kernel Device Manager.
[ [0;32m  OK   [0m] Stopped Create Static Device Nodes in /dev.
[ [0;32m  OK   [0m] Stopped Create list of required static device nodes for 
the current kernel.
[ [0;32m  OK   [0m] Closed udev Kernel Socket.
[ [0;32m  OK   [0m] Closed udev Control Socket.
 Starting Cleanup udevd DB...
[ [0;32m  OK   [0m] Started Cleanup udevd DB.
[ [0;32m  OK   [0m] Reached target Switch Root.
 Starting Switch Root...
 %G %G[ [0;1;31mFAILED [0m] Failed to start Qubes DB agent.
See 'systemctl status qubes-db-dom0.service' for details.
[ [0;32m  OK   [0m] Started Login Service.
[ [0;32m  OK   [0m] Started The Xen xenstore.
 Starting Virtualization daemon...
 Starting Xenconsoled - handles logging from guest consoles and 
hypervisor...
 Starting xen-init-dom0, initialise Dom0 configuration (xenstore 
nodes, JSON configuration stub)...
[ [0;32m  OK   [0m] Started Xenconsoled - handles logging from guest 
consoles and hypervisor.
[ [0;32m  OK   [0m] Started xen-init-dom0, initialise Dom0 configuration 
(xenstore nodes, JSON configuration stub).
[ [0;32m  OK   [0m] Started Daemon for power management.
[ [0;32m  OK   [0m] Started Virtualization daemon.
[ [0;1;31mFAILED [0m] Failed to start Qubes memory management daemon.
See 'systemctl status qubes-qmemman.service' for details.
[ [0;1;31mFAILED [0m] Failed to start Qubes OS daemon.
See 'systemctl status qubesd.service' for details.
 Starting Qubes Dom0 startup setup...
[ [0;32m  OK   [0m] Started Qubes Dom0 startup setup.
 Starting Start Qubes VM sys-usb...
 Starting Start Qubes VM sys-usb-input...
[ [0;1;31mFAILED