I am setting up my new hard drive.

[a2_4am@mastodon.social]

@mcc "GPT's haunted."

[gwenverbsnouns@mastodon.social]

@mcc last I checked, which was wildly outdated like a decade ago, it was easier to install windows first over the whole disk, then fix the situation in gparted later. windows doesn't generally understand that it has to share

[orca@nya.one]

@mcc@mastodon.social I don't think that matters.

Though creating GPT on a disk under Windows would automatically creates a Microsoft Reserved (MSR) partition that's about 128 or 256 MB in size. You can see or delete that partitionwith command line tool diskpart under Windows (or any other partitioner softwares of your liking, MSRs' are only hidden in diskmgmt.msc ). It wasn't anywhere near affecting functionality, but it's certainly annoying.
Edit: and you can certainly say diskmgmt.msc is haunted because of that :)

Oh, and, if you're installing Windows on this disk (skip this entire section if you're not) and intent to use diskpart to create partition layout for it, remember to format EFI System Partition after creation because diskpart default to not automatically formatting the partitions it created, and ESP aren't formattable in diskmgmt.msc or windows file explorer.

[faraiwe@mstdn.social]

@glyph @mcc ::motions at the sea of broken GRUB sectors, f*ed up by windows disk tools:: Lo! There do I see...

[hatzka@tech.lgbt]

@dlakelan I thought it would be obvious, but I meant using LUKS with a blank passphrase and scrambling the passphrase when you decommission the drive.

as I understand it, LUKS master keys are not derived directly from the passphrase but instead generated randomly and encrypted with it, precisely so that you can change the password without rewriting the whole drive. so scrambling the LUKS password should render the data just as unrecoverable as your strategy would with less effort, shouldn't it?

[kwi@mastodon.online]

@hatzka @dlakelan Correct. The (blank) passphrase just decrypts a key slot containing the randomly generated key used for actual disk encryption, and removing these key slots renders the partition unreadable. https://www.man7.org/linux/man-pages/man8/cryptsetup-erase.8.html

[jerojasro@col.social]

@mcc reverse Betteridge's Law applies here.

[onyxraven@hachyderm.io]

@glyph @mcc IIRC there’s some arcane writings on the correct order of things to make modern windows happy (tpm/secure boot and drive encryption throw a wrench in things I think) AND have it not clobber grub/etc. it’s been a while.

I had to do some similar malarkey with macos on an intel mini and at some point I lost the ability to boot the macos partition (frankly, no loss, it was ancient and I only boot it to Linux now)