Check if there’re any recoverable issues regarding the read operation’s failure, and resolve them accordingly. You might need to contact the corresponding vendor for storage connectivity issues such as  issues with physical port, hardware issue, and so on.

For example, to check whether the underlying disk is not available, enter:

vxprint –g diskgroup_name volume_name

If the subdisk is in NODEVICE state, the underlying disk of volume is not available or seen by the operating system due to storage connectivity issues.

After you fix the issue, restart the recovery manually:

• For single node setup, enter:

# vxrecover

• For cluster setup, on Master node, enter:

# vxrecover –c –s

If and only if the READ error persists due to unrecoverable issues such as bad sectors on disks, should you do as follows in order:

1. Remove the plex that is in DETACHED state due to READ error from its associated volume. Enter:

# vxplex -g diskgroup -o rm dis plex

2. Create a new plex using other free disks or storage. Enter:

# vxmake -g diskgroup plex plex sd=subdisk1[,subdisk2,...]

3. Attach the plex to the volume on which the synchronizing read loop fails. Enter:

# vxplex -g diskgroup] att volume plex