Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

How to fix? Installed Solaris 9 on new (non-Sun) drive - now getting WARNING: ... (dad0) Corrupt label - wrong magic number

Posted on 2006-03-24
7
Medium Priority
?
704 Views
Last Modified: 2013-12-21
Hi,

I recently replaced the original 15GB Seagate drive in my Sun Blade 100 with a retail (non-Sun) Seagate 120GB drive.  I then did a new installation of Solaris 9 on the drive, and everything seems to be ok, i.e., I can boot to Solaris, etc.

The problem that I'm having is that whenever the system boots, I am getting a warning msg:

WARNING: /pci@1f,0 ................ (dad0)
Corrupt label - wrong magic number

I understand that this msg is because the disk is not properly "labeled" for Solaris (again, this was not a Sun drive, which I gather are pre-formatted and pre-labelled).

My question are:  

1) Is there any way to either eliminate the warning msg without having to re-install Solaris?  If so, how (in detail) can I do this?

2) If I have to, to get rid of the warning, I don't mind re-installing Solaris, but I've done Solaris installations a lot of times.  All of the previous times were on Sun drives, and I didn't see anywhere during the installation procedure that I'm suppose to label the drive, so:  If I have to do a re-install to eliminate the warning, what do I have to do differently during the installation?


In researching this, I found some information that indicates that the problem may be because the Solaris installation configured some slices/partitions to start in cylinder 0, so I have tried to boot from cdrom into single-user mode, and run format->partition->label, but I still get the warning.  

I've also tried format->partition, and adjusted the swap partition to start at cylinder 1 instead of cylinder 0, then done "label", but I still get the warning when I reboot.

Here's the current "prtvtoc /dev/rdsk/c0t0d0s0":

bash-2.05# prtvtoc /dev/rdsk/c0t0d0s0
* /dev/rdsk/c0t0d0s0 (volume "abc") partition map
*
* Dimensions:
*     512 bytes/sector
*     255 sectors/track
*      16 tracks/cylinder
*    4080 sectors/cylinder
*   57461 cylinders
*   57459 accessible cylinders
*
* Flags:
*   1: unmountable
*  10: read-only
*
* Unallocated space:
*       First     Sector    Last
*       Sector     Count    Sector
*           0      4080      4079
*   234428640      4080 234432719
*
*                          First     Sector    Last
* Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
       0      2    00    8192640 205754400 213947039   /
       1      3    01       4080   8188560   8192639
       2      5    00          0 234432720 234432719
       7      8    00  213947040  20481600 234428639   /export/home

And, here's the current format->partition->print:

partition> print
Volume:  abc
Current partition table (original):
Total disk cylinders available: 57459 + 2 (reserved cylinders)

Part      Tag    Flag     Cylinders         Size            Blocks
  0       root    wm    2008 - 52437       98.11GB    (50430/0/0) 205754400
  1       swap    wu       1 -  2007        3.90GB    (2007/0/0)    8188560
  2     backup    wm       0 - 57458      111.79GB    (57459/0/0) 234432720
  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                0         (0/0/0)             0
  7       home    wm   52438 - 57457        9.77GB    (5020/0/0)   20481600

Finally, here's the current /format.dat file:

bash-2.05# cat format.dat
#
# New disk/partition type  saved on Fri Mar 24 03:06:28 2006
#
disk_type = "ST3120814A" \
         : ctlr = ata : ncyl = 57459 : acyl = 2 : pcyl = 57461 \
         : nhead = 16 : nsect = 255 : rpm = 5400

partition = "original" \
         : disk = "ST3120814A" : ctlr = ata \
         : 0 =  2008, 205754400 : 1 =  0, 8192640 : 2 =  backup, \
         wm, 0, 234432720 : 7 =  home, wm, 52438, 20481600

I hope that someone here can help me with this.  I know that this is kind of dumb (a couple of people have suggested I just ignore the warning), but this is really bugging me, and I've spent a couple of days already on this :(!!

Thanks in advance,
Jim
0
Comment
Question by:jimcpl
6 Comments
 
LVL 1

Author Comment

by:jimcpl
ID: 16286867
Hi,

I did some further testing...

I installed Solaris 9 9/05 onto the 120GB drive.  Then, when I boot Solaris 9 9/05 off of the hard drive OR off of the 9 9/05 CDROM, I get the "corrupted label" warning.

If I boot a Solaris 10 1/06 CDROM, I *DON'T* get the "corrupt label" warning.

If I boot a Solaris 9 12/03 CDROM, I *DO* get the "corrupt label" warning.

If I go by the Solaris 10 test, the hard drive IS properly labelled, but if I go by either Solaris 9 9/05 or 12/03, the hard drive gives the "corrupt label" warning.

In all cases, when I go into format->partition-print, the partitions/slices look all right.

Any guesses as to what might be going on?

Jim
0
 
LVL 10

Expert Comment

by:Nukfror
ID: 16290731
Could be for several reasons including the /etc/format.dat file in Solaris 10 is more up to date and the sd device driver in Solaris 10 1/06 is more intelligent/flexible then the sd drivers in Solaris 9 12/03.

Just out of curiousity, are you trying Solaris 9 12/03 for a specific reason ?  If you can, go straight to Solaris 10 1/06.
0
 
LVL 6

Expert Comment

by:durindil
ID: 16291236
You can label the disk without it re-formatting it.  Just go into "format" and select the drive and label it.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 1

Author Comment

by:jimcpl
ID: 16291890
Hi,

Thanks for the suggestions.  As I think I mentioned earlier, I have tried format many times, but still was getting the warning at boot.

At this point in time, I believe that the problem is that an earlier Solaris 10 installation had done something or written something to the drive that prevented the Solaris 9 format command from properly writing a label, or from writing a proper (to Solaris 9) label.  

I removed the drive from the SB100, and put it into a PC, and wiped it clean using Seagate DiscWizard, and it's ok now.

FYI, since I've come up with a resolution, I am going to request that this question be closed.


Nukfor,

My actual goal when all of this started was to go to Solaris 9 9/05.  I just mentioned about booting to the Solaris 9 12/03 CD because I had used that to test if it was also having the warning msg.

Jim
0
 
LVL 6

Expert Comment

by:durindil
ID: 16294365
You can also post to the "Misc" area to ask that this question be closed and your points refunded.
0
 

Accepted Solution

by:
GranMod earned 0 total points
ID: 16345564
Closed, 300 points refunded.
GranMod
The Experts Exchange
Community Support Moderator of all Ages
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When you do backups in the Solaris Operating System, the file system must be inactive. Otherwise, the output may be inconsistent. A file system is inactive when it's unmounted or it's write-locked by the operating system. Although the fssnap utility…
In tuning file systems on the Solaris Operating System, changing some parameters of a file system usually destroys the data on it. For instance, changing the cache segment block size in the volume of a T3 requires that you delete the existing volu…
Learn how to get help with Linux/Unix bash shell commands. Use help to read help documents for built in bash shell commands.: Use man to interface with the online reference manuals for shell commands.: Use man to search man pages for unknown command…
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
Suggested Courses
Course of the Month21 days, 5 hours left to enroll

810 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question