SCF Reference Manual for the Storage Subsystem (G06.28+, H06.05+, J06.03+)

Troubleshooting Doubly Allocated File Extents
1. Repeat “Identifying Doubly Allocated File Extents” (page 106) to see whether any doubly
allocated file extents remain:
• If none remain, you are finished with the procedure and you can restart applications.
• If doubly allocated file extents remain, continue to the next step.
2. Use FUP DUP or BACKUP to copy to another volume the files identified in the DSAP report
that contain doubly allocated extents.
3. Purge these files from the original volume.
If purging a file causes file-system errors, resolve them by repeating Step 4 of “Rebuilding the
Disk Free Space Table” (page 106).
4. Repeat “Identifying Doubly Allocated File Extents” (page 106) to ensure that all doubly allocated
file extents have been corrected. If none remain, continue with the next step. Otherwise, repeat
from Step 2.
5. Use FUP DUP or RESTORE to copy the files back to the original volume.
6. Restart applications.
Replacing the Bootstrap Program
NOTE: The REPLACEBOOT attribute does not apply to Integrity NonStop NS-series servers.
Instead, the bootstrap program is installed through firmware update into flash memory.
The REPLACEBOOT attribute of the CONTROL DISK command replaces the disk bootstrap program.
You must replace the disk bootstrap program on a disk in any of these cases:
• You migrate the system to a new software RVU that has a new bootstrap program.
• You plan to install a system disk that is incompatible with your current bootstrap program.
• You want to create an alternate system-load volume.
• You cannot perform a system load from a disk that has been used on other occasions to load
the system. This error indicates that the bootstrap program is corrupted or incompatible with
the format of the target SYSnn.OSIMAGE file.
If a system failure occurs during the CONTROL DISK, REPLACEBOOT operation, the disk bootstrap
program could be unusable. This procedure can help you recover from such a situation.
Replacing the Disk Bootstrap Program on a Mirrored Volume (NonStop S-Series
Servers)
CAUTION: If you are replacing the disk bootstrap program on the system disk, use the procedure
described here. Do not attempt to replace the bootstrap program on both disks of a mirrored
volume simultaneously.
This procedure replaces the disk bootstrap program on the primary disk of a mirrored volume and
then verifies that the disk is functional before replacing the bootstrap program on the mirror disk.
1. Review information about the REPLACEBOOT attribute.
2. If the disk volume you plan to replace the bootstrap program on is not already started, start
it. This command executes a revive operation if the primary and mirror disks are not current
with each other.
-> START $SYSTEM
3. Verify the disk is started:
-> STATUS $SYSTEM-*
Replacing the Bootstrap Program 107