|
This article is a part of a set on troubleshooting failed, or failing, disks. Click here to start at the beginning:
|
Note: "Failing" should
not be confused with "failed was." This is a different status. Further
information on the "failed was" status can be found here:
1. Check the disk array as well as any connected SAN components for hardware problems.
2. Review the messages log, for the operating system, for events that refer to disk read and write errors.
3. If no persistent I/O errors are discovered, it may be that the
"failing" status was triggered by transient error rather than a truly
failing disk. In this case, you can simply clear the status. If the
failing status continues to reappear for the same disk, it may be a
sign that there is genuine, hardware problem with the disk, or with the
SAN connectivity.
Note: If the "failing"
status appears to be a genuine problem, and not just a transient
error, the disk may be replaced. Information about replacing failing
disks can be found here:
Use vxedit to clear the "failing" status (Figure 1):
Figure 1 - Using vxedit to clear the "failing" status
Syntax:
vxedit -g set failing=off
Example, with typical output:
# vxedit -g rootdg2 set failing=off rootdg01
Vxdisk now shows that the "failing" status has been cleared:
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 auto:sliced rootdg01 rootdg online
c0t1d0s2 auto:sliced rootdg01 rootdg2 online
|
