Veritas Storage Foundation lists the status of a disk as "failing" in response to errors that are detected while reading or writing to a disk. The status is designed to draw administrative attention to disks that have experienced errors. Reviewing the status of the disks in the disk array, as well as any connected storage area network (SAN) components, is recommended to determine if a hardware problem exists.
Since it is possible for a disk to be flagged as "failing" in response to an isolated event, this status does not necessarily mean that the disks have a hardware problem.
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 auto:sliced rootdg01 rootdg online
c0t1d0s2 auto:sliced rootdg01 rootdg2 online failing
|This article is a part of a set on troubleshooting failed, or failing, disks. Click here to start at the beginning: http://www.symantec.com/docs/TECH200618|
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.
Use vxedit to clear the "failing" status (Figure 1):
Figure 1 - Using vxedit to clear the "failing" status
vxedit -g <diskgroup> set failing=off <disk_media_name>
Example, with typical output:
Vxdisk now shows that the "failing" status has been cleared: