Veritas Cluster Server Bundled Agents Reference Guide
Veritas⢠Cluster Server Bundled Agents Reference Guide - Symantec Veritas⢠Cluster Server Bundled Agents Reference Guide - Symantec
180 Troubleshooting bundled agents Troubleshooting storage agents There is/are folder mount(s) mounted on the same drive. Folder mount = folder_mount. Error :Error_code. Volumes information could be incomplete. More than one folders are mounted on the same drive. Recommended Action: Make sure no additional folders are mounted on the specified drive. The configured Volume is also mounted as a drive letter. Failed to get the Drive letter. Error : Error_code Recommended Action: Unmount the volume or specify another volume information. The configured Volume is also mounted as a drive letter drive_letter. Recommended Action: Unmount the volume or specify another volume information. Validate disk partition failed. Error : Error_code This is a VCS internal error. Recommended Action: Contact Symantec Technical Support. Could not find the Disk with number disk_no. Error : Error_code This is a VCS internal error. Recommended Action: Contact Symantec Technical Support. Unabletolockthevolume.DiskNo.= disk_no,PartitionNo= partition_no.Error : Error_code The agent could not lock the volume while dismounting, indicating a potential hardware error or that other applications are accessing the volume. Recommended Action: Verify that no other applications, including Windows Explorer, are accessing the volume. Verify the installed disk and the configured partition. Set the ListApplications attribute to 1 to obtain a list of applications that are accessing the volume. Failed to unlock the volume. Disk No. = disk_no, PartitionNo =partition_no. Error : Error_code The agent could not unlock the volume while dismounting, indicating a potential hardware error or that other applications are accessing the volume. Recommended Action: Ensure that no other applications, including Windows Explorer, are accessing the volume. Verify the installed disk and the configured partition. Contact Symantec Technical Support if the problem persists.
Troubleshooting bundled agents Troubleshooting storage agents 181 Failed to mount the volume. Disk No. = disk_no, PartitionNo =partition_no. Error : Error_code This is a VCS internal error. Recommended Action: Contact Symantec Technical Support. Failed to dismount the volume. Disk No. = disk_no, PartitionNo =partition_no. Error : Error_code This is a VCS internal error. Recommended Action: Contact Symantec Technical Support. Could not access the volume. Disk No. = disk_no, PartitionNo = partition_no Mount Path = Mount_path. Error : Error_code The specified device path is inaccessible, indicating a potential hardware error. Recommended Action: Verify the installed disk and the configured partition. Also make sure no other application is accessing the volume. Set the ListApplications attribute to 1 to obtain a list of applications that are accessing the volume. Failed to unmount the volume. Disk No. = disk_no, PartitionNo = partition_no Mount Path = Mount_path. Error : Error_code This is a VCS internal error. Recommended Action: Contact Symantec Technical Support. File system is dirty. Cannot online the resource. Unmounting the volume. Error : Error_code The filesystem at the specified driver letter or mount path is not clean. Recommended Action: Set the AutoFSClean to 1 if you want the agent to clean the filesystem. Otherwise, clean the filesystem manually. Drive letter drive_letter is not assigned Exit code : Exit_code This is a VCS internal error. Recommended Action: Contact Symantec Technical Support. Failed to flush the Volume. Error : Error_code This is a VCS internal error. Recommended Action: Contact Symantec Technical Support. Failed to get the application log information. Error : Error_code The agent could not find the name of the application accessing the volume.
- Page 129 and 130: Chapter 7 VCS infrastructure and su
- Page 131 and 132: VCS infrastructure and support agen
- Page 133 and 134: VCS infrastructure and support agen
- Page 135 and 136: VCS infrastructure and support agen
- Page 137 and 138: VCS infrastructure and support agen
- Page 139 and 140: VCS infrastructure and support agen
- Page 141 and 142: VCS infrastructure and support agen
- Page 143 and 144: VCS infrastructure and support agen
- Page 145 and 146: VCS infrastructure and support agen
- Page 147 and 148: VCS infrastructure and support agen
- Page 149 and 150: VCS infrastructure and support agen
- Page 151 and 152: VCS infrastructure and support agen
- Page 153 and 154: VCS infrastructure and support agen
- Page 155 and 156: VCS infrastructure and support agen
- Page 157 and 158: VCS infrastructure and support agen
- Page 159 and 160: VCS infrastructure and support agen
- Page 161 and 162: Chapter 8 VCS hardware replication
- Page 163 and 164: VCS hardware replication agent for
- Page 165 and 166: VCS hardware replication agent for
- Page 167 and 168: VCS hardware replication agent for
- Page 169 and 170: VCS hardware replication agent for
- Page 171 and 172: Chapter 9 Troubleshooting bundled a
- Page 173 and 174: Troubleshooting bundled agents Trou
- Page 175 and 176: Troubleshooting bundled agents Trou
- Page 177 and 178: Troubleshooting bundled agents Trou
- Page 179: Troubleshooting bundled agents Trou
- Page 183 and 184: Troubleshooting bundled agents Trou
- Page 185 and 186: Troubleshooting bundled agents Trou
- Page 187 and 188: Troubleshooting bundled agents Trou
- Page 189 and 190: Troubleshooting bundled agents Trou
- Page 191 and 192: Troubleshooting bundled agents Trou
- Page 193 and 194: Troubleshooting bundled agents Trou
- Page 195 and 196: Troubleshooting bundled agents Trou
- Page 197 and 198: Troubleshooting bundled agents Trou
- Page 199 and 200: Troubleshooting bundled agents Trou
- Page 201 and 202: Troubleshooting bundled agents Trou
- Page 203 and 204: Troubleshooting bundled agents Trou
- Page 205 and 206: Troubleshooting bundled agents Trou
- Page 207 and 208: Troubleshooting bundled agents Trou
- Page 209 and 210: Troubleshooting bundled agents Trou
- Page 211 and 212: Troubleshooting bundled agents Trou
- Page 213 and 214: Troubleshooting bundled agents Trou
- Page 215 and 216: Troubleshooting bundled agents Trou
- Page 217 and 218: Troubleshooting bundled agents Trou
- Page 219 and 220: Index Symbols
- Page 221 and 222: Index 221 FileOnOnly agent (continu
- Page 223 and 224: Index 223 Process agent agent funct
Troubleshooting bundled agents<br />
Troubleshooting storage agents<br />
181<br />
Failed to mount the volume. Disk No. = disk_no, PartitionNo =partition_no.<br />
Error : Error_code<br />
This is a VCS internal error.<br />
Recommended Action: Contact Symantec Technical Support.<br />
Failed to dismount the volume. Disk No. = disk_no, PartitionNo =partition_no.<br />
Error : Error_code<br />
This is a VCS internal error.<br />
Recommended Action: Contact Symantec Technical Support.<br />
Could not access the volume. Disk No. = disk_no, PartitionNo = partition_no<br />
Mount Path = Mount_path. Error : Error_code<br />
The specified device path is inaccessible, indicating a potential hardware error.<br />
Recommended Action: Verify the installed disk and the configured partition. Also<br />
make sure no other application is accessing the volume. Set the ListApplications<br />
attribute to 1 to obtain a list of applications that are accessing the volume.<br />
Failed to unmount the volume. Disk No. = disk_no, PartitionNo = partition_no<br />
Mount Path = Mount_path. Error : Error_code<br />
This is a VCS internal error.<br />
Recommended Action: Contact Symantec Technical Support.<br />
File system is dirty. Cannot online the resource. Unmounting the volume.<br />
Error : Error_code<br />
The filesystem at the specified driver letter or mount path is not clean.<br />
Recommended Action: Set the AutoFSClean to 1 if you want the agent to clean the<br />
filesystem. Otherwise, clean the filesystem manually.<br />
Drive letter drive_letter is not assigned Exit code : Exit_code<br />
This is a VCS internal error.<br />
Recommended Action: Contact Symantec Technical Support.<br />
Failed to flush the Volume. Error : Error_code<br />
This is a VCS internal error.<br />
Recommended Action: Contact Symantec Technical Support.<br />
Failed to get the application log information. Error : Error_code<br />
The agent could not find the name of the application accessing the volume.
Change language