SUMMARY: Sun T5220 Hardware Mirror Problem : Corrupt label - bad geometry

Hi ALL,

Thank you all for your replies.  What I eventually had to do was use
Solaris10 update 7 to create the mirror and perform all the functions as
per the documentation ie type and label the new mirror and the errors
disappeared.  Now I will install Solaris 10 with update 8 CD.

Thanks
Andrew Luande

-----Original Message-----
From: sunmanagers-bounces@sunmanagers.org
[mailto:sunmanagers-bounces@sunmanagers.org] On Behalf Of sun
Sent: Tuesday, November 17, 2009 12:19 PM
To: sunmanagers@sunmanagers.org
Subject: Sun T5220 Hardware Mirror Problem : Corrupt label - bad
geometry

Hi All,

I am having some problem with my new productions server which is only
about 2 weeks old.  It is a Sun SPARC Enterprise T5220 Server, 4 Core
1.2GHz UltraSPARC T2 processor, 4GB FBDIMM memory (4 * 1GB), 2 * 146GB
10K RPM SAS disks, 1 DVD+/-RW, 4 - 10/100/1000 Ethernet ports, 1 serial
port, 4 USB ports, 4 dedicated PCI-E low profile slots, 2 PCI-E low
profile or XAUI (10Gb ethernet) slots, 2 (N+1) 750W power supplies,
Solaris 10 and Java Enterprise System software pre-installed, RoHS-6
compliant Server with 2 146GB 10K RPM 2.5" SAS disk drives.

I am trying to create a hardware mirror using raidctl but I get the
warning

"WARNING: /pci@0/pci@0/pci@2/scsi@0/sd@0,0 (sd0):Corrupt label - bad
geometry"

throughout after the process and the error below trying to label.

Label says 286718976 blocks; Drive says 286607360 blocks
Warning: error writing VTOC.
Warning: no backup labels
Write label failed

I cannot label the disks after I create this mirror using raidctl.  When
I delete the mirror I am able to use the disks as normal without any
raid functionality.  I have tried to type and label the disk before
creating the mirror but to no avail.

This is my second 5220 server, the other one is about 1 year older but I
never struggled as much on that one.  I have tried to search the net but
I have no solution.  Has anyone experienced this problem?  I will
summarize as normal.  I am pasting the process below.

Thanks
Andrew Luande

# format
Searching for disks...done

c1t0d0: configured with capacity of 136.71GB
c1t1d0: configured with capacity of 136.71GB

AVAILABLE DISK SELECTIONS:
       0. c1t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
          /pci@0/pci@0/pci@2/scsi@0/sd@0,0
       1. c1t1d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
          /pci@0/pci@0/pci@2/scsi@0/sd@1,0
Specify disk (enter its number): 0
selecting c1t0d0
[disk formatted]
Disk not labeled.  Label it now? yes

format> type
Specify disk type (enter its number)[19]: 0
c1t0d0: configured with capacity of 136.71GB
<SUN146G cyl 14087 alt 2 hd 24 sec 848>
selecting c1t0d0
[disk formatted]

partition> label
Ready to label disk, continue? yes

# newfs   /dev/dsk/c1t0d0s6
newfs: construct a new file system /dev/rdsk/c1t0d0s6: (y/n)? y
Warning: 4992 sector(s) in last cylinder unallocated
/dev/rdsk/c1t0d0s6:     286698624 sectors in 46664 cylinders of 48
tracks, 128 s
ectors
        139989.6MB in 2917 cyl groups (16 c/g, 48.00MB/g, 5824 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
 32, 98464, 196896, 295328, 393760, 492192, 590624, 689056, 787488,
885920,
Initializing cylinder groups:
..........................................................
super-block backups for last 10 cylinder groups at:
 285773216, 285871648, 285970080, 286068512, 286166944, 286265376,
286363808,
 286462240, 286560672, 286659104

# raidctl -c -r 1 c1t0d0 c1t1d0
Creating RAID volume will destroy all data on spare space of member
disks, proceed (yes/no)? yes
/pci@0/pci@0/pci@2/scsi@0 (mpt0):
        Physical disk 0 created.
/pci@0/pci@0/pci@2/scsi@0 (mpt0):
        Physical disk 1 created.
/pci@0/pci@0/pci@2/scsi@0 (mpt0):
        Volume 0 created.
/pci@0/pci@0/pci@2/scsi@0 (mpt0):
        Physical disk (target 1) is |out of sync||online|
/pci@0/pci@0/pci@2/scsi@0 (mpt0):
        Volume 0 is |enabled||degraded|
/pci@0/pci@0/pci@2/scsi@0 (mpt0):
        Volume 0 is |enabled||resyncing||degraded|
WARNING: /pci@0/pci@0/pci@2/scsi@0/sd@0,0 (sd0):
        Corrupt label - bad geometry

        Label says 286718976 blocks; Drive says 286607360 blocks
WARNING: /pci@0/pci@0/pci@2/scsi@0/sd@0,0 (sd0):
        Corrupt label - bad geometry

        Label says 286718976 blocks; Drive says 286607360 blocks
Volume c1t0d0 is created successfully!


partition> label
Specify disk type (enter its number)[19]: 0
c1t0d0: configured with capacity of 136.49GB
<LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 273>
selecting c1t0d0
[disk formatted]
WARNING: /pci@0/pci@0/pci@2/scsi@0/sd@0,0 (sd0):
        Corrupt label - bad geometry

        Label says 286718976 blocks; Drive says 286607360 blocks
Disk not labeled.  Label it now? yes
WARNING: /pci@0/pci@0/pci@2/scsi@0/sd@0,0 (sd0):
        Corrupt label - bad geometry

        Label says 286718976 blocks; Drive says 286607360 blocks
WARNING: /pci@0/pci@0/pci@2/scsi@0/sd@0,0 (sd0):
        Corrupt label - bad geometry

        Label says 286718976 blocks; Drive says 286607360 blocks
WARNING: /pci@0/pci@0/pci@2/scsi@0/sd@0,0 (sd0):
        Corrupt label - bad geometry

        Label says 286718976 blocks; Drive says 286607360 blocks
Warning: error writing VTOC.
Warning: no backup labels
Write label failed
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers