On Wed, 2016-03-23 at 18:22 +0300, Alexander Gordeev wrote: > Hello Dmitry, > > ..... > > Yep, astute needs to be fixed as the way how it wipes the disks is > way too fragile, dangerous and not always reliable due to what you > mentioned above. > > Nope, I think that zeroing of 446 bytes is not enough. Why don't we > want to wipe bios_boot partition too? Let's wipe all grub leftovers > such as bios_boot partitions too. They doesn't contain any FS, so > unlikely that kernel or any other process will prevent us from wiping > it. No errors, no kernel panic are expected. > > > On Tue, Mar 22, 2016 at 5:06 PM, Dmitry Guryanov <dguryanov@mirantis. > com> wrote: > > For GPT disks and non-UEFI boot this method will work, since MBR > > will still contain first stage of a bootloader code. > > > Agreed, it will work. But how about bios_boot partition? What do you > think? >
I have no objections against clearing bios boot partition, but could you describe scenario, how non-efi system will boot with valid BIOS_grub and wiped boot code in MBR? > > Thanks, Alex. > > _____________________________________________________________________ > _____ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubs > cribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev