PK> WARNING : Device geometry and CHS-beginsector do not match LBA offset.
 PK>           Some possible causes are: Change in BIOS level or BIOS
settings,
 PK>           changed EIDE of SCSI adapter (or firmware) with different LBA
 PK>           mapping or an upgrade of DISK/SCSI device-drivers or filters
 PK>           (Fixpack ?).           
 PK>           Or the partition-table has been corrupted, possibly by a Virus.
 PK>           Id 02=D:
 PK> WARNING : Partition does not start on head-1 (cylinder boundary) Id 02=D: 

 PK> WARNING : Partition doesn't end on last head (cylinder boundary) Id 02=D: 

 PK> WARNING : Logical partition extends beyond extended-container Id 02=D:
 PK> WARNING : Extended partition extends beyond extended-container  Id 02=D:
 PK> WARNING : Extended partition extends beyond end of the disk
 PK>
 PK> [...]
 PK>
 PK> I now think I can figure out whats going on. About 5 months ago I
 PK> changed the SCSI HA from an Adaptec ISA card to an NEC based PCI
 PK> card. [...] It looks like the drive mapping schemes used by each HA 
 PK> do not exactly match, [...]
 PK>
 PK> I guess I will have to remove EVERYTHING off DRIVE 2, remove ALL
 PK> partitions on that drive, Re-boot and then re-allocate them again.
 PK> Hopefully this will fix the problem by updating the new controller
 PK> geometry info for ALL partitions. 

No you won't.  PARTLIST, in the OS/2 Command Line Utilities version 2.0, was
made for this very problem.  If you run it without any options, it will
display the raw partition information and a list of errors that it finds.  If
you run it with the /FIX option it will adjust the CHS start/end information
for each partition to match the logical sector start/offset information,
according to the current reported geometry of the drive.

PARTLIST is non-destructive, inasmuch as it doesn't require you to erase and
re-create partitions.  The only thing that it alters is the contents of the
partition table, specifically the CHS fields.  Nontheless, run PARTLIST
without the /FIX option to see what errors it *would* fix, and have a look at
them, before running it with the /FIX option to actually fix them.

 ¯ JdeBP ®

--- FleetStreet 1.22 NR
138/2
397/1