| PRIMECLUSTER Global Disk Services Configuration and Administration Guide 4.1 (Solaris(TM) Operating System) |
|
Contents
|
| Appendix F Troubleshooting | > F.1 Resolving Problems |
The following description shows resolutions to problems relevant to system disks on which the file systems / (root), /usr, and /var operates.
In one of the following circumstances, take action as indicated for the relevant situation.
Mirroring the system disk will protect data in case one of the physical disks crashes. However, to restore data damaged by critical failures caused by multiple breakdown or misoperation, you must create backup data in advance.
See "Backing Up."
For some reason, the system disk data is invalid. You must restore data from the backup data created in advance.
See "Restoring (When the System Can Be Booted)."
Even when you have the system disk mirrored, you may experience unsuccessful booting. For example, you may encounter such a problem when the file accessed during the booting process in the boot disk is physically damaged, or when a disk is swapped improperly. If the console message of the unsuccessful boot disk indicates such is the case, try booting from the other boot disk, i.e. the mirror disk.
1) Confirm the name of the mirror disk. Use the OpenBoot ok prompt shown below.
|
ok printenv boot-device |
In this example, the original disk name is /pci@1f,4000/scsi@3/disk@0,0:a, which is indicated on the left. The mirror disk is /pci@1f,4000/scsi@3/disk@1,0:a. When mirroring is configured with three-way or more multiplexing, multiple mirror disks exist.
2) Boot from the mirror disk.
|
ok boot /pci@1f,4000/scsi@3/disk@1,0:a |
3) If booting is successful, find out what caused the original disk to fail, and recover by swapping the disk.
For details on disk swapping, see "sdxswap - Swap disk" and resolutions described in "Disk Swap."
When the procedures above cannot resolve the problem, causes other than data errors in the original boot disk unit may exist, or data errors may also exist in the mirror disk.
If it would appear that data errors also exist in the mirror disk, see "System cannot be booted (Boot disk data damage)."
For some reason, the system disk data is invalid. You must restore data from the backup data created in advance. If restoring data from the mirror disk was unsuccessful, follow the procedures shown below.
See "Restoring (When the System Cannot Be Booted)."
By mirroring system disks, the system's boot disk device name (boot-device parameter) is automatically set and updated. However, in some systems GDS cannot recognize correct device names and thus sets incorrect device names. In that event, the following console message is output and booting the system fails.
|
ok boot |
In this example the boot disk device name is "/ssm@0,0/pci@18,700000/pci@1/scsi@2/sd@0,0:a", but the correct device name is "/ssm@0,0/pci@18,700000/pci@1/scsi@2/disk@0,0:a" and thus booting the system fails.
Create the bootdevtab file (boot disk device name file) for proper device name configuration.
1)Specify the correct boot device name and boot the system.
|
ok boot /ssm@0,0/pci@18,700000/pci@1/scsi@2/disk@0,0:a |
For the correct boot disk device name, perform the following.
1-1) View device names of disks connected to the system.
For the following procedures, make a copy of the displayed results.
|
ok show-disks
|
1-2) Based on a) in the displayed results, "/ssm@0,0/pci@18,700000/pci@1/scsi@2/sd@0,0:a" should be replaced with "/ssm@0,0/pci@18,700000/pci@1/scsi@2/disk@0,0:a" as that is the correct boot disk device name.
2) Create the bootdevtab file.
2-1) Create a template.
|
# sdxinfo -x BootDev > /tmp/bootdevtab |
2-2) Edit the template.
|
# vi /tmp/bootdevtab
|
Specify the physical disk name in the first field.
Specify the corresponding boot disk device name in the second field. Neither field requires partition assignment, such as s0 and :a.
To the template a boot disk device name assumed by GDS will be output. If the output boot disk name is incorrect, replace it with the correct device name. The correct device name can be checked as described in 1-1) through 1-2). Note that two boot disk device names may be output. In that event, delete one of the names and replace the remaining one with the correct device name.
Separate one field from another in space or tab delimited format. Lines starting with the number sign (#) are assumed as comments.
All disks registered with a root class are output to the template.
Specify disks that may be used as the boot disk in the bootdevtab file. The relevant disks are:
Original boot disk
Mirror disk
Spare disk connected to a boot disk's group
Boot and spare disks in an alternative boot environment
(When using the system volume snapshot function of PRIMECLUSTER GDS Snapshot)
Do not specify the following disks in the bootdevtab file. Delete them from the bootdevtab file or comment out the relevant lines. Leaving them unedited will not affect the operation.
Disks not used as the boot disk
Disks for which GDS correctly assumed the boot disk device name and no assignment in the bootdevtab file is required
When FC-AL internal disks are swapped, the boot disk device name changes. Declare as follows so that recreation of the bootdevtab file is not required every time disks are swapped. Put the asterisk (*) after the last at mark (@). GDS will then complement the asterisk portion automatically.
| Before edit : c0t0d0 /ssm@0,0/pci@1d,700000/SUNW,qlc@1/fp@0,0/ssd@w50020f230000798c,0 After edit : c0t0d0 /ssm@0,0/pci@1d,700000/SUNW,qlc@1/fp@0,0/disk@* |
2-3) Place the template in the /etc/opt/FJSVsdx/lib directory.
|
# cd /etc/opt/FJSVsdx/lib |
2-4) Confirm that the bootdevtab file was created normally.
|
# sdxinfo -x BootDev c0t0d0 /ssm@0,0/pci@18,700000/pci@1/scsi@2/disk@0,0 |
Check whether the boot disk device name is output normally.
3) Check whether the system's boot disk device name (boot-device parameter) is set normally.
3-1) Stop the system and specify the correct boot disk device name.
|
# init 0 ~ |
3-2) Check the boot-device parameter values.
|
# eeprom boot-device boot-device=/ssm@0,0/pci@18,700000/pci@1/scsi@2/disk@0,0:a \ |
In the boot-device parameter, the device name of the boot device where synchronization copying is complete is set. If synchronization copying is incomplete, perform the check after it is complete.
To add a disk to the root class and specify the disk in the bootdevtab file, before connecting to the disk to a group, re-create the bootdevtab file according to the procedures described in 2).
When the disk is connected to a group and synchronization copying is complete, the boot disk device name is added to the boot-device parameter.
When the bootdevtab file is not re-created before synchronization copying is complete, a boot disk device name assumed by GDS is added to the boot-device parameter when the synchronization copying ends. In that event, re-create the bootdevtab file and set the correct boot disk device name as follows. Alternatively, reboot the system for proper boot disk device name configuration.
|
# eeprom boot-device boot-device=... /ssm@0,0/pci@18,700000/pci@1/scsi@2/sd@1,0:a
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
(Incorrect boot disk device name)
# eeprom boot-device="... /ssm@0,0/pci@18,700000/pci@1/scsi@2/disk@1,0:a"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
(Correct boot disk device name) |
|
Contents
|