Re: [EXT] Re: [qubes-users] XSAs released on 2021-11-23
On 11/27/21 11:03 AM, 'awokd' via qubes-users wrote: Qubes: Is there Qubes documentation outlining the steps to increase the size of /boot, or does one follow general disk management, with tools like using GParted for example. Although the disk is a LUKS encrypted volume. Can one decrypt, use GParted to resize, and then encrypt again? Note that /boot itself is not encrypted, but you're right, you would Since GRUB can load LUKS-encrypted /boot, one could even encrypt /boot, but a part of GRUB is also encrypted then, it seems. At least there isn't much GRUB functionality until the LUKS volume is unlocked. And it seems you only have one attempt to enter the passphrase correctly. Also GRUB decryption seems much slower than kernel decryption... have to decrypt the rest to resize it. No Qubes specific docs. Procedure you describe should work, but might be further ahead by backing up your VMs to a removable encrypted drive, doing a fresh install of R4.1 (rc2 last I saw) and adjusting the boot partition size on the installer screen, then restoring? -- 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/492c9a9c-e566-38c1-bb6d-81fd792282db%40rz.uni-regensburg.de.
Re: [EXT] Re: [qubes-users] XSAs released on 2021-11-23
On 11/26/21 3:47 PM, Qubes wrote: 'awokd' via qubes-users wrote: Qubes: And that is it. When I run update from CLI I get this, "Error Summary - Disk Requirements: At least 33MB more space needed on the /boot filesystem." Is that normal behavior? The disk /boot lives on is not full, the complaint is with /boot specific. What does "df -h" say about /boot? If it's full and you've been updating the system for a while, check for old EFI images that haven't been cleaned up. df -h shows /boot is full, 100% used. I am not sure how to fix this, can you please give me advice? Looking at ls -l for /boot I can see a lot of old images, but I guess that is because I have set my system to keep 15 kernels. However, I have Interestingly I see three kernels (and corresponding initramfs) here, but only one Xen version. So it seems kernels have versioning, but not Xen. Of my 700MB /boot 41% (283MB) are used. been on the 5.xxx kernel now since it was launched so I can safely remove the 4. kernels. How does one clean this up properly. If I just delete the files from /boot the system may still think they are there, is there a built-in process/procedure to follow for this? -- 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/7b6775ba-b76d-5908-3ffc-e0c1013b8984%40rz.uni-regensburg.de.
