Re: [qubes-users] Can’t boot after attempting to verify backup

2019-04-01 Thread Ryan Tate 

> On Apr 1, 2019, at 11:48 AM, Chris Laprise  wrote:
> 
> I think its more related to this issue:
> 
> https://github.com/QubesOS/qubes-issues/issues/4791

I think you nailed it. The first time I ran the verification, I panicked when 
it said it was extracting data, as it seemed to have already “verified” various 
VMs, and I hit cancel. Then I ran again and kept my determination to finish, 
and it seemed to work and give a happy “Finished” message. (I did not see any 
lvm alerts, but as you note, I was probably away from the machine at various 
points.)

The issue above mentions that if a prior restore fails, and then you do 
another, you  may run out of disk space. I think the equivalent happened to me, 
except instead of failing, it was cancelled (same result).

Right now I’m restoring my backup to a fresh Qubes install. At least I have my 
Qubes menu back, and fedora29, and my backup is about as fresh as one could 
hope.

Thanks for the help.

-- 
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/B29D2902-72DF-4934-B5A9-B858D1D2961F%40ryantate.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

[qubes-users] Can’t boot after attempting to verify backup

2019-04-01 Thread Ryan Tate 
On Friday I backed up my machine and attempted to verify the backup by 
launching qubes-backup-restore (GUI interface) and ticking the verify only box. 

Is it possible this box does not work? I was a bit alarmed when qubes began 
unpacking the backup after verifying each qube, but thought perhaps it was 
checking the data.

This morning is my first time booting since then. It goes into emergency mode. 
Warnings include “dracut-initqueue timeout - starting timeout scripts” (many 
times) “Could not boot.” “/dev/mapper/qubes_dom0-root does not exist” 
“/dev/qubes_dom0/root does not exist”. 

The only thing significant I can think I did to system Friday was the backup. 
It’s possible I also ran system update before or after backup and I vaguely 
recall a dom0 update but can’t recall if it was fRiday. 

Thanks for any help. Worried it’s a wipe and restore situation :-(

-- 
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/ADC61334-2172-4540-AABA-8E17C6FD06ED%40ryantate.com.
For more options, visit https://groups.google.com/d/optout.