This discussion is archived
11 Replies Latest reply: Aug 18, 2010 12:43 AM by 807557 RSS

Solaris 10 hardware mirroring

807557 Newbie
Currently Being Moderated
I have the new V445 Sun server with 4 73 Gbyte 2.5-inch disk drives wit SAS interface

Drives c0t0d0 and c0t1d0 I am using as a system drives and will install mirroring using SXM
Drives c0t2d0 ans c0t3d0 I am going to use as a data volume for Sybase DBMS.
I configured Hardware Mirriring

# raidctl -c c0t2d0 c0t3d0
.....
# raidctl
RAID Volume RAID RAID Disk
Volume Type Status Disk Status
------------------------------------------------------
c0t2d0 IM RESYNCING c0t2d0 OK
c0t3d0 OK

Then I created partitions on the volume c0t2d0 using format utility
Part Tag Flag Cylinders Size Blocks
0 unassigned wm 1 - 31 154.03MB (31/0/0) 315456
1 unassigned wm 32 - 60 144.09MB (29/0/0) 295104
2 backup wu 0 - 14086 68.35GB (14087/0/0) 143349312
3 unassigned wm 61 - 3358 16.00GB (3298/0/0) 33560448
4 unassigned wm 3359 - 6656 16.00GB (3298/0/0) 33560448
5 unassigned wm 6657 - 8305 8.00GB (1649/0/0) 16780224
6 unassigned wm 8306 - 14081 28.03GB (5776/0/0) 58776576
7 unassigned wm 0 0 (0/0/0) 0

And then I try to labeling drive and get a message:

Warning: Current geometry overshoots actual geometry of disk
and then
Continue labelling disk? yes
Warning: error writing VTOC.
Warning: error reading backup label.
Warning: error reading backup label.
Warning: error reading backup label.
Warning: error reading backup label.
Warning: error reading backup label.
Warning: no backup labels
Label failed.

and a bunch of messages in /var/adm/messages like
Aug 16 09:43:38 nyc-sor-cr-04 Error for Command: read(10) Error Level: Informational
Aug 16 09:43:38 nyc-sor-cr-04 scsi: [ID 107833 kern.notice] Requested Block: 0 Error Block: 0
Aug 16 09:43:38 nyc-sor-cr-04 scsi: [ID 107833 kern.notice] Vendor: FUJITSU Serial Number: 0728S0C74E
Aug 16 09:43:38 nyc-sor-cr-04 scsi: [ID 107833 kern.notice] Sense Key: Illegal Request
Aug 16 09:43:38 nyc-sor-cr-04 scsi: [ID 107833 kern.notice] ASC: 0x21 (logical block address out of range), ASCQ: 0x0, FRU: 0x22
Aug 16 09:43:38 nyc-sor-cr-04 scsi: [ID 107833 kern.warning] WARNING: /pci@1e,600000/pci@0/pci@2/scsi@0/sd@2,0 (sd4):

Please, help me. I was unable to find any information how to handle this situation
  • 1. Re: Solaris 10 hardware mirroring
    807557 Newbie
    Currently Being Moderated
    I have the new V445 Sun server with 4 73 Gbyte
    2.5-inch disk drives wit SAS interface

    Drives c0t0d0 and c0t1d0 I am using as a system
    drives and will install mirroring using SXM
    Drives c0t2d0 ans c0t3d0 I am going to use as a data
    volume for Sybase DBMS.
    I configured Hardware Mirriring

    # raidctl -c c0t2d0 c0t3d0
    .....
    # raidctl
    RAID Volume RAID RAID Disk
    Volume Type Status Disk
    Status
    -------------------------------------------
    c0t2d0 IM RESYNCING c0t2d0 OK
    c0t3d0 OK
    he volume c0t2d0 using format utility
    Part Tag Flag Cylinders Size
    Blocks
    ned wm 1 - 31 154.03MB (31/0/0)
    315456
    assigned wm 32 - 60 144.09MB
    (29/0/0) 295104
    backup wu 0 - 14086 68.35GB
    (14087/0/0) 143349312
    unassigned wm 61 - 3358 16.00GB
    (3298/0/0) 33560448
    unassigned wm 3359 - 6656 16.00GB
    (3298/0/0) 33560448
    unassigned wm 6657 - 8305 8.00GB
    (1649/0/0) 16780224
    unassigned wm 8306 - 14081 28.03GB
    (5776/0/0) 58776576
    unassigned wm 0 0
    (0/0/0) 0
    en I try to labeling drive and get a message:

    Warning: Current geometry overshoots actual geometry
    of disk
    and then
    Continue labelling disk? yes
    Warning: error writing VTOC.
    Warning: error reading backup label.
    Warning: error reading backup label.
    Warning: error reading backup label.
    Warning: error reading backup label.
    Warning: error reading backup label.
    Warning: no backup labels
    Label failed.

    and a bunch of messages in /var/adm/messages like
    Aug 16 09:43:38 nyc-sor-cr-04 Error for Command:
    read(10) Error Level: Informational
    Aug 16 09:43:38 nyc-sor-cr-04 scsi: [ID 107833
    kern.notice] Requested Block: 0
    Error Block: 0
    cr-04 scsi: [ID 107833 kern.notice] Vendor:
    FUJITSU Serial Number:
    0728S0C74E
    Aug 16 09:43:38 nyc-sor-cr-04 scsi: [ID 107833
    kern.notice] Sense Key: Illegal Request
    Aug 16 09:43:38 nyc-sor-cr-04 scsi: [ID 107833
    kern.notice] ASC: 0x21 (logical block address out
    of range), ASCQ: 0x0, FRU: 0x22
    Aug 16 09:43:38 nyc-sor-cr-04 scsi: [ID 107833
    kern.warning] WARNING:
    /pci@1e,600000/pci@0/pci@2/scsi@0/sd@2,0 (sd4):

    Please, help me. I was unable to find any information
    how to handle this situation
    Same exact issue for me
  • 2. Re: Solaris 10 hardware mirroring
    807557 Newbie
    Currently Being Moderated
    I already resolved problem.
    Do you need help?
  • 3. Re: Solaris 10 hardware mirroring
    807557 Newbie
    Currently Being Moderated
    Hi eds288,

    I'm having the same issue, can you post your fix?

    Thanks,

    sfo07
  • 4. Re: Solaris 10 hardware mirroring
    807557 Newbie
    Currently Being Moderated
    I had problem to create raid volume on disks c0t2d0 and c0t3do.
    First of all physical disks should be labeled correctly.
    Use 'format' for each disk.
    Choose type from the format menu and then choose "0. Auto configure"
    Then write label (using label command from the format prompr), do not bother to configure partitions

    Now, create raid volume
    raidctl -c c0t2d0 c0t3d0 (raid 1)
    or
    raidctl -c -r 0 c0t2d0 c0t3d0 (raid 0 stripe)

    Using raidctl check status, wait until status will become OK

    Now, again use 'format' command, choose drive c0t2d0 (it should be no c0t3d0),
    again choose type and Auto configure. You will see

    LSILOGIC-LogicalVolume3000 cyl 65533 alt 2 hd 16 sec 136

    Write the new label (using label command from the format prompr) without partishioning.

    After you perform these steps the drive is ready for use. You can now partition the drive as needed and use the volume within Solaris normally
  • 5. Re: Solaris 10 hardware mirroring
    807557 Newbie
    Currently Being Moderated
    hello

    I'm having excactly the same problem with a Sun Fire x4200 version 5.10, I've tried the above solution however I'm still getting the same error, with the "geometry not being the same," any other suggestions would much be appriciated.

    Thanks.
  • 6. Re: Solaris 10 hardware mirroring
    807557 Newbie
    Currently Being Moderated
    I had the same problem - here's how I fixed it.

    System Configuration: Sun Microsystems Sun Blade X6220 Server Module
    SunOS santiago 5.10 Generic_127112-03 i86pc i386 i86pc

    I wanted a secondary raidctl volume using 2 "LSILOGIC-LogicalVolume-3000" 143gb disks.
    *# raidctl -c c2t2d0 c2t3d0*
    *# format c2t2d0*
    format> type 0 (for auto configure)
    format> label
    this worked, but gave the "Current geometry overshoots actual geometry of disk" error.

    *# raidctl -d c2t2d0* delete the raidctl disk
    *# cfgadm -c configure c2::dsk/c2t3d0* (it becomes "unconfigured" after deletion !)
    *# format c2t2d0* (this timer, on the raw disk, not the raidctl volume)
    format> type 0
    format> label

    *# newfs /dev/dsk/c2t2d0s6* (creates a FileSystem on the disk - I mounted / un-mounted it afterwards to check everything was OK)
    *# raidctl -c c2t2d0 c2t3d0* (create the raidctl volume)
    *# mount /dev/dsk/c2t2d0s6 /mnt*

    The raidctl volume picked up the format and FileSystem details from the original disk, and everything seems to be fine.
  • 7. Re: Solaris 10 hardware mirroring
    807557 Newbie
    Currently Being Moderated
    There is a known issues with Solaris 10/09. After you use raidctl to RAID some disks together: When you use format, it won't let you "label" the disk after selecting "type" > Auto Configure. Gives the errors:

    Warning: error writing VTOC
    Warning: no backup labels
    Label failed.

    As a workaround, boot to single-user mode off of older version of Solairis 10. Then, it will let you label the LSI disk.
  • 8. Re: Solaris 10 hardware mirroring
    807557 Newbie
    Currently Being Moderated
    Do you know the bug ID for the know issue on Solairs10/09?
  • 9. Re: Solaris 10 hardware mirroring
    807557 Newbie
    Currently Being Moderated
    You are probably looking for bug# 6901327 - Creation of a hardware raid via raidctl with s10u8 fails to create a valid VTOC and disk label
  • 10. Re: Solaris 10 hardware mirroring
    807557 Newbie
    Currently Being Moderated
    I've run into the same issue when dealing with stripe sets built on a Hitachi Tagmastore frame. This disks will show up in format, but will all show our default LUN size rather than the size of the striped lun. We ran format->type->autoconfigure and got the same error message when attempting to write a label to the striped LUN.

    We tried two different workarounds that both seemed to work- booting single user off an older version of Solaris 10 (we used update 6) then doing format->type->autoconfigure->label. The other workaround was to attach the problem LUNs temporarily to a server running Solaris 9 09/05 (using the QLA2300 driver to run our qlogic fiber cards rather than leadville) and we were able to label the LUNs correctly and swing them back to our Solaris 10 10/09 box.

    I suspect that the core issue may be within the Leadville driver maybe? We didn't try using the qlogic branded driver on the 10/09 build so we can't rule out that it's an issue with format yet.. although I admit I haven't fully read over the bug report yet.
  • 11. Re: Solaris 10 hardware mirroring
    807557 Newbie
    Currently Being Moderated
    You can label the disk as EMI and then back to SMI as follows to get round this issue:

    format -e <disk>

    format> label
    [0] SMI Label
    [1] EFI Label
    Specify Label type[0]: *1*
    Warning: This disk has an SMI label. Changing to EFI label will erase all
    current partitions.
    Continue? y
    format> q

    format -e <disk>

    format> label
    [0] SMI Label
    [1] EFI Label
    Specify Label type[1]: 0
    Auto configuration via format.dat[no]?
    Auto configuration via generic SCSI-2[no]?
    format> q