Replaced drive in Sun Blade 100 - getting "corrupt label"

Replaced drive in Sun Blade 100 - getting "corrupt label"

Post by ohay » Sat, 25 Mar 2006 16:35:45



Hi,

I replaced the 15GB drive in my Sun Blade 100 with a 120GB drive, and
did a clean installation of Solaris 9 9/05.  The installation seemed to
have gone ok, and I can boot from the newly-installed Solaris system,
but whenever I reboot the system, I get a msg:

WARNING: ....... (dad0)
Corrupt label - Wrong magic number

I've been researching this, and I'm wondering, was I suppose to do a
format -> label during the installation?  

If so, when/how was I suppose to have done that.

Also, the system seems to be running ok, now, other than that msg at
boot.  Can I label the drive now without destroying the Solaris
installation?

Thanks!

Jim

 
 
 

Replaced drive in Sun Blade 100 - getting "corrupt label"

Post by Wolfgan » Sat, 25 Mar 2006 19:20:04


ohaya schrieb:
Quote:> Hi,

> I replaced the 15GB drive in my Sun Blade 100 with a 120GB drive, and
> did a clean installation of Solaris 9 9/05.  The installation seemed to
> have gone ok, and I can boot from the newly-installed Solaris system,
> but whenever I reboot the system, I get a msg:

> WARNING: ....... (dad0)
> Corrupt label - Wrong magic number

> I've been researching this, and I'm wondering, was I suppose to do a
> format -> label during the installation?  

> If so, when/how was I suppose to have done that.

> Also, the system seems to be running ok, now, other than that msg at
> boot.  Can I label the drive now without destroying the Solaris
> installation?

> Thanks!

> Jim

what is your prtvtoc output?
I see this message on raw disks when they begin the partition with the
first cylinder, and running devfsadm or similar.

 
 
 

Replaced drive in Sun Blade 100 - getting "corrupt label"

Post by ohay » Sat, 25 Mar 2006 21:21:38



> ohaya schrieb:
> > Hi,

> > I replaced the 15GB drive in my Sun Blade 100 with a 120GB drive, and
> > did a clean installation of Solaris 9 9/05.  The installation seemed to
> > have gone ok, and I can boot from the newly-installed Solaris system,
> > but whenever I reboot the system, I get a msg:

> > WARNING: ....... (dad0)
> > Corrupt label - Wrong magic number

> > I've been researching this, and I'm wondering, was I suppose to do a
> > format -> label during the installation?

> > If so, when/how was I suppose to have done that.

> > Also, the system seems to be running ok, now, other than that msg at
> > boot.  Can I label the drive now without destroying the Solaris
> > installation?

> > Thanks!

> > Jim
> what is your prtvtoc output?
> I see this message on raw disks when they begin the partition with the
> first cylinder, and running devfsadm or similar.

Wolfgang,

For which device did you want the prtvtoc?

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

bash-2.05# prtvtoc /dev/rdsk/c0t0d0s0
* /dev/rdsk/c0t0d0s0 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
*   234428640      4080 234432719
*
*                          First     Sector    Last
* Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
       0      2    00    8192640 205754400 213947039   /
       1      3    01          0   8192640   8192639
       2      5    00          0 234432720 234432719
       7      8    00  213947040  20481600 234428639   /export/home
bash-2.05#

If the problem is as you mentioned, how do I fix it?

Thanks,
Jim

 
 
 

Replaced drive in Sun Blade 100 - getting "corrupt label"

Post by ohay » Sat, 25 Mar 2006 21:26:52




> > ohaya schrieb:
> > > Hi,

> > > I replaced the 15GB drive in my Sun Blade 100 with a 120GB drive, and
> > > did a clean installation of Solaris 9 9/05.  The installation seemed to
> > > have gone ok, and I can boot from the newly-installed Solaris system,
> > > but whenever I reboot the system, I get a msg:

> > > WARNING: ....... (dad0)
> > > Corrupt label - Wrong magic number

> > > I've been researching this, and I'm wondering, was I suppose to do a
> > > format -> label during the installation?

> > > If so, when/how was I suppose to have done that.

> > > Also, the system seems to be running ok, now, other than that msg at
> > > boot.  Can I label the drive now without destroying the Solaris
> > > installation?

> > > Thanks!

> > > Jim
> > what is your prtvtoc output?
> > I see this message on raw disks when they begin the partition with the
> > first cylinder, and running devfsadm or similar.

> Wolfgang,

> For which device did you want the prtvtoc?

> Here's "prtvtoc /dev/rdsk/c0t0d0s0":

> bash-2.05# prtvtoc /dev/rdsk/c0t0d0s0
> * /dev/rdsk/c0t0d0s0 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
> *   234428640      4080 234432719
> *
> *                          First     Sector    Last
> * Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
>        0      2    00    8192640 205754400 213947039   /
>        1      3    01          0   8192640   8192639
>        2      5    00          0 234432720 234432719
>        7      8    00  213947040  20481600 234428639   /export/home
> bash-2.05#

> If the problem is as you mentioned, how do I fix it?

> Thanks,
> Jim

Hi,

Also, here's a format -> verify:

format> verify

Primary label contents:

Volume name = <        >
ascii name  = <ST3120814A cyl 57459 alt 2 hd 16 sec 255>
pcyl        = 57461
ncyl        = 57459
acyl        =    2
nhead       =   16
nsect       =  255
Part      Tag    Flag     Cylinders         Size            Blocks
  0       root    wm    2008 - 52437       98.11GB    (50430/0/0)
205754400
  1       swap    wu       0 -  2007        3.91GB    (2008/0/0)  
8192640
  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

format>

It looks like swap is occupying cylinder 0?

If I have to do a re-install to fix this, what additional steps do I
need to do on the next install to avoid this problem?  I don't recall
anywhere where I set the starting cylinders?

Jim

 
 
 

Replaced drive in Sun Blade 100 - getting "corrupt label"

Post by ohay » Sat, 25 Mar 2006 22:24:26





> > > ohaya schrieb:
> > > > Hi,

> > > > I replaced the 15GB drive in my Sun Blade 100 with a 120GB drive, and
> > > > did a clean installation of Solaris 9 9/05.  The installation seemed to
> > > > have gone ok, and I can boot from the newly-installed Solaris system,
> > > > but whenever I reboot the system, I get a msg:

> > > > WARNING: ....... (dad0)
> > > > Corrupt label - Wrong magic number

> > > > I've been researching this, and I'm wondering, was I suppose to do a
> > > > format -> label during the installation?

> > > > If so, when/how was I suppose to have done that.

> > > > Also, the system seems to be running ok, now, other than that msg at
> > > > boot.  Can I label the drive now without destroying the Solaris
> > > > installation?

> > > > Thanks!

> > > > Jim
> > > what is your prtvtoc output?
> > > I see this message on raw disks when they begin the partition with the
> > > first cylinder, and running devfsadm or similar.

> > Wolfgang,

> > For which device did you want the prtvtoc?

> > Here's "prtvtoc /dev/rdsk/c0t0d0s0":

> > bash-2.05# prtvtoc /dev/rdsk/c0t0d0s0
> > * /dev/rdsk/c0t0d0s0 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
> > *   234428640      4080 234432719
> > *
> > *                          First     Sector    Last
> > * Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
> >        0      2    00    8192640 205754400 213947039   /
> >        1      3    01          0   8192640   8192639
> >        2      5    00          0 234432720 234432719
> >        7      8    00  213947040  20481600 234428639   /export/home
> > bash-2.05#

> > If the problem is as you mentioned, how do I fix it?

> > Thanks,
> > Jim

> Hi,

> Also, here's a format -> verify:

> format> verify

> Primary label contents:

> Volume name = <        >
> ascii name  = <ST3120814A cyl 57459 alt 2 hd 16 sec 255>
> pcyl        = 57461
> ncyl        = 57459
> acyl        =    2
> nhead       =   16
> nsect       =  255
> Part      Tag    Flag     Cylinders         Size            Blocks
>   0       root    wm    2008 - 52437       98.11GB    (50430/0/0)
> 205754400
>   1       swap    wu       0 -  2007        3.91GB    (2008/0/0)
> 8192640
>   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

> format>

> It looks like swap is occupying cylinder 0?

> If I have to do a re-install to fix this, what additional steps do I
> need to do on the next install to avoid this problem?  I don't recall
> anywhere where I set the starting cylinders?

> Jim

Hi,

I forgot to mention, this is a non-Sun Seagate drive.  I guess that the
drives that are purchased from Sun are already formatted to avoid this
problem?

In any event, I still would like to know how to do this correctly, with
this drive.

Thanks,
Jim

 
 
 

Replaced drive in Sun Blade 100 - getting "corrupt label"

Post by Wolfgan » Sat, 15 Apr 2006 18:25:24


ohaya schrieb:


>>ohaya schrieb:

>>>Hi,

>>>I replaced the 15GB drive in my Sun Blade 100 with a 120GB drive, and
>>>did a clean installation of Solaris 9 9/05.  The installation seemed to
>>>have gone ok, and I can boot from the newly-installed Solaris system,
>>>but whenever I reboot the system, I get a msg:

>>>WARNING: ....... (dad0)
>>>Corrupt label - Wrong magic number

>>>I've been researching this, and I'm wondering, was I suppose to do a
>>>format -> label during the installation?

>>>If so, when/how was I suppose to have done that.

>>>Also, the system seems to be running ok, now, other than that msg at
>>>boot.  Can I label the drive now without destroying the Solaris
>>>installation?

>>>Thanks!

>>>Jim

>>what is your prtvtoc output?
>>I see this message on raw disks when they begin the partition with the
>>first cylinder, and running devfsadm or similar.

> Wolfgang,

> For which device did you want the prtvtoc?

> Here's "prtvtoc /dev/rdsk/c0t0d0s0":

> bash-2.05# prtvtoc /dev/rdsk/c0t0d0s0
> * /dev/rdsk/c0t0d0s0 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
> *   234428640      4080 234432719
> *
> *                          First     Sector    Last
> * Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
>        0      2    00    8192640 205754400 213947039   /
>        1      3    01          0   8192640   8192639
>        2      5    00          0 234432720 234432719
>        7      8    00  213947040  20481600 234428639   /export/home
> bash-2.05#

> If the problem is as you mentioned, how do I fix it?

> Thanks,
> Jim

it dont seems to be my problem, since it is not cylinder 0 nor it is a
raw artition. Most Disks from Sun are prelabeld, maybe the installation
dont care for that.  I think you can label the disk without destroying
your installation.
 
 
 

Replaced drive in Sun Blade 100 - getting "corrupt label"

Post by ohay » Sat, 15 Apr 2006 20:04:56


Quote:

> it dont seems to be my problem, since it is not cylinder 0 nor it is a
> raw artition. Most Disks from Sun are prelabeld, maybe the installation
> dont care for that.  I think you can label the disk without destroying
> your installation.

Wolfgang,

I gave up on using that 120GB Seagate in my Sun Blade awhile ago, and
swapped in an older WD 60GB drive.  That got labelled with no problem.

Jim

 
 
 

1. "value too large for defined data type" with mt on Sun Blade 100

Last night using "tar -cvf /dev/rmt/0" I backed up about 2.5 GB onto a
WangDAT 3400DX DDS2 tape drive using a 120m tape.  After the backup was
complete I ran mt -f /dev/rmt/0 status and received the "value too large
for defined data type" message.  I understand that some apps have a
problem with large file sizes but how would that effect a simple mt
status message?  No matter what mt option I run gives the "value too
large" message.  My tests with tar -tvf appear to show that the backup
worked but I didn't have time to restore the tape last night to make
sure.  When I start using ufsdump aren't I going to need a working mt?

Thanks, Greg

2. gcc_linux as a cross development system for dos and other targets

3. "ok" prompt is stuck on my sun blade 100

4. (HELP?!)Anyone get a SB Vibra 16 to work right?

5. Export Cdrom on Sun Blade 100 or Sun Blade 150

6. Mounting floppies formatted with fdformat

7. FS: Sun Blade 100/2GB Mem/60GB HD/KDS 17" Monitor

8. Accelerated-X 6.0 and Mandrake 8.0

9. Upgrading from sun blade 100 to sun fire 100

10. GETSERVBYNAME()????????????????????"""""""""""""

11. """"""""My SoundBlast 16 pnp isn't up yet""""""""""""

12. "Corrupt label - bad geometry" on Wren VII - can't eradicate msg.

13. Any utility can replace a label "DATE" in a file with `date output