thanks for the reply and clarifications. much appreciated.
after reading the reply i went back and checked the disk. on amd64 Linux and OpenBSD fdisk shows the GPT properly. (output of Linux fdisk) Disk /dev/sdc: 235.58 GiB, 252933308416 bytes, 494010368 sectors Disk model: SSD-PEU3 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 15420EC6-BC4C-4DAB-BA8E-D4BAAD59640A Device Start End Sectors Size Type /dev/sdc1 2048 494008319 494006272 235.6G Linux filesystem (output of amd64 OpenBSD fdisk) sd2: 1> Disk: sd2 Usable LBA: 34 to 494010334 [494010368 Sectors] GUID: 15420ec6-bc4c-4dab-ba8e-d4baad59640a #: type [ start: size ] guid name ------------------------------------------------------------------------ 0: Linux files* [ 2048: 494006272 ] 1c5211a4-927b-4836-b2cf-92660b3d7988 2 on macppc OpenBSD fdisk replies "Not Found" ... BUT "fdisk -e" shows: (output of macppc OpenBSD fdisk) Enter 'help' for information sd0: 1> Disk: sd0 geometry: 30750/255/63 [494010368 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start: size ] ------------------------------------------------------------------------------- 0: EE 0 0 2 - 30750 184 26 [ 1: 494010367 ] EFI GPT 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 3: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused i have very limited knowledge of GPT/MBR/disklabels but that start seems odd. maybe it was created by the original SW used when the device was manufactured? 3 tested MBR on a separate USB drive, and the device got properly detected by macppc > MBR or GPT label? Yes. based on the simple test with the MBR on USB drive and that in mind i nuked the problem disk's GPT. created an MBR partition matching the size of the original partition. fsck on a Linux machine didn't return any errors. so ~ (output of Linux fdisk) Disk /dev/sdc: 235.58 GiB, 252933308416 bytes, 494010368 sectors Disk model: SSD-PEU3 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sdc4 * 2048 494008319 494006272 235.6G 83 Linux (output of macppc OpenBSD fdisk) Disk: sd0 geometry: 30750/255/63 [494010368 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start: size ] ------------------------------------------------------------------------------- 0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused *3: 83 0 32 33 - 30750 151 57 [ 2048: 494006272 ] Linux files* checking on macppc, disklabel has been kept intact !! now were rolling ~ # /dev/rsd0c: type: SCSI disk: SCSI disk label: SSD-PEU3 duid: 0000000000000000 flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 30750 total sectors: 494010368 boundstart: 0 boundend: 494010368 drivedata: 0 16 partitions: # size offset fstype [fsize bsize cpg] c: 494010368 0 unused i: 494006272 2048 ext2fs checking on macppc, mount was OK: /dev/sd0i on /mnt/sd0 type ext2fs (local) mounted without problems on amd64 Linux and OpenBSD too maybe i just got lucky lesson for the day ... stay old skool MBR yorosiku ~ December 19, 2019 9:17 AM, "Theo de Raadt" <dera...@openbsd.org> wrote: > The disklabel sector is a not a machine-independent format, and it > moves between different sectors on some machines. > > You'll find we make no promises about this type of disk-portability. > MBR or GPT label? Yes. > > Our own disklabels, unfortunately not. > > rgci...@disroot.org wrote: > >> dear all, >> >> to transfer files between an amd64 Linux, amd64 OpenBSD-current, and macppc >> OpenBSD-current i have a USB drive. last night was the first time i tried to >> use the drive on the macpcc. >> >> Dec 19 06:09:06 apbg4 /bsd: umass0 at uhub0 port 2 configuration 1 interface >> 0 "BUFFALO SSD-PEU3" >> rev 2.10/1.10 addr 2 >> Dec 19 06:09:06 apbg4 /bsd: umass0: using SCSI over Bulk-Only >> Dec 19 06:09:06 apbg4 /bsd: scsibus4 at umass0: 2 targets, initiator 0 >> Dec 19 06:09:06 apbg4 /bsd: sd0 at scsibus4 targ 1 lun 0: <BUFFALO, >> SSD-PEU3, PMAP> >> serial.04110210357B1BD7B099 >> Dec 19 06:09:06 apbg4 /bsd: sd0: 241216MB, 512 bytes/sector, 494010368 >> sectors >> >> the disklabel was not detected properly. this is the disklabel on macppc >> OpenBSD-current (#638: Mon Dec 16): >> >> # /dev/rsd0c: >> type: SCSI >> disk: SCSI disk >> label: SSD-PEU3 >> duid: 0000000000000000 >> flags: >> bytes/sector: 512 >> sectors/track: 63 >> tracks/cylinder: 255 >> sectors/cylinder: 16065 >> cylinders: 30750 >> total sectors: 494010368 >> boundstart: 0 >> boundend: 494010368 >> drivedata: 0 >> >> 16 partitions: >> # size offset fstype [fsize bsize cpg] >> c: 494010368 0 unused >> >> i tried both USB ports of the Powerbook5,8. same results. >> >> this is the **correct** disklabel on amd64 OpenBSD-current (#637: Sun Dec >> 15): >> >> # /dev/rsd1c: >> type: SCSI >> disk: SCSI disk >> label: SSD-PEU3 >> duid: 0000000000000000 >> flags: >> bytes/sector: 512 >> sectors/track: 63 >> tracks/cylinder: 255 >> sectors/cylinder: 16065 >> cylinders: 30750 >> total sectors: 494010368 >> boundstart: 0 >> boundend: 494010368 >> drivedata: 0 >> >> 16 partitions: >> # size offset fstype [fsize bsize cpg] >> c: 494010368 0 unused >> i: 494006272 2048 ext2fs >> >> partition can be mounted properly on amd64 Linux and OpenBSD. >> >> IIRC the drive was initialized / created on Linux. >> >> i have other USB drives (whole disk, msdos format) that work properly across >> all >> 3 machines. >> >> what am i missing here? looking forward to some pointers. >> >> yorosiku ~