Article ID: 194351 - View products that this article applies to.
This article was previously published under Q194351
This article has been archived. It is offered "as is" and will no longer be updated.
If the system experiences a failure on a mirror set, Windows NT will break the mirror and orphan the faulty drive. There may be a situation where bad data is passed back to applications after breaking the mirror. This can cause a variety of problems, such as application problems and read media errors on a healthy disk.
In addition to symptoms
Although one of the mirrored disks was orphaned because of hardware failure, users continue to use the system without replacing the failed disk and re-creating the mirror set. During this time, disk I/O is suppose to be performed only from the partition of the healthy disk.
If an application requests data from the disk, and a read I/O error is encountered on the healthy disk, Ftdisk.sys erroneously retrieves data from the orphaned disk, which results in unreliable data from the orphaned disk being returned to the application as reliable data.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/152734/EN-US/ )How to Obtain the Latest Windows NT 4.0 Service Pack
To work around the problem, before you shut down the server and replace the disk, you should manually break the mirror set in Disk Administrator.
For additional information, please see the following article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/120227/EN-US/ )Steps to Recover a Failed Mirrored System/Boot Partition
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.