Error Messages for Component ID 0511

AIX Version 4.3 Messages Guide and Reference

Error Messages for Component ID 0511

0511-023 Cannot write to the DirectoryName directory

Possible Causes

The directory you specified using the cpio -p command does not exist.
You do not have write access permissions in the directory you specified for copying files.

Procedures for Recovery

Verify that the directory exists.
Enter the ls -ld/ DirectoryName command to check if the directory exists. If it does not exist, create the directory with the mkdir DirectoryName command.
If the directory exists, verify that you own the directory and that you have access permissions to it.
If you are not the owner but you are in the group, enter the chmod 770 xxx command, where xxx is the directory on which you want to change the access permissions.

If you are not the owner and are not in the group, enter the chmod 777 xxx command, where xxx is the directory on which you want to change the access permissions.

For more information, see "Recovering from File and Directory Permission Errors" .

0511-037 Cannot read from the specified input

Possible Causes

From the command line, you issued the cpio command, with the -c flag, to extract an archived file that was not created initially with the -c flag.
You attempted to use the cpio command to extract archived files that were not created using the cpio format.

Procedures for Recovery

Rerun the cpio command without the -c flag.
Run one of the following formats from the command line to check the correct format of the file/device:
For tar format:
```
tar -tvf FileOrDeviceName
```
For backup format:
```
restore -Tv FileOrDeviceName 
```

0511-038 Cannot write to the specified output

Possible Causes

You issued the cpio command to create an archive but specified an incorrect blocking factor with the -C or -B flag.
The tape is damaged.

Procedures for Recovery

Use the tctl command to check the block size of the tape device.
```
tctl -f /dev/rmt# status
```
Use the -C# flag to specify a multiple block factor of the physical device, for example, if the tape block size is set to 1024, use the -C2 flag.
Note: Do not use the -B flag if the tape device block size is 4096.
Check the error log for tape errors:
```
errpt -a
```

0511-051 The read failed

Possible Causes

The tape is backed up on a tape device with a block size that differs from the one on which it is currently set.
The value specified with either the bs, ibs, or obs flag is not a multiple of the block size of the tape device.
The value specified for the fskip flag is greater than the number of end-of-file marks on the tape.
The tape is damaged.

Procedures for Recovery

Use the chdev command to change the block size on the tape device:
```
chdev -1 rmt# -a block size=0
```
Use the tctl command to check the block size of the tape device:
```
tctl -f /dev/rmt# status
```
Then, specify the value of the bs, ibs, or obs flag as a multiple of the block size.
Use the tcopy command to check the number of files or records that can be accessed on tape.
Check the error log for tape errors:
```
errpt -a
```

0511-053 The write failed

Possible Causes

From the command line, you issued the following command:
```
dd if=Filename of=Device conv=block
```
but did not specify the cbs parameter.
You issued the dd command, but the length of the data was not a multiple of 512 bytes, and you did not use the conv=sync parameter.
You issued the dd command with the obs or bs parameter, which did not have a corresponding value as a multiple of the tape device block size.
You attempted to write data to a diskette with the dd command, but the length of the data was greater than the capacity of the diskette.

Procedures for Recovery

Use the cbs=value parameter with the conv=block parameter.
Use the conv=sync parameter if the data length is not a multiple of 512 bytes.
Use the lsattr command to check the block size of the tape drive:
```
lsattr -1 rmt# -E
```
Specify the obs or bs parameter with a value that is a multiple of the tape block size.
If the data is greater than the capacity of the diskette, use a different medium.

0511-079 The backup media may be damaged

Possible Causes

From the command line, you issued the backup command naming a tape device with the block size set to 0, but specified a value with the -b flag that is larger than the maximum allowable write size for the tape device.
From the command line, you issued the backup command naming a tape device, but specified a value with the -b flag that does not yield a whole number multiple of the tape device's physical block size.
From the command line, you issued the following command:
```
find File -print| backup -ivf FileSystem/FileName
```
but the specified FileSystem was full.
The backup media is damaged.

Procedures for Recovery

Specify a value with the -b flag that does not exceed the maximum allowable write size for the tape device, or do not use this flag.
Specify a value with the -b flag that yields a whole number multiple of the tape device's physical block size (-b Number, where Number is the number of 512-byte blocks).
Note: You can use the lsattr command to check the physical block size of the device:
```
lsattr -l rmt# -E
```
Remove unnecessary files from the file system, or use the chfs command to increase the file system and rerun the backup command.
Check the error log for media errors:
```
errpt -a
```
Use a different tape or disk to run the backup.

0511-080 Pathname is too long

Possible Causes

During the backup process, the find command could not locate data because the path name specified was too long.

Procedures for Recovery

Limit the path name to one that is less than 255 characters.
Start the backup process from a lower directory.

Error message "0511-088 The backup tape may be damaged. Use a different disk to run the backup.

0511-103 The volume not correct restore expects volume X

Possible Causes

This message indicates that the number X tape was inserted in the incorrect order.
If it is a single volume archive, then it is possible that the archive is corrupt and is making the tape device think that it has reached end-of-file when this is not the case.

Procedures for Recovery

Check the tape and see if it is damaged or corrupted.
If it is a multi-volume archive, it is likely that tapes got misnumbered.
Check and see if the disks were inserted into the tape drive in the correct order.

0511-123 The volume on String is not in backup format

Possible Causes

You attempted to access data beyond the end of the tape marker, using the restore command.
From the command line, you issued the restore command, with the -s flag, but did not specify the no-rewind tape device.
From the command line, you issued the installp command and specified the device as:
```
/dev/rmt#.1.
```
You tried to access a file or device with the restore command, but the file or device was not in the backup format.
The /var or /tmp directory is too small.
The tape or drive is damaged.

Procedures for Recovery

Use the tctl command to rewind the tape, then rerun the restore command. For example:
```
tctl -f /dev/rmt# rewind
restore -xvf /dev/rmt#.1
```
1. Specify the no-rewind tape device, /dev/rmt#.1 with the -s flag.
2. Specify the tape device as /dev/rmt#.
3. Run one of the following formats from the command line to check the correct format of the file or device:
  For tar format:
```
tar -tvf DeviceOrFileName
```
  For cpio format:
```
cpio -itv DeviceOrFileName
```
Increase the size of the /var or /tmp directory.
Fix the tape or drive.

0511-133 There is a data read error

Possible Causes

From the command line, you issued the following command:
```
restore -sNumber -f Device
```

Procedures for Recovery

Use the tcopy command to check the number of records on the tape, and specify a correct value with the skip flag.
```
tcopy Device
```

0511-160 Cannot read the backup media

Possible Causes

The tape is backed up on a tape device with a block size that differs from the one on which it is currently set.
The backup medium is damaged.

Procedures for Recovery

Log in as the root user and use the chdev command to change the block size on the tape device:
```
chcev -1 rmt# -a block size=0
```
You can also change the block size by selecting the SMIT Devices-> Tape Drive->Change/Show Characteristics of a Tape Drive menu options. Select the appropriate drive and change the block size.
Check the error log for tape errors:
```
errpt -a
```

0511-169 A directory checksum error on media: MediaName not equal to Number

Possible Causes

From the command line, you issued the tar command to extract files from an archive that was not created with the tar command.
You issued the tar command for a file that became damaged while being copied over the network.
You issued the tar command for a file that was copied over the network, using the ftp command, but did not specify the binary flag.

Procedures for Recovery

Ensure that the file is in the correct format by running the cpio or the restore command.
Run the sum command on the copied file and also on the original file. Recopy the file if the sizes are different.
Rerun the ftp command using the binary flag to copy the file, then rerun the tar command.

0511-193 An error occurred while reading from the media

Possible Causes

You issued the tar command to read an archive from a tape device that has a different block size than when the archive was created.
The tape is damaged.

Procedures for Recovery

From the command line, run the tctl command to check the tape block size.
```
tctl -f /dev/rmt# status
```
Use the chdev command to change the block size, for example:
```
chdev -1 rmt0 -a block size=0
```
Check the error log for tape errors:
```
errpt -a
```

0511-195 An error occurred while writing to the storage media

Possible Causes

You issued the tar command without the -b flag, but the tape drive had an incorrect block size (4096).
You attempted to create a new archive beyond the end of the tape marker using the tar command.
The tape density is incorrect.
The tape medium is defective.

Procedures for Recovery

From the command line, run the tctl command to check the tape block size:
```
tctl -f /dev/rmt# status
```
If a block size of 4096 is desired, specify the -b flag with a value of 8 or multiple of 8;
OR

run the chdev command to change the tape block size, for example:
```
chdev -1 rmt0 -a block size=1024
```
A block size 512 or 2048 can also be used.
Rewind the tape and reissue the command:
```
tctl -f /dev/rmt# rewind
```
Change the tape density with the chdev command, and rerun the original command:
```
chdev -1 rmt# -a density_set_1=value
```
Check the error log for tape errors:
```
errpt -a
```
and take action as indicated; for example, clean the drive head if it is dirty.

0511-317 The specified restore level is higher than expected

Possible Causes

You made several incremental backups of a file system, with the levels in nonsequential order (for example: 0, 1, 3, 2) and tried to restore them in sequential order (0, 1, 2, 3). Each backup level is marked with a time stamp. When a backup with a lower level (but a higher time stamp) than the next in sequence is restored, the restore command fails.
You tried to restore the same backup level more than once.

Procedures for Recovery

Restore the backups in the order of the level in which they were created.
To ensure that the most current changes are restored, restore sequentially, ignoring the higher level that is out of sequence.

Using the previous example, restore levels 0, 1, 2. The most recent changes in level 2 are restored, and level 3 changes are lost.
Select the next backup level to be restored.

0511-432 A write error occurred

See Error Messages 0511-079 .

0511-903 Out of phase! cpio attempting to continue

See Error Message 0511-037 for recovery information.