Hacker News new | past | comments | ask | show | jobs | submit login

Perhaps, but either way it is not great to hear some UEFI has been designed to be "clever" to the point it's trying to hand hold users by deciding what should be in the superblock of a device without your explicit permission.

I can almost forgive it for OS designed for novices but even then they tend to ask permission - however, putting these assumptions into hardware and not even asking permission - that's a broken piece hardware IMO.




GPT has a backup/recovery feature. If the disk was ever a valid GPT disk, then there'll be a copy of the partition table in the final block -- and if that wasn't cleared properly then a functioning UEFI is supposed to restore the primary table from it.

The UEFI bios may be following the spec to the letter, here. If so, the takeaway is to always use `wipefs -a`.


The spec actually says that software should prompt for confirmation and report that it performed changes (see elsewhere in this thread).

`wipefs -a` is a good recommendation, but perhaps it can delete too much? In my case, I used `sgdisk --zap` to delete specifically the GPT bytes without deleting other data.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact