Backup and Recovery Error Messages

unix: dks0d1s0: Process [tar] ran out of disk space

This error, or similar errors reporting a shortage of disk space, may occur if you are backing up data to a disk partition that does not have enough free space left to contain the data to be backed up.

Such errors may likewise occur in data restores if the data being recovered does not fit on the destination disk partition. Note that if you are uncompressing data that was compressed for backup, the uncompressed data could easily require twice as much space as the compressed data.

You may wish to add disk space, reclaim disk space, repartition existing disk space (see "IRIX Admin: Disks and Filesystems"), or redesign your backup procedure, for example, to use data compression (see "Saving Files Using Data Compression").

unix: ec0: no carrier: check Ethernet cable

unix: NFS write error 151 on host garfield

unix: NFS2 getattr failed for server some.host.name: Timed out

These and similar network errors only represent a problem if you are using network resources (for example, a remote tape or disk drive) in your backup or recovery procedure. If this is the case, reestablish proper network connections (see "IRIX Admin: Networking and Mail") and either verify that your backup or recovery was successful or reinitiate it.

unix: Tape 3: Hardware error, Non-recoverable

mediad: Could not access device /dev/rmt/tps0d6nr, Device busy

unix: Tape 3: requires cleaning

unix: Tape 3: Unrecoverable media error

unix: NOTICE: SCSI tape #0, 6 had 1 successful retried commands (0% of r/w)

unix: NOTICE: SCSI tape #0,7 Incompatible media when reading

These are all examples of tape access errors. Depending on whether you were trying to back up or recover data, the system encountered a problem writing or reading the tape. Be sure there is a tape in the drive indicated in the error message, and that it is not set on write-protect if you are attempting a backup. (Also, tape drives should be periodically cleaned according to manufacturer instructions.)

If these are not the problem, test the tape for read and/or write capabilities using one or more of the backup and recover utilities. Note that a media error can occur anywhere on a tape; to verify the tape, write and read the entire tape. You can also select "Run Confidence Tests" from the System toolchest and double-click on the Tape Drive test.

If you have any doubts about the quality of the tape you're using (for example, it is getting old), copy it to a new tape (if it still has good data) and discard it. If you are using a tape drive that you have not used before, verify that the tape type is compatible with the new drive. Run the mt(1) command to reset the tape drive. Run the hinv(1M) command to determine if the tape drive is recognized by the system.