ADVM-07930
Continuing will result in the storage accelerator volume being removed from the file system, which could leave the file system in an inconsistent and possibly unusable state if critical system metadata is stored on the storage accelerator volume.
Cause
fsck (Unix or Linux) or acfschkdsk.exe (Windows) could not open the specified storage accelerator volume. This could be because the ASM disk group containing the storage accelerator volume is not mounted.
Action
If the accelerator volume has no known problems, verify that the ASM disk group containing the storage accelerator volume is mounted. Then rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows). Or, if the accelerator volume is known to have problems such as disk corruption and you wish to have fsck (Unix of Linux) or acfschkdsk.exe (Windows) disassociate the accelerator volume from the file system, allow it to continue.
ADVM-07930
Continuing will result in the storage accelerator volume being removed from the file system, which could leave the file system in an inconsistent and possibly unusable state if critical system metadata is stored on the storage accelerator volume.
Cause
fsck (Unix or Linux) or acfschkdsk.exe (Windows) could not open the specified storage accelerator volume. This could be because the ASM disk group containing the storage accelerator volume is not mounted.
Action
If the accelerator volume has no known problems, verify that the ASM disk group containing the storage accelerator volume is mounted. Then rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows). Or, if the accelerator volume is known to have problems such as disk corruption and you wish to have fsck (Unix of Linux) or acfschkdsk.exe (Windows) disassociate the accelerator volume from the file system, allow it to continue.
ADVM-07930
Continuing will result in the storage accelerator volume being removed from the file system, which could leave the file system in an inconsistent and possibly unusable state if critical system metadata is stored on the storage accelerator volume.
Cause
fsck (Unix or Linux) or acfschkdsk.exe (Windows) could not open the specified storage accelerator volume. This could be because the ASM disk group containing the storage accelerator volume is not mounted.
Action
If the accelerator volume has no known problems, verify that the ASM disk group containing the storage accelerator volume is mounted. Then rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows). Or, if the accelerator volume is known to have problems such as disk corruption and you wish to have fsck (Unix of Linux) or acfschkdsk.exe (Windows) disassociate the accelerator volume from the file system, allow it to continue.
