On 12/12/25 18:24, Mik J wrote:
Brad: I have recreated the a partition after the problem I mention. Before
doing my manipulations the a partition was exactly the same as the c partitition
In my experience, the offset for partition a is 64 after fdisk -iy *and*
then disklabel -E.
Here is an example... no fdisk (only disklabel -E):
-bash-5.3# disklabel sd6
# /dev/rsd6c:
type: SCSI
disk: SCSI disk
label: Patriot Memory
duid: 53b9991e23c57229
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 7540
total sectors: 121145344
boundstart: 0
boundend: 121145344
16 partitions:
# size offset fstype [fsize bsize cpg]
a: 121145344 0 4.2BSD 2048 16384 1
c: 121145344 0 unused
And here is an example of fdisk -iy, *and* then disklabel -E:
-bash-5.3# disklabel sd6
# /dev/rsd6c:
type: SCSI
disk: SCSI disk
label: Patriot Memory
duid: d4bc584900e5098b
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 7540
total sectors: 121145344
boundstart: 64
boundend: 121145344
16 partitions:
# size offset fstype [fsize bsize cpg]
a: 121145280 64 4.2BSD 2048 16384 1
c: 121145344 0 unused
IMO, there is no need to run fdisk on a hard drive that's only going to
be mounted and used after the system has booted. disklabel -E and newfs
is enough.
And when you do not use fdisk, then the offset of partition a will be
zero and that is correct. No?
Brad
