Deployment Solution
450
Error Codes
Partition Error Messages
Error Message
Description
"Collision in partition-table .
."
"Collision with . . ."
Explanation:
More than one partition was defined for a
given partition table slot. It can mean one of two things:
Possible cause:
The on-disk partition-tables (including
partition tables in extended partitions) are corrupt.
The program was unable to merge an image file with the
local disk contents because both the image and the local disk
contain a partition definition that must reside in the same
slot.
"No partitions to process."
Explanation:
No partitions were found in the partition table.
The program has nothing to image (upload).
"Segment boundary error:
doesn't start on track
boundary."
"Invalid partition . . . "
Explanation:
An invalid partition definition exists.
Possible cause:
The invalid entry might be in the partition
table’s extended partitions.
Action:
Try running
ibmaster.exe
with the
-sz
or
-szf
switch.
"Error: No partition-table
segment to update."
"Error: Expected container
segment not found."
Explanation:
An extended partition was found that
contained no internal partition table, or contained no internal
definitions.
Action:
The invalid configuration can be resolved by
removing the invalid partition definition (using FDISK or
similar utility).
"Not enough free disk space
to accept image."
"Underlap error while placing
segment."
"Overlap error while placing
segment."
Explanation:
The local disk doesn't have enough free space
to accept the image being downloaded.
Possible cause:
The image may have more data than can fit
on the client computer hard drive, or the partition cannot be
resized to fit the drive.
"Collision at beginning of disk
while trying to place boot
record."
Explanation:
The program was unable to place the boot
record on the disk.
Possible cause:
Another partition may be defined to “cover”
the required space. This usually indicates corruption in the
target disk's partition table, because it is illegal for a partition
to occupy the space required by the boot record.
Action:
Run FDISK to remove all partitions, then reboot the
computer and run FDISK/MBR. Also check for viruses.