The boot manager simply for everyone!  
Product
Order
Support
  Miscellaneous (3)
About us

Error messages on integrity checks

When reading the list of all partitions from all disks an automatic integrity check of all partitions is carried out. As a result of these checks the following warning or error messages could be displayed for individual partitions. Warnings are marked as W<nnn> and error messages as E<nnn>:

E001: MBR of disk <xx> is invalid: signature 0xAA55 missing.
Either the disk is empty or the MBR is corrupt.

E003: partition sector (LBA=<xx>) invalid: signature 0xAA55 missing.
Either the partition sector is corrupt or the address of the partition sector is wrong.

E004: boot sector (LBA=<xx>) invalid: signature 0xAA55 missing.
Either the boot sector is corrupt or the address of the boot sector is wrong.

E005: MBR of disk <xx> contains more than one extended partition.
The extended partition was created with a partition manager which violates the established standards. You should use a partition manager which sticks to the established standards.

E006: log. partition sector (LBA=<xx>) invalid: signature 0xAA55 missing.
Either the logical partition sector is corrupt or the address of the logical partition sector is wrong.

E007: log. partition sector (LBA=<xx>) invalid: found two partitions in partition sector.
The logical partition was created with a partition manager which violates the established standards. You should use a partition manager which sticks to the established standards.

E008: log. partition sector (LBA=<xx>) invalid: found two extended partitions in partition sector.
The logical partition was created with a partition manager which violates the established standards. You should use a partition manager which sticks to the established standards.

E009: log. partition not fully contained in extended partition.
The logical partition was created with a partition manager which violates the established standards. You should use a partition manager which sticks to the established standards.

E010: boot sector is true hidden, but ID=<xx> represents unhidden partition.
The corresponding partition was unhid incompletely. This error can be solved easily by hiding or unhiding the partition a second time.

E011: partitions overlap. There is a serious danger to lose data!!
Sooner or later this error will lead to data corruption. You must delete one of the two partitions to prevent the partitions from overwriting each others data. The respective partitions were created by an erroneous partition manager. You should use a partition manager which is working accurately.

E012: LBA values from partition table and effective values do not agree.
The computed LBA start position or the number of sectors of the partition do not agree with the values found in the partition table. The partition was created with a partition manager which violates the established standards. You should use a partition manager which sticks to the established standards.

E013: MBR of disk <xx> is invalid.
The field for active partitions contains invalid values. The MBR is corrupt or the disk does not contain a partition table.

E014: primary GPT table of disk <xx> is invalid.
The primary GPT table is defect. You can try to repair it.

E015: backup GPT table of disk <xx> is invalid.
The primary GPT table seems ok, only the backup GPT table is defect. This problem should be repairable.

E016: boot sector is true hidden, but attribute <xx> represents unhidden GPT partition.
The corresponding partition was unhid incompletely. This error can be solved easily by hiding or unhiding the partition a second time.

E017: CRC error in GPT table of disk <xx>.
The CRC checksums in the header of the GPT table are wrong. The other fields seem to be ok. This problem should be repairable.

E018: GPT header of disk <xx> is empty.
The header of the primary GPT table is completely empty. You can try to create a GPT partition, this should result in a valid header.

E019: GPT header of disk <xx> contains wrong signature.
The signature EFI PART in the header of the primary GPT table is wrong. It is unclear whether a GPT table should be present or whether the GPT table is corrupt. You can try to repair it.

E020: End of log. partition overlaps (<xx> MB) with next log. partition sector.
Repair: Shrink the logical partition by the overlap amount. Usually shrinking by a few MB is sufficient to solve the problem.

E021: log. partition sector (LBA=<xx>) invalid: first entry contains ext. partition.
The logical partition was created with a partition manager which violates the established standards. You should use a partition manager which sticks to the established standards.

E022: log. partition sector (LBA=<xx>) invalid: second entry does not contain ext. partition.
The logical partition was created with a partition manager which violates the established standards. You should use a partition manager which sticks to the established standards.

W001: NTFS format of partition is invalid.
The NTFS format of the partition seems to be corrupt.

W002: CHS values from partition table and effective values do not agree.
The alignment of partitions is relevant only for very old operating systems (e.g DOS). If you use current operating systems you can ignore this warning.

W003: partition does not start and end on cylinder boundaries.
The alignment of partitions is relevant only for very old operating systems (e.g DOS). If you use current operating systems you can ignore this warning.

W004: partition does not start on cylinder boundaries.
The alignment of partitions is relevant only for very old operating systems (e.g DOS). If you use current operating systems you can ignore this warning.

W005: partition does not end on cylinder boundaries.
The alignment of partitions is relevant only for very old operating systems (e.g DOS). If you use current operating systems you can ignore this warning.

W006: partition is not aligned on 1 MiB boundary.
The alignment of partitions is relevant only for very old operating systems (e.g DOS). If you use current operating systems and no SSD you can ignore this warning. If you use a SSD then the alignment on 1 MiB boundaries is recommended for performance reasons.

W007: true hiding uses outdated variant.
The partition was true hid with an old version of Boot-US. You need to upgrade to Boot-US 3.7.0 (or higher) for using the new variant of true hiding a partition.

W008: disk signature exists multiple times.
Internal disks should have different non-empty disk signatures, see glossary. Removable disks sometimes have empty disk signatures. This warning also occurs when an empty disk signature is present multiple times. In this case disabling the warnings in the configuration settings will disable the appearance of this warning. Only when cloning a disk such a collison should occur. In all other cases you should try to fix this collision.

The disk signature can be changed by the following command:

    bootusc set disksig drive=d id=<disk_signature>
Attention: Changing the disk signature can affect the bootability of the operating systems installed on the affected disk.

W009: disk unique GUID exists multiple times.
GPT disks should have unique disk GUIDs. Only when cloning a disk such a collison may occur. In all other cases you should try to fix this collision.

W010: partition unique GUID exists multiple times.
Partitions on GPT disks should have unique partition GUIDs. Only when cloning a disk such a collison may occur. In all other cases you should try to fix this collision.