[qubes-users] Re: No Bootable Device after installing Qubes 4.0, Updating VMs and dom0, and rebooting

2018-09-29 Thread Zelda
Hello again all, It has been a week since my last post. I again tried reinstalling Qubes 4. Here is what I found made the difference between working and getting the error I described previously: In the installer: -- Select the option to manually set up partitioning rather than auto. Within

[qubes-users] Re: No Bootable Device after installing Qubes 4.0, Updating VMs and dom0, and rebooting

2018-09-29 Thread Zelda
Hello again all, It has been a week since my last post. I again tried reinstalling Qubes 4. Here is what I found made the difference between working and getting the error I described previously: In the installer: -- Select the option to manually set up partitioning rather than auto. Within

Re: [qubes-users] No Bootable Device after installing Qubes 4.0, Updating VMs and dom0, and rebooting

2018-09-22 Thread Zelda
On Saturday, September 22, 2018 at 8:45:28 AM UTC-4, awokd wrote: > > On Friday, September 21, 2018 at 7:14:33 AM UTC-4, awokd wrote: > >>> Hello all, > >>> > >>> After a recent dom0 update froze my Qubes 3.2 system I'd been using for > >>> the past year and a half, I upgraded to Qubes 4.0 on the

Re: [qubes-users] No Bootable Device after installing Qubes 4.0, Updating VMs and dom0, and rebooting

2018-09-22 Thread Zelda
On Friday, September 21, 2018 at 7:14:33 AM UTC-4, awokd wrote: > > Hello all, > > > > After a recent dom0 update froze my Qubes 3.2 system I'd been using for the > > past year and a half, I upgraded to Qubes 4.0 on the same Samsung EVO 850 > > SSD. My PC has a Gigabyte AORUS GA-Z270X-Gaming 7