Re: [qubes-users] Re: 4.0 wouldn't boot after update

2018-04-25 Thread 'awokd' via qubes-users
On Wed, April 25, 2018 7:48 pm, Jon Solworth wrote:

>
> Didn't get to far with troubleshooting.  I got a shell, was able to
> decrypt the volume, but not sure wha to do next.

>From that point, you should be able to mount the LVM private partition for
the VMs you want to recover and copy out the data.

-- 
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/205da9c71d521e8f032e64e4352638ac.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: 4.0 wouldn't boot after update

2018-04-25 Thread Jon Solworth
On Wednesday, April 25, 2018 at 2:43:46 PM UTC-5, john wrote:
> On 04/25/18 05:13, Jon Solworth wrote:
> > I updated qubes 4.0 and there were some errors (about transactions on--I 
> > believe--some crypto stuff).  Afterwards, I couldn't boot getting the 
> > message
> > 
> > kernel panic -- not syncing: VFS unable to mount fs on unknown block (0,0)
> > 
> > the problem is that my backup is a bit old, and if possible I would like to 
> > retrieve the data.  So:
> > 
> >1. Is there a way to restore the kernel to a working one? or 
> > alternatively
> >2. If I build qubes on an external disk, is there a way to copy over the
> >   files from my SSD?
> >3. Any other suggestions.
> > 
> > (I tried to use troubleshooting with a 4.0 usb stick, but couldn't figure 
> > out how to recover).
> > 
> > thanks
> > Jon
> > 
> 
> Just curious was this a legacy or efi installation ?  and in your 
> Bios/EFI boot settings do you see two choices for the USB installation 
> media?
> 
> What happened when you tried 'troubleshooting'  USB media exactly ?

legacy.

Didn't get to far with troubleshooting.  I got a shell, was able to decrypt the 
volume, but not sure wha to do next.

-- 
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/151c2074-6b0d-46eb-a2e3-67ceed5dbeb0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: 4.0 wouldn't boot after update

2018-04-25 Thread john

On 04/25/18 05:13, Jon Solworth wrote:

I updated qubes 4.0 and there were some errors (about transactions on--I 
believe--some crypto stuff).  Afterwards, I couldn't boot getting the message

kernel panic -- not syncing: VFS unable to mount fs on unknown block (0,0)

the problem is that my backup is a bit old, and if possible I would like to 
retrieve the data.  So:

   1. Is there a way to restore the kernel to a working one? or alternatively
   2. If I build qubes on an external disk, is there a way to copy over the
  files from my SSD?
   3. Any other suggestions.

(I tried to use troubleshooting with a 4.0 usb stick, but couldn't figure out 
how to recover).

thanks
Jon



Just curious was this a legacy or efi installation ?  and in your 
Bios/EFI boot settings do you see two choices for the USB installation 
media?


What happened when you tried 'troubleshooting'  USB media exactly ?

--
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/efd4e79b-6d2d-fbb6-4daa-27effe9fd7b3%40riseup.net.
For more options, visit https://groups.google.com/d/optout.