Error Failed To Hot Remove Scsi Disk System Error
Contents |
Software Issues Identifying a Failed or Failing Component Troubleshooting Bad Stripe Warnings Recovering From a Disk Drive Failure Understanding Hot-Plug Limitations and Conditions Rebuilding Logical https://docs.oracle.com/cd/E23383_01/html/E23089-01/chapter13.html Drives Solving Notification Problems Creating a Support Archive File Understanding Error and http://h41379.www4.hpe.com/doc/82final/6318/6318pro_024.html Warning Messages Troubleshooting Potential Software Issues If you experience problems installing or using the Sun StorageTek RAID Manager software, follow these suggestions: Ensure that you are logged into the Sun StorageTek RAID Manager software at the permission level you need to perform the tasks you want. (See Understanding error failed Permission Levels for more information.) Ensure that all managed systems are powered on and that you are logged in to any remote systems you want to manage. (See Understanding Permission Levels for more information.) Check all cable connections. Try uninstalling and reinstalling the Sun StorageTek RAID Manager software. Identifying a Failed or Failing Component When a Warning- or Error-level event occurs, error failed to use the rapid fault isolation feature of the Sun StorageTek RAID Manager software to quickly identify the source of the problem. For instance, in this example, a disk drive has failed. To find the failed disk drive, follow the yellow Error icons. FIGURE 12-1 Using Icons to Identify Failures Troubleshooting Bad Stripe Warnings This section describes what to do when a bad stripe warning is generated in the software. The section contains the following topics: Understanding Why Bad Stripe Warnings Occur Addressing Bad Stripe Warnings Preventing Bad Stripe Warnings From Occurring Understanding Why Bad Stripe Warnings Occur When the software tracks stripes across a logical drive and that drive contains invalid or incomplete data, the software displays a Warning-level status icon (yellow triangle with an exclamation point) next to the drive in a Bad Stripe table. This table is stored in an area that is reserved for configuration information on each physical disk grouped into an array that hosts one or more logical drives. There is a separate Bad Stripe table for each logical drive. A bad stripe
on the same SCSI bus: For versions prior to OpenVMS Alpha Version 7.2, a node's access to a disk will not fail over from a direct SCSI path to an MSCP served path. There is also no failover from an MSCP served path to a direct SCSI path. Normally, this type of failover is not a consideration, because when OpenVMS discovers both a direct and a served path, it chooses the direct path permanently. However, you must avoid situations in which the MSCP served path becomes available first and is selected by OpenVMS before the direct path becomes available. To avoid this situation, observe the following rules: A node that has a direct path to a SCSI system disk must boot the disk directly from the SCSI port, not over the LAN. If a node is running the MSCP server, then a SCSI disk must not be added to the multihost SCSI bus after a second node boots (either by physically inserting it or by reconfiguring an HSZxx). If you add a device after two nodes boot and then configure the device using SYSMAN, the device might become visible to one of the systems through the served path before the direct path is visible. Depending upon the timing of various events, this problem can sometimes be avoided by using the following procedure: $ MCR SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER SYSMAN> IO AUTOCONFIGURE To ensure that the direct path to a new device is used (including HSZxx virtual devices), reboot each node after a device is added. For versions prior to OpenVMS Alpha Version 7.2, if there are two paths to a device, the $DEVICE_SCAN system service and the F$DEVICE lexical function list each device on a shared bus twice. Devices on the shared bus are also listed twice in the output from the DCL command SHOW DEVICE if you boot a non-SCSI system disk. These double listings are errors in the display programs. They do not indicate a problem or imply that the MSCP served path is being used instead of the direct SCSI path. When a system powers up, boots, or shuts down, it resets the SCSI bus. These resets cause other hosts on the SCSI bus to experience I/O errors. For Files-11 volumes, the Mount Verification facility automatically recovers from these errors and completes the I/O. As a result, the user's process continues to run without error. This level of error recovery is not possible for volumes that are mounted with the /FOREIGN qualifier. Instead, the user's process receives an I/O error notification if it has I/O outstanding when a bus reset occurs. If possible, avoid mounting foreign devices on multihost SCSI buses. If foreign devices are mounted on the shar