B1FN ENZ0(02) PRIMEQUEST. System Disk Mirror for Windows User's Guide V1.0

Transcription

1 B1FN ENZ0(02) PRIMEQUEST System Disk Mirror for Windows User's Guide V1.0

2

3 Preface Purpose of This Manual This manual describes the functions and usage of PRIMEQUEST System Disk Mirror for Windows (referred to as PSDM hereinafter). Intended Readers This manual is devoted to PSDM users. Organization of Contents of This Manual This manual consists of three chapters, two appendices, and a glossary. The contents are as follows: Headers Chapter 1 Functions Chapter 2 Setup Chapter 3 Operation Appendix A Command Reference Appendix B Messages Appendix C Notes Glossary Contents Describes the functions and features of PSDM. Explains how to set and unset the mirroring configuration. Explains how to use and maintain PSDM. Describes the PSDM commands. Describes PSDM messages and the causes of errors and explains what to do in response to the messages. Describes cautions for use of PSDM. Explains terms used in this manual. Other Reference Manuals Refer to the following manual as needed. PRIMEQUEST SystemcastWizard Lite User s Guide PRIMEQUEST 500/400 Series Installation Manual Manual Printing To print manual pages, use the PDF manual. To refer to or print PDF files, Adobe Reader is required, and prepare Adobe Reader 5.0 or higher. i

4 Preface Symbols Used in This Manual The following conventions are used in this manual: Main points are explained. Items that require attention are explained. Useful information is given. Manual names and sections of this manual you should refer to are given. Abbreviations In this manual, the following abbreviations are used. Abbreviations PSA PSDM ScWL Formal names PRIMEQUEST Server Agent PRIMEQUEST System Disk Mirror for Windows SystemcastWizard Lite Export Control This manual shall be exported or provided only under control of the "Foreign Exchange and Foreign Trade Control Law" and US export control-related regulations. Trademark Acknowledgements Microsoft, Windows, and other Microsoft product names are registered trademarks of Microsoft Corporation in the United States and/or other countries. Other product and brand names are trademarks or registered trademarks of their respective owners. February 2008 ii

5 Preface Notice No part of this manual may be reproduced without permission. This manual is subject to change without advance notice. All Rights Reserved, Copyright(C) Fujitsu LIMITED 2008 iii

6 Preface Contents Preface... i Chapter1 Functions Features Configurations Operations Mirror Disk Status Mirror Group States...10 Chapter 2 Setup Mirroring Unmirroring...19 Chapter 3 Operation Disk Swap Preparing for Disk Swap (Removing Disks) Swapping Disks Restoring Disks after Swapping (Adding Disks) Boot Disk Backup and Restore Backing Up the Boot Disk Restoring the Boot Disk Data Disk Backup and Restore Operation Monitoring Collecting Information for Troubleshooting Starting/Stopping the Service...33 Appendix A Command Reference A.1 sdxsysdisk - Mirroring and unmirroring...35 A.2 sdxinfo - Disk configuration and status viewing...39 A.3 sdxsnap - Collection of information for troubleshooting...47 Appendix B Messages B.1 Driver Messages...49 B.1.1 Driver Error Messages (20XXX)...50 B.1.2 Driver Warning Messages (22XXX)...53 B.1.3 Driver Information Message (24XXX)...60 iv

7 Preface B.2 Service Messages...63 B.2.1 Service Stop Messages (40XXX)...64 B.2.2 Service Error Messages (42XXX)...66 B.2.3 Service Warning Messages (44XXX)...72 B.2.4 Service Information Messages (46XXX)...76 B.3 Command Messages...79 B.3.1 Command Error Messages (60XXX)...81 B.3.2 Command Warning Messages (62XXX)...94 B.3.3 Command Information Messages (64XXX)...95 B.3.4 Command Help Messages (65XXX)...96 Appendix C Notes C.1 System Design/Implementation...99 C.2 Operation/Maintenance C.3 Troubleshooting Glossary v

8 Preface vi

9 Chapter 1 Functions 1.1 Features PRIMEQUEST System Disk Mirror for Windows (PSDM) is software which improves the availability of the PRIMEQUEST system by mirroring the system disk where Windows is installed. The mirroring function replicates the data of one disk onto other separate disks in real time. This way if any one of the disks fails, the system can continuously access the data on the disks functioning normally, and thus maintain system availability. If the master disk unexpectedly becomes unrecognizable for the OS during system operation, the service or system may stop operating. This is because information on the unrecognizable disk partition (such as C: or D:) is deleted automatically by the OS and the partition will be no longer accessible from the OS or applications. Even in this event, data is maintained on the disk in normal status, and operation can simply be resumed through system reboot. A disk may become unrecognizable for the OS, for example, if a disk path failure or power failure occurs or if the disk is removed accidentally. Unrecognizable disks are not indicated with the sdxinfo -P command. Figure 1_1: System disk mirroring 1

10 Chapter 1 Functions PSDM has the following features. Full-disk mirroring This software mirrors the entire system disk including the EFI System Partition (ESP) and the Microsoft Reserved Partition (MSR). EFI boot entry automatic update In the event that the system disk fails, the user can boot from one of the mirror disks. The EFI boot entry required for the booting is automatically created for each mirror disk when mirroring setup is completed. If the mirroring configuration or state is changed, the EFI boot entry will also be updated automatically. Figure 1_2: Boot disk mirroring 2

11 1.1 Features Just Resynchronization Mechanism (JRM) If a system failure occurs, the I/O process may be interrupted. Therefore, the data equivalence between the mirrored disks will no longer be guaranteed. To resynchronize the disks, data copying is automatically performed after the system is rebooted. The Just Resynchronization Mechanism (JRM) is a mechanism that speeds up this resynchronization. JRM realizes high-speed resynchronization by initiating the copy from the region that may be out-of-sync due to the failure instead of replicating the entire disk data. Figure 1_3: Just Resynchronization Mechanism (JRM) 3

12 Chapter 1 Functions Just resynchronization copying on the boot disk JRM does not function on the boot partition (usually C:). On this partition, full resynchronization copying will be performed after the reboot following the system failure. For example, if ESP, C: (boot partition), and D: exist on the boot disk, only out-of-sync regions are copied for ESP and D: but the entire partition is copied for C: in that event. Figure 1_4: Just resynchronization copying on the boot disk 1.2 Configurations This section describes components of mirroring. Mirror group The mirror group is a unit of disks to be mirrored. Mirror disks registered with a mirror group are mirrored one another. A mirror group is created when mirroring is set up and assigned a unique mirror group name, Groupn (the mirror group number n is 0 or 1). The mirror group to which the boot disk belongs is referred to as the boot group, and the one to which data disks belong, as the data group. 4

13 1.2 Configurations Mirror disk The disk registered with a mirror group is referred to as a mirror disk. The mirror disk is assigned a unique mirror disk name, Diskn (the mirror disk number n is 0, 1, 2, or 3). A mirror disk may be referred to as the master disk, the sub disk, or the read disk depending on its function in the mirror group. For these terms, see "Glossary" and "1.5 Mirror Group States." The mirror disk number is a unique number assigned to each mirror disk for identification. This number does not correspond to the one indicated with Windows Disk Management or the diskpart command. The number of mirror groups and mirror disks The maximum numbers of mirror disks and mirror groups are limited as follows. Table 1_1: The number of mirror groups and mirror disks Item Upper limit Mirror group count per system 2 Boot group count per system 1 Data group count per system 1 Mirror disk count per system 4 Mirror disk count per mirror group 2 Do not create more than one data group for one system. Reserved partition A disk partition that stores mirroring management information is referred to as the reserved partition. This partition is automatically created at the end of every disk when the disk is registered with a mirror group and it is deleted when the disk is removed from the mirror group. Its size is 256 MB. 5

14 Chapter 1 Functions Boot entry name For each disk that is registered with the mirror group of the boot disk and is in VALID status, a boot entry is created. The boot entry naming conventions are as follows. Master Boot Entry Name (MIRROR DISK Mirror Group Number Mirror Disk Number) Master Boot Entry Name : The boot entry name selected at system startup Mirror Group Number : The number postfixed to the boot disk s mirror group name Mirror Disk Number : The number postfixed to the name of a mirror disk that belongs to the boot disk s mirror group For example, if the system is booted from the master boot entry "Windows Server 2003, Enterprise Edition" and the boot disk mirroring configuration is set to mirror two disks named Disk2 and Disk3 in the mirror group named Group0, the master boot entry (Windows Server 2003, Enterprise Edition) is removed and the following boot entries are added. Windows Server 2003, Enterprise Edition (MIRROR DISK 0-2) Windows Server 2003, Enterprise Edition (MIRROR DISK 0-3) The master boot entry name can contain standard ASCII characters. The master boot entry OS friendly name must be set. 6

15 1.3 Operations 1.3 Operations This section provides a brief overview of mirroring operations. Mirror group creation Perform this operation to set the mirroring configuration. Figure 1_5: Mirror group creation For details on the procedures, see "2.1 Mirroring." Mirror disk removal Perform this operation to remove the disks to be replaced from the mirroring configuration before swapping mirror disks. After the mirror disk removal, the system will be rebooted automatically. Figure 1_6: Mirror disk removal For details on the procedures, see "3.1.1 Preparing for Disk Swap (Removing Disks)." 7

16 Chapter 1 Functions Mirror disk addition Perform this operation to add the new disks to the mirroring configuration after swapping disks. Figure 1_7: Mirror disk addition For details on the procedures, see "3.1.3 Restoring Disks after Swapping (Adding Disks)." Mirror group removal Perform this operation to unset the mirroring configuration. After the mirror group removal, the system will be rebooted automatically. Figure 1_8: Mirror group removal For details on the procedures, see "2.2 Unmirroring." The mirror group removal operation also removes disk partitions on disks except the read disk in the mirror group allowing only the read disk to maintain disk partitions and data. To keep disk partitions and data on a disk other than the read disk, remove the other disks from the mirror group and reboot the system before removing the mirror group. For more information on how to identify the read disk, see "1.5 Mirror Group States." 8

17 1.4 Mirror Disk Status 1.4 Mirror Disk Status The mirror disks will be in one of the following states. Table 1_2: Mirror disk status Status VALID INVALID COPY ERROR Description The data is valid. Data on VALID disks in the same mirror group is always synchronized. The data is invalid. Data on the disk in this status may no longer be synchronized with data on VALID disks in the same mirror group. Disks will be in INVALID status before synchronization copying is initiated or after it is canceled. The synchronization copying is a process to copy data from a VALID disk to other mirror disks in the mirror group in order to set up mirroring or to increase the multiplicity of the mirroring configuration. Synchronization copying is in process. To synchronize the data, data from a VALID disk is being copied. An error occurred. Disks in INVALID or ERROR status are no longer mirrored and become inaccessible. However, if all disks in a mirror group become INVALID or ERROR disks, the last ERROR disk can be accessed. Figure 1_9: Disk state transition 9

18 Chapter 1 Functions If the copying process is canceled, the copying will be restarted from the beginning next time. The copying process cannot take over the previous process if it is canceled once. Resynchronization copying is performed when the system is rebooted in one of the following situations to recover the mirroring state. INVALID mirror disks are found when the system is booted. The system is rebooted after it failed. In the resynchronization copying process performed when the system is booted, specific amount of data is copied every 50 milliseconds to reduce the load on the system. 1.5 Mirror Group States The typical mirror group states are as follows. The state before mirror group creation Before creating a mirror group, you must create partitions on the mirror source disk and remove all partitions from the mirror destination disk. Figure 1_10: Before mirror group creation 10

19 1.5 Mirror Group States The state after mirror group creation After a mirror group is created, synchronization copying from the mirror source disk to the mirror destination disk is performed, and the mirroring state of the disks is established when the copy is completed. The mirror source disk will be the master disk and also the read disk and the mirror destination disk will be the sub disk. Figure 1_11: After mirror group creation The state when booted from the mirror destination disk When the system is booted from the boot disk s mirror destination disk, the mirror destination disk will be the master disk and also the read disk and the mirror source disk will be the sub disk. Figure 1_12: When booted from the mirror destination disk 11

20 Chapter 1 Functions The state after sub disk I/O error occurrence If an I/O error occurs on the sub disk, the sub disk will be a non-mirrored disk as an ERROR disk. Figure 1_13: After sub disk I/O error occurrence The state after sub disk removal If the sub disk is removed from the mirror group, sub disk partitions are removed and the sub disk will be a non-mirrored disk. Figure 1_14: After sub disk removal 12

21 1.5 Mirror Group States The state after master disk I/O error occurrence If an I/O error occurs on the master disk, the sub disk will be the read disk and the master disk will be a non-mirrored disk as an ERROR disk. If the system is rebooted in this state, the sub disk will be the new master disk. Figure 1_15: After master disk I/O error occurrence 13

22 Chapter 1 Functions The state after master disk removal If the master disk is removed from the mirror group, the sub disk will be the read disk and the master disk will be a non-mirrored disk. In this event, the system will be rebooted automatically, and the previous master disk s partitions are removed. After the reboot, the sub disk will be the new master disk. Figure 1_16: After master disk removal The read disk The read disk is also the master disk under normal conditions. However, the sub disk will be the read disk: If an I/O error occurs on the master disk when the sub disk is VALID During the period before the system reboot after the master disk removal 14

23 Chapter 2 Setup 2.1 Mirroring This section explains how to set the mirroring configuration. To set up mirroring, you must be a user with administrator privileges (a user of the Administrators group). 1. Opening the command prompt Select [start]-[all Programs]-[Accessories]-[Command Prompt] to open Command Prompt. 2. Checking the mirrored disks Check the disk numbers, space, partition configuration of the mirror source and mirror destination disks. Disks to be mirrored must meet the following conditions. The disk is not a disk connected to a SAN. The disk partition table is in GPT format. The disk is a basic disk. At the end of the disk, there is contiguous free space for the reserved partition (which is a 256 MB disk partition that stores mirroring management information). The number of disk partitions on the mirror source disk is nine or less. Mirror source disk space and mirror destination disk space are equal. The mirror destination disk contains no partition. The mirror source disk and the mirror destination disk belong to the same I/O unit or the same expansion file unit. 15

24 Chapter 2 Setup To check the disk number, space, and partition configuration, use any one of the following methods. a) Windows "Disk Management" To use "Disk Management," select [start]-[control Panel]-[Administrative Tools]-[Computer Management]-[Disk Management]. b) The diskpart command s list disk command > diskpart DISKPART> list disk Disk ### Status Size Free Dyn Gpt Disk 0 Online 68 GB 256 MB * Disk 1 Online 68 GB 256 MB * c) The sdxinfo -P command Check the NAME field for the disk number, the BLOCKS field for the space, and the LOCATION field for the location. > sdxinfo -P OBJ NAME BLOCKS STATUS DKNAME LOCATION device * * IOU#0-HDD#0 device * * IOU#0-HDD#1 For details on the sdxinfo command, see "A.2 sdxinfo - Disk configuration and status viewing." 16

25 2.1 Mirroring 3. Setting up mirroring With the sdxsysdisk -M command, set up mirroring. Before performing this procedure, exit "Disk Management" or the diskpart command if it is active. Example: The mirror source disk number is 0 and the mirror destination disk number is 1. > sdxsysdisk -M -p 0:keep,1:undef Specify ":keep" after the mirror source disk number and ":undef" after the mirror destination disk number. For details on the sdxsysdisk command, see "A.1 sdxsysdisk - Mirroring and unmirroring." 17

26 Chapter 2 Setup 4. Confirming the mirroring state If mirroring is set up, a mirror group is created and the mirror source disk and the mirror destination disk are registered with the mirror group. Next, synchronization copying from the mirror source disk to the mirror destination disk is performed. When the synchronization copying is in execution, the copy destination disk is in COPY status. Example: The mirror source disk number is 0 and the disk name is Disk0, the mirror destination disk number is 1 and the disk name is Disk1, and the mirror group name is Group0. > sdxinfo -D OBJ NAME TYPE GROUP DEVNAM DEVBLKS STATUS disk Disk0 mirror Group VALID disk Disk1 mirror Group COPY The synchronization copying progress (%) is shown in the RATE field in the sdxinfo -G -e long command output. When the synchronization copying is completed, the RATE field comes to display an asterisk (*). > sdxinfo -G -e long OBJ NAME DISKS BLKS SPARE JRM TYPE COPY RATE CURBLKS COPYBLKS DLY group Group0 Disk0:Disk on mirror run When the synchronization copying is ended normally, all the disks in the mirror group will be in VALID status. > sdxinfo -D OBJ NAME TYPE GROUP DEVNAM DEVBLKS STATUS disk Disk0 mirror Group VALID disk Disk1 mirror Group VALID For details on the sdxinfo command, see "A.2 sdxinfo - Disk configuration and status viewing." 18

27 2.2 Unmirroring 2.2 Unmirroring This section explains how to unset the mirroring configuration. To unset mirroring, you must be a user with administrator privileges (a user of the Administrators group). 1. Opening the command prompt Select [start]-[all Programs]-[Accessories]-[Command Prompt] to open Command Prompt. 2. Checking the mirror group name Check the GROUP field in the sdxinfo -D command output for the mirror group name. > sdxinfo -D OBJ NAME TYPE GROUP DEVNAM DEVBLKS STATUS disk Disk0 mirror Group VALID disk Disk1 mirror Group VALID For details on the sdxinfo command, see "A.2 sdxinfo - Disk configuration and status viewing." 3. Unsetting mirroring With the sdxsysdisk -R command, unset the mirroring. Responding to the message "Do you want to proceed (yes/no)?," type "yes" and press the Enter key. When the command is ended normally, the system is automatically rebooted. Example: The mirror group name is Group0. > sdxsysdisk -R -g Group0 SDX: sdxsysdisk: 64206: INFO: After execution of this command, the system will reboot automatically. Do you want to proceed (yes/no)? yes For details on the sdxsysdisk command, see "A.1 sdxsysdisk - Mirroring and unmirroring." 19

28 Chapter 2 Setup 4. Opening the command prompt After the system is rebooted, select [start]-[all Programs]-[Accessories]-[Command Prompt] to open Command Prompt. 5. Confirming the current state If mirroring is unset, the mirror group and mirror disks that belong to that group are excluded from PSDM management. One of the disks in VALID status will then be a disk that stores data and data on the other disks will no longer be ensured. With the sdxinfo -G command, confirm that the mirror group was removed. > sdxinfo -G OBJ NAME DISKS BLKS SPARE JRM Confirm that the disks were excluded from PSDM management. If excluded, the DKNAME field in the sdxinfo -P command output displays an asterisk (*). > sdxinfo -P OBJ NAME BLOCKS STATUS DKNAME LOCATION device * * IOU#0-HDD#0 device * * IOU#0-HDD#1 Select [start]-[control Panel]-[Administrative Tools]-[Computer Management]-[Disk Management] to check the disk that stores data. Partitions other than the boot partition (the C drive) may not automatically be mounted after the mirroring is unset. Check mount conditions from "Disk Management," and if they are not currently mounted, mount those partitions manually. For details on the sdxinfo command, see "A.2 sdxinfo - Disk configuration and status viewing." 20

29 Chapter 3 Operation 3.1 Disk Swap This section explains how to replace disks mirrored with PSDM with others. The procedures are applicable for replacing either normal or failed disks. If no disk in VALID status exists within the mirror group, the procedures described in this section cannot be used for exchanging disks within a mirror group. In this event, unmirror the disks once and then perform disk swap Preparing for Disk Swap (Removing Disks) Before exchanging disks, remove disks to be replaced from PSDM management. To perform the preparatory procedures (to remove disks) for disk swap, you must be a user with administrator privileges (a user of the Administrators group). 1. Setting boot control If a disk is removed, the system is rebooted automatically. Because it is required to turn off the power to the PRIMEQUEST partition during disk swapping, configure the setting to prevent Windows automatic startup on system reboot. The procedure below explains how to configure this setting. 1) Open [Partition]-[Partition#x]-[Boot Control] on the MMB Web-UI. Where #x is the PRIMEQUEST partition number. 2) Select [Force boot into EFI Boot Manager] from the [Boot Selector] pull-down menu and click [Apply]. 2. Opening the command prompt Select [start]-[all Programs]-[Accessories]-[Command Prompt] to open Command Prompt. 21

30 Chapter 3 Operation 3. Checking the disk to be replaced Check the disk name, status, mirror group name, and location of the disk to be replaced. For faulty disks, the STATUS field shows "ERROR." Example: The disk number of the disk to be replaced is 1, the disk name is Disk1, the status is ERROR, the mirror group name is Group0, and the location is IOU#0-HDD#1. > sdxinfo -D OBJ NAME TYPE GROUP DEVNAM DEVBLKS STATUS disk Disk0 mirror Group VALID disk Disk1 mirror Group ERROR > sdxinfo -P OBJ NAME BLOCKS STATUS DKNAME LOCATION device VALID Disk0 IOU#0-HDD#0 device ERROR Disk1 IOU#0-HDD#1 For details on the sdxinfo command, see "A.2 sdxinfo - Disk configuration and status viewing." If only one VALID disk exists in the mirror group, it is not possible to replace only the VALID disk with another. Disks other than the VALID disk must be swapped first. If no disk in VALID status exists in the mirror group, the procedures described in this section are not applicable. In this event, remove the mirroring once and then perform disk swap. 22

31 3.1 Disk Swap 4. Removing the disk Remove the disk to be replaced from PSDM management. Responding to the message Do you want to proceed(yes/no)?, type yes and press the Enter key. If the command ends normally, system reboot will commence automatically. Example: The disk Disk1 is swapped. > sdxsysdisk -R -d Disk1 SDX: sdxsysdisk: 64206: INFO: After execution of this command, the system will reboot automatically. Do you want to proceed (yes/no)? yes For details on the sdxsysdisk command, see "A.1 sdxsysdisk - Mirroring and unmirroring." 5. Stopping the system When the EFI Boot Manager menu is displayed and the input mode is entered, turn off the power to the PRIMEQUEST partition. EFI Boot Manager ver 1.xx [xx.xx] Please select a boot option Windows Server 2003, Enterprise Edition(MIRROR DISK 0-0) EFI Shell [Built-in] Boot Option Maintenance Menu Setup Menu Use and to change option(s). Use Enter to select an option If Windows automatic startup occurred, shut down Windows before turning off the power to the PRIMEQUEST partition Swapping Disks Please contact your local customer support to have disks swapped. Hot swap is not supported. To swap disks, it is necessary to turn off the power to the PRIMEQUEST partition. For details, see the PRIMEQUEST manual. 23

32 Chapter 3 Operation Restoring Disks after Swapping (Adding Disks) After swapping disks, add the new disks to the mirror group. The procedure below explains how to add disks to a mirror group. You must be a user with administrator privileges (a user of the Administrators group) to perform this procedure. 1. Checking the replacement disk Check the disk number of the replacement disk. Its location can be different from the location of the disk that was replaced. Example: The replacement disk location is IOU#0-HDD#1. > sdxinfo -P OBJ NAME BLOCKS STATUS DKNAME LOCATION device VALID Disk0 IOU#0-HDD#0 device * * IOU#0-HDD#1 For details on the sdxinfo command, see "A.2 sdxinfo - Disk configuration and status viewing." 2. Adding the disk Add the replacement disk to the mirror group. Before performing this procedure, exit "Disk Management" or the diskpart command if it is active. Example: The mirror group name is Group0 and the disk number of the replacement disk is 1. > sdxsysdisk -A -g Group0 -p 1 For details on the sdxsysdisk command, see "A.1 sdxsysdisk - Mirroring and unmirroring." 24

33 3.1 Disk Swap 3. Confirming the mirroring state After a disk is added, the synchronization copying from a VALID disk in the mirror group to the disk is automatically initialized. During the synchronization, the disk will be in COPY status. Example: The mirror group name is Group0, and the disk number of the added disk is 1 and the disk name is Disk1. > sdxinfo -D OBJ NAME TYPE GROUP DEVNAM DEVBLKS STATUS disk Disk0 mirror Group VALID disk Disk1 mirror Group COPY The synchronization copying progress (%) is shown in the RATE field in the sdxinfo -G -e long command output. When the synchronization copying is completed, the RATE field comes to display an asterisk (*). > sdxinfo -G -e long OBJ NAME DISKS BLKS SPARE JRM TYPE COPY RATE CURBLKS COPYBLKS DLY group Group0 Disk0:Disk on mirror run When the synchronization copying is ended normally, all the disks in the mirror group will be in VALID status. > sdxinfo -D OBJ NAME TYPE GROUP DEVNAM DEVBLKS STATUS disk Disk0 mirror Group VALID disk Disk1 mirror Group VALID For details on the sdxinfo command, see "A.2 sdxinfo - Disk configuration and status viewing." 25

34 Chapter 3 Operation 3.2 Boot Disk Backup and Restore This section explains how to back up and restore the boot disk mirrored with PSDM Backing Up the Boot Disk Back up the boot disk with ScWL. Choose a disk which is in VALID status as the backup target. The entire disk including the reserved partition will be backed up, and if you change the mirroring configuration, it is necessary to re-create the backup. 1. Opening the command prompt Select [start]-[all Programs]-[Accessories]-[Command Prompt] to open Command Prompt. 2. Checking the disk to be backed up Check and write down the mirror group name, disk name, and location of the disk to be backed up. The mirror group name and the disk name are parameters required for restore. The disk location is a parameter required for backup. Example: The mirror group name is Group0, the disk name is Disk0, and the location is IOU#0-HDD#0. > sdxinfo -D OBJ NAME TYPE GROUP DEVNAM DEVBLKS STATUS disk Disk0 mirror Group VALID disk Disk1 mirror Group VALID > sdxinfo -P OBJ NAME BLOCKS STATUS DKNAME LOCATION device VALID Disk0 IOU#0-HDD#0 device VALID Disk1 IOU#0-HDD#1 For details on the sdxinfo command, see "A.2 sdxinfo - Disk configuration and status viewing." 26

35 3.2 Boot Disk Backup and Restore 3. Backing up Back up the disk at the location confirmed in step 2. with ScWL. For the usage of ScWL, see the "PRIMEQUEST SystemcastWizard Lite User s Guide." Restoring the Boot Disk Restore the boot disk with ScWL. 1. Removing the data group Boot the system if possible, and remove the data group. If the boot disk is restored, the data group will be removed automatically. However, partitions are not removed in this event, and drive letter assignment may not be performed normally. For this reason, before restoring the boot disk, you are recommended to remove the data group. For more information on how to remove groups, see "2.2 Unmirroring." 2. Stopping the system Stop the system. 3. Restoring Restore the backup data created as described in "3.2.1 Backing Up the Boot Disk" to a disk at the location where the backed up disk resides. For the restore operation, use ScWL. Restore backup data to only one disk. Even if the backup data is restored to multiple disks, the mirroring state is not restored. For the usage of ScWL, see "PRIMEQUEST SystemcastWizard Lite User s Guide." 27

36 Chapter 3 Operation 4. Booting the system From the EFI Boot Manager menu, select the boot entry indicating the restored boot disk, and boot the system. Example: The mirror group name of the backed up boot disk is Group0 and the disk name is Disk0. EFI Boot Manager ver 1.xx [xx.xx] Please select a boot option Windows Server 2003, Enterprise Edition(MIRROR DISK 0-0) Windows Server 2003, Enterprise Edition(MIRROR DISK 0-1) EFI Shell [Built-in] Boot Option Maintenance Menu Setup Menu Select Use and to change option(s). Use Enter to select an option For the boot entry naming conventions, see "Boot entry name" of "1.2 Configurations." 5. Opening the command prompt Select [start]-[all Programs]-[Accessories]-[Command Prompt] to open Command Prompt. 28

37 3.2 Boot Disk Backup and Restore 6. Confirming the state If the boot disk is restored: The data group is removed. Disks swapped after the boot disk was backed up will be in ERROR status. In a situation where disks other than the restored disk exist in the mirror group of the boot disk, synchronization copying from the restored disk to those disks is performed. When the synchronization copying is in execution, the copy destination disks are in COPY status. Example: The disk number of the restored disk is 0 and the disk name is Disk0. > sdxinfo -D OBJ NAME TYPE GROUP DEVNAM DEVBLKS STATUS disk Disk0 mirror Group VALID disk Disk1 mirror Group COPY The synchronization copying progress (%) is shown in the RATE field in the sdxinfo -G -e long command output. When the synchronization copying is completed, the RATE field comes to display an asterisk (*). > sdxinfo -G -e long OBJ NAME DISKS BLKS SPARE JRM TYPE COPY RATE CURBLKS COPYBLKS DLY group Group0 Disk0:Disk on mirror run When the synchronization copying is ended normally, all the disks in the mirror group will be in VALID status. > sdxinfo -D OBJ NAME TYPE GROUP DEVNAM DEVBLKS STATUS disk Disk0 mirror Group VALID disk Disk1 mirror Group VALID For details on the sdxinfo command, see "A.2 sdxinfo - Disk configuration and status viewing." 29

38 Chapter 3 Operation 7. Restoring disks swapped after backup Disks swapped after the boot disk was backed up will be in ERROR status if the boot disk is restored. To restore the normal status, remove the disks in ERROR status from the mirror group once and add them again to the group. For more information on how to remove disks, see "3.1.1 Preparing for Disk Swap (Removing Disks)." For more information on how to add disks, see "3.1.3 Restoring Disks after Swapping (Adding Disks)." 8. Restoring the data group The boot disk restore operation has no effect on data disk content, but data disks are excluded from PSDM management. To restore the mirroring configuration of the data disks, remove all partitions on the mirror destination disks and set up mirroring again. For the mirroring setup method, see "2.1 Mirroring." 3.3 Data Disk Backup and Restore Backup and restore operations of data disks should be performed in disk partition (drive) units, file system units, or file units but not in disk units. To back up and restore non-boot disks, use the backup and restore procedures used when PSDM is not involved. For details, see the manual of your backup software. For the following reasons, it is not recommended to use ScWL to back up data disks. The backup operation by ScWL requires stopping the system. The restore operation by ScWL also restores the EFI configuration. If the EFI configuration and the system disk configuration or content conflict, the system may not be booted. 30

39 3.4 Operation Monitoring 3.4 Operation Monitoring Use the Windows OS Event Viewer to view the PSDM event log. To open the Event Viewer, select [start]-[control Panel]-[Administrative Tools]-[Event Viewer]. The event log records information as follows. Table 3-1: Event logs Type Source Description System log F6GADRV The device driver log, which mainly contains information about errors that occurred during operation. F6GASRV The service log, which is mainly used to record changes in the EFI boot menu. Application log F6GACMD The command log, which contains errors that occurred during command execution. The following Windows OS event logs may be recorded, but the system and the PSDM will operate normally. Table 3-2: Windows OS event logs Disk Source Event ID Description Output when VDS Basic Provider Virtual Disk Service The driver detected that the device xxxxx has its write cache enabled. Data corruption may occur. The driver disabled the write cache on device xxxxx. Unexpected failure. Error code: xxxxx Unexpected failure. Error code: xxxxx VDS fails to claim a disk (xxxxx) due to error. Error Code: xxxxx Synchronization copying starts. Synchronization copying ends. "Disk Management" opens, diskpart runs, etc. "Disk Management" opens, diskpart runs, etc. "Disk Management" opens, diskpart runs, etc. 31

40 Chapter 3 Operation 3.5 Collecting Information for Troubleshooting If an error occurs in a system that uses PSDM and the cause of or resolution to the error is not found based on the error message, follow the procedures below to collect information for troubleshooting and submit it to your local customer support. To collect information for troubleshooting, you must be a user with administrator privileges (a user of the Administrators group). 1. Opening the command prompt Select [start]-[all Programs]-[Accessories]-[Command Prompt] to open Command Prompt. 2. Collecting information for troubleshooting With the sdxsnap command, collect information for troubleshooting. The information will be saved in a file named sdxsnapradxxxxx.cab (where XXXXX is a variable string that PSDM automatically generates). Example: Collect information required for troubleshooting and save it to the C:\snap directory > sdxsnap -k -d C:\snap For details on the sdxsnap command, see "A.3 sdxsnap - Collection of information for troubleshooting." If a problem occurs, collect information for troubleshooting as soon as possible because necessary information might be lost over time. 32

41 3.6 Starting/Stopping the Service 3.6 Starting/Stopping the Service The PSDM service (F6GASRV) automatically starts when the system is booted and stops when the system is stopped in normal situations. However, if the system stops running due to some event or stopping the service fails, it is necessary to take action according to the event log message and then start or stop the service manually. To start or stop the service, you must be a user with administrator privileges (a user of the Administrators group). 1. Opening [Services] Select [start]-[control Panel]-[Administrative Tools]-[Services] to open Services. 2. Starting or stopping the F6GASRV service In the details window, select F6GASRV and then [Action]-[Start] or [Action]-[Stop]. If the system is rebooted by the action taken according to the message, the service is automatically started at system startup and it is not required to start it manually. 33

42 Chapter 3 Operation 34

43 Appendix A Command Reference A.1 sdxsysdisk - Mirroring and unmirroring Command name sdxsysdisk Mirroring and unmirroring Synopsis sdxsysdisk -A -g group -p device,... [-e delay=msec] sdxsysdisk -M -p device[:type][,device[:type]] sdxsysdisk -R {-g group,... -d disk,...} sdxsysdisk {-h /?} Description The sdxsysdisk command sets or unsets the mirroring configuration. To use this command, you must be a user with administrator privileges (a user of the Administrators group). 35

44 Appendix A Command Reference Primary options -A Adds mirror destination disks to an existing mirror group. If a mirror disk in VALID status exists within the mirror group, synchronization copying from the VALID mirror disk to the added mirror destination disks is performed. -M Creates a new mirror group. If a mirror destination disk is registered, synchronization copying from the mirror source disk to the mirror destination disk is performed. -R Removes mirror groups or mirror disks. When mirror disks are removed, one or more mirror disks in VALID status must remain in the mirror group after the removal. If a mirror group is removed, mirror disks within the mirror group are also removed. One of the disks in VALID status will then be a disk that stores data and data on the other disks will no longer be ensured. After any mirror disk or mirror group removal, the system will be rebooted automatically. -h Shows the usage of the command. /? Shows the usage of the command. 36

45 A.1 sdxsysdisk - Mirroring and unmirroring Sub options -d disk,... Sets mirror disks that are removed from the mirror group. For disk, specify the mirror disk name in the format of Diskn (where n is the mirror disk number). -e delay=msec Sets delay time of the synchronization copying process (in milliseconds). An integer in the range of 0 to 1000 (including 0 and 1000) can be set. The default delay time is 0. If this option is set, for the mirror destination disks added to the mirror group, given quantity of copying is performed at msec millisecond intervals. With this option, the synchronization copying load imposed on the system can be reduced. Note, however, that if larger delay time is set, longer time is required to complete synchronization copying. -g group Sets the mirror group to which disks are added or the mirror group that is removed. For group, specify the mirror group name in the format of Groupn (where n is the mirror group number). -p device,... (along with -A) Sets the disk numbers of disks added to the mirror group. The disk numbers are displayed in Windows [Disk Management] or in the Disk ### field output by the list disk command of the diskpart command. -p device[:type][,device[:type]] (along with -M) Sets the disk numbers and type attributes of disks registered with the mirror group by the combination of device and type. For type, specify either one of the following values. The keep attribute must be specified to one of the disks. The default disk type attribute is undef. keep Sets the disk as the mirror source disk. undef Sets the disk as a mirror destination disk. 37

46 Appendix A Command Reference Exit codes 0 : Normal end 1 : Abnormal end (indicating that the error is not a temporary error and the command will fail even if it is retried after a while) 2 : Abnormal end (indicating that the error is a temporary error and the command may succeed if it is retried after a while) 3 : Abnormal end (indicating that an option was specified incorrectly) Execute the following command immediately after this command ends to get the exit code. > echo %ERRORLEVEL% Examples a. Set up mirroring using a disk numbered 0 as the mirror source and a disk numbered 1 as the mirror destination. > sdxsysdisk -M -p 0:keep,1:undef b. Remove the mirror group Group0 to unset mirroring. > sdxsysdisk -R -g Group0 c. Add a disk numbered 2 to the mirror group Group0. > sdxsysdisk -A -g Group0 -p 2 d. Remove the mirror disk Disk1 from PSDM management. > sdxsysdisk -R -d Disk1 38

47 A.2 sdxinfo - Disk configuration and status viewing A.2 sdxinfo - Disk configuration and status viewing Command name sdxinfo - Disk configuration and status viewing Synopsis sdxinfo [-DG] [-e long] sdxinfo -P sdxinfo {-h /?} Description The sdxinfo command displays the configuration and status of disks. To use this command, you must be a user with administrator privileges (a user of the Administrators group). Primary options The following primary options can be set. By default, mirror disk information and mirror group information are displayed. -D Displays mirror disk information. -G Displays mirror group information. -P Displays physical disk information. -h Shows the usage of the command. /? Shows the usage of the command. 39

48 Appendix A Command Reference Sub options -e long Displays detailed information. Displayed information Information displayed in response to the sdxinfo command is explained below. For pieces of information not displayed for some reason, a question mark (?) is displayed. Mirror disk information This information is displayed by default or if the -D option is set. OBJ Indicated as disk. NAME Displays the mirror disk names. The mirror disk name is given in the format of Diskn (where n is the mirror disk number). TYPE Indicated as mirror. GROUP Displays the mirror group names. The mirror group name is given in the format of Groupn (where n is the mirror group number). DEVNAM Displays the disk numbers. DEVBLKS Displays the disk size (the number of blocks in 512-byte units). 40

49 A.2 sdxinfo - Disk configuration and status viewing STATUS Displays the statuses classified as shown below. VALID The data is valid. Data on VALID disks in the same mirror group is always synchronized. INVALID The data is invalid. Data on the disk in this status may no longer be synchronized with data on VALID disks in the same mirror group. Disks will be in INVALID status before synchronization copying is initiated or after it is canceled. COPY Synchronization copying is in process. ERROR An error occurred. Mirror disk detailed information This information is displayed by default or with the -D option if the -e long option is set. WB Indicated as 0. Mirror group information This information is displayed by default or if the -G option is set. OBJ Indicated as group. NAME Displays the mirror group names. The mirror group name is given in the format of Groupn (where n is the mirror group number). DISKS Displays the mirror disk names, each separated by a colon (:). The mirror disk name is given in the format of Diskn (where n is the mirror disk number). 41

50 Appendix A Command Reference BLKS Displays the group size (the number of blocks in 512-byte units). SPARE Indicated as 0. JRM Displays the just resynchronization mode setting, which is one of the following values. on Resynchronization copying executed when the system is rebooted after it was down copies only the part that was being written when the system was down. However, for the boot partition (usually C:), the entire partition is copied. off Resynchronization copying executed when the system is rebooted after it was down copies the entire disk. Mirror group detailed information This information is displayed by default or with the -G option if the -e long option is set. TYPE Indicated as mirror. COPY Indicated as run. If copying is not in process, an asterisk (*) is displayed. RATE Displays the synchronization copying progress (%). If copying is not in process, or if just resynchronization copying is in process, an asterisk (*) is displayed. CURBLKS Displays the number of blocks copied already. If copying is not in process, an asterisk (*) is displayed. COPYBLKS Displays the number of blocks that are copied. If copying is not in process, an asterisk (*) is displayed. DLY Displays delay time of the copying process (in milliseconds). If copying is not in process, an asterisk (*) is displayed. 42

51 A.2 sdxinfo - Disk configuration and status viewing Physical disk information This information is displayed if the -P option is set. OBJ Indicated as device. NAME Displays the disk numbers. BLOCKS Displays the disk size (the number of blocks in 512-byte units). STATUS Displays the mirror disk statuses classified as shown below. VALID The data is valid. Data on VALID disks in the same mirror group is always synchronized. INVALID The data is invalid. Data on the disk in this status may no longer be synchronized with data on VALID disks in the same mirror group. Disks will be in INVALID status before synchronization copying is initiated or after it is canceled. COPY Synchronization copying is in process. ERROR An error occurred. * The disk is not configured as a mirror disk. DKNAME Displays the mirror disk names. If the disk is not configured as a mirror disk, an asterisk (*) is displayed. 43

52 Appendix A Command Reference LOCATION Displays the disk location. This information is given in the format of the unit name displayed by the PSA s diskctrl -lu command. Exit codes 0 : Normal end 1 : Abnormal end (indicating that the error is not a temporary error and the command will fail even if it is retried after a while) 2 : Abnormal end (indicating that the error is a temporary error and the command may succeed if it is retried after a while) 3 : Abnormal end (indicating that an option was specified incorrectly) Execute the following command immediately after this command ends to get the exit code. > echo %ERRORLEVEL% 44

53 A.2 sdxinfo - Disk configuration and status viewing Examples a. View information about mirror disks and mirror groups. > sdxinfo OBJ NAME TYPE GROUP DEVNAM DEVBLKS STATUS disk Disk0 mirror Group VALID disk Disk1 mirror Group COPY OBJ NAME DISKS BLKS SPARE JRM group Group0 Disk0:Disk on b. View information about mirror disks. > sdxinfo -D OBJ NAME TYPE GROUP DEVNAM DEVBLKS STATUS disk Disk0 mirror Group VALID disk Disk1 mirror Group COPY c. View information about mirror groups. > sdxinfo -G OBJ NAME DISKS BLKS SPARE JRM group Group0 Disk0:Disk on d. View information about physical disks. > sdxinfo -P OBJ NAME BLOCKS STATUS DKNAME LOCATION device VALID Disk0 IOU#0-HDD#0 device * * IOU#0-HDD#1 e. View detailed information about mirror groups. > sdxinfo -G -e long OBJ NAME DISKS BLKS SPARE JRM TYPE COPY RATE CURBLKS COPYBLKS DLY group Group0 Disk0:Disk on mirror run

54 Appendix A Command Reference If an error occurs during the sdxinfo command process, error messages may be output in the middle of information display. Disk configurations and states are output to the standard output and error messages are output to the standard error output. Therefore, for convenience, you can specify that error messages are output together at the beginning or at the end or are not output at all using the following methods. Example 1) Display error messages together at the beginning. > sdxinfo 1> out1 2> out2 & type out2 & type out1 & del out1 out2 Alternatively, specify as follows. > sdxinfo > out1 & type out1 & del out1 Example 2) Display error messages together at the end. > sdxinfo 1> out1 2> out2 & type out1 & type out2 & del out1 out2 Alternatively, specify as follows. > sdxinfo 2> out2 & type out2 & del out2 Example 3) Skip displaying error messages. > sdxinfo 2> NUL For more information on the redirect operator (>), the type command, the del command, and the NUL device, see the Windows Help. 46

55 A.3 sdxsnap - Collection of information for troubleshooting A.3 sdxsnap - Collection of information for troubleshooting Command name sdxsnap Collection of information for troubleshooting Synopsis sdxsnap [-k] [-d dir] sdxsnap {-h /?} Description The sdxsnap command collects information such as PSDM configuration, status, and operation history for troubleshooting. To use this command, you must be a user with administrator privileges (a user of the Administrators group). The collected information is compressed in CAB format and saved to a file named sdxsnapradxxxxx.cab (where XXXXX is a variable string that PSDM automatically generates). The file name will be displayed when the command ends. 47

56 Appendix A Command Reference Options -d dir Specifies the storage directory for collected information. The default storage directory is Temp located in the PSDM installation directory. -k Collects the kernel log additionally. If disk free space is insufficient or if the transmittable file size is limited because of communication limitation and so on, do not specify this option to reduce the size of information collected for troubleshooting. If there is no special reason, this option should be specified. -h Shows the usage of the command. /? Shows the usage of the command. Exit codes 0 : Normal end 1 : Abnormal end (indicating that the error is not a temporary error and the command will fail even if it is retried after a while) 2 : Abnormal end (indicating that the error is a temporary error and the command may succeed if it is retried after a while) 3 : Abnormal end (indicating that an option was specified incorrectly) Execute the following command immediately after this command ends to get the exit code. > echo %ERRORLEVEL% Examples a. Collect information for troubleshooting, except the kernel log, to C:\snap. > sdxsnap -d C:\snap b. Collect information for troubleshooting to \Temp located in the PSDM installation directory. > sdxsnap -k 48

57 Appendix B Messages B.1 Driver Messages This section describes driver messages and explains what to do in response to the messages. Message output and viewing Driver messages are output to the Windows event log. The event log can be viewed in Windows Event Viewer. To open Event Viewer, select [start]-[control Panel]-[Administrative Tools]-[Event Viewer]. Variable description Italic texts in the messages denote variables and vary depending on the situations where the messages are output. The following table shows variables and the descriptions. Table B_1: Variable description Variable name device(s) disk(s) driver error group offset reason time Description Disk number(s) Mirror disk name(s) Driver name I/O error code Mirror group name Disk offset where an I/O error occurred The cause of the failure or the error description Timeout seconds 49

58 Appendix B Messages Severity Driver messages are categorized into the following three types listed from higher to lower severity. Table B_2: Severity Message number Severity Description 20XXX ERROR This type of message is output when an event that causes the system to pause was detected. 22XXX WARNING This type of message is output to give warning when an error that does not cause the system to pause was detected. 24XXX INFO This type of message is output to track driver activities. B.1.1 Driver Error Messages (20XXX) Mirror driver was not able to start because of load error. error reason : reason An error occurred at driver load and startup failed. Collect information for troubleshooting and contact your local customer support Mirror driver was not able to start because of initializing process failure. error reason : reason An error occurred at driver initialization and startup failed. Collect information for troubleshooting and contact your local customer support. 50

59 B.1 Driver Messages Mirror driver was not able to start because of add device process failure. error reason : reason An error occurred in the driver device adding process and startup failed. Collect information for troubleshooting and contact your local customer support Mirror driver was not able to start because of registry accessing error. An error occurred in the driver registry access process and startup failed. Collect information for troubleshooting and contact your local customer support Mirror driver was not able to start because of broken reserved data. Data on the reserved partition is invalid and startup failed. Collect information for troubleshooting and contact your local customer support. 51

60 Appendix B Messages The error occurred on all disks in the mirror group. group name : group device names : devices disk names : disks All disks in the mirror group group failed. devices are the disk numbers of the disks in group. disks are the disk names of the disks in group. The possible causes of an error that occurs in a disk may not only be a disk failure but also a failure or defect of a hardware component such as an adapter, a cable, and a controller. Check the event log and other relevant information to pinpoint the faulty part on the hardware. With the boot disk, replace the failed disk or component with another and then restore the backup data. For more information on restore, see "3.2.2 Restoring the Boot Disk." With a data disk, unset the mirroring configuration of group and then replace the failed disk or component with another, set the mirroring configuration again, and restore the backup data. For more information on restore, see "3.3 Data Disk Backup and Restore." 52

61 B.1 Driver Messages B.1.2 Driver Warning Messages (22XXX) JRM copy process was failed and disk status changed to INVALID. device name : device disk name : disk group name : group Resynchronization of the mirror group group failed and the disk disk is now INVALID. device is the disk number of disk. Check the event log and other relevant information to pinpoint the faulty part on the hardware and swap the failed disk or component. For more information on how to swap disks, see "3.1 Disk Swap." Full disk copy for recovering equivalence process was failed and disk status changed to INVALID. device name : device disk name : disk group name : group Synchronization copying of the mirror group group failed and the disk disk is now INVALID. device is the disk number of disk. Check the event log and other relevant information to pinpoint the faulty part on the hardware and swap the failed disk or component. For more information on how to swap disks, see "3.1 Disk Swap." 53

62 Appendix B Messages Disk surprise removal occurred. device name : device disk name : disk The physical disk device of the disk disk was removed from the system and is no longer available. The possible causes are as follows. Cause a: A disk managed with PSDM was removed from the system by mistake. Cause b: Before a disk managed with PSDM was removed from the system, the disk was not removed from PSDM management. Cause c: Before a disk managed with PSDM was swapped, the disk was not removed from PSDM management. In the event of cause a, b, or c, take action as described in resolution a, b, or c respectively. a: Add the relevant disk back to the system, and then perform disk removal and addition. For more information on how to remove disks, see "3.1.1 Preparing for Disk Swap (Removing Disks);" for more information on how to add disks, see "3.1.3 Restoring Disks after Swapping (Adding Disks)." b: From PSDM management, remove the disk removed from the system. > sdxsysdisk -R -d disk c: Referring to "3.1 Disk Swap," follow proper procedures for exchanging disks Disk is not mirrored because only 1 disk remains in the mirror group. group name : group Only one disk exists in the mirror group group and disk data is not redundant. Add one or more disks to group. For more information on how to add disks, see "3.1.3 Restoring Disks after Swapping (Adding Disks)." 54

63 B.1 Driver Messages The following mirror group has been removed automatically. group name : group device names : devices disk names : disks The mirror group group was removed automatically when the system was booted. Automatic mirror group removal may occur, for example, if no VALID disk exists in the mirror group, reserved partition content contains an error, or boot disk restoration occurs. devices are the disk numbers of the disks removed from group. disks are the disk names of the disks removed from group. Take actions as follows and set the mirroring configuration as needed. If any, delete unnecessary boot entries with the bootcfg command. If a disk failure occurred, replace the faulty disk with another. If any, remove unnecessary partitions with Disk Management or the diskpart command. If drive letter assignment was not performed normally, reassign the drive letter with "Disk Management" or the diskpart command The reserved partition has been removed automatically from the following disk. device name : device An error was found in reserved partition content, and the reserved partition on the physical disk device was removed. Delete unnecessary partitions first and add device to the mirror group. 55

64 Appendix B Messages Disk read error occurred and disk status changed to ERROR. device name : device disk name : disk error status : error offset : offset A read request to the physical disk device ended abnormally and the disk disk is now in ERROR status. Check the event log and other relevant information to pinpoint the faulty part on the hardware and swap the failed disk or component. For more information on how to swap disks, see "3.1 Disk Swap." Disk read error occurred by time-out and disk status changed to ERROR. device name : device disk name : disk error status : error offset : offset wait time : time A read request to the physical disk device ended abnormally and the disk disk is now in ERROR status. Check the event log and other relevant information to pinpoint the faulty part on the hardware and swap the failed disk or component. For more information on how to swap disks, see "3.1 Disk Swap." 56

65 B.1 Driver Messages Disk write error occurred and disk status changed to ERROR. device name : device disk name : disk error status : error offset : offset A write request to the physical disk device ended abnormally and the disk disk is now in ERROR status. Check the event log and other relevant information to pinpoint the faulty part on the hardware and swap the failed disk or component. For more information on how to swap disks, see "3.1 Disk Swap." Disk write error by time-out occurred and disk status changed to ERROR. device name : device disk name : disk error status : error offset : offset wait time : time A write request to the physical disk device ended abnormally due to timeout and the disk disk is now in ERROR status. Check the event log and other relevant information to pinpoint the faulty part on the hardware and swap the failed disk or component. For more information on how to swap disks, see "3.1 Disk Swap." 57

66 Appendix B Messages JRM read error and disk status changed to ERROR. device name : device disk name : disk error status : error offset : offset A JRM read request to the physical disk device ended abnormally and the disk disk is now in ERROR status. Check the event log and other relevant information to pinpoint the faulty part on the hardware and swap the failed disk or component. For more information on how to swap disks, see "3.1 Disk Swap." JRM read error by time-out and disk status changed to ERROR. device name : device disk name : disk error status : error offset : offset wait time : time A JRM read request to the physical disk device ended abnormally due to timeout and the disk disk is now in ERROR status. Check the event log and other relevant information to pinpoint the faulty part on the hardware and swap the failed disk or component. For more information on how to swap disks, see "3.1 Disk Swap." 58

67 B.1 Driver Messages JRM write error and disk status changed to ERROR. device name : device disk name : disk error status : error offset : offset A JRM write request to the physical disk device ended abnormally and the disk disk is now in ERROR status. Check the event log and other relevant information to pinpoint the faulty part on the hardware and swap the failed disk or component. For more information on how to swap disks, see "3.1 Disk Swap." JRM write error by time-out and disk status changed to ERROR. device name : device disk name : disk error status : error offset : offset wait time : time A JRM write request to the physical disk device ended abnormally due to timeout and the disk disk is now in ERROR status. Check the event log and other relevant information to pinpoint the faulty part on the hardware and swap the failed disk or component. For more information on how to swap disks, see "3.1 Disk Swap." 59

68 Appendix B Messages Disk status changed to ERROR by disk access except for read and write process. device name : device disk name : disk group name : group error reason : reason In some process other than read/write, the disk disk came into the ERROR status. Check the event log and other relevant information to pinpoint the faulty part on the hardware and swap the failed disk or component. For more information on how to swap disks, see "3.1 Disk Swap." B.1.3 Driver Information Message (24XXX) driver driver started. The driver started normally driver driver stopped. The driver stopped normally. 60

69 B.1 Driver Messages System does not shutdown normally last time. At system startup, it was detected that the system was not shut down normally last time JRM copy process was completed successfully. group name : group Resynchronization of the mirror group group ended normally Full disk copy for recovering equivalence process was completed successfully. group name : group Synchronization copying of the mirror group group ended normally Disk is removed from the mirror group. device name : device disk name : disk group name : group The disk disk was removed from the mirror group group. device is the disk number of disk. 61

70 Appendix B Messages Conflict has been found between the configuration database and the actual, but this problem has been resolved automatically. The disk specifications does not match the mirroring management information stored in the reserved partition. The mirroring management information was modified for continuous normal operation and no action is required. This message is output in a situation where disks are swapped or removed from the system after the system is shut down and before it is rebooted The following mirror group has been removed. group name : group device names : devices disk names : disks The mirror group group was removed. devices are the disk numbers of the disks removed from group. disks are the disk numbers of the disks removed from group Write caching of the following disk has been disabled. group name : group device name : device disk name : disk Write caching for the disk disk was disabled. device is the disk number of disk. 62

71 B.2 Service Messages B.2 Service Messages This section describes service messages and explains what to do in response to the messages. Message output and viewing Service messages are output to the Windows event log. The event log can be viewed in Windows Event Viewer. To open Event Viewer, select [start]-[control Panel]-[Administrative Tools]-[Event Viewer]. Variable description Italic texts in the messages denote variables and vary depending on the situations where the messages are output. The following table shows variables and the descriptions. Table B_3: Variable description Variable name disk entryn group Description Mirror disk name EFI boot entry name Mirror group name Severity Service messages are categorized into the following four types listed from higher to lower severity. Table B_4: Severity Message number Severity Description 40XXX STOP This type of message is output when an event that causes the service to pause was detected. 42XXX ERROR This type of message is output when an event that causes part of the service to pause was detected. 44XXX WARNING This type of message is output to give warning when an error that does not cause the service to pause was detected. 46XXX INFO This type of message is output to track service activities. 63

72 Appendix B Messages B.2.1 Service Stop Messages (40XXX) STOP:The service was stopped because of insufficient memory. Memory is insufficient and the service stopped. Check memory use and, for example, exit some running applications to increase available memory, and start the F6GASRV service. For more information on how to start the service, see "3.6 Starting/Stopping the Service." STOP:The service was stopped because the driver was not executed. The PSDM driver is not running and the service stopped. If the system was not rebooted after the PSDM installation, reboot the system. In other situations, check the event log or other relevant information for a driver or system error and take action to resolve the error. After resolving the problem or error, start the F6GASRV service. For more information on how to start the service, see "3.6 Starting/Stopping the Service." STOP:The service was stopped because an error occurred in the Windows Service Control Manager. An error occurred in Windows Service Control Manager and the service stopped. Check the event log or other relevant information for a system error and take action to resolve the error, and then start the F6GASRV service. For more information on how to start the service, see "3.6 Starting/Stopping the Service." 64

73 B.2 Service Messages STOP:The service was stopped because an error occurred in a Windows API. An error occurred in a Windows API and the service stopped. Check the event log or other relevant information for a system error and take action to resolve the error, and then start the F6GASRV service. For more information on how to start the service, see "3.6 Starting/Stopping the Service." STOP:The service was stopped because of a program level inconsistency. The versions of the PSDM driver and the PSDM service are inconsistent and the service stopped. Check whether PSDM fixes are applied properly. If not, apply available fixes. In other situations, perform the overwrite installation of PSDM STOP:The service was stopped because an unavoidable driver error occurred. An error occurred in the PSDM driver and the service stopped. Check the event log of the PSDM F6GADRV driver and take action as needed, and then start the F6GASRV service. For more information on how to start the service, see "3.6 Starting/Stopping the Service." 65

74 Appendix B Messages B.2.2 Service Error Messages (42XXX) STOP:Stopping of the service failed because of insufficient memory. Memory is insufficient and stopping the service failed. Check memory use and, for example, exit some running applications to increase available memory, and stop the F6GASRV service. For more information on how to stop the service, see "3.6 Starting/Stopping the Service." Stopping of the service failed because the driver was not executed. The PSDM driver is not running and stopping the service failed. If the system was not rebooted after the PSDM installation, reboot the system. In other situations, check the event log or other relevant information for a driver or system error and take action to resolve the error. After resolving the problem or error, stop the F6GASRV service. For more information on how to stop the service, see "3.6 Starting/Stopping the Service." Stopping of the service failed because an error occurred in the Windows Service Control Manager. An error occurred in the Windows Service Control Manager and stopping the service failed. Check the event log or other relevant information for a system error and take action to resolve the error, and then stop the F6GASRV service. For more information on how to stop the service, see "3.6 Starting/Stopping the Service." 66

75 B.2 Service Messages Stopping of the service failed because an error occurred in a Windows API. A Windows API error occurred and stopping the service failed. Check the event log or other relevant information for a system error and take action to resolve the error, and then stop the F6GASRV service. For more information on how to stop the service, see "3.6 Starting/Stopping the Service." Stopping of the service failed because of a program level inconsistency. The versions of the PSDM driver and the PSDM service are inconsistent and stopping the service failed. Check whether PSDM fixes are applied properly. If not, apply available fixes. In other situations, perform the overwrite installation of PSDM Stopping of the service failed because a driver error occurred. An error occurred in the PSDM driver and stopping the service failed. Check the PSDM F6GADRV driver event log and take action to resolve the error, and then stop the F6GASRV service. For more information on how to stop the service, see "3.6 Starting/Stopping the Service." 67

76 Appendix B Messages Changing of the EFI Boot Entry of the keep disk failed when the mirror group was created, because of insufficient memory. group name: group disk name: disk Memory is insufficient, and in the process of creating the mirror group group, the EFI boot entry of the mirror disk disk was not changed. Check memory use and, for example, exit some running applications to increase available memory. Additionally, if any, delete unnecessary boot entries with the bootcfg command. After performing these operations, retry mirroring setup Changing of the EFI Boot Entry of the keep disk failed when the mirror group was created, because an error occurred in a Windows API. group name: group disk name: disk A Windows API error occurred, and in the process of creating the mirror group group, the EFI boot entry of the mirror disk disk was not changed. Check the event log or other relevant information for a system error and take action to resolve the error. Additionally, if any, delete unnecessary boot entries with the bootcfg command. After performing these operations, retry mirroring setup. 68

77 B.2 Service Messages Changing of the EFI Boot Entry of the keep disk failed when the mirror group was created, because a bootcfg command error occurred. group name: group disk name: disk A bootcfg command error occurred, and in the process of creating the mirror group group, the EFI boot entry of the mirror disk disk was not changed. Check the event log or other relevant information for a system error and take action to resolve the error. Additionally, if any, delete unnecessary boot entries with the bootcfg command. After performing these operations, retry mirroring setup. When using ETERNUS disk array units, see also "Boot disk mirroring setup or operation fails in the environment connecting ETERNUS" in "C.3 Troubleshooting." Addition of the EFI Boot Entry of the disk failed when the mirror disk was added, because of insufficient memory. group name: group disk name: disk Memory is insufficient, and in the process of adding the mirror disk disk, the EFI boot entry was not added. disk will be INVALID. Check memory use and, for example, exit some running applications to increase available memory. Additionally, if any, delete unnecessary boot entries with the bootcfg command. After performing these operations, remove disk once and add it again. For more information on how to remove disks, see "3.1.1 Preparing for Disk Swap (Removing Disks);" for more information on how to add disks, see "3.1.3 Restoring Disks after Swapping (Adding Disks)." 69

78 Appendix B Messages Addition of the EFI Boot Entry of the disk failed when the mirror disk was added, because an error occurred in a Windows API. group name: group disk name: disk A Windows API error occurred, and in the process of adding the mirror disk disk, the EFI boot entry was not added. disk will be INVALID. Check the event log or other relevant information for a system error and take action to resolve the error. Additionally, if any, delete unnecessary boot entries with the bootcfg command. After performing these operations, remove disk once and add it again. For more information on how to remove disks, see "3.1.1 Preparing for Disk Swap (Removing Disks);" for more information on how to add disks, see "3.1.3 Restoring Disks after Swapping (Adding Disks)." Addition of the EFI Boot Entry of the disk failed when the mirror disk was added, because a bootcfg command error occurred. group name: group disk name: disk A bootcfg command error occurred, and in the process of adding the mirror disk disk, the EFI boot entry was not added. disk will be INVALID. Check the number of disk partitions on the mirror source disk, and if 10 or more partitions exist, delete unnecessary ones to reduce the number to nine or less. Additionally, check the event log or other relevant information for a system error and take action to resolve the error. Additionally, if any, delete unnecessary boot entries with the bootcfg command. After performing these operations, retry mirroring setup. When using ETERNUS disk array units, see also "Boot disk mirroring setup or operation fails in the environment connecting ETERNUS" in "C.3 Troubleshooting." 70

79 B.2 Service Messages Internal error. An internal error occurred in the PSDM service. Collect information for troubleshooting and contact your local customer support An internal error occurred during editing of the EFI Boot Entry. group name: group disk name: disk In the process of editing the EFI boot entry, an internal error occurred in the PSDM service. Collect information for troubleshooting and contact your local customer support Changing of the EFI Boot Entry of the keep disk failed when the mirror group was created, because there was no valid Boot Entry. group name: group disk name: disk No valid EFI boot entry exists, and in the process of creating the mirror group group, the EFI boot entry of the mirror disk disk was not changed. Check the event log or other relevant information for a system error and take action to resolve the error. Additionally, with the bootcfg command, check the EFI entry and set the boot entry names properly. 71

80 Appendix B Messages B.2.3 Service Warning Messages (44XXX) The EFI Boot Entry of the disk was not deleted, because memory was insufficient when the mirror disk was deleted. group name: group disk name: disk Memory is insufficient, and in the process of removing the mirror disk disk, the EFI boot entry was not deleted. Check memory use and, for example, exit some running applications to increase available memory. Additionally, with the bootcfg command, delete the boot entry "~(MIRROR DISK Mirror Group Number Mirror Disk Number)" that was not deleted The EFI Boot Entry of the disk was not deleted, because an error occurred in a Windows API when the mirror disk was deleted. group name: group disk name: disk A Windows API error occurred, and in the process of removing the mirror disk disk, the EFI boot entry was not deleted. Check the event log or other relevant information for a system error and take action to resolve the error. Additionally, with the bootcfg command, delete the boot entry "~(MIRROR DISK Mirror Group Number Mirror Disk Number)" that was not deleted. 72

81 B.2 Service Messages The EFI Boot Entry of the disk was not deleted, because a problem occurred with the bootcfg command when the mirror disk was deleted. group name: group disk name: disk A bootcfg command error occurred, and in the process of removing the mirror disk disk, the EFI boot entry was not deleted. Check the event log or other relevant information for a system error and take action to resolve the error. Additionally, with the bootcfg command, delete the boot entry "~(MIRROR DISK Mirror Group Number Mirror Disk Number)" that was not deleted. When using ETERNUS disk array units, see also "Boot disk mirroring setup or operation fails in the environment connecting ETERNUS" in "C.3 Troubleshooting." The EFI Boot Entry of the disk was not deleted, because the EFI Boot Entry of the disk was not found when the mirror disk was deleted. group name: group disk name: disk In the process of removing the mirror disk disk, the EFI boot entry was not deleted. With the bootcfg command, delete the boot entry "~(MIRROR DISK Mirror Group Number-Mirror Disk Number)" that is unnecessary. If any boot entry is not unnecessary, no error has occurred and therefore no action is required. 73

82 Appendix B Messages The EFI Boot Entry of the valid system disk was not changed, because memory was insufficient when the mirror group was deleted. group name: group disk name: disk Memory is insufficient, and in the process of removing the mirror group group, the EFI boot entry name was not changed to the original boot entry name used before the mirroring configuration was set. Check memory use and, for example, exit some running applications to increase available memory. Additionally, with the bootcfg command, change the boot entry name "Original Boot Entry Name (MIRROR DISK Mirror Group Number Mirror Disk Number)" to "Original Boot Entry Name." The EFI Boot Entry of the valid system disk was not changed, because an error occurred in a Windows API when the mirror group was deleted. group name: group disk name: disk A Windows API error occurred, and in the process of removing the mirror group group, the EFI boot entry name was not changed to the original boot entry name used before the mirroring configuration was set. Check the event log or other relevant information for a system error and take action to resolve the error. Additionally, with the bootcfg command, change the boot entry name "Original Boot Entry Name (MIRROR DISK Mirror Group Number Mirror Disk Number)" to "Original Boot Entry Name." 74

83 B.2 Service Messages The EFI Boot Entry of the valid system disk was not changed, because a problem occurred with the bootcfg command when the mirror group was deleted. group name: group disk name: disk A bootcfg command error occurred, and in the process of removing the mirror group group, the EFI boot entry name was not changed to the original boot entry name used before the mirroring configuration was set. Check the event log or other relevant information for a system error and take action to resolve the error. Additionally, with the bootcfg command, change the boot entry name "Original Boot Entry Name (MIRROR DISK Mirror Group Number Mirror Disk Number)" to "Original Boot Entry Name." When using ETERNUS disk array units, see also "Boot disk mirroring setup or operation fails in the environment connecting ETERNUS" in "C.3 Troubleshooting." The EFI Boot Entry of the valid system disk was not changed, because the EFI Boot Entry of the disk was not found when the mirror group was deleted. group name: group disk name: disk In the process of removing the mirror group group, the EFI boot entry name was not changed to the original boot entry name used before the mirroring configuration was set. With the bootcfg command, change the boot entry name "Original Boot Entry Name (MIRROR DISK Mirror Group Number Mirror Disk Number)" to "Original Boot Entry Name." 75

84 Appendix B Messages The service has already been started. An instruction to start the service was sent but the service is already running. No action is required. B.2.4 Service Information Messages (46XXX) Service started. The service started Service stopped. Stopping the service succeeded When the mirror group was created, the EFI Boot Entry of the keep disk was changed. group name: group disk name: disk OS Friendly Name(before): entry1 OS Friendly Name(now): entry2 In the process of creating the mirror group group, the boot entry name of the mirror disk disk was changed from entry1 to entry2. 76

85 B.2 Service Messages When the mirror disk was added, an EFI Boot Entry was added. group name: group disk name: disk OS Friendly Name: entry1 The boot entry entry1 of the mirror disk disk added to the mirror group group was added When the mirror disk was deleted, the EFI Boot Entry was deleted. group name: group disk name: disk OS Friendly Name: entry1 The boot entry entry1 was removed. It is a boot entry of the mirror disk disk removed from the mirror group group. 77

86 Appendix B Messages When the mirror group was deleted, the EFI Boot Entry of the valid system disk was changed. group name: group disk name: disk OS Friendly Name(before): entry1 OS Friendly Name(now): entry2 In the process of removing the mirror group group, the boot entry name of the mirror disk disk was changed from entry1 to entry2. 78

87 B.3 Command Messages B.3 Command Messages This section describes command messages and explains what to do in response to the messages. Message output and viewing Command messages are output to the standard output and to the standard error output. (When the command prompt is used to execute commands, messages of the commands are displayed in the command prompt window.) Some messages are also output to the Windows event log. The event log can be viewed in Windows Event Viewer. To open Event Viewer, select [start]-[control Panel]-[Administrative Tools]-[Event Viewer]. Output format The command message output formats vary depending on the output destinations. command is the command name, number is the message number, severity is the severity level, and message is message text. For messages output to the standard/standard error output SDX: command: number: severity: message For messages output to the event log command: message 79

88 Appendix B Messages Variable description Italic texts in the messages denote variables and vary depending on the situations where the messages are output. The following table shows variables and the descriptions. Table B_5: Variable description Variable name arg attribute details device(s) disk(s) group item option seconds value Description Command operand Attribute name Detailed information Disk number Mirror disk name Mirror group name sdxinfo command output item name Command option Time in seconds Attribute value Severity Command messages are categorized into the following four types listed from higher to lower severity. Table B_6: Severity Message number Severity Description 60XXX ERROR This type of message is output to explain the cause of the failure when the command ends abnormally. 62XXX WARNING This type of message is output to give warning when an error that does not cause the command to end abnormally was detected. 64XXX INFO This type of message is output to provide information about command activities. 65XXX HELP This type of message is output to provide helpful information explaining corrective actions for proper command use. Generally, the command syntax is displayed. 80

89 B.3 Command Messages B.3.1 Command Error Messages (60XXX) option: Illegal option. The option option is invalid. Referring to the succeeding help message and "Appendix A Command Reference," set the correct option Syntax error. details The syntax of the executed command is wrong. Referring to the succeeding help message and "Appendix A Command Reference," set the options properly attribute: Invalid attribute name. The attribute name attribute is invalid. Referring to the succeeding help message and "Appendix A Command Reference," set the options properly. 81

90 Appendix B Messages attribute=value: Invalid attribute value. The attribute value value of the attribute attribute is invalid. Referring to the succeeding help message and "Appendix A Command Reference," set the option properly device: No such device found. No physical device was found based on the disk number device. Check the physical disk configuration with the sdxinfo -P command or "Disk Management," and specify the correct disk number disk: No such disk found. No disk was found based on the disk name disk. Check the physical disk configuration with the sdxinfo command, and specify the correct disk name group: No such group found. No mirror group was found based on the group name group. Check the mirroring configuration with the sdxinfo command, and specify the correct group name. 82

91 B.3 Command Messages device: Failed to get physical disk information. For the physical disk device, getting the geometry information, partition table, or device number failed. Check whether the physical disk device is operating normally Unable to proceed as the user does not have admin level privileges. Administrator privileges are required for this command execution. Log on as a user with administrator privileges (a user that belongs to the Administrators group) and execute the command Command terminated as it has reached the time out limit of seconds seconds. The command did not end in seconds, the time restriction, and timeout occurred. Retry the command Memory allocation error. An error occurred due to insufficient memory. Check memory use and, for example, exit some running applications to increase available memory, and retry the command. 83

92 Appendix B Messages Error occurred while calling a Windows API. A Windows API error occurred. Check the event log or other relevant information for a system error and take action to resolve the error, and then retry the command Another command is running. Another PSDM command is currently running. Wait until the running command ends, and retry the command No driver found. The PSDM driver is not running. If the system was not rebooted after the PSDM installation, reboot the system. In other situations, check the event log or other relevant information for a driver or system error and take action to resolve the error. After resolving the problem or error, retry the command Only one keep device is allowed, but more than one are specified. Two or more mirror source disks (keep disks) were specified and the mirroring configuration cannot be set. Specify only one disk as the mirror source disk. 84

93 B.3 Command Messages Device type keep is required, but none is specified. The mirror source disk was not specified and the mirroring configuration cannot be set. For the -p option of the sdxsysdisk -M command, specify :keep next to the mirror source disk number Driver error. An error occurred in the processing of the driver. Check PSDM messages in the event log and take corrective action. If you cannot identify the cause, collect information for troubleshooting and contact your local customer support Temporary driver error, please retry after a while. Due to insufficient memory or a conflict with another process, a temporary error occurred in the processing of the driver. Retry the command, and the next command execution may succeed. Wait for a while and retry the command The current number of groups has reached the limit. The number of mirror groups has reached the upper limit. As needed, reconfigure the mirroring. 85

94 Appendix B Messages Unable to add disks as the total number of disks would exceed the limit. The number of mirror disks has reached the upper limit. As needed, reconfigure the mirroring Unable to add more disks as the total number of mirrored disks in the group would exceed the limit. The number of mirror disks in the mirror group will exceed the upper limit and mirror group creation or mirror disk addition cannot be performed. As needed, reconfigure the mirroring The device device is already registered. The physical disk device is already managed by PSDM. Check the physical disk configuration with the sdxinfo -P command or "Disk Management," and specify the correct disk number The partition of the device device is not GPT. The partition table on the physical disk device is not the GPT and the disk cannot be mirrored. For mirroring of the physical disk device, change the partition table on device to the GPT. 86

95 B.3 Command Messages The device device is not a basic disk. The physical disk device is not a basic disk and the disk cannot be mirrored. For mirroring of the physical disk device, change device to a basic disk. Even if device is a basic disk, this message is output in a situation where multiple EFI system partitions exist. In that event, initialize device into a GPT basic disk All partitions on the device device are already in use. On the physical disk device, the number of partitions has reached the upper limit and the PSDM reserved partition cannot be created. For this reason, the disk cannot be mirrored. To use the physical disk device as the mirror source for mirroring, delete a partition on device There is not enough disk space left on the device device. Free space on the physical disk device is insufficient and the disk cannot be mirrored. In the end of the mirror source disk, 256 MB or more contiguous free spaces to create the reserved partition are required. To use the physical disk device as the mirror source for mirroring, delete unnecessary partitions to reserve 256 MB or more contiguous free spaces in the end of device. 87

96 Appendix B Messages Partition found on the device device. There are partitions on the physical disk device and the disk cannot be mirrored. To use the physical disk device as the mirror destination for mirroring, delete all partitions on device The size of the device device is different from the size of the keep device. The physical disk device is unequal to the mirror source disk in size and cannot be mirrored. Choose a disk that is equal to the mirror source disk in size as the mirror destination The group group is undergoing synchronization copying. For the mirror group group, synchronization copying is in execution, and no operation can be performed. Wait until the synchronization copying for group is completed, and perform the procedures The size of the device device is different from the size of the group group. The physical disk device is unequal to the mirror group group in size and cannot be added to group. To add a disk to group, choose a disk that is equal to group in size. The mirror group size means the smallest disk size in the mirror group. For the mirror group size, check the BLKS field in the sdxinfo -G command output. For the physical disk size, check the BLOCKS field in the sdxinfo -P command output. 88

97 B.3 Command Messages The disk disk is not a mirror disk. The disk disk is not a mirror disk. Check the disk configuration with the sdxinfo command, and specify the correct disk name Unable to remove the disk disk as it is the only VALID disk left in the group. If the disk disk is removed, no more VALID disk exists in the mirror group, and disk cannot be removed. To reduce the number of disks in a mirror group, leave one or more VALID disks in the mirror group. For the disk status, check the STATUS field in the sdxinfo -D command output. To remove all disks from a mirror group, set the -g option to the sdxsysdisk -R command and remove the entire mirror group The device device is not registered. The physical disk device is not managed by PSDM. Collect information for troubleshooting and contact your local customer support The system is waiting for reboot after removal of a group. A mirror group was removed and the system is now rebooting, and no command can be executed. Wait until the system is rebooted to execute the command. 89

98 Appendix B Messages The F6GASRV service has not been started. The PSDM F6GASRV service is not running and no command can be executed. If the system was not rebooted after the PSDM installation, reboot the system and then execute the command. If this message is output even after the system is rebooted, check the event log or other relevant information for a system or F6GASRV service error and take action to resolve the error, and then retry the command The F6GASRV service was not found. The PSDM F6GASRV service is not registered with the system, and no command can be executed. Perform the overwrite installation of PSDM Unable to retrieve the information item. Information displayed in the item field in the sdxinfo command output cannot be retrieved. Collect information for troubleshooting and contact your local customer support Internal error!(details) An internal error occurred. Collect information for troubleshooting and contact your local customer support. 90

99 B.3 Command Messages Illegal argument found: arg. The command operand arg is wrong. Referring to the succeeding help message and "Appendix A Command Reference," set the correct operand. If arg is given as follows, the cause of this error is an attempt of registration of three or more physical disks with a mirror group. Up to two physical disks can be registered with a mirror group. Format: X1:Y1,X2:Y2,...,Xn:Yn (Where n is an integer larger than 3, including 3, Xn is the physical disk number, and Yn is keep or undef) Example: 0:keep,1:undef,2:undef Failed to remove the group group. Removal of the mirror group group failed. Check the PSDM F6GADRV driver event log and take action to resolve the error. If the problem is not solved, collect information for troubleshooting and contact your local customer support Failed to reboot after group deletion. Please reboot manually. Rebooting the system after mirror group removal failed. If another user has locked the computer, this event occurs. Reboot the system immediately. 91

100 Appendix B Messages Failed to remove the disk disk from the group group. Removal of the disk disk from the mirror group group failed. Collect information for troubleshooting and contact your local customer support Failed to restart IO trace after taking kernel memory snap. Restarting I/O tracing after kernel log retrieval failed. Collect information for troubleshooting and contact your local customer support The device correspond to the disk disk is not found. There is no physical disk corresponding to the disk disk. Check whether physical disks are connected properly The device constituting the group group is not found. There is no physical disk corresponding to any one of the disks constituting the mirror group group. Check whether physical disks are connected properly. 92

101 B.3 Command Messages Found no VALID disk in the group group. No VALID disk exists in the mirror group group and no operation can be performed. Remove group, and restore the data as needed The reserved partition has already existed in the device device. The reserved partition is already on the physical disk device. The possible causes are as follows. Cause a: A mirror disk for another system has been mounted wrongly. Cause b: Reserved partition removal failed when device was removed from the mirror group. In the event of cause a, mount a correct disk. In the event of cause b, remove the reserved partition with the diskpart command Failed to reboot after disk deletion. Please reboot manually. Rebooting the system after the mirror disk removal failed. This event occurs if another user has locked the computer. Reboot the system immediately Could not find the required library. details Library load failed. PSDM may not be installed normally. Perform the overwrite installation of PSDM. 93

102 Appendix B Messages Memory allocation error. details An error occurred due to insufficient memory. Check memory use and, for example, exit some running applications to increase available memory, and retry the command Error occurred while calling a Windows API. details A Windows API error occurred and the command was terminated. Check the event log or other relevant information for a system error and take action to resolve the error, and then retry the command Internal error! details An internal error occurred. Collect information for troubleshooting and contact your local customer support. B.3.2 Command Warning Messages (62XXX) The disk is not mirrored since only one disk is registered in the group group. Only one disk exists in the mirror group and disk data redundancy is not achieved. Add mirror disks to the mirror group. For more information on how to add disks, see "3.1.3 Restoring Disks after Swapping (Adding Disks)." 94

103 B.3 Command Messages B.3.3 Command Information Messages (64XXX) System mirror has been created with the device devices, Group group Disk disks The mirror group group was created, and the physical disks devices were assigned the disk names disks and registered with group. The physical disks devices are mirrored The following disk has been added to group group, Device device Disk disk The physical disk device was assigned the disk name disk and added to the mirror group group. disk and the other disks in group are mirrored The group group will be removed. It is ready to remove the mirror group group. After the system is rebooted, group is removed The system will reboot automatically to complete the operation. To complete the mirror group removal, the system is automatically rebooted. 95

104 Appendix B Messages The disk disk has been deleted from the group group. The mirror disk disk was removed from the mirror group group After execution of this command, the system will reboot automatically. Do you want to proceed (yes/no)? After the group is removed, the system is automatically rebooted. Type yes to remove the group or no to cancel the removal process, and press the Enter key Command canceled by user The group removal process was canceled. This message is output in response to the "message 64206" if a value other than yes is input. B.3.4 Command Help Messages (65XXX) sdxsysdisk -M -p device[:type][,device[:type],...] sdxsysdisk -A -g group -p device,... [-e delay=msec] sdxsysdisk -R {-g group,... -d disk,...} This message shows how to use the sdxsysdisk command. For details, see "A.1 sdxsysdisk - Mirroring and unmirroring." Specify one or two physical disks with the -p option of the sdxsysdisk -M command. 96

105 B.3 Command Messages sdxinfo [-DG] [-e long] sdxinfo -P This message shows how to use the sdxinfo command. For details, see "A.2 sdxinfo - Disk configuration and status viewing." sdxsnap [-k] [-d dir] This message shows how to use the sdxsnap command. For details, see "A.3 sdxsnap - Collection of information for troubleshooting." 97

106 Appendix B Messages 98

107 Appendix C Notes C.1 System Design/Implementation Partition configuration The ESP and the boot partition must be on the same disk. Partition size The MB for the reserved partition size (256 MB) and the partition size set in the "Hard Disk" window of ScWL or Installation Support Tool is 1024 * 1024 bytes. In contrast, the GB for the Fujitsu's PRIMEQUEST internal disk size (73 GB or 147 GB) is 1000 * 1000 * 1000 bytes. Pay attention to this difference when estimating the partition size. OS installation For installing the OS, free disk space for the reserved partition must be reserved. When you install the OS using ScWL or Installation Support Tool, do not select "Auto" in the "Hard Disk" window. If "Auto" is selected, free space for the reserved partition is not reserved. FC (Fibre Channel) cards For connecting FC cards to PRIMEQUEST, the BIOS Boot option for the EFI driver must be set to the default value, Disabled. For the EFI driver setting method, see the "PRIMEQUEST 500/400 Series Installation Manual" (C122-E001). 99

108 Appendix C Notes C.2 Operation/Maintenance EFI boot entry setting After setting up mirroring of the boot disk, unless you are instructed to do so to deal with an error as described in "Appendix B Messages," do not change the EFI boot entry using the bootcfg command. If the EFI boot entry is manually changed, EFI boot entry automatic setting by PSDM may not function normally and thus the EFI boot entry may become corrupted. Windows "Disk Management" and the diskpart command If mirroring is set up, the mirror destination disk is no longer recognized by "Disk Management" or the diskpart command and thus is protected against accidental operation. Note, however, that if "Disk Management" or the diskpart command was active when the mirroring was set, the mirror destination disk is still recognized and is not protected against accidental operation. Therefore, before setting up mirroring or adding mirror disks, exit "Disk Management" or the diskpart command if it is active. Partition operations on a mirror disk On a mirror disk, partition addition, removal, or property modification cannot be performed. To add or remove mirror disk partitions or edit the properties, unset the mirroring configuration in advance. Disk write caching Mirror disk write caching is enabled for the copy destination disk of synchronization copying and disabled for the other disks. Do not change the setting of disk write caching for mirror disks. Disk double failure If no more VALID disk exists in a mirror group, remove the mirror group immediately and replace the faulty disk with another or restore the data as needed. If the system is rebooted in a situation where no VALID disk exists in a mirror group, EFI boot entry renaming, removal of disk partitions on disks other than the read disk, or drive letter allocation may not be done. In that event, edit the EFI boot entry names with the bootcfg command, and remove unnecessary partitions and allocate the drive letter with "Disk Management" or the diskpart command to restore the system to the normal state. 100

109 C.2 Operation/Maintenance System shutdown and reboot Before shutting down or rebooting the system, remove ERROR mirror disks from the mirror group. For operating the system using the script to reboot the system periodically and automatically, a process to remove ERROR disks before rebooting the system must be added to the script. Use the script sample stored in \PSDM\sample\autoreboot.bat on the product CD as an example. Crash dump A dump taken when a Windows crash occurs is collected on the boot disk. For this reason, the following point must be noted. When rebooting the system immediately after the system abended, do not perform boot disk selection. If the system is booted from a disk different from the previous boot disk, no dump file is generated. If the sub disk in the boot group is the read disk, a crash dump is not generated when the system fails. To enable crash dump collection, reboot the system or replace the faulty boot disk with another. For more information on how to identify the read disk, see "1.5 Mirror Group States." Recovery Console Recovery Console does not activate the PSDM driver and so synchronization of mirrored data will no longer be ensured. When using Recovery Console, unset the mirroring by removing all reserved partitions with the diskpart command. 101

110 Appendix C Notes C.3 Troubleshooting Boot disk mirroring setup or operation fails in the environment connecting ETERNUS. [] If the following conditions are all satisfied, an error may occur in the mirroring setup or operation. Additionally, under these circumstances, the mirror destination disk may become INVALID after synchronization copying or resynchronization copying is completed. 1. The ETERNUS multipath driver is not in use. 2. The ETERNUS disk array unit is connected or disconnected during system operation or ETERNUS is not recognized by the system due to its malfunction. 3. The system has not been shut down after 2. If the conditions 1. to 3. are satisfied, the OS bootcfg command will not function normally, and thus, EFI boot entry addition and deletion will fail, which causes this error. The above event is assumed to be the cause if: The system log in the event log contains the error message or or the warning message or for the service (F6GASRV). Executing the bootcfg command with no option setting in the command prompt returns "(null)" as a value for the "BootFilePath" to the current boot entry. [] Perform the following procedures for restoration. 1. Shut down the system. 2. Restore the failed component if an ETERNUS disk or cable is faulty. 3. Reboot the system. 4. Take action responding to the message (42008, 42011, 44002, or 44006) for the service (F6GASRV) output in the system log in the event log. For the resolutions relevant to the service messages, see "B.2 Service Messages." 102

111 Glossary [B] basic disk A type of disk organization in Windows. The other type of organization is a dynamic disk. boot disk The disk where the boot partition resides. To use PSDM, the ESP must also be on the boot disk. Disk Management A Windows system utility used for disk and partition management. To open the Disk Management window, select [Start]-[Control Panel]-[Administrative Tools]-[Computer Management]-[Disk Management]. [E] boot group The mirror group to which the boot disk belongs. EFI Extensible Firmware Interface Firmware used to start up (boot) the OS. boot partition The partition where system files configuring Windows are stored. This partition is usually C:. [D] data disk Disks other than the boot disk. data group The mirror group to which data disks belong. EFI boot entry The boot option provided on the EFI Boot Manager menu. Choose a boot option on the EFI Boot Manager menu to select the boot disk. EFI menu The EFI Boot Manager menu window. EFI System Partition The special partition on a GPT disk to store files required for OS startup (boot). dirty shutdown An abnormal shutdown of the system caused, for example, by disconnection of the power to the computer or an abnormal end of the system due to a hardware or software failure. ESP GPT [G] EFI System Partition An abbreviation for EFI System Partition. Globally unique identifier Partition Table The type of partitioning system that the EFI supports. 103

112 Glossary JRM [J] Just Resynchronization Mechanism An abbreviation for Just Resynchronization Mechanism. MSR partition MicroSoft Reserved partition An abbreviation for a Microsoft reserved partition. This is a disk area reserved on every disk for Windows to use. These partitions are not displayed in "Disk Management." just resynchronization The high-speed resynchronization copying carried out by the Just Resynchronization Mechanism. Just Resynchronization Mechanism A mechanism that realizes high-speed resynchronization by initiating the copy from the region that may be out-of-sync due to the failure instead of replicating the entire disk data. PSA [P] PRIMEQUEST Server Agent System management software to perform PRIMEQUEST hardware fault monitoring and configuration management. This is essential software for PRIMEQUEST and provided with PRIMEQUEST hardware. [M] master disk The only disk in a mirror group whose partition configuration can be viewed with "Disk Management" or the diskpart command. mirror disk A disk registered with a mirror group. mirror group A unit of disks to be mirrored. Mirror disks registered with a mirror group are mirrored one another. MMB Management Board An abbreviation for the server management board. This is a system control unit whose tasks include control and monitoring of PRIMEQUEST resources, partition management, and system initialization. [R] read disk The only disk in a mirror group from which data is read out. reserved partition A disk partition that stores mirroring management information. This is automatically created in the end of a disk configured for mirroring. The size is 256 MB. resynchronization copying To copy data between mirror disks to recover the mirroring state when the system is rebooted, for example, after it was down. [S] ScWL SystemcastWizard Lite Software to install the OS and back up and restore hard disks via the network. This is provided with PRIMEQUEST hardware. 104

113 Glossary sub disk Disks other than the master disk in a mirror group. synchronization The state where mirroring is operating normally. synchronization copying To copy data in a mirror group to mirror disks added to the mirror group in order to set up mirroring or to increase the multiplicity of the mirroring configuration. system disk A synonym of the boot disk. [W] Web-UI Web User Interface An abbreviation for Web User Interface. This is an interface that uses a Web browser for displaying information to users and for user operations. 105

114 Glossary 106

115

116