Re: [qubes-users] Re: No Bootable Device after installing Qubes 4.0, Updating VMs and dom0, and rebooting
Zelda wrote on 9/29/18 12:10 PM: Does anyone have any insight/ideas as to why the OS is only booting with the backup drive present? During typical use, I don't usually keep the backup drive connected when using the operating system. I'm guessing your system's EFI partition is on the backup drive. To confirm, you could try repeating the install with only SSD attached, and using auto partitioning. -- 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/6ab0f4c6-6f0b-184b-f023-61c1e0d90b6c%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: No Bootable Device after installing Qubes 4.0, Updating VMs and dom0, and rebooting
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 the manual partitioning section, there is an option to automatically set up partitions. Selecting this option will set up the partitions for you, but display the partitioning scheme so you can alter the partition arrangement. I selected this option and wound up with an ext4/LUKS/swap partitioning scheme -- Continue to install normally -- Select updates over TOR -- Set up sys-net/sys-whonix systems, but not work/private/vault Once that was done, I proceeded incrementally, rebooting after each step, confirming that each new change did not result in the system failing to boot. (Update/reboot, restore/reboot, etc... etc...) For increased isolation, I have set up my hardware such that I am able to swap in different SSD drives using a trayless removable hard drive rack, each with its own install of Qubes 4. I also have a removable hard drive rack for a 7200 RPM backup drive. The 7200 RPM drive holds my my qubes templates and appvm backups. During my incremental installation process, I tested booting with and without the backup drive present. My newly reinstalled Qubes OS worked fine for the next 5 days, during which the backup drive was always present. There were some template and appvm updates done during this time. I shut down and removed the SSD and the backup drive when I was expecting repairmen to visit my residence and I could not be present. When I inserted the SSD and rebooted it this morning (Saturday 9/29/2018) without the backup drive present, I got the error that caused me to start this thread - "No bootable device found - Insert a bootable device." I tried swapping in one of the other SSDs and got the same problem. Then I inserted the previously functioning SSD drive AND the backup drive. This time it booted. Does anyone have any insight/ideas as to why the OS is only booting with the backup drive present? During typical use, I don't usually keep the backup drive connected when using the operating system. Thank you -- 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/de1fe238-09b9-43b2-8837-e9bc13c684e3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: No Bootable Device after installing Qubes 4.0, Updating VMs and dom0, and rebooting
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 the manual partitioning section, there is an option to automatically set up partitions. Selecting this option will set up the partitions for you, but display the partitioning scheme so you can alter the partition arrangement. I selected this option and wound up with an ext4/LUKS/swap partitioning scheme -- Continue to install normally -- Select updates over TOR -- Set up sys-net/sys-whonix systems, but not work/private/vault Once that was done, I proceeded incrementally, rebooting after each step, confirming that each new change did not result in the system failing to boot. (Update/reboot, restore/reboot, etc... etc...) For increased isolation, I have set up my hardware such that I am able to swap in different SSD drives using a trayless removable hard drive rack, each with its own install of Qubes 4. I also have a removable hard drive rack for a 7200 RPM backup drive. The 7200 RPM drive holds my my qubes templates and appvm backups. During my incremental installation process, I tested booting with and without the backup drive present. My newly reinstalled Qubes OS worked fine for the next 5 days, during which the backup drive was always present. There were some template and appvm updates done during this time. I shut down and removed the SSD and the backup drive when I was expecting repairmen to visit my residence and I could not be present. When I inserted the SSD and rebooted it this morning (Saturday 9/29/2018) without the backup drive present, I got the error that caused me to start this thread - "No bootable device found - Insert a bootable device." I tried swapping in one of the other SSDs and got the same problem. Then I inserted the previously functioning SSD drive AND the backup drive. This time it booted. Does anyone have any insight/ideas as to why the OS is only booting with the backup drive present? During typically use, I don't usually keep the backup drive connected when using the operating system. Thank you -- 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/0d3a57d1-675f-4b86-b04b-aea4d9786d14%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
