raidctl on SUN T5240


 
Thread Tools Search this Thread
Operating Systems Solaris raidctl on SUN T5240
# 1  
Old 08-12-2008
raidctl on SUN T5240

Setting up a T5240 with two disks c1t0d0 and c1t1d0.

I am trying to use raidctl but when I issue.
Code:
raidctl -l

I get
Code:
Controller 1
    Disk: 0.0.0
    Disk: 0.1.0

So I try
Code:
raidctl -c '0.0.0 0.1.0' -r 1 1

and I get "Array in use."

I try
Code:
raidctl -c c1t0d0 c1t1d0

and I get "Array in use."

Does someone know what to do here? ThanksSmilie
# 2  
Old 08-12-2008
you have booted from c0t0d0? if so, you can't use raidctl on this disk cause it is already in use. you have to boot from cd/dvd and setup the raid BEFORE the os installation!
# 3  
Old 08-13-2008
ok, that is what I thought.

Solaris 10 is a 10G DVD, but download server is down currently.

OpenSolaris has a 686 MB CD iso I could use to boot off.

The T5240 has two 146GB Disks and 32GB FBDIMM memory.

The two disks on T5240 will just run OS, all applications will be
installed in zpool on a StorageTek Array.

What would be the recommendation for format and partition
of root, swap, etc... on T5240?
# 4  
Old 08-14-2008
Solaris 10 7/08 version has the same problem in that case, boot from that older version of Solaris 10 in single user mode and copy the binary of raidctl to replace the existing one. It will solve your problem also.
# 5  
Old 09-16-2008
Ok, this is what I did using new raidctl

In new raidctl you have to use raidctl -l volumename now and not just
raidctl

ok> boot cdrom -s

#raidctl -c -r 1 c1t0d0 c1t1d0

#format

at prompt format>
format c1t0d0 (it appears as one drive)
Auto Config
label

now you have to install OS, this is a must.

ok> boot cdrom - nowin

That is it.

I will post sun docs below if someone needs.

Code:
Solution Type Technical Instruction

Solution  203544 :   Labeling volumes and drives when working with Sun Fire[TM] T2000 RAID  

Related Categories

    * Home>Product>Systems>Servers
       


Description

JYBFU5F Internal ID use only.


After creating or deleting a RAID volume on the Sun Fire[TM] T2000 server, steps need to be taken to properly label the newly created volume or the available drives (used in the RAID volume) so that Solaris[TM] may use them correctly.

Steps to Follow

NA8WC3F Internal ID use only.


After using the 'raidctl' command to create a RAID volume on the T2000 the user needs to ensure that steps are taken to label the volume properly for use by Solaris. The 'raidctl' command will create the volume, but it does not create a new label for this volume so Solaris will not see the correct information until this step is taken.

here is an example of creating and labeling a striped RAID volume:
----------

root@t2000 # raidctl -c -r 0 c3t1d0 c3t2d0 c3t3d0
Creating RAID volume c3t1d0 will destroy all data on member disks, proceed (yes/no)? yes
Apr 14 11:23:40 t2000 scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 (mpt0):
Apr 14 11:23:40 t2000         Physical disk 0 created.
Apr 14 11:23:40 t2000 scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 (mpt0):
Apr 14 11:23:40 t2000         Physical disk 1 created.
Apr 14 11:23:41 t2000 scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 (mpt0):
Apr 14 11:23:41 t2000         Physical disk 2 created.
Apr 14 11:23:42 t2000 scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 (mpt0):
Apr 14 11:23:42 t2000         Volume 1 created.
Apr 14 11:23:42 t2000 scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 (mpt0):
Apr 14 11:23:42 t2000         Volume 1 is |enabled||optimal|
Apr 14 11:23:42 t2000 scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 (mpt0):
Apr 14 11:23:42 t2000         Volume 1 is |enabled||optimal|
Volume 'c3t1d0' created
root@t2000 #

root@t2000 # raidctl
RAID    Volume  RAID            RAID            Disk
Volume  Type    Status          Disk            Status
------------------------------------------------------
c3t1d0  IS      OK              c3t1d0          OK
                                c3t2d0          OK
                                c3t3d0          OK

root@t2000 # format
Searching for disks...done

AVAILABLE DISK SELECTIONS:
       0. c3t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
          /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@0,0
       1. c3t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
          /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@1,0
Specify disk (enter its number): 1

----------
As you can see the volume c3t1d0 still displays the label of the 72GB disk even though it is now a striped RAID volume of ~204 GB. It needs to be labeled correctly by using the 'type' and 'label' options in the format utility.

First, eelect the 'type' command at the 'format>' prompt, then select 0 (zero) to auto configure the volume:
----------

Specify disk (enter its number): 1
selecting c3t1d0
[disk formatted]

FORMAT MENU:
        disk       - select a disk
        type       - select (define) a disk type
        partition  - select (define) a partition table
        current    - describe the current disk
        format     - format and analyze the disk
        repair     - repair a defective sector
        label      - write label to the disk
        analyze    - surface analysis
        defect     - defect list management
        backup     - search for backup labels
        verify     - read and display labels
        save       - save new disk/partition definitions
        inquiry    - show vendor, product and revision
        volname    - set 8-character volume name
        !<cmd>     - execute <cmd>, then return
        quit
format> type

AVAILABLE DRIVE TYPES:
        0. Auto configure
        1. Quantum ProDrive 80S
        2. Quantum ProDrive 105S
        3. CDC Wren IV 94171-344
        4. SUN0104
        5. SUN0207
        6. SUN0327
        7. SUN0340
        8. SUN0424
        9. SUN0535
        10. SUN0669
        11. SUN1.0G
        12. SUN1.05
        13. SUN1.3G
        14. SUN2.1G
        15. SUN2.9G
        16. Zip 100
        17. Zip 250
        18. Peerless 10GB
        19. SUN72G
        20. other
Specify disk type (enter its number)[19]: 0
c3t1d0: configured with capacity of 204.49GB
<LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 409>
selecting c3t1d0
[disk formatted]
format>

------------
Write the new label to the disk using the 'label' command:
------------

format> label
Ready to label disk, continue? yes

format> disk

AVAILABLE DISK SELECTIONS:
       0. c3t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
          /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@0,0
       1. c3t1d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 409>
          /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@1,0
Specify disk (enter its number)[1]:

----------
Now, after the label has been fixed, the volume will be properly recognized by the format utility.

The same needs to be done after deleting a volume for Solaris to properly recognize the newly available disks that were previously used by the RAID volume. Before correcting the label, you may see messages like this indicating the label is not correct:
----------

WARNING: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@1,0 (sd4):
        Corrupt label - bad geometry 

        Label says 428854496 blocks; Drive says 143374738 blocks

----------
These messages will be not be seen after the label is corrected. Here is an example of the deletion of a volume and creating a proper label afterwards:
----------

root@t2000 # raidctl
RAID    Volume  RAID            RAID            Disk
Volume  Type    Status          Disk            Status
------------------------------------------------------
c3t1d0  IS      OK              c3t1d0          OK
                                c3t2d0          OK
                                c3t3d0          OK

root@t2000 # raidctl -d c3t1d0
Deleting volume c3t1d0 will destroy all data it contains, proceed (yes/no)? yes
Apr 14 15:38:23 t2000 scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 (mpt0):
Apr 14 15:38:23 t2000         Volume 1 deleted.
Apr 14 15:38:23 t2000 scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 (mpt0):
Apr 14 15:38:23 t2000         Physical disk 0 deleted.
Apr 14 15:38:23 t2000 scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 (mpt0):
Apr 14 15:38:23 t2000         Physical disk 1 deleted.
Apr 14 15:38:23 t2000 scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 (mpt0):
Apr 14 15:38:23 t2000         Physical disk 2 deleted.
Volume 'c3t1d0' deleted.
root@t2000 # raidctl
No RAID volumes found

root@t2000 # format
Searching for disks...done 

AVAILABLE DISK SELECTIONS:
       0. c3t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
          /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@0,0
       1. c3t1d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 409>
          /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@1,0
       2. c3t2d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
          /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@2,0
       3. c3t3d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
          /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@3,0
Specify disk (enter its number):

----------
Notice that the RAID volume label is still showing on c3t1d0. This will be corrected with the same steps used to create the label before. Select the 'type' command at the 'format>' prompt, then select 0 (zero) to auto configure the drive:
----------

Specify disk (enter its number): 1
selecting c3t1d0
[disk formatted]

FORMAT MENU:
        disk       - select a disk
        type       - select (define) a disk type
        partition  - select (define) a partition table
        current    - describe the current disk
        format     - format and analyze the disk
        repair     - repair a defective sector
        label      - write label to the disk
        analyze    - surface analysis
        defect     - defect list management
        backup     - search for backup labels
        verify     - read and display labels
        save       - save new disk/partition definitions
        inquiry    - show vendor, product and revision
        volname    - set 8-character volume name
        !<cmd>     - execute <cmd>, then return
        quit 
format> type

AVAILABLE DRIVE TYPES:
        0. Auto configure
        1. Quantum ProDrive 80S
        2. Quantum ProDrive 105S
        3. CDC Wren IV 94171-344
        4. SUN0104
        5. SUN0207
        6. SUN0327
        7. SUN0340
        8. SUN0424
        9. SUN0535
        10. SUN0669
        11. SUN1.0G
        12. SUN1.05
        13. SUN1.3G
        14. SUN2.1G
        15. SUN2.9G
        16. Zip 100
        17. Zip 250
        18. Peerless 10GB
        19. SUN72G
        20. LSILOGIC-LogicalVolume-3000
        21. other
Specify disk type (enter its number)[20]: 0
c3t1d0: configured with capacity of 68.35GB
<SUN72G  cyl 14087 alt 2 hd 24 sec 424>
selecting c3t1d0
[disk formatted]
format>

------------
Write the new label to the disk using the 'label' command:
------------

format> label
Ready to label disk, continue? yes

format> disk

AVAILABLE DISK SELECTIONS:
       0. c3t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
          /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@0,0
       1. c3t1d0 <SUN72G  cyl 14087 alt 2 hd 24 sec 424>
          /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@1,0
       2. c3t2d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
          /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@2,0
       3. c3t3d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
          /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@3,0
Specify disk (enter its number)[1]:

----------
The drives may now be used normally by Solaris again. Depending upon what type of RAID volume was in use, you may need to run through these step for each of the disks that were part of the RAID.

Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Solaris

Bizarre Sun T5240 behavior

Hi - I have a T5240 with 7 LDOMS configured. One night, network comm was broken somehow. Nobody was doing anything on the machine at the time. Here is what I saw in messages: WARNING: nxge3 : nxge_dma_mem_alloc: ddi_dma_mem_alloc kmem alloc failed WARNING: nxge3 : nxge_alloc_rx_buf_dma:... (2 Replies)
Discussion started by: pyroman
2 Replies

2. Shell Programming and Scripting

help in a script using raidctl

getStatusi86() { #storing logical volume name volumelist=`cfgadm -val | grep "Logical Volume" | awk '{print substr($1,9,14)}'` controller=`echo $volumelist | awk '{print substr($1,2,1)}'` #errordisk="" volume1=`echo $volumelist | awk '{print $1}'` for volume in $volumelist do... (1 Reply)
Discussion started by: frintocf
1 Replies

3. Solaris

SUN T5240 vs M3000

Hi, We are planning to buy new server for our data center. Sun T5240 or M3000 which one have better performance, we are going to create many dt sessions in this server. So, i need your suggestions. RJS (4 Replies)
Discussion started by: rajasekg
4 Replies

4. Solaris

Raidctl - Sun T5240 Solaris 10 Problem

I tried using raidctl earlier today to use my 2 disks in a RAID1 setup and I totally destroyed my OS install. I'm sure I did something funky and it freaked out. No big deal...right? This is what I was seeing after a reboot. I decided to just reinstall the OS. It let me go through all of... (3 Replies)
Discussion started by: kingdbag
3 Replies

5. UNIX for Dummies Questions & Answers

Information About raidctl

Hello people i have a question, when i put raidctl -l on sun fire show this Volume Size Stripe Status Cache RAID Sub Size Level Disk ... (0 Replies)
Discussion started by: enkei17
0 Replies

6. UNIX for Advanced & Expert Users

Solaris 10 Raidctl

Hello World: Recently I ran into an issue where a collegue had installed a Sun T5140 with twin 136GB disks in them. However, he forgot to execute the raidctl command first to mirror c1t0d0 to c1t1d0 boo hoo:) So along I come and try to mirror the disks by booting to sigle user... (1 Reply)
Discussion started by: rambo15
1 Replies

7. Solaris

raidctl

At my own eys I can see 4 disks inside of server. Previous admin told me that hardware mirror is done. What I see with "format" is 2 disks - I suspect that these are 2 MIRRORS. I just cant be sure because raidctl show this: # raidctl -l c0t0d0 Volume Size Stripe ... (0 Replies)
Discussion started by: czezz
0 Replies

8. UNIX for Dummies Questions & Answers

raidctl and resync when reboot

I am using raidctl on a v440 disk and noticed it resyncs after every boot, which takes about 30 minutes because of the size of the partition. I am concerned with what happens during the resync if "writes" happen to the disk before it is complete? Any info would be helpful. Thanks (0 Replies)
Discussion started by: csgonan
0 Replies

9. UNIX for Dummies Questions & Answers

disksuite and raidctl used together

I have a live Sunfire v440 server with 4 drives and I want to mirror drive 0 & 1 to 2 & 3. The on-board raid controller only allows for 1 live mirror. I was thinking of disksuite, but unfortunately the second disk is just one large partition with no free slices. I was thinking of using... (0 Replies)
Discussion started by: csgonan
0 Replies
Login or Register to Ask a Question