I have a Windows SBS 2003 Premium R2 Server
I had to replace the MoBo because two of the SATA controllers failed. AS a result, the 2 Windows 500GB Mirror Sets C: Boot & D: Data were out of sync.
After replacing the MoBo things worked fine, I re-mirrored the C and D drives successfully. Disk manager reported Healthy partitions after re-syncing.
The next time I re-booted the server, a week later, the system would not boot. Although all the drives were recognized in the BIOS I am now getting “A disk read error has occurred” in the post.
I unplugged both master D and D mirror and the C mirror and booted to the master C drive. I was able to boot into the OS. So I shutdown and plugged in the master D drive oping to have one boot and one data drive functioning. But the “A disk read error has occurred” message returned.
So, then I unplugged the D drive and tried to boot back into just the one C drive as that we previously successful. No such luck, the “A disk read error has occurred” happened again.
Any suggestions on how to resolve this issue?
I had to replace the MoBo because two of the SATA controllers failed. AS a result, the 2 Windows 500GB Mirror Sets C: Boot & D: Data were out of sync.
After replacing the MoBo things worked fine, I re-mirrored the C and D drives successfully. Disk manager reported Healthy partitions after re-syncing.
The next time I re-booted the server, a week later, the system would not boot. Although all the drives were recognized in the BIOS I am now getting “A disk read error has occurred” in the post.
I unplugged both master D and D mirror and the C mirror and booted to the master C drive. I was able to boot into the OS. So I shutdown and plugged in the master D drive oping to have one boot and one data drive functioning. But the “A disk read error has occurred” message returned.
So, then I unplugged the D drive and tried to boot back into just the one C drive as that we previously successful. No such luck, the “A disk read error has occurred” happened again.
Any suggestions on how to resolve this issue?