
When the first hard drives appeared that were bigger than the 2TiB limit that the MBR partition format could cope with, it seemed like the only tool available that could manage partitions in the new GPT format was GNU parted. So you had to say goodbye to the old fdisk and sfdisk utilities, and learn a new way of setting things up. Well, it turns out that the old programs have been updated with new features, and they can now cope with setting up and using GPT-partitioned disks just fine. I particularly like the “sfdisk -d” command, which dumps out the partition table in a detailed format that can be backed up and then used for restoration later, if the disk’s partition table should somehow get corrupted. As far as I could see, parted never gave the exact numbers, down to the sector, that were necessary for this. Also, in the past day, two problems with parted have manifested themselves acutely to me: * All partitioning changes are made immediately, unlike fdisk. * Also unlike fdisk, it didn’t seem to notice if you were clobbering existing partitions, and would happily overwrite them. Each of these (mis)features might seem bad enough on its own, but putting them together is a recipe for woe. So in future, I think I am going to abandon parted and go back to fdisk and sfdisk.

On Fri, Aug 18, 2017 at 12:38:27PM +1200, Lawrence D'Oliveiro wrote:
So in future, I think I am going to abandon parted and go back to fdisk and sfdisk.
Yes, I prefer fdisk, but the fact it no longer supports making BSD disklabels does detract somewhat from it. Cheers Michael.

On Sun, 20 Aug 2017 16:41:24 +1200, Michael Cree wrote:
Yes, I prefer fdisk, but the fact it no longer supports making BSD disklabels does detract somewhat from it.
The man page says “It understands GPT, MBR, Sun, SGI and BSD partition tables”. One minor irritation I found was when listing the available partition types. I had to set one relatively small (1MiB) partition of type “BIOS boot”, otherwise GRUB couldn’t install itself. But when I tried to find out what the code was for this, it scrolled off up the top of my text console. All I knew was that it was a small number. So I had to guess and try various small numbers until I hit on the right one.

On Sun, 20 Aug 2017 17:42:28 +1200, I wrote:
One minor irritation I found [with fdisk] was when listing the available partition types. I had to set one relatively small (1MiB) partition of type “BIOS boot”, otherwise GRUB couldn’t install itself. But when I tried to find out what the code was for this, it scrolled off up the top of my text console.
I am doing the same thing again, this time from Debian, not from SystemRescueCd. And it has brought up a pager, so I can still see all the output it has produced so far. So it seems to be something wrong with the setup of SystemRescueCd.
participants (2)
-
Lawrence D'Oliveiro
-
Michael Cree