| | DisplayName | Description | ID | Target | Category | Enabled | Instance Name | Counter Name | Frequency | Event_ID | Event Source | Alert Generate | Alert Severity | Alert Priority | Remotable | Event Log |
|---|
 | Thread allocation failed! [DDM_1] | DDM cannot control this device correctly because there is a lack of memory. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_1 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 1 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx: Configuration error. Mirror size less used disk space. Data loss possible! [DDM_16] | The size of the disk, to which the data of the other disk of the DW group should be copied (Mirror) is less than all partitions listed in the partition-table of the source disk. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_16 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 16 | ddm | True | Warning | Normal | True | System |
| MP PxPxTxLx: failed and was disabled! [DDM_18] | DDM has detected a failure on this path. The path is not usable anymore. Recovering from error will be logged by event id 4354. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_18 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 18 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx failed! [DDM_2] | DDM has discovered a failure at the device PxPxTxLx. The status of the device is set to error, and no data is written to this device anymore. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_2 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 2 | ddm | True | Warning | Normal | True | System |
| MP PxPxTxLx: Memory allocation problem! [DDM_21] | DDM cannot control this device correctly because there is a lack of memory. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_21 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 21 | ddm | True | Warning | Normal | True | System |
| MP PxPxTxLx: Device was removed / path gone! This path was removed by Plug and Play functions of the system, after an error was detected. [DDM_25] | This event may occur after event id 18, but may also appear without any other id. If the path reappears, this will be logged by event id 4354. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_25 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 25 | ddm | True | Warning | Normal | True | System |
| DDM PxPxTxLx: Device had signature that was already found for another disk! [DDM_26] | All disks should have signatures (stored in the Master Boot Record (MBR)), which are unique to the system. Exception: The two pieces (or two disks) of a DuplexWrite group are identical and have the same signature. When this error is logged, DDM has found a disk which has the same signature as another disk in the system, and which are not members of a DuplexWrite group. That disk will be disabled and not be accessible. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_26 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 26 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx: Memory allocation problem! [DDM_3] | DDM cannot control this device correctly because there is a lack of memory. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_3 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 3 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx: Signatures on piece0 and piece1 are different but cannot be restored. [DDM_4368] | This is a serious problem which cannot be fixed by the driver. It is necessary to repair signatures on both pieces by hand (i.e. with ddmutil). | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_4368 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 4368 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx: Second try to write FastRecoverArray while both pieces are online! [DDM_4369] | There was an error keeping track of the changes written to disk. Delta Recover is disabled. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_4369 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 4369 | ddm | True | Error | High | True | System |
| DW PxPxTxLx: Someone has written a wrong Signature to MBR! [DDM_4370] | This could destroy a cluster, a cluster resource or a Duplex Write group! | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_4370 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 4370 | ddm | True | Error | High | True | System |
| DW PxPxTxLx: Piece was removed. [DDM_4371] | Duplex Write piece was removed by Plug and Play event. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_4371 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 4371 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx: The other piece is missing! [DDM_4373] | Logged only if 'StrictChecking' is enabled. In this case, IO to a DW group is only possible if both pieces of a DW group are accessible - if not this event entry is logged. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_4373 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 4373 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx: The array for Delta Recover Information is already initialized. [DDM_4374] | FastRecoverEnabled is already set! This might be an internal error. Contact your local Fujitsu Helpdesk. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_4374 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 4374 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx: DWLun for this piece is not set. [DDM_4376] | In data structure DeviceExtension is flag DWLun not set. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_4376 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 4376 | ddm | True | Warning | Normal | True | System |
| Fault tolerance for the RootDisk is not warranted anymore. [DDM_4384] | Fault tolerance for the RootDisk is not warranted anymore. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_4384 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 4384 | ddm | True | Error | High | True | System |
| DW PxPxTxLx: DuplexWrite has discovered a possible split brain situation, caused by a broken fibre channel connection. [DDM_4385] | In this situation, both nodes have access to one piece of this DW-Group. To avoid data corruption, this may occur, if the node, which did not own this disk, does a failover of it, this piece was set to DISABLED. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_4385 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 4385 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx: The second piece of this DW-Group is more recent, but it is not set to online, because there were write-commands sent to the first piece. [DDM_4387] | This event log may occur, if a piece of a DW-group is returned to its original system after it was attached to another system, which also runs with DDM. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_4387 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 4387 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx: A command was retried after failure. [DDM_4388] | This event log may occur, if an access to a device in Failover Cluster (Windows Server 2008, Persistent Reservation) failed. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_4388 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 4388 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx: A DuplexWrite RootDisk mirror (system mirror) was detected. Therefore the DuplexDataManager support for Microsoft Failover Clustering is switched off. [DDM_4389] | This event log may occur, if the Microsoft Failover Clustering feature is enabled and a DuplexWrite RootDisk mirror (system mirror) is configured. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_4389 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 4389 | ddm | True | Warning | Normal | True | System |
| DuplexDataManager Service could not initialize. [DDM_5122] | Check for a correct installation. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5122 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5122 | ddm | True | Error | High | True | System |
| No NVRAM or BIOS access. [DDM_5123] | DuplexWrite cannot support an automatic reboot in case of system/boot disk failure. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5123 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5123 | ddm | True | Error | High | True | System |
| Consistency Check (SCSI address of both pieces) READ at block number failed. [DDM_5125] | The data for comparing will be read from both pieces via SCSI PassThrough commands. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5125 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5125 | ddm | True | Error | High | True | System |
| Consistency Check (SCSI addresses of both pieces) failed. The data is different at block number. [DDM_5126] | DDM SERVICE CONSISTENCY CHECK INTERRUPT | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5126 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5126 | ddm | True | Error | High | True | System |
| Consistency Check (SCSI addresses of both pieces) failed (no normal termination). [DDM_5127] | DDM SERVICE CONSISTENCY CHECK CATCH | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5127 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5127 | ddm | True | Error | High | True | System |
| Consistency Check (SCSI addresses of both pieces) canceled at block number. There are different numbers of blocks found! [DDM_5129] | The consistency check is canceled by user. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5129 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5129 | ddm | True | Error | High | True | System |
| Consistency Check (SCSI addresses of both pieces) finished with different blocks found. [DDM_5131] | Consistency Check (SCSI addresses of both pieces) finished with different blocks found. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5131 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5131 | ddm | True | Error | High | True | System |
| xxx. [DDM_5132] | Only used for development or debugging case! | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5132 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5132 | ddm | True | Error | High | True | System |
| Found inconsistent signatures in DuplexWrite group www:xxx, yyy:zzz. [DDM_5133] | Please check if anyone changed the disk signature in the master boot record (MBR). Use ddmutil to fix this problem. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5133 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5133 | ddm | True | Error | High | True | System |
| Fatal error caught in a routine. [DDM_5135] | DDM SERVICE FATAL ERROR | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5135 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5135 | ddm | True | Error | High | True | System |
| CloneData (port/path/target/lun) failed (no normal termination). [DDM_5138] | Please restart DuplexDataManager service. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5138 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5138 | ddm | True | Error | High | True | System |
| CloneData (port/path/target/lun of device) READ at block number failed. [DDM_5139] | CloneData (4/0/2/0) READ at block number 254378 failed. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5139 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5139 | ddm | True | Error | High | True | System |
| CloneData (data) WRITE at block number failed. [DDM_5140] | CloneData (4/0/2/0) WRITE at block number 254378 failed. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5140 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5140 | ddm | True | Error | High | True | System |
| CloneData (port/path/target/lun). [DDM_5144] | Terminate CloneData because status of source piece changed | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5144 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5144 | ddm | True | Error | High | True | System |
| Manage AutoAdjust xxx: Unexpected storage access path configuration (ctrl/port: yyy). [DDM_5146] | The feature AutoAdjust not released. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5146 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 5146 | ddm | True | Warning | Normal | True | System |
| Manage AutoAdjust xxx: Different access paths to storage -> activate yyy. [DDM_5147] | The feature AutoAdjust not released. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5147 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 5147 | ddm | True | Warning | Normal | True | System |
| Due starting the DuplexDataManager service the process ddmwatch.exe is still running / hanging. [DDM_5151] | DDM SERVICE DDMWATCH RUNNING | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5151 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5151 | ddm | True | Error | High | True | System |
| MultiPath configuration changed. The path is missing. [DDM_5152] | DDM SERVICE MONITOR | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5152 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5152 | ddm | True | Error | High | True | System |
| DuplexDataManager Service. [DDM_5156] | DDM_SERVICE MPIO WARNING | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5156 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 5156 | ddm | True | Warning | Normal | True | System |
| DuplexDataManager Service [DDM_5157] | DDM SERVICE MPIO ERROR | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5157 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5157 | ddm | True | Error | High | True | System |
| The Virtual Disk Service (VDS) is active. The Storage Manager for SANs may produce VDS error entries in the system event log. [DDM_5158] | DDM SERVICE VDS ACTIVE | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5158 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 5158 | ddm | True | Warning | Normal | True | System |
| Found inconsistent Disk GUIDs in DuplexWrite group xxx. [DDM_5162] | Please check if anyone changed the Disk GUID in the GPT partition table. Use ddmutil to fix this problem. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5162 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5162 | ddm | True | Error | High | True | System |
| The MultiPath configuration changed. The disk identification is different: xxx. If the current configuration is correct, please acknowledge this configuration via the MMC snap-in to suppress this error message. [DDM_5163] | This error event only generated for acknowledged (stored) MultiPath configurations, where no disk signature available / accessible at the acknowledge time. Please check the MultiPath configuration for missing paths and devices. If the current configuration is correct, please acknowledge this configuration via the MMC snap-in to suppress this error message. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5163 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5163 | ddm | True | Error | High | True | System |
| The MultiPath configuration changed. Path(s) missing to disk: xxx. If the current configuration is correct, please acknowledge this configuration via the MMC snap-in to suppress this error message. [DDM_5164] | Please check the MultiPath configuration for missing paths and devices. If the current configuration is correct, please acknowledge this configuration via the MMC snap-in to suppress this error message. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5164 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5164 | ddm | True | Error | High | True | System |
| The MultiPath configuration changed. The disk: xxx is missing. If the current configuration is correct, please acknowledge this configuration via the MMC snap-in to suppress this error message. [DDM_5165] | Please check the MultiPath configuration for missing paths and devices. If the current configuration is correct, please acknowledge this configuration via the MMC snap-in to suppress this error message. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5165 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5165 | ddm | True | Error | High | True | System |
| The MultiPath configuration changed. There are xxx disk(s) missing. If the current configuration is correct, please acknowledge this configuration via the MMC snap-in to suppress this error message. [DDM_5166] | Please check the MultiPath configuration for missing paths and devices. If the current configuration is correct, please acknowledge this configuration via the MMC snap-in to suppress this error message. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5166 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5166 | ddm | True | Error | High | True | System |
| Failed to start x10sureIS configuration script: xxx - yyy [DDM_5168] | The DDM service calls the x10sureIS script to manage the DuplexWrite groups. Check if script is available and accessible. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5168 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5168 | ddm | True | Error | High | True | System |
| No any xxx disk for x10sureIS configuration found. [DDM_5169] | The DDM service does not find x10sureIS supported disks. Check iSCSI and disk configuration. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5169 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5169 | ddm | True | Error | High | True | System |
| In a Microsoft Failover Cluster environment a DuplexWrite RootDisk (system mirror) is not supported. [DDM_5171] | DuplexDataManager does support RootDisk (system mirror) and Microsoft Failover Cluster configurations, but not both together in a configuration. This restriction is only valid for Windows Server 2008 and newer. Please determine one configuration. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5171 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5171 | ddm | True | Error | High | True | System |
| Failed to remove the Boot Flag on the degraded RootDisk (system mirror) piece xxx. [DDM_5174] | To prevent a boot inconsistent RootDisk piece, the Boot Flag is removed. The Boot Flag will be set to active when the recover is finished. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5174 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 5174 | ddm | True | Warning | Normal | True | System |
| Failed to update the Boot Flag on the online RootDisk (system mirror) piece xxx. [DDM_5176] | To prevent a boot inconsistent RootDisk piece, the Boot Flag is removed. The Boot Flag will be set to active when the recover is finished. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5176 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 5176 | ddm | True | Warning | Normal | True | System |
| Any automatic fail-safe configuration stopped. Found a newer (most recent) operating system on disk xxx. [DDM_5178] | In an x10sureIS environment a DuplexWrite group was found which holds an operating system which is most recent. If the current booted operating system (RootDisk) should further be used, please delete the newer DuplexWrite group using the DuplexDataManager MMC snap-in. If the newer (most recent) operating system should be used, please shutdown the operating system and reconfigure the boot settings. (Additional a message box is displayed on all active terminals.) | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5178 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5178 | ddm | True | Error | High | True | System |
| Any automatic fail-safe configuration stopped. Found a newer (most recent) DuplexWrite data group xxx. [DDM_5179] | In an x10sureIS environment a DuplexWrite group was found which holds the newer data lun which is most recent. If the current used DuplexWrite data group should further be used, please delete the newer DuplexWrite group using the DuplexDataManager MMC snap-in. If the newer (most recent) DuplexWrite data group should be used, please stop all I/O to the older one, delete this group, adapt the drive letters and start I/O. (Additional a message box is displayed on all active terminals.) | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5179 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5179 | ddm | True | Error | High | True | System |
| The protection (change disk signature) of the xxx against the error/missing piece failed. [DDM_5180] |
x10sureIS environment:
1. Change the disk signature of the RootDisk.
2. RootDisk: Update the boot menu (BCD).
One of these actions failed.
The operation system may not be bootable!
Please open a command box and type the following three commands:
"bcdedit.exe /set {current} device partition=c:"
"bcdedit.exe /set {current} osdevice partition=c:"
"bcdedit.exe /set {bootmgr} device partition=c:"
| Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5180 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5180 | ddm | True | Error | High | True | System |
| An invalid configuration found. Found a DuplexWrite partner group xxx with 2 pieces. [DDM_5181] | In an x10sureIS environment found another DuplexWrite group with a same COD key with 2 pieces. Please the check DuplexWrite configuration. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5181 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5181 | ddm | True | Error | High | True | System |
| Delete of the xxx failed. In an x10sureIS environment one piece of the mirror is failed or missing. Therefore this piece ... [DDM_5184] | In an x10sureIS environment one piece of the mirror is failed or missing. Therefore this piece has to be deleted and the disk signature of the remaining piece has to be changed. This saves the operating system for unauthorized access to the error or missing piece. Please the check the configuration. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5184 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5184 | ddm | True | Error | High | True | System |
| In an x10sureIS installation the DuplexWrite parameter 'Autostart Recover' should be enabled. [DDM_5186] | Please enable DuplexWrite 'Autostart Recover'. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5186 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 5186 | ddm | True | Warning | Normal | True | System |
| The update of the bootstat.dat files failed. [DDM_5189] | In a RootDisk configuration the DDM service updates the bootstat.dat file(s). Please check your RootDisk configuration. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5189 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 5189 | ddm | True | Warning | Normal | True | System |
| x10sure DuplexWrite Data Group Protection not supported! [DDM_5203] | In an x10sure environment the identity (Production Node or Control Node) is needed to protect the DuplexWrite data groups in a failover case. Please the check the configuration. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5203 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 5203 | ddm | True | Warning | Normal | True | System |
| Delete missing piece of partner group xxx failed. This DuplexWrite group should be prepared (deleted) for using as mirror for the DuplexWrite group yyy. [DDM_5205] | Please the check the configuration. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5205 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5205 | ddm | True | Error | High | True | System |
| Delete missing piece of partner group xxx failed. This DuplexWrite group should be prepared (deleted) for using as mirror for the DuplexWrite group yyy. [DDM_5206] | Please the check the configuration. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5206 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5206 | ddm | True | Error | High | True | System |
| Any automatic fail-safe configuration stopped. The Boot Configuration Data (BCD) is not accessible. For the x10sureIS failover processing it is mandatory to access the BCD data. Please contact ... [DDM_5207] | Please the check the configuration or contact system operator immediately to solve this problem. (Additional a message box is displayed on all active terminals.) | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5207 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5207 | ddm | True | Error | High | True | System |
| Any automatic fail-safe configuration stopped. The operating system is running on the disk xxx. The future mirror disk belongs to the DuplexWrite group yyy. Please solve this inconsistence. [DDM_5209] | Please use the DuplexDataManager MMC snap-in to solve this inconsistence. At least restart the DuplexDataManager service. (Additional a message box is displayed on all active terminals.) | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5209 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5209 | ddm | True | Error | High | True | System |
| Any automatic fail-safe configuration stopped. The operating system is running on the disk xxx. Found the DuplexWrite group yyy on other port. Please solve this inconsistence. [DDM_5210] | Please use the DuplexDataManager MMC snap-in to solve this inconsistence. At least restart the DuplexDataManager service. (Additional a message box is displayed on all active terminals.) | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5210 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5210 | ddm | True | Error | High | True | System |
| Any automatic fail-safe configuration stopped. An invalid x10sure environment found. [DDM_5211] | Please check the x10sureIS environment. (Additional a message box is displayed on all active terminals.) | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5211 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5211 | ddm | True | Error | High | True | System |
| The DuplexWrite error piece xxx of the DuplexWrite group yyy is the most recent piece. Nevertheless it was set to error, because write commands were sent to the other piece, before the more recent piece appeared. If ... [DDM_5212] |
The data on the more recent piece should be overwritten:
Disable the error piece and start recover.
The data on the more recent piece should be conserved:
If it is a system disk, the system has to be rebooted, while the first piece with older data must be disconnected. (Unmap LUN or change BIOS settings etc.) If it is a data disk, you can either reboot with disconnected older piece (see above) or follow these steps: Stop applications accessing this disk - remove drive letters - disable the online piece - set the error piece to online - start recover - reassign drive letters - start applications.
(Additional a message box is displayed on all active terminals.)
| Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5212 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 5212 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx: No or invalid on disk configuration found! [DDM_6] | DDM cannot find the configuration data on this disk. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_6 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 6 | ddm | True | Warning | Normal | True | System |
| DuplexDataManager MPIO event watch process - Fatal error caught in routine. [DDM_6144] | DDM WATCH PROCESS FATAL ERROR | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_6144 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 6144 | ddm | True | Error | High | True | System |
| DW PxPxTxLx: Too many SCSI ports in system! [DDM_7] | DDM supports up to 256 ports. This number is reached now. DDM will not work in this case. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_7 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 7 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx: Recover aborted! [DDM_8] | While a DuplexWrite group (DW group) was recovering, this recover process was aborted. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_8 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 8 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx: Forced to be ONLINE! [DDM_9] | This piece of a DW-Group was set from a non-online state (error, disabled, recover) to online by the driver. This may happen, if the other piece was not online too. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_9 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 9 | ddm | True | Warning | Normal | True | System |
Home