Sponsored Content
Full Discussion: wrong magic number
Operating Systems Solaris wrong magic number Post 302321132 by tirupathi on Saturday 30th of May 2009 10:19:47 AM
Old 05-30-2009
hardisk

thanks for mailing us
that is not my problem iam instaling new o/s it showing this problem
/pci@if,0/pci@1,1/ide@3/dad@0,0 corrupt label wrong magic number
 

10 More Discussions You Might Find Interesting

1. 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

2. Shell Programming and Scripting

shell magic number with a -

In one of our internal scripts (unix.run), I have noticed that the following shebang. #!/bin/sh - for i in test1 test2 test3 ; do . . . Any idea what the - in the magic number stands for ? And what impact does it have on the script ? Continuing on the same script, I have the... (3 Replies)
Discussion started by: vino
3 Replies

3. Filesystems, Disks and Memory

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... (0 Replies)
Discussion started by: wesweshahaha
0 Replies

4. Filesystems, Disks and Memory

Bad Super Block: Magic Number Wrong

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. Filesystems, Disks and Memory

Bad super block: Magic number wrong

Whenever i run, # fsck -F ufs /dev/dsk/c0t0d0s7 The following error prompt out:- ** /dev/dsk/c0t0d0s7 BAD SUPER BLOCK: MAGIC NUMBER WRONG USE AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; eg. fsck -o b=# where # is the alternate super block. SEE fsck_ufs(1M). ... (3 Replies)
Discussion started by: beginningDBA
3 Replies

6. UNIX for Dummies Questions & Answers

Solaris magic number problem

Hello, When I boot up my ancient SUNOS 5 system. it stops at the OK prompt and complains about a bad magic number. I have told that I need run fsck but I cannot seem to do so from the OK prompt. How can I get into a diagnostic mode so I can run fsck? Thanks, (1 Reply)
Discussion started by: mojoman
1 Replies

7. Solaris

corrupt label - wrong magic number

I have created 1 LUN. 1)LUN 00BB 200GB /dev/rdsk/c1t3d44 /dev/rdsk/c2t28d44 /dev/rdsk/c3t19d44 /dev/rdsk/c4t12d44 2) Already added the new entry into sd.conf and rebooted. 3) Already done these: powercf –q power config 4) power display dev=all I can see the new Symmetrix device.... (1 Reply)
Discussion started by: sirius20d
1 Replies

8. Solaris

Recover label, wrong magic number

Is there a way to recover label? I could install (sparc) Solaris again, but it would take a lot of time. (5 Replies)
Discussion started by: orange47
5 Replies

9. 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

10. Solaris

Magic number error

hi . my " /usr " was full ,so i went into the failsafe mode in solaris 10 and used format utilily to adjust space for it and labeled it. But after that whenever i try to boot solaris normally ,it is giving "magic number error" I tried fsck -o b=32 /dev/dsk/c0d0s6 (for /usr) newfs -N... (6 Replies)
Discussion started by: tushardul
6 Replies
dad(7D) 							      Devices								   dad(7D)

NAME
dad - driver for IDE disk devices SYNOPSIS
dad@ target,lun:partition DESCRIPTION
This driver handles the ide disk drives on SPARC platforms. The type of disk drive is determined using the ATA IDE identify device command and by reading the volume label stored on block 0 of the drive. The volume label describes the disk geometry and partitioning; it must be present or the disk cannot be mounted by the system. The block-files access the disk using the system's normal buffering mechanism and are read and written without regard to physical disk records. There is also a "raw" interface that provides for direct transmission between the disk and the user's read or write buffer. A single read or write call usually results in one I/O operation; raw I/O is therefore considerably more efficient when many bytes are trans- mitted. The names of the block files are found in /dev/dsk; the names of the raw files are found in /dev/rdsk. I/O requests to the raw device must be aligned on a 512-byte (DEV_BSIZE) boundary and must have a length that is a multiple of 512 bytes. Requests which do not meet the restrictions will cause the driver to return an EINVAL error. I/O requests to the block device have no alignment or length restrictions. Device Statistics Support Each device maintains I/O statistics both for the device and for each partition allocated on that device. For each device/partition, the driver accumulates reads, writes, bytes read, and bytes written. The driver also takes hi-resolution time stamps at queue entry and exit points, which facilitates monitoring the residence time and cumulative residence-length product for each queue. Each device also has error statistics associated with it. These must include counters for hard errors, soft errors and transport errors. Other data may be implemented as required. FILES
/dev/dsk/cntndnsn block files /dev/rdsk/cntndnsn raw files where: cn controller n tn IDE target id n (0-3) dn Always 0. sn partition n (0-7) The target ide numbers are assigned as: 0 Master disk on Primary channel. 1 Slave disk on Primary channel. 2 Master disk on Secondary channel 3 Slave disk on Secondary channel. IOCTLS
Refer to dkio(7I). ERRORS
EACCES Permission denied. EBUSY The partition was opened exclusively by another thread. EFAULT The argument was a bad address. EINVAL Invalid argument. EIO An I/O error occurred. ENOTTY This indicates that the device does not support the requested ioctl function. ENXIO During opening, the device did not exist. EROFS The device is a read-only device. SEE ALSO
format(1M), mount(1M), lseek(2), read(2), write(2), driver.conf(4), vfstab(4), dkio(7I) X3T10 ATA-4 specifications. DIAGNOSTICS
Command:<number>, Error:<number>, Status:<number> Indicates that the command failed with an error and provides status register contents. Where <number> is a hexadecimal value. offline The driver has decided that the target disk is no longer there. disk ok The target disk is now responding again. corrupt label - bad geometry The disk label is corrupted. corrupt label - label checksum failed The disk label is corrupted. corrupt label - wrong magic number The disk label is corrupted. disk not responding to selection The target disk is not responding. i/o to invalid geometry The geometry of the drive could not be established. incomplete read/write - retrying/giving up There was a residue after the command completed normally. no bp for disk label A bp with consistent memory could not be allocated. no memory for disk label Free memory pool exhausted. ATA transport failed: reason 'nnnn': {retrying|giving} The host adapter has failed to transport a command to the target for the reason stated. The driver will either retry the command or, ultimately, give up. corrupt label - wrong magic number The disk label is corrupted. corrupt label - label checksum failed The disk label is corrupted. corrupt label - bad geometry The disk label is corrupted. no mem for property Free memory pool exhausted. transport rejected (<n>) Host adapter driver was unable to accept a command. Device Fault There has been a Device Fault - reason for such error is vendor specific. SunOS 5.10 15 Mar 2004 dad(7D)
All times are GMT -4. The time now is 06:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy