On 2020-09-09 23:02, David wrote:
On Thu, 10 Sep 2020 at 11:26, David Christensen
<dpchr...@holgerdanske.com> wrote:
On 2020-09-09 08:03, David Wright wrote:
... having been bitten by
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923561
I have a 300 GB drive that has been causing me some confusion. Did I
elicity the bug when I partitioned the disk as follows?
I have not read all relevant messages, but in case it helps you can
check your exact device partition boundaries by running:
parted /dev/disk/by-id/ata-ST3300622AS_******** 'unit compact print
free unit s print free unit b print free'
That parted(8) incantation has issues, as does the disk:
2020-09-10 14:00:52 root@tinkywinky ~
# parted /dev/disk/by-id/ata-ST3300622AS_******** 'unit compact print
free unit s print free unit b print free'
Error: The backup GPT table is corrupt, but the primary appears OK, so
that will be used.
parted: invalid token: unit
OK/Cancel? ok
Model: ATA ST3300622AS (scsi)
Disk /dev/sdb: 300GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
17.4kB 1049kB 1031kB Free Space
1 1049kB 300GB 300GB ext2 ********
300GB 300GB 139kB Free Space
This is how I invoke parted(8):
2020-09-10 14:01:58 root@tinkywinky ~
# parted /dev/disk/by-id/ata-ST3300622AS_******** unit s print free
Error: The backup GPT table is corrupt, but the primary appears OK, so
that will be used.
OK/Cancel? ok
Model: ATA ST3300622AS (scsi)
Disk /dev/sdb: 586072368s
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
34s 2047s 2014s Free Space
1 2048s 586072063s 586070016s ext2 ********
586072064s 586072334s 271s Free Space
Looking at the above information, my first partition starts at sector
2048 and ends at sector 586072063 (inclusive). Both of these values
represent 1 MiB alignment, so it appears that the partition has not been
affected by bug 923561.
David
