Partitionmagic error code

The error message and possible solution of partition magic are listed behind by number. The information is also divided into groups according to the error category.

1. Other errors (3-38)

(1) #3 insufficient memory
This error may occur when you adjust the size, move or copy a very large partition (60 GB), or process a small partition in the DOS load of emm386.
Emm386 limits the amount of memory that a program can access. To solve this problem, modify the config. SYS file and add comments to the line emm386.

TIPS:
In the top 640 KB (traditional Memory) Of the computer address space, the DOS version of partitionmagic executable file requires at least 585 KB of memory and 8 MB of total memory to be executed.
In this case, we may need to reboot to A: prompt symbol, enter lock_c:, and execute partitionmagic from the rescue disk to solve this problem.

(2) #8 unable to configure/cancel configuring DoS real-mode memory

When the DOS version of partitionmagic executable file is executed under DOS, Windows 3.x, Windows 95, and Windows 98, part of the memory needs to be occupied in the first 1 MB of the Computer address space (partitionmagic uses the DOS extension ). If you do not have enough available memory, partitionmagic cannot access the hard disk. For solutions, see the DOS manual. You only need to release the memory to execute partitionmagic in DOS.

(3) #27 the disk cannot be locked

In a multi-task operating system, such as Windows 95, partitionmagic must first lock the partition to safely modify its content. If another handler is using a file on the hard disk, partitionmagic cannot lock the partition.

(4) #29 unable to lock the locked Disk

Make sure that the partition you want to modify is not on the locked hard disk.

(5) #34 the beta version has expired the trial period

Powerquest sometimes releases the beta and trial versions of partitionmagic. These two versions are not as secure as official releases, so powerquest will set an expiration date in these versions. After a pre-determined test period, the Beta or trial version will no longer be available.

Ii. Disk access error (40-56)

An error ranging from 40 to 56 indicates that the system cannot access the disk, which is usually caused by hardware problems. Some problems may be easily solved, and some problems may have to be solved by replacing the hard disk.
Partitionmagic tries its best to detect major errors before making any changes so that you can back up data before changing the hard disk.

(1) #45. CRC errors in Data

When partitionmagic or any other program reads information from the hard disk, it first checks the CRC information contained in each sector (cyclic check. If the program performs a CRC Test
However, if the result is different from the value stored in the slice, a CRC error occurs. This usually
There are two meanings:
★The file being read is damaged due to some factors.
★A part of the stored file is damaged, causing damage to that part of the file.
The solution is to perform a surface test and mark all damaged sectors as damaged,
Then re-install the relevant software to ensure that the files on the system are not damaged. You can also try
Run partitionmagic with the/IRE parameter.

(2) # sector not found in 48

This error may be reported when the system cannot read or write data to a specific sector. There are many reasons for this error. If you encounter this error, make sure that the BiOS supports the operating system and the hard disk on the system. At the same time, perform a thorough Scandisk for the disk to avoid writing data to damaged sectors.

(3) #49 write errors #50 read errors

Partitionmagic cannot write/read a specific sector on the hard disk. Possible causes include:
★If your computer beep or a black box is displayed in the center of the screen, you have enabled virus protection in the computer BIOS. Disable virus or boot sector protection in Bois.
★The anti-virus application (possibly a TSR or DLL program) is in use. Disable anti-virus applications before using partitionmagic.
★There are damaged sectors on the hard disk (this problem usually only occurs on the old hard disk ). Run Scandisk to scan the hard disk surface and check whether any damaged sector exists. If there are damaged sectors on the hard disk, we recommend that you replace the hard disk.
★You have used PC-tools to set disk ing. Disable disk ing.

3. Other errors

(1) #70 windows deleted

If you are using Windows 3.x, you must create a partitionmagic rescue disk and execute the DOS version of partitionmagic.

(2) #89 ez-drive is detected on the disk, but ez-drive is not executed.

(3) #90 ez-drive is detected on the disk, but ez-drive is damaged.

(4) #91 "disk administrator" is detected on the disk, but "disk administrator" is not executed.

These errors are the "first Head" errors. You can solve these problems with the help of the powerquest Technical Support Department. Before contacting the Technical Support Department, enter the following command in the DOS prompt: wrprog/bak> X: head1.dat, where X refers to a disk on the computer. The wrprog.exe file can be found in the utility/DOS folder in the powerquest product folder.
(5) #98 Windows 2000 sleeping
(6) #99 Windows Me sleeping
Sleep saves the system's Ram to a file, and then uses advanced power management to shut down the system. Then, when the computer is awakened, it will read the Sleep file into RAM and continue executing from where it stops before hibernation. The sleep system assumes that the system remains in the same state when it is awakened. Any changes made to system hardware (including disks and disk partitions) may result in unexpected results. To avoid this error, shut down the computer as usual and restart the computer.

4. Partition Table error (100-199)

Error in the range from 100 to 199 is a partition table error.

(1) #100 Partition Table Corruption

The primary Boot Record (MBR) can contain at most one extended partition, and each extended Partition Boot Record (epbr) can contain at most one link pointing to another epbr. This error occurs when the Partition Table violates the preceding rules. At this time, we must re-create a partition table without errors to solve this problem.

(2) # No sector in partition 104

All partitions should contain sectors. Before using partitionmagic, delete the slice.

(3) #105 partitions start with the wrong Boundary

The hard disk partition table contains an error value. Partitionmagic expected partition should start and end in the correct column boundary. If not, the disk may be partially damaged. In this case, if partitionmagic makes any modification, data may be lost. Therefore, partitionmagic rejects recognition of any partition on the hard disk.

(4) #106 The partition does not start from the first sector. See Error #105.

(5) #107 the partition starts after the end of the disk. If the partition error is extended to the end of the hard disk object, this error occurs. This problem may also occur if the hard disk has been used on different computers, used with Different Hard Disk controllers, or has changed the BIOS settings.

(6) # partition does not end at the end of the column. See Error #108.

(7) #109 When the partition ends after the end of the disk, see Error #107.

(8) # The number of partitions in the 110 Partition Table is inconsistent. The hard disk partition table contains two inconsistent hard disk sectors. If the hard disk is used by both dos and another operating system, this error is very serious. Because dos uses one of the descriptions, and another operating system may use another description, data may be lost once the partition is almost full.

(9) #111 an extended Partition Boot Record (epbr) is the sector of the hard disk that contains the Partition Table outside the extended partition.

The epbr Partition Table is quite special because it usually has only two valid items: one for logical partitions, and the other for the indication pointing to the next epbr. According to the standard, the project in the logical partition is the first project, and the second project is the instruction pointing to the next epbr. The third and fourth projects are not used. For some utilities (such as IBM Boot manager), the order of these projects is very important because these utilities will expect the first project to be a logical project, the second project directs to the next epbr. If partitionmagic detects that the epbr project is not in order, you will be prompted to correct this error. If you choose to correct this error, partitionmagic will automatically re-adjust the order of the epbr project.

(10) #112 When a logical partition ends outside the extended partition, see Error #111.

(11) #113 partition overlapping hard disk partition tables contain incorrect values.

If data partitions overlap, writing data to one partition may damage the data in another partition. This error is sometimes caused by the OS/2 fdisk error. If the extended partitions still have available space, the OS/2 fdisk program will allow you to create a primary partition that overlaps the extended partitions. Then, a logical partition is created in the space occupied by the primary overlapping partitions.
If the primary partition overlaps the end of the extended partition but does not overlap any logical partition in the extended partition, this problem can be solved by correcting the partition table. Only qualified personnel can try this repair! Incorrect correction may damage all data on the hard disk!

(12) #116 The Beginning of the partition table is inconsistent with the start position. The hard disk partition table contains two different descriptions of the Start sector of the partition.

This error occurs if the hard disk specification reported by the operating system is different from the specification used when writing the partition table. Possible causes include: (1) different operating systems (such as DOS and OS/2) report different hard disk specifications; (2) the driver loaded when the disk is started is different from the driver loaded when the hard disk is started. (3) Upgrade the operating system (for example, upgrade from OS/2 2.x to OS/2)
Warp) causes different drivers to be used; (4) the hard disk or hard disk controller has been changed; (5) the BIOS has been upgraded; (6) the bios lba settings have been changed; (7) if the Partition Table virus exists on the hard disk, we can use a virus scanner to remove the Partition Table virus. In addition, if the number of heads or the number of sectors of each track has changed after the first partition is created, data may also be lost.

(13) #117 If the disk drive character of the partition cannot be identified under OS/2, partitionmagic must be able to identify the disk drive character of each partition before modification. OS/2 cannot identify the disk drive characters in each partition for many reasons. For example, a driver on the system may change the default disk drive character, or your partition may have no serial number.
This error may also occur when you execute partitionmagic in windows. The solution is to execute partitionmagic from DoS or from MS-DOS mode (in Windows 95 or Windows 98 ). When you execute partitionmagic from DoS or from MS-DOS mode, you do not need to find disk drive characters for each partition. Therefore, if this error message is the only problem, partitionmagic can be executed smoothly.

(14) #120 incompatible Logical Disk chains

In some operating systems, this error occurs if the logical partition is not linked in the expected sequence. Dos, OS/2, Windows 95, Windows 98, and Windows NT require logical partitions to be linked in ascending order. Other operating systems do not have this requirement. For example, in some versions of Linux fdisk utilities, they are linked together in the order of logical partitions. This error message is very dangerous. In this case, using DOS fdisk may cause loss of one or more partitions.
In this case, you can back up data and create a new partition. Of course, you may need to use the same partition program when creating a partition before deleting these partitions. In addition, we recommend that you use dos fdisk or partitionmagic to create a new partition for powerquest.

(15) #121 unable to read the first sector of the hard disk

The first sector (magnetic column 0, head 0, and sector 1) of the hard disk contains the primary Boot Record (MBR) and the primary partition table. An error occurred while reading the first sector of partitionmagic. The hard disk cannot be changed. To solve this error, see Error #50.

(16) #122 find the damaged sector in the current or new partition area. The partition cannot be moved safely because there are damaged sectors in the new or current partition area. When you see this error message, the mobile work has been terminated before any damage is caused. Try to move the partition to another location. Before proceeding, perform Scandisk or chkdsk/F for surface scanning. If the disk contains damaged fan sectors, we recommend that you replace the hard disk.

(17) #140 find overlapping partitions, and you cannot cancel deleting partitions. Find two or more deleted file systems in the unconfigured space. However, the space occupied by each file system is also the space occupied by other file systems. No split slice can be deleted.