10-13-2010
You can get this error when bringing cpio from a foreign system, because magic numbers on the remote box do not match local magic numbers. Or the file you are loading is bad or was bad to start with.
use the cpio -k option to skip header checking.
magic number example
#!/bin/something
The #! is a unversal magic number on line one, the first two bytes of the file. It means
1. this is a script
2. exec is expected to invoke the "/bin/something" as an interpreter. /bin/something is not part of the magic number.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am running mandrake 8.2 and when booting I get the message:
e2fschk: Bad magic number in super-block while trying to open /dev/hda8.
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and really contains a valid an ext2 filesystem (and... (1 Reply)
Discussion started by: Jay
1 Replies
2. UNIX for Advanced & Expert Users
Hi,
when installing a piece of third part software I get the error "Bad magic number" at one point when it tries to use libraries from the bea tuxedo server. Am I correct that this means that the software is expecting 32bit while I'm on 64bit? Is there a way around it or can it only be solved... (5 Replies)
Discussion started by: rein
5 Replies
3. Filesystems, Disks and Memory
Dear All,
i have a SCSI hard disk drive i'm installing on it solaris 5 and the workstation is sun sparc, i made an image of this H.D using Norton Ghost 6, so i took off the SCSI H.D from the sun workstation and put it on a Compaq server then i booted the server from the Norton Ghost floppy disk... (0 Replies)
Discussion started by: wesweshahaha
0 Replies
4. Filesystems, Disks and Memory
I had a power outage a day ago and when the power came back on my FreeBSD 4.6 webserver had problems. It said it was unable to mount /var and made me start in single user mode and said to run fsck MANUALY. So i did and this is now what i get.
www# fsck /dev/ad0s1e
** /dev/ad0s1e
BAD SUPER... (4 Replies)
Discussion started by: matthewbane
4 Replies
5. UNIX for Advanced & Expert Users
Hello All,
(RHEL4)
Few weeks ago I had posted a message in this forum about the problem I had when I replaced my two scsi disks and tried rebuild raid1 array.
I somehow managed to up the system with working raid1 array.
But the main problem persisted..
i.e when I reboot the system, mounting... (0 Replies)
Discussion started by: ravinandan
0 Replies
6. Solaris
Hello All,
I m very new to this forum.
i m having SUN NETRA X1 server with 40 GB HDD (Seagate) & 128 MB RAM.
i m trying this server for SUN 10 Practise.
As i m installing SUN 9 /10 with CD ,its giving me error after OK propmt
***************************
#boot cdrom
or
#boot cdrom... (16 Replies)
Discussion started by: amrut_k
16 Replies
7. Solaris
Hi guys, I have a big problem wiht my old Netra T1 200. I want to install OpenSolaris 2009 but there's a problem, I burned the ISO image on a CD-RW and then I tryied to install it on netra, but the setup won't to start and the error is that in the attached image.
Thanks for the support and sorry... (5 Replies)
Discussion started by: Ducati87
5 Replies
8. Solaris
I'll keep it fairly straight forward. I work with a Solaris server and magically today it decided to take a dump on me. At first it give a long list of files that couldn't be acessed before terminating the boot process and returning to the 'ok' prompt. Booting in single-user mode allowed me to run... (4 Replies)
Discussion started by: Aon
4 Replies
9. Solaris
So we have a new to us v240 server with no OS installed. It has an outdated version of OB and ALOM so before we install the OS we want to update both. We have a DVD with the latest OB patch burned on it.
We do the boot cdrom command but receive the Bad Magic Number Error. Does an OS need to... (2 Replies)
Discussion started by: dunkpancakes
2 Replies
10. Solaris
This is first time post...found this forum when looking for possible solution to fix my sun pc. Just one day can't boot it already showing the following:
Boot device: disk File args:
Bad magic number in disk label
Can't open disk label package
Evaluating: boot
Can't open boot device... (40 Replies)
Discussion started by: SHuKoSuGi
40 Replies
LEARN ABOUT MOJAVE
cfront
fileutil::magic::cfront(n) file utilities fileutil::magic::cfront(n)
__________________________________________________________________________________________________________________________________________________
NAME
fileutil::magic::cfront - Generator core for compiler of magic(5) files
SYNOPSIS
package require Tcl 8.4
package require fileutil::magic::cfront ?1.0?
package require fileutil::magic::cgen ?1.0?
package require fileutil::magic::rt ?1.0?
package require struct::list
package require fileutil
::fileutil::magic::cfront::compile path...
::fileutil::magic::cfront::procdef procname path...
::fileutil::magic::cfront::install path...
_________________________________________________________________
DESCRIPTION
This package provides the frontend of a compiler of magic(5) files into recognizers based on the fileutil::magic::rt recognizer runtime
package. For the generator backed used by this compiler see the package fileutil::magic::cgen.
COMMANDS
::fileutil::magic::cfront::compile path...
This command takes the paths of one or more files and directories and compiles all the files, and the files in all the directories
into a single recognizer for all the file types specified in these files.
All the files have to be in the format specified by magic(5).
The result of the command is a Tcl script containing the generated recognizer.
::fileutil::magic::cfront::procdef procname path...
This command behaves like ::fileutil::magic::cfront::compile with regard to the specified path arguments, then wraps the resulting
recognizer script into a procedure named procname, puts code setting up the namespace of procname in front, and returns the result-
ing script.
::fileutil::magic::cfront::install path...
This command uses ::fileutil::magic::cfront::procdef to compile each of the paths into a recognizer procedure and installs the
result in the current interpreter.
The name of each new procedure is derived from the name of the file/directory used in its creation, with file/directory "FOO" caus-
ing the creation of procedure ::fileutil::magic::/FOO::run.
BUGS, IDEAS, FEEDBACK
This document, and the package it describes, will undoubtedly contain bugs and other problems. Please report such in the category fileutil
:: magic of the Tcllib SF Trackers [http://sourceforge.net/tracker/?group_id=12883]. Please also report any ideas for enhancements you may
have for either package and/or documentation.
SEE ALSO
file(1), fileutil, magic(5)
KEYWORDS
file recognition, file type, file utilities, mime, type
CATEGORY
Programming tools
fumagic 1.0 fileutil::magic::cfront(n)