I want to make clear that in each case, the new kernel has worked fine once I persuaded my BIOS to boot it. The problem is always that, after each kernel upgrade, the BIOS no longer recognizes any bootable partition, not even listing the drive among its boot options.
Unmounting before fsck is the standard process, but I wonder why and how the dom0 kernel upgrade script leaves the boot partition in a state that the BIOS will not boot. I am far from certain that the fsck.vfat was what restored bootability, but something did. dom0 kernel upgrade should not leave the boot partition in such undesired state, unless there is some hard to reproduce bug. Otherwise it will get fixed really soon. I do not have whole lot of details about your configuration.. but if you really believe this issue is caused by the dom0 kernel upgrade script, then try to reproduce it in a minimal amount of steps, e.g.: 1. install qubes os of version X.Y.Z with the /boot on FAT FS (+ any other custom settings you have, including if you have a dual boot); 2. run qubes-dom0-update kernel-x.y.z; Otherwise it's hard to help. You can also inspect the install scripts by yourself: $ rpm -q --scripts kernel $ less /bin/kernel-install Kind regards, Andrey Arapov -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6a462707231ce372a7168232fec690a7%40nixaid.com.
