

I've been chasing this for many, many hours. Windows disk utility tells a different story: How about Minitool? Seems just fine and it can even see the contents (right click D: -> Explore)! # new logical, default start, default endīack in Windows, if I click on D:, I get prompted to format it and told that it's not a recognized format. # new extended, default start, default end # new primary, default start, +50G, change type from 83 -> 7 How about letting fdisk do the work? # fdisk /dev/sdb

So, obviously something funky is going on with the extended/logical partitions (error from fdisk and 256G != 1.2T.). I/O size (minimum/optimal): 512 bytes / 512 bytesĭevice Boot Start End Sectors Size Id Type Sector size (logical/physical): 512 bytes / 512 bytes Invalid flag 0xefdb of EBR (for partition 5) will be corrected by w(rite).ĭisk /dev/sdb: 238.5 GiB, 256060514304 bytes, 500118192 sectors This reboot happened to be one of those times. Now, boot into an Arch linux install USB and see what it thinks: # sometimes booting to USB reverses the normal /dev/sda for the SDD Windows disk utility seems to think the operation went fine! Like this:Īfter clicking apply (note I've just got a final chunk of unallocated space and no partitions): I could add them to the action queue, click apply, it would say "Operation successful," but the space would show back up as unallocated. Somewhere along the way, I stopped being able to create logical partitions in Minitool. There was a lot of creating/deleting/formatting of volumes involved from Minitool but nothing else (e.g. I'll shorten the middle of the story, which involved being unable to get EasyBCD to chainload to my logical /boot partition. Logical: 512M for /boot, unformatted, ID 83.Primary: 100G for TrueCrypt NTFS, formatted as NTFS (temporarily), ID 7.

I also needed my shared partition for TrueCrypt/NTFS, so I created the following out of the free space: Next, I installed Minitool Partition Wizard since Windows doesn't change partition IDs (that I know of), and I needed /boot and / as type 83 for installing linux.

I backed up the latter two, and extended C: The computer started with the following partitions: MBR, not GPT (googling problems like this are often GPT related.The tl dr background is that I'm trying to set up a dual boot system with a shared TrueCrypt/NTFS partition for work files.
