The default behavior of Windows is to attach and mount every logical unit that it detects when the HBA driver loads. If multiple hosts mount the same disk, file system damage can occur. It is up to the configuration of the SAN to insure that only one host can access a particular logical disk at a time.
Symptoms of multiple hosts accessing the same logical disk are: Disk Management displays the same logical disk on multiple hosts. Plug and Play notification that new hardware is found may occur on multiple hosts when you add or configure a new logical disk. When you try to access a logical disk by using My Computer or Windows Explorer, you may receive an "Access Denied", "Device not Ready", or similar error message that may indicate that other hosts have access to the same logical disk.
Your computer stops responding hangs or has slow response times. This can indicate that there is a high latency to the pagefile, and this may be accompanied by events in the System Log such as:. If the preceding error messages are in the System Log, it indicates that Windows was trying to access a disk and there was a problem.
If the disk that is referenced is on the SAN, it could indicate a latency issue. If an Event ID 51 is shown, this indicates that Memory Manager was attempting to copy data to or from memory and had a problem. Another indicator of pagefile latency issues is if the Windows server has a system failure, and either of the following error messages are displayed on a blue screen:. A possible resolution is to place the pagefile on the host's local hard disk.
Windows needs reliable access to the pagefile as data is paged in or out of memory. Having the pagefile local to the host guarantees that access is not influenced by other devices and hosts on the SAN. A Memory. For information about how to configure your computer for a crashdump, see Windows Help. There are several ways to resolve the preceding problems.
The first method is to try and correlate the time with any events that are occurring on the SAN. Another example is if HostB produces errors whenever HostA is rebooted. These can often be corrected by reconfiguring the SAN, and this requires the assistance of the hardware vendor. Any type of latency issues might be resolved by placing pagefile on the Windows server's local hard disk, but again, this disables the creation of a memory dump.
A key point to understand is that the hardware vendor of the SAN will have the most information about the proper configuration, and must be the first point of contact for all configuration questions and concerns. Skip to main content. This browser is no longer supported. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy. See the Setup log files for more information. Windows is unable to install to a RAW disk with multiple physical paths. If the boot LUN is presented on a single physical path or if the boot LUN has already been initialized prior to installing Windows, Setup will proceed as expected. Configure a single path to the boot LUN when installing Windows.
This method is ideal for scenarios where physically disconnecting the additional SAN connections isn't possible or is difficult. In multiple-path disk configurations Windows Setup doesn't recognize a disk as bootable until the disk is initialized and the disk signature is present. To initialize the boot LUN and prepare the disk for Windows Setup, you must create a new partition and then delete the newly created partition.
0コメント