^Icorrupt label - wrong magic number

kris_p used Ask the Experts™
I am getting the following error messge in the /var/adm/messages Log file it is keep on filling the log file.
^Icorrupt label - wrong magic number
last message repeated 1 time
unix: WARNING: /sbus@2,0/fcaw@1,0/sd@0,3 (sd183):
and one more message is
unix: WARNING: /sbus@6,0/fcaw@1,0/sd@0,20 (sd752):
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Check all the external drives are powered on.

I think this is the problem with fiber channer cords and drivers. We also opened a ticket with sun. We are waiting for the answer from Sun.

Is this on a dual-path system?, i.e. are sd183 and sd752 the same disk?

Regards, Nisus
Introduction to R

R is considered the predominant language for data scientist and statisticians. Learn how to use R for your own data science projects.

If fiber channel, and the cords are not bent to much or otherwise damaged. It's probablt the gbic interfaces and/or I/O board that's about to break.
Do you get repeated online vs offline messages for these paths? Do they persist after reboot?

Not long ago (last year) I had such a problem. First I tried new gbic interfaces, and it seemed to get better. But after a few days it started again, and this time worse (no contact with the disk what so ever). Actually it was the system reboot that made things better for a while, and one of the I/O boards was the real problem.

look in :

corrupt label - wrong magic number or corrupt label or corrupt label - label checksum failed

After a power cycle, the machine displays either of the following error messages:


      corrupt label - label checksum failed

      corrupt label - wrong magic number

format(1M) displayed the following:

  0 unassigned    wm       0               0         (0/0/0)          0
  1 unassigned    wm       0               0         (0/0/0)          0
  2     backup    wm       0 - 5460        4.2G    (5460/0/0)   4154160
  3 unassigned    wm       0               0         (0/0/0)          0
  4 unassigned    wm       0               0         (0/0/0)          0
  5 unassigned    wm       0               0         (0/0/0)          0
  6 unassigned    wm       0 - 2730       2.1G       (0/0/0)          0
  7 unassigned        wm       2730-5460      2.1G       (0/0/0)          0

The disks were using raw partitions beginning at block 0 (cylinder 0). The disk label (VTOC) is kept on the block 0 of cylinder 0. The label eventually gets overwritten by database programs using raw partitions, if the raw partition begins at cylinder 0. (UNIX® file systems avoid this area of the partition.)

As a workaround, do the following:


      Go into format(1M) and get the backup label using the backup command.

      Relabel the disk using this backup label. You should then be able to access the disk.

      Backup the data on this disk.

      Go back to the disk and relabel it, starting the raw partition at cylinder 1. (This loses one cylinder, but prevents corrupting the VTOC.)

      Label again.

      Restore the data from your backup.

oh yes... oracle :-(

Maybe I missed it:

Can you give the type of Sun machine and disc cabinette you have
and the version of Solaris you are running

Are you running a hw based RAID ?

Did the problem occur right of the blue ?
or was it a result of a rebuild/install etc ?

Give me something to work with


Thnaks for suggestions. problem fixed.

No comment has been added lately, so it's time to clean up this TA.
I will leave a recommendation in the Cleanup topic area that this question is:

PAQ  No refund

Please leave any comments here within the next four days.


EE Cleanup Volunteer
PAQed - no points refunded (of 50)

Community Support Moderator

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial