Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
We are experiencing file access problems that result in an error message (on Windows) that says disk error. An ex-employee says that this has occurred before and was resolved by determining where the problem was, breaking the mirror, reformatting the "bad" disk, and recreating the mirror. Does this make sense? If so, how can I determine where the problem is and what mirror to "break" and what disk to format?

Hi, this seems that your disk might be physically damaged. This you can make sure by executing the following command. Assume that d10 is your mirror point which is made out of d11 & d12.
# metastat d10
You can see the status of any of the sub-mirror or both the sub mirror if they are having physical issues attached with d10.To Break the mirror
------------------
# umount /mirror# metadetach d10 d12
then mount d10 on top of some other mount moint and transfer the data and create filesystem and then attach with primary mirror again.
# mount /dev/md/dsk/d10 /tmp_mnt
# cd /tmp-mnt
# cp -r * /tmp_data# umount /tmp_data
# newfs /dev/md/rdsk/d10
# newfs /dev/md/rdsk/d12# metattach d10 d12
After completion of successfull sync, mount d10 again on top of original mount point.
# mount /dev/md/dsk/d10 /mirror
# cd /tmp_data
# cp -r * /mirrorThats it. hope this would help you.
:)
Ganesh

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |