cpio: Bad magic number/header.

Cause
A cpio(1) archive has either become corrupted or was written out with an
incompatible version of cpio(1).
Action
Use the -k option to cpio(1) to skip I/O errors and corrupted file headers. This
might permit you to extract other files from the cpio(1) archive. To extract files with
corrupted headers, try editing the archive with a binary editor such as emacs(1). Each
cpio(1) file header contains a filename as a string.

################################################################

cpio : can’t read input : end of file encountered
prior to expected end of archive.


Cause
This message appears when trying to read a multi-volume floppy in bar format
using the following command:

# cpio -id -H bar -I /dev/diskette0

Action

kill /usr/sbin/vold by running /etc/init.d/volmgt stop and use the
device name /dev/rfd0.

###############################################################


Cross-device link


Cause

An attempt was made to make a hard link to a file on another device, such as on
another file system.

Action

Establish a symbolic link using ln -s instead. Symbolic links are permitted across
file system boundaries.

Technical Notes
The symbolic name for this error is EXDEV, errno=18.
#############################################################

"D"

data access exception

Cause

This message appears when running an old version of the operating system that
does not support new hardware or when running an operating system that is not
configured for new hardware. It can also be the result of an incorrectly installed
DSIMMs or a disk problem.

Action

Upgrade your operating system to a version that supports the new hardware or
machine architecture.
############################################################

Data fault

Cause

This error is a kind of BAD TRAP that usually causes a system panic. When this
message appears after a BAD TRAP message, a system text or data access fault
probably occurred.2 In the absence of a BAD TRAP message, this message might
indicate a user text or data access fault. Data loss is possible, if the problem occurs
other than at boot time.

Action

Make sure the machine can reboot, then check the log file /var/adm/messages for
hints about what went wrong.
############################################################

Deadlock situation detected/avoided

Cause

A programming deadlock situation was detected and avoided.

Action

If the system had not detected and avoided a deadlock, a piece of software would
have hung. Run the program again. The deadlock might not reoccur.

Technical Notes

This error usually relates to file and record locking, but can also apply to mutexes,
semaphores, condition variables, and read/write locks.
The symbolic name for this error is EDEADLK, errno=45.

Comments

Post a Comment

Popular posts from this blog

Understanding How ZFS Calculates Used Space

This document explains how ZFS calculates the amount of used space within a zpool and provides examples of how various ZFS features affect that calculation. DETAILS A ZFS storage pool is a logical collection of devices that provide space for datasets such as filesystems, snapshots and volumes. A zfs pool can be used as a filesystem, i.e. such as mounting/unmounting; to take snapshots that provides read-only (clones are writable copies of snapshots) copies of the filesystem taken in the past; to create volumes that can be accessed as a raw and a block device and for setting properties on datasets. Interaction of all these datasets and associated properties such as quotas, reservations, compression and deduplication (Solaris 11 only) play a role in how ZFS calculates space usage. Neither the du nor df command have been updated to account for ZFS file system space usage. When calculating zfs space usage, always use the following command. # zfs list -r -o space <pool_name...
Read more

How To Verify Remote System Controller (RSC) is Configured and Current on Sun Fire[TM] 280R/V480/V490/V880/V890 servers

Steps to Follow: How To Verify Remote System Controller(RSC) is Configured and Current 1.Check to see if the RSC software is already installed. # /usr/bin/pkginfo | grep SUNWrsc 2.If the software is installed the command should output the package name and info.   The version of the package installed in Solaris should match the version of firmware installed on the card.   `rscadm version` in Solaris will display the firmware version. 3.If the software is not installed the packages can be found on the supplemental CD that came with the Solaris Operating Environment. If you do not have the CD the software can be downloaded from MOS: RSC 2.2.2 is supported with Solaris 10, but you need to get this from a supplemental CD (for Solaris 9, since there is no supplemental CD for S10). The packages for Solaris 8 and 9 (and later) are both in the zip file. There are two options of the zip file, 32bit, and 64bit, but they both have the same checksums, so there are...
Read more

Restart autosys agent

#/etc/init.d/uajm_agent stop CA-UAJM Agent stopped. #/etc/init.d/uajm_agent start CA-UAJM Agent started. Follow the below workaround if the autosys agent does not start. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1.Run the command to check the status of both process, auto_remote and csampmuxf # ps -ef|grep 'auto'     root 14712     1  0   Aug 27 ?        2:42 auto_remote     root 27652     1  0 13:00:22 ?        0:00 auto_remote     root 27782     1  0 13:00:40 ?        0:00 auto_remote     root 29066 24480  0 13:01:07 pts/7    0:00 grep auto 2.There should be two entries for /opt/CA/SharedComponents/Csam/SockAdapter/bin/csampmux status . If you see one entry then stop agent and check the autore...
Read more