[qubes-users] Re: New installation of Qubes OS stopped booting for no reason?

2018-04-21 Thread billollib


Thanks everybody for the replies. I apologize for the delay in responding -- 
I've been traveling and just got off the plane on the last leg of the trip.

I had not installed any updates in Qubes, afaik, but did install upgrades in 
both Netrunner and Windows.  Yes, my troubleshooting failed also.  No big deal 
-- I'll reinstall when I get a chance.

-- 
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/a1351be9-b80b-46f5-84e3-8907eb362212%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: New installation of Qubes OS stopped booting for no reason?

2018-04-21 Thread john

On 04/19/18 08:05, billollib-re5jqeeqqe8avxtiumw...@public.gmane.org wrote:

So, I had installed Qubes 4 on a triple boot laptop (Win 10, Netrunner linux, Qubes OS).  
It had installed fine, and I had booted up in Qubes three or four times, played with the 
VMS, ran firefox, poked around a little, and was happy.  Then I got busy with some other 
stuff and set it aside, and worked mostly in Netrunner for my "real" work.

Today, I come back to it, and Qubes won't boot.  I get the following errors on 
the boot screen:

Failed to load kernal modules

Kfd: kgd2kfd_probe failed

Reached target basic system



 dracut - initqueue[334]: Warning: dracut-initque time out - 
starting timeout script



Could not boot
/dev/mapper/qubes_dom0_root does not exist
/dev/qubes_dome0/root does not exist

and I'm dumped into the rescue prompt.

This has repeated three times.  I tried taking out my usb mouse (which has 
caused problems in the past, though not this), but that didn't change anything.

Is this some configuration thing, or did aliens from outer space corrupt my 
partition with their evil laptop killer ray and I need to reinstall -- I don't 
mind, since I'm just playing around with Qubes, but I'd rather fix it...

Thanks!

billo



sounds a bit like my meltdown in Q4 ; did you try the  troubleshooting 
choice then #1  enter LUKS passphrase  from the installation media  ? 
in my case it failed, and I finally gave up,  after  Awokd  kind of 
confirmed I was SOOL  or so


--
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/818ca905-cdcd-68d5-3303-16aaf445b0db%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: New installation of Qubes OS stopped booting for no reason?

2018-04-19 Thread cooloutac
On Thursday, April 19, 2018 at 2:05:44 PM UTC-4, bill...@gmail.com wrote:
> So, I had installed Qubes 4 on a triple boot laptop (Win 10, Netrunner linux, 
> Qubes OS).  It had installed fine, and I had booted up in Qubes three or four 
> times, played with the VMS, ran firefox, poked around a little, and was 
> happy.  Then I got busy with some other stuff and set it aside, and worked 
> mostly in Netrunner for my "real" work.
> 
> Today, I come back to it, and Qubes won't boot.  I get the following errors 
> on the boot screen:
> 
> Failed to load kernal modules
> 
> Kfd: kgd2kfd_probe failed
> 
> Reached target basic system
> 
> 
> 
>  dracut - initqueue[334]: Warning: dracut-initque time out - 
> starting timeout script
> 
> 
> 
> Could not boot
> /dev/mapper/qubes_dom0_root does not exist
> /dev/qubes_dome0/root does not exist 
> 
> and I'm dumped into the rescue prompt.
> 
> This has repeated three times.  I tried taking out my usb mouse (which has 
> caused problems in the past, though not this), but that didn't change 
> anything.
> 
> Is this some configuration thing, or did aliens from outer space corrupt my 
> partition with their evil laptop killer ray and I need to reinstall -- I 
> don't mind, since I'm just playing around with Qubes, but I'd rather fix it...
> 
> Thanks!
> 
> billo

Maybe one of the other os's did.  Maybe qubes dom0 updated its kernel and its 
no longer recognized by whatever grub you are using?

-- 
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/3a01a80d-a0b8-419c-b2fa-ccd6201e361b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.