Bad Magic Number


 
Thread Tools Search this Thread
Special Forums Hardware Filesystems, Disks and Memory Bad Magic Number
# 1  
Old 05-18-2006
Bad Magic Number

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 and i saved the image file on the server (*.gho), when i got back to the SUN workstation and then installed the SCSI H.D, it gave me the message "Bad Magic Number", so i want to get the system back as it was without loosing the data. please tell me the right way to recover the system back without loses.
Thanks and regards
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Bad magic number in disk label.

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

2. Solaris

Bad magic number error

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

3. Filesystems, Disks and Memory

Can't repair super block, bad magic number

Hello all, I have a hard drive that I can't repair. The drive is WD15EARS - Filesystem ext4 ( not 100% sure ) It's used in a Synology DS110j NAS. I try to run fsck -p /dev/sdb on the HD and I get this: Bad magic number in super-block while trying to open /dev/sdb /dev/sdb: The superblock... (4 Replies)
Discussion started by: dallasw1983
4 Replies

4. Solaris

cpio: Bad magic number/header.

Hi, i got the following error while unpacking the archive file. cpio -icvd < as_sun_x86_101202_disk2.cpio Disk2/stage/Components/oracle.webdb.wwdoc/10.1.2.0.1/1/DataFiles/wwdoc.jar Disk2/stage/Components/oracle.webdb.wwdoc/10.1.2.0.1/1/DataFiles... (2 Replies)
Discussion started by: malikshahid85
2 Replies

5. Solaris

Solaris 8.2 Bad magic number

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

6. Solaris

OpenSolaris 2009 bad magic number

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

7. Solaris

BAD magic number in disc label...

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

8. UNIX for Advanced & Expert Users

Bad magic number on /dev/md0

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

9. UNIX for Advanced & Expert Users

bad magic number

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

10. UNIX for Dummies Questions & Answers

Bad magic number in super-block

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
Login or Register to Ask a Question
diskinfo(1M)															      diskinfo(1M)

NAME
diskinfo - describe characteristics of a disk device SYNOPSIS
character_devicefile DESCRIPTION
The command determines whether the character special file named by character_devicefile is associated with a SCSI or floppy disk drive. If so, summarizes the disk's characteristics. The command displays information about the following characteristics of disk drives: Vendor name Manufacturer of the drive (SCSI only) Product ID Product identification number or ASCII name Type Floppy or SCSI classification for the device Disk Size of disk specified in bytes Sector Specified as bytes per sector Both the size of disk and bytes per sector represent formatted media. Options The command recognizes the following options: Return the size of the disk in 1024-byte sectors. Display a verbose summary of all of the information available from the device. For floppy drives, this option has no effect. SCSI disk devices return the following: Vendor and product ID Device type Size (in bytes and in logical blocks) Bytes per sector Revision level SCSI conformance level data DIAGNOSTICS
Most of the diagnostic messages from are self-explanatory. However, one diagnostic message deserves further clarification. If the command fails to access the lunpath corresponding to a given special file, it displays the following diagnostics data, which contains device iden- tification and capability information: device type 127 (unknown); device is inaccessible iso ecma ansi rmb dtq resv rdf WARNINGS
As of release 10.20 of HP-UX, certain IDE devices, CD-ROMs in particular, will respond to inquiries as if they were SCSI devices. There- fore, the text "SCSI describe" in the output of the command does not definitively mean that the disk is in fact a SCSI drive (especially in the case of CD-ROMs). Use to check which type of INTERFACE node, SCSI or IDE, the device's hardware path lies beneath, in order to defini- tively determine a drive's interface. DEPENDENCIES
General The command supports floppy and HP SCSI disk devices. SCSI Devices The SCSI specification provides for a wide variety of device-dependent formats. For non-HP devices, may be unable to interpret all of the data returned by the device. Refer to the drive operating manual accompanying the unit for more information. AUTHOR
was developed by HP. SEE ALSO
ioscan(1M), lsdev(1M), disktab(4), disk(7). diskinfo(1M)