Media management

Media management problems

Description

An AIT medium cannot be formatted. Formatting fails with the following error:
"Illegal Request ([0x83,0x02] AIT: No MIC detected.)"

Explanation

AIT media without MIC or with a damaged MIC cannot be formatted.

Workaround

OpenArchive (OA) can use such a medium as a “single-volume” medium, similarly to an LTO medium. To prepare it for use, you must initialize it without formatting, as follows:
ivdmedium --init Barcode

Description

Volume overflow when initializing empty medium volumes.

Explanation

In some cases if a medium is bad, this might not be detected immediately by the drive. It is possible that the tape drive skips bad areas of the medium until it reaches the end of the medium. If this happens, then a misleading SCSI error is reported. For example:
ivd_Error: 11005: Medium overflow (physical EOM).
Volume Overflow ([0x00,0x02] End-of-partition/medium detected.
The current operation fails. The next time an attempt is made to use this medium, the drive detects it is bad and marks it accordingly.

Workaround

None

Description

If an AIT-3 tape drive is switched off during migration to an AIT-3 tape medium, the medium becomes unusable. New data cannot be migrated to it nor can the already migrated data be recalled.

Explanation

A medium to which a migration was interrupted by switching off the drive cannot be rewound to a specific location/block, and the data cannot be read from the medium. Consequently, no OA medium volumes on it can be accessed.

Workaround

The problematic medium cannot be used in the OA implementation any more. If another OA media pool exists for the same OA partition, the unusable medium contents can be copied to another medium in the pool. This way the data can be accessed again and the number of the configured migrated data copies is retained. To create additional copy of data on this medium from some other OA pool, enter:
ivdmedium --copy-contents Barcode

Description

If you remove an OA medium from its OA media pool without physically removing it from an OA library, then add it to whichever OA media pool, and finally start an OA administrative job to format the medium, the job seems to be blocked before formatting actually begins.

Explanation

When an OA administrative job commands the Resource Manager (RM) to allocate a particular OA medium, the RM cannot execute the allocation unless it knows the medium’s physical location in the OA library. After an OA medium is added to an OA media pool, the OA library where the medium is located must be physically rescanned in order to record the medium’s location in the Resource Management Database (RMDB). The formatting can start after the medium location information is known.

Workaround

Before starting to format the re-added OA media, run the following command to physically rescan the OA library. The command will add location information for the re-added OA media into the RMDB:
ivdlibrary --update-inventory LibraryName --rescan
This also unblocks formatting jobs that have already started from waiting for the missing location information, enabling them to allocate the re-added OA media and continue with execution.

Description

Recreating Fast Recovery Information (FRI) on a closed but empty OA disk medium volume fails.

Explanation

Closed OA disk medium volumes which are empty are not handled correctly by the Back End Agent.

Workaround

Do not recreate FRI on empty closed OA disk medium volumes.

Description

If reorganization of an OA medium volume fails for any reason, you cannot re-run the reorganization job for the volume, because the 'scanned' indicator is removed from the medium volume status.

Explanation

If the medium with the source medium volume is worn out or there is a problem with SCSI hardware, the reorganization may fail when reading data from the volume. In this case, to prevent further problems that might lead to a data loss, the indicator scanned is cleared for the problematic medium volume.

Workaround

Resolve the problem that caused the failure of the OA reorganization job, and run the reorganizational scan again.

Description

A reorganizational scan fails with the following message:
"Volume {VOLID} has already status 73 set"

Explanation

This occurs when the reorganization has already finished writing to a target medium volume and was then aborted or terminated with the medium volume staying in the state recycled.

Workaround

Run the ivdmedium --init command for recycled volumes. The source volume's content has already been copied to the target medium and the medium can be initialized. problems

Description

An AIT medium cannot be formatted. Formatting fails with the following error:
"Illegal Request ([0x83,0x02] AIT: No MIC detected.)"

Explanation

AIT media without MIC or with a damaged MIC cannot be formatted.

Workaround

OPENARCHIVE (OA) can use such a medium as a “single-volume” medium, similarly to an LTO medium. To prepare it for use, you must initialize it without formatting, as follows:
ivdmedium --init Barcode

Description

Volume overflow when initializing empty medium volumes.

Explanation

In some cases if a medium is bad, this might not be detected immediately by the drive. It is possible that the tape drive skips bad areas of the medium until it reaches the end of the medium. If this happens, then a misleading SCSI error is reported. For example:
ivd_Error: 11005: Medium overflow (physical EOM).
Volume Overflow ([0x00,0x02] End-of-partition/medium detected.
The current operation fails. The next time an attempt is made to use this medium, the drive detects it is bad and marks it accordingly.

Workaround

None

Description

If an AIT-3 tape drive is switched off during migration to an AIT-3 tape medium, the medium becomes unusable. New data cannot be migrated to it nor can the already migrated data be recalled.

Explanation

A medium to which a migration was interrupted by switching off the drive cannot be rewound to a specific location/block, and the data cannot be read from the medium. Consequently, no OA medium volumes on it can be accessed.

Workaround

The problematic medium cannot be used in the OA implementation any more. If another OA media pool exists for the same OA partition, the unusable medium contents can be copied to another medium in the pool. This way the data can be accessed again and the number of the configured migrated data copies is retained. To create additional copy of data on this medium from some other OA pool, enter:
ivdmedium --copy-contents Barcode

Description

If you remove an OA medium from its OA media pool without physically removing it from an OA library, then add it to whichever OA media pool, and finally start an OA administrative job to format the medium, the job seems to be blocked before formatting actually begins.

Explanation

When an OA administrative job commands the Resource Manager (RM) to allocate a particular OA medium, the RM cannot execute the allocation unless it knows the medium’s physical location in the OA library. After an OA medium is added to an OA media pool, the OA library where the medium is located must be physically rescanned in order to record the medium’s location in the Resource Management Database (RMDB). The formatting can start after the medium location information is known.

Workaround

Before starting to format the re-added OA media, run the following command to physically rescan the OA library. The command will add location information for the re-added OA media into the RMDB:
ivdlibrary --update-inventory LibraryName --rescan
This also unblocks formatting jobs that have already started from waiting for the missing location information, enabling them to allocate the re-added OA media and continue with execution.

Description

Recreating Fast Recovery Information (FRI) on a closed but empty OA disk medium volume fails.

Explanation

Closed OA disk medium volumes which are empty are not handled correctly by the Back End Agent.

Workaround

Do not recreate FRI on empty closed OA disk medium volumes.

Description

If reorganization of an OA medium volume fails for any reason, you cannot re-run the reorganization job for the volume, because the 'scanned' indicator is removed from the medium volume status.

Explanation

If the medium with the source medium volume is worn out or there is a problem with SCSI hardware, the reorganization may fail when reading data from the volume. In this case, to prevent further problems that might lead to a data loss, the indicator scanned is cleared for the problematic medium volume.

Workaround

Resolve the problem that caused the failure of the OA reorganization job, and run the reorganizational scan again.

Description

A reorganizational scan fails with the following message:
"Volume {VOLID} has already status 73 set"

Explanation

This occurs when the reorganization has already finished writing to a target medium volume and was then aborted or terminated with the medium volume staying in the state recycled.

Workaround

Run the ivdmedium --init command for recycled volumes. The source volume's content has already been copied to the target medium and the medium can be initialized.