[qubes-users] Here is some graphical documentation - with commands - for the Qubes boot and decrypt process
Hi, I've graphically documented (with commands) the Qubes boot and decrypt process to the best of my knowledge in QUBES-BOOTUP.svg @ https://github.com/rshetye/good-karma/ I had run into some problems while testing Qubes, and found the documentation lacking (or my understanding lacking). So I documented it myself for my better understanding and would like to share it with the general Qubes community. Thanks for making Qubes such for a great product ! Regards, Ranjeet -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CALvHdtYm-d2nFP0nY0sinZ8b_h-jY9BrsWRKzwWGWuLMRKwf5g%40mail.gmail.com.
[qubes-users] Re: Need to fix boot process broken by kernel update. Data is safe.
Hi, Following up on my previous post: I've documented the Qubes boot process to the best of my knowledge in QUBES-BOOTUP.svg @ https://github.com/rshetye/good-karma/ It took some time to document and organize everything. Thanks, Ranjeet On Wednesday, February 10, 2021 at 12:51:56 PM UTC-6 Ranjeet Shetye wrote: > > Hi, > > I got my system up and running. > > It was a problem with the efi boot details. I had installed the latest > kernel (not manually) and that install process somehow messed up the efi > boot as it existed. After boot was broken, the console would show what it > was going to boot but the xen never loaded. Now it does. > > Thank you donoban, Bernhard, and Jinoh for the right pointers. > > I have made a list of steps that helped me gauge the situation. I will > post it within a few hours. > > Regards, > Ranjeet > > On Wed, Feb 10, 2021, 8:21 AM Jinoh Kang wrote: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA256 >> >> On 2/10/21 3:05 AM, Ranjeet Shetye wrote: >> > Hi, >> > >> > Is there a standard HOWTO I can follow to fix the boot process (to go >> from a grub / xen.cfg that fails to LUKS decrypt and load unencrypted >> rootfs) >> > >> > I am reasonably knowledgeable about Linux. Gaps exist in my knowledge >> regarding BIOS and UEFI boot processes. >> > >> > Unfortunately the grub update for the kernel upgrade seems to have >> messed up the boot process. How do I figure out if it's installed for BIOS >> or UEFI mode ? >> > >> > My data is safe and LUKS encrypted . I can use a live USB to decrypt >> it, access it and I also have made 2 backup copies. >> > >> > So with nothing to lose I tried to fix the boot manually from a live >> USB including creating /etc/default/grub but situation is no better. >> > >> > Between BIOS / (UEFI) / grub2 / xen / vmlinuz / LUKS / LVM2 , I am lost >> where the fix might be. Might be grub flags, grub modules, grub defaults, >> xen cfg, EFI manager etc. Hence my question. >> > >> > Thanks, >> > Ranjeet >> >> Also note that Qubes R4.0 on UEFI does not boot via GRUB -- it boots >> directly via \EFI\qubes\xen.efi. >> >> - -- >> Sincerely, >> Jinoh Kang >> -BEGIN PGP SIGNATURE- >> >> iQJMBAEBCAA2FiEEzGktrvc/U3kFXd9AGlqQRGyEq/UFAmAj67YYHGppbm9oLmth >> bmcua3JAZ21haWwuY29tAAoJEBpakERshKv1oLIP/jjFOQkzyYlMxZWAicelCeiS >> g3k/f8Gg6L7yBEQhXdBSiFVHKz5V35VUcseLk8gqrxxrAuzSuJwRwzno/f/DR7Jk >> 9IIc6LuQNrFjSMt327wqGsXvt7i/AObT8mUHiuKI8CTZOmX5kA1COk5jE5psCWks >> pG4ahB/chbUUS6rgx0JfgitKJopHCN9MXIc+xaJJatoLeJH89rJC/Lu8hSLjYwXx >> /TQIY4MJdM/HHP2dtye/ZbR6NT7kR/f985vqreN2D+83pCjSzqUu1aZt10oh92in >> 4qxel9DkLg0plnwi2AFgLZfHNXmTkR13eoc9awW+L7nZvhZbPKZ3Kt0X/QfWNFK+ >> ThHZzLsWG+BNDU70fWkDJ137GhggfxChANLjX8ltRSgPh7ApIofYfOaoAUqXBz4j >> QF8rYp+xhR5aMIGiXVBYeThHva8P6Zy/JwMq/Bo5hl52FAUwUGl5920+t/W66iTC >> eL3UyRsO9akD5ovbEkCdhkBISy9KDsE5KkI7cKa+ccl08yyTjbLpfZ1etYbIKRSQ >> OOtE0csiByZjS7sUtmgHcbGYRXMLbJ4xQMOptjNrndcY2JM3Di4q+JX/UwAhLO52 >> VYB3zHYBnKDJai5iPFARzoCG86otjlU9/gGbx/4JjKC+SjZ1XI7gZYdfFvF+ZRBf >> OCGR9pkKQunhiNhLJ8OT >> =pSYS >> -END PGP SIGNATURE- >> > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/142aed7a-dd7d-4fbc-bd72-4183b1f0e38fn%40googlegroups.com.
[qubes-users] Re: Need to fix boot process broken by kernel update. Data is safe.
Hi, I got my system up and running. It was a problem with the efi boot details. I had installed the latest kernel (not manually) and that install process somehow messed up the efi boot as it existed. After boot was broken, the console would show what it was going to boot but the xen never loaded. Now it does. Thank you donoban, Bernhard, and Jinoh for the right pointers. I have made a list of steps that helped me gauge the situation. I will post it within a few hours. Regards, Ranjeet On Wed, Feb 10, 2021, 8:21 AM Jinoh Kang wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 2/10/21 3:05 AM, Ranjeet Shetye wrote: > > Hi, > > > > Is there a standard HOWTO I can follow to fix the boot process (to go > from a grub / xen.cfg that fails to LUKS decrypt and load unencrypted > rootfs) > > > > I am reasonably knowledgeable about Linux. Gaps exist in my knowledge > regarding BIOS and UEFI boot processes. > > > > Unfortunately the grub update for the kernel upgrade seems to have > messed up the boot process. How do I figure out if it's installed for BIOS > or UEFI mode ? > > > > My data is safe and LUKS encrypted . I can use a live USB to decrypt it, > access it and I also have made 2 backup copies. > > > > So with nothing to lose I tried to fix the boot manually from a live USB > including creating /etc/default/grub but situation is no better. > > > > Between BIOS / (UEFI) / grub2 / xen / vmlinuz / LUKS / LVM2 , I am lost > where the fix might be. Might be grub flags, grub modules, grub defaults, > xen cfg, EFI manager etc. Hence my question. > > > > Thanks, > > Ranjeet > > Also note that Qubes R4.0 on UEFI does not boot via GRUB -- it boots > directly via \EFI\qubes\xen.efi. > > - -- > Sincerely, > Jinoh Kang > -BEGIN PGP SIGNATURE- > > iQJMBAEBCAA2FiEEzGktrvc/U3kFXd9AGlqQRGyEq/UFAmAj67YYHGppbm9oLmth > bmcua3JAZ21haWwuY29tAAoJEBpakERshKv1oLIP/jjFOQkzyYlMxZWAicelCeiS > g3k/f8Gg6L7yBEQhXdBSiFVHKz5V35VUcseLk8gqrxxrAuzSuJwRwzno/f/DR7Jk > 9IIc6LuQNrFjSMt327wqGsXvt7i/AObT8mUHiuKI8CTZOmX5kA1COk5jE5psCWks > pG4ahB/chbUUS6rgx0JfgitKJopHCN9MXIc+xaJJatoLeJH89rJC/Lu8hSLjYwXx > /TQIY4MJdM/HHP2dtye/ZbR6NT7kR/f985vqreN2D+83pCjSzqUu1aZt10oh92in > 4qxel9DkLg0plnwi2AFgLZfHNXmTkR13eoc9awW+L7nZvhZbPKZ3Kt0X/QfWNFK+ > ThHZzLsWG+BNDU70fWkDJ137GhggfxChANLjX8ltRSgPh7ApIofYfOaoAUqXBz4j > QF8rYp+xhR5aMIGiXVBYeThHva8P6Zy/JwMq/Bo5hl52FAUwUGl5920+t/W66iTC > eL3UyRsO9akD5ovbEkCdhkBISy9KDsE5KkI7cKa+ccl08yyTjbLpfZ1etYbIKRSQ > OOtE0csiByZjS7sUtmgHcbGYRXMLbJ4xQMOptjNrndcY2JM3Di4q+JX/UwAhLO52 > VYB3zHYBnKDJai5iPFARzoCG86otjlU9/gGbx/4JjKC+SjZ1XI7gZYdfFvF+ZRBf > OCGR9pkKQunhiNhLJ8OT > =pSYS > -END PGP SIGNATURE- > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CALvHdtY90NWaR1i0vJJ7M%2BrcX07x%2Bv1rWQEooCMQNj4KAo-5bA%40mail.gmail.com.
[qubes-users] Need to fix boot process broken by kernel update. Data is safe.
Hi, Is there a standard HOWTO I can follow to fix the boot process (to go from a grub / xen.cfg that fails to LUKS decrypt and load unencrypted rootfs) I am reasonably knowledgeable about Linux. Gaps exist in my knowledge regarding BIOS and UEFI boot processes. Unfortunately the grub update for the kernel upgrade seems to have messed up the boot process. How do I figure out if it's installed for BIOS or UEFI mode ? My data is safe and LUKS encrypted . I can use a live USB to decrypt it, access it and I also have made 2 backup copies. So with nothing to lose I tried to fix the boot manually from a live USB including creating /etc/default/grub but situation is no better. Between BIOS / (UEFI) / grub2 / xen / vmlinuz / LUKS / LVM2 , I am lost where the fix might be. Might be grub flags, grub modules, grub defaults, xen cfg, EFI manager etc. Hence my question. Thanks, Ranjeet -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CALvHdtbQ9ptWR9%3DEwdN2Uss2jtxZLu%3DqN9M-K50X%3DC%3Dv2Ry7eQ%40mail.gmail.com.
