Error: "An I/O error has compromised pool integrity."

  • 3400559
  • 10-Oct-2006
  • 16-Mar-2012


Novell NetWare 6.0
Novell NetWare 6.5


Error: "An I/O error has compromised pool integrity."
NSS-3.00-5001: Pool BCCB4/SOFTW is being deactivated
An I/O error at block 7679234(file block 7679234)(ZID 0) has compromised pool integrity


Before running a PoolRebuild it is highly recommended that the latest NSS patch, that can be obtained from, be applied.

To rebuild the volume, type NSS /PoolRebuild=; ensure that you have a good backup as rebuild can be destructive.
Prior to running a PoolRebuild if you are unsure about the state of your backups and are concerned that the PoolRebuild may cause data loss, you can run a NSS /PoolVerify= and review the PoolVerify log file for errors.
A PoolVerify that completes successfully typically indicates that a PoolRebuild will also run through successfully.
Please note that there are certain situations where PoolVerify will report errors and running a rebuild is necessary to fix these errors.
After the NSS /PoolRebuild the pool is returned to an active state you will need to mount the volume(s) contained in the pool again.
If the pool is still broken after the PoolRebuild NSS will keep it in a maintenance mode state.

Both the REBUILD and VERIFY utilities generate log files in the root of the boot partition (usually C:\); they are calledpoolname_iv_.vlf for the PoolVerify andpoolname_iv_.rlf for the PoolRebuild, and in most cases will be truncated to 8.3 format.

Running a REBUILD is dissimilar to the process of running VREPAIR on legacy volumes: VREPAIR compares data and corrects differences, REBUILD will validate the consistency of a 'master' set of metadata and make other (subset) instances of that data consistant - even if the result is corrupt data that is now consistantly corrupt; Therefore the possibility of data loss exists with REBUILD.

Additional Information

Data Corruption

Formerly known as TID# 10071749