Sponsored Content
Operating Systems Solaris corrupt label - wrong magic number Post 302500262 by sirius20d on Monday 28th of February 2011 04:58:54 AM
Old 02-28-2011
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:
Code:
powercf –q
power config

4) power display dev=all
I can see the new Symmetrix device.

5)But I have been receiving these errors :

Code:
scsi: [ID 107833 kern.warning] WARNING: /ssm@0,0/pci@18,600000/lpfc@1/sd@3,2d (sd1061):
corrupt label - wrong magic number

Anyone know what is going on?
 

10 More Discussions You Might Find Interesting

1. Solaris

Big UH-OH "Bad magic number in disk label"

I tried rebooting my Sun server just a few minutes ago and I got the following at boot: -- Sun Fire 280R (UltraSPARC-III+) , No Keyboard Copyright 1998-2002 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.5, 1024 MB memory installed, Serial #xxxxxxxxx Ethernet address... (6 Replies)
Discussion started by: deckard
6 Replies

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

3. Solaris

ultra 10 boot warning---corrupt label

Hi All, Any idea why i'm having this warning during boot: WARNING: /pci@1f,0/pci@1,1/ide@3/dad@1,0 (dad1): corrupt label - wrong magic number This happens after I added another ide HD and reinstall it from solaris 10 to solaris 8. Thanks in advance. (7 Replies)
Discussion started by: itik
7 Replies

4. Solaris

Corrupt label bad geometry

Hi, I have a Sun X4200, when I try to reboot the machine it's not detecting the drive and it shows the following error when I try to rebuilt it. I am not sure whether its a bad HD or something else. Label says 983040 blocks: Drive says 983039 blocks WARNING:... (1 Reply)
Discussion started by: gunnervarma
1 Replies

5. Solaris

wrong magic number

/pci@if,0/pci@1,1/ide@3/dad@0,0 corrupt label wrong magic number can u plz suggustion me (6 Replies)
Discussion started by: tirupathi
6 Replies

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

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. 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. Emergency UNIX and Linux Support

Ubuntu filesystem error corrupt GPT label

Need help/advice urgently.:wall: I really shot myself in the foot this time. Here is the scenario Have a Solaris server Solaris 10 x86 Update 8. Installed an LSI MegaRaid 9280 raid controller and attached a 16 bay JBOD box to it, created a RAID6 virtual drive with 1 hot spare. Created a... (2 Replies)
Discussion started by: ccj4467
2 Replies

10. 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
volrmmount(1)							   User Commands						     volrmmount(1)

NAME
volrmmount - call rmmount to mount or unmount media SYNOPSIS
volrmmount [-i | -e] [name | nickname] volrmmount [-d] DESCRIPTION
The volrmmount utility calls rmmount(1M) to, in effect, simulate an insertion (-i) or an ejection (-e). Simulating an insertion often means that rmmount will mount the media. Conversely, simulating an ejection often means that rmmount will unmount the media. However, these actions can vary depending on the rmmount configuration and media type (see rmmount.conf(4)). For example, if you use the default /etc/rmmount.conf and insert a music CD, it will not be mounted. However, you can configure rmmount so that it calls workman whenever a music CD is inserted. This command allows you to override Volume Management's usual handling of media (see EXAMPLES below). OPTIONS
The following options are supported: -i Simulates an insertion of the specified media by calling rmmount. -e Simulates an ejection of the specified media by calling rmmount. -d Displays the name of the default device for volrmmount to handle. This device is used if no name or nickname is supplied. OPERANDS
The following operands are supported: name The name that Volume Management recognizes as the device's name. See volfs(7FS). nickname A shortened version of the device's name. Following is the list of recognized nicknames: +-----------------------------+-----------------------------+ | Nickname | Path | +-----------------------------+-----------------------------+ |fd |/dev/rdiskette | +-----------------------------+-----------------------------+ |fd0 |/dev/rdiskette | +-----------------------------+-----------------------------+ |fd1 |/dev/rdiskette1 | +-----------------------------+-----------------------------+ |diskette |/dev/rdiskette | +-----------------------------+-----------------------------+ |diskette0 |/dev/rdiskette0 | +-----------------------------+-----------------------------+ |diskette1 |/dev/rdiskette1 | +-----------------------------+-----------------------------+ |rdiskette |/dev/rdiskette | +-----------------------------+-----------------------------+ |rdiskette0 |/dev/rdiskette0 | +-----------------------------+-----------------------------+ |rdiskette1 |/dev/rdiskette1 | +-----------------------------+-----------------------------+ |floppy |/dev/rdiskette | +-----------------------------+-----------------------------+ |floppy0 |/dev/rdiskette0 | +-----------------------------+-----------------------------+ |floppy1 |/dev/rdiskette1 | +-----------------------------+-----------------------------+ |cdrom0 |/vol/dev/rdsk/cXtYdZ/label | +-----------------------------+-----------------------------+ |zip0 |/vol/dev/rdsk/cXtYdZ/label | +-----------------------------+-----------------------------+ |jaz0 |/vol/dev/rdsk/cXtYdZ/label | +-----------------------------+-----------------------------+ |rmdisk0 |/vol/dev/rdsk/cXtYdZ/label | +-----------------------------+-----------------------------+ EXAMPLES
Example 1: Using the volrmmount command When Volume Management finds a floppy that contains a filesystem, it calls rmmount to mount it. If you wish to run tar(1) or cpio(1) on that floppy, it must first be unmounted. To unmount the floppy use: example% volrmmount -e floppy0 After volrmmount unmounts the floppy, if you wish to re-mount it (rather than ejecting it and reinserting it) use: example% volrmmount -i floppy0 Notice that if you are using a named floppy, you can use its name in place of floppy0. FILES
/dev/volctl Volume Management control port ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWvolu | +-----------------------------+-----------------------------+ SEE ALSO
cpio(1), eject(1), tar(1), rmmount(1M), vold(1M), rmmount.conf(4), attributes(5), volfs(7FS) NOTES
Volume Management (vold) must be running to use this command. SunOS 5.10 30 Aug 2000 volrmmount(1)
All times are GMT -4. The time now is 03:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy