Sponsored Content
Full Discussion: Disk controller reassignment
Operating Systems Solaris Disk controller reassignment Post 302819017 by kerrygold on Monday 10th of June 2013 05:28:23 AM
Old 06-10-2013
Hi,

Thanks for the help so far.
The problem is seen just after the solaris is installed (it tries to create the root mirror on the 600gb disk instead of the 300gb)

the output of metastat is:
Code:
# metastat d0
d0: Mirror
    Submirror 0: d10
      State: Okay         
    Submirror 1: d20
      State: Resyncing    
    Resync in progress: 0 % done
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 542925000 blocks (258 GB)

d10: Submirror of d0
    State: Okay         
    Hot spare pool: hsp001
    Size: 542925000 blocks (258 GB)
    Stripe 0:
        Device                             Start Block  Dbase        State Reloc Hot Spare
        /dev/dsk/c0t5000CCA03C3B0B70d0s0          0     No            Okay   Yes 


d20: Submirror of d0
    State: Resyncing    
    Hot spare pool: hsp001
    Size: 1048576968 blocks (500 GB)
    Stripe 0:
        Device                             Start Block  Dbase        State Reloc Hot Spare
        /dev/dsk/c0t5000CCA03C3F98F8d0s0          0     No            Okay   Yes 


Device Relocation Information:
Device                           Reloc  Device ID
/dev/dsk/c0t5000CCA03C3B0B70d0   Yes    id1,sd@n5000cca03c3b0b70
/dev/dsk/c0t5000CCA03C3F98F8d0   Yes    id1,sd@n5000cca03c3f98f8
#

I will try to break mirrors manually with raid tools and see what i can do...
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Controller Naming

Hello all, How does the Solaris identifies the controller subscript ? ( like c0txdxs0 or c1txdxsx ?? ) I have a unix box ( Ultra 30) running with 2.5.1. When I connected an external hard disk to the on-board scsi port, it got identified as c0t1dxsx... (... (1 Reply)
Discussion started by: shibz
1 Replies

2. Solaris

Controller target disk?

Hi, I am a newbie to Solaris. I want to know how to find out the controller target and disk number on a SunFire V890 box that has 6X72GB disks. The probe-scsi output is as shown below: /pci@8,600000/SUNW,qlc@2 LiD HA LUN --- Port WWN --- ----- Disk description ----- 0 0 0 ... (1 Reply)
Discussion started by: sudhir_shet
1 Replies

3. Solaris

changing controller name

Dear Solarizer, If i have a disk let say like this c1t0d0s0 How to change the controller to be come example : c3t0d0s0 Thanxs For your replay Regads, tpx (3 Replies)
Discussion started by: tpx99
3 Replies

4. SCO

Warning HD: no root disk controller was found

hi... i hav a problem to install sco unix while installing sco unix 5.0.5 in acer altos with hardware raid am getting error "Warning HD: no root disk controller was found system error 5: while getting fs type flushing controller: DAC960PRL cache done." i hav use the following... (18 Replies)
Discussion started by: mselvaprakash
18 Replies

5. HP-UX

[Joy Share] - Replace an unknown status controller on HP FC60 disk array

Replace an unknown status controller on HP FC60 disk array Author:JoyOnline JoyChangLu@gmail.com Trouble description: The users detected that the status of controller at A is unknown. Analysis and diagnostic: Physical observed all leds on enclosure of disk array is normal. The... (4 Replies)
Discussion started by: JoyOnLine
4 Replies

6. SCO

SCO 5.0.7 no root disk controller found error during install

I'm "attempting" to install SCO 5.0.7 on an HP ML370 G4 server and am ready to bash the keyboard with head now. I keep getting the error message "WARNING hd: no root disk controller found" when running the bootable install cd. I have a raid 5 array with an online spare created using 4 36.3 GB... (2 Replies)
Discussion started by: FrictionBurn
2 Replies

7. Solaris

Help needed to find out the disk controller for veritas disks

hi all i am using vxvm 5.1 on my sun blade 150 which is running with solaris 5.10. When i give the command "vxdisk list" it gives the following output # vxdisk list DEVICE TYPE DISK GROUP STATUS c0t0d0s2 auto:none - - online... (2 Replies)
Discussion started by: kingston
2 Replies

8. SCO

Change Disk controller in SCO 6.0.0

So today I tried to upgrade a customer from a Proliant with an HPSAS controller to an Intel server with a MEGASAS controller. First, I downloaded the megasas driver from SCO and installed it on the old system. Then I created a new Microlite Edge emergency boot cd with the new driver on it. I... (2 Replies)
Discussion started by: jgt
2 Replies

9. Solaris

Changed disk controller -> drops into GRUB?!

I changed disk controller. Unplugged every disk, inserted another controller card, an IBM M1015. The disks are recognized in BIOS, and the controller card's BIOS shows up. But after that, I drop into GRUB and a prompt. That is all. How shall I solve this problem? I am thinking of booting from... (2 Replies)
Discussion started by: kebabbert
2 Replies

10. Solaris

Sun Fire v440 Hard disk or controller broken? WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1)

Hi, I have a Sun Fire V440 server that fails to boot up correctly. A lot of services are not started and the sytems acts really slow to commands. During boot I can see the following Error: WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1): SCSI transport failed: reason 'reset': retrying... (15 Replies)
Discussion started by: oliwei
15 Replies
metastat(1M)															      metastat(1M)

NAME
metastat - display status for metadevice or hot spare pool SYNOPSIS
/usr/sbin/metastat -h /usr/sbin/metastat [-a] [-B] [-c] [-i] [-p] [-q] [-s setname] [-t] [metadevice...] [hot_spare_pool...] /usr/sbin/metastat [-a] [-B] [-c] [-i] [-p] [-q] [-s setname] component... The metastat command displays the current status for each metadevice (including stripes, concatenations, concatenations of stripes, mir- rors, RAID5, soft partitions, and trans devices) or hot spare pool, or of specified metadevices, components, or hot spare pools. It is helpful to run the metastat command after using the metattach command to view the status of the metadevice. metastat displays the state of each Solaris Volume Manager RAID-1 volume on the system. The possible states include: Okay The device reports no errors. Needs maintenance A problem has been detected. This requires that the system administrator replace the failed physical device. Vol- umes displaying Needs maintenance have incurred no data loss, although additional failures could risk data loss. Take action as quickly as possible. Last erred A problem has been detected. Data loss is a possibility. This might occur if a component of a submirror fails and is not replaced by a hot spare, therefore going into Needs maintenance state. If the corresponding component also fails, it would go into Last erred state and, as there is no remaining valid data source, data loss could be a pos- sibility. Unavailable A device cannot be accessed, but has not incurred errors. This might occur if a physical device has been removed with Solaris Dynamic Reconfiguration (DR) features, thus leaving the Solaris Volume Manager volume unavailable. It could also occur if an array or disk is powered off at system initialization, or if a >1TB volume is present when the system is booted in 32-bit mode. After the storage has been made available, run the metastat command with the -i option to update the status of the metadevices. This clears the unavailable state for accessible devices. See the for instructions on replacing disks and handling volumes in Needs maintenance or Last erred states. The following options are supported: -a Display all disk sets. Only metadevices in disk sets that are owned by the current host are displayed. -B Display the current status of all of the 64-bit metadevices and hot spares. -c Display concise output. There is one line of output for each metadevice. The output shows the basic structure and the error status, if any, for each metadevice. The -c output format is distinct from the -p output format. The -p option does not display metadevice status and is not intended as human-readable output. -h Display usage message. -i Check the status of RAID-1 (mirror) volumes, RAID-5 volumes, and hot spares. The inquiry checks each metadevice for accessibility, starting at the top level metadevice. When problems are discovered, the metadevice state databases are updated as if an error had occurred. -p Display the list of active metadevices and hot spare pools in the same format as md.tab. See md.tab(4). The -p output is designed for snapshotting the configuration for later recovery or setup. -q Display the status for metadevices without the device relocation information. -s setname Specify the name of the disk set on which metastat works. Using the -s option causes the command to perform its administrative function within the specified disk set. Without this option, the command performs its function on metadevices and hot spare pools in the local disk set. -t Display the current status and timestamp for the specified metadevices and hot spare pools. The timestamp provides the date and time of the last state change. The following operands are supported: component Display the status of the component hosting a soft partition, including extents, starting blocks, and block count. hot_spare_pool Display the status of the specified hot spare pool(s). metadevice Display the status of the specified metadevice(s). If a trans metadevice is specified, the status of the master and log devices is also displayed. Trans metadevices have been replaced by UFS logging. See NOTES. Example 1: Output Showing Mirror with Two Submirrors The following example shows the partial output of the metastat command after creating a mirror, d0, consisting of two submirrors, d70 and d80. # metastat d0 d0: Mirror Submirror 0: d80 State: Okay Submirror 1: d70 State: Resyncing Resync in progress: 15 % done Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 2006130 blocks . . . Example 2: Soft Partition on Mirror with Submirror The following example shows the partial output of the metastat command after creating a soft partition, d3, on concat d2, which is built on a soft partition. # metastat d2: Concat/Stripe Size: 204800 blocks Stripe 0: Device Start Block Dbase State Hot Spare d0 0 No Okay d0: Soft Partition Component: c0t3d0s0 Status: Okay Size: 204800 blocks Extent Start Block Block count 0 129 204800 d3: Soft Partition Component: d2 Status: Okay Size: 202752 blocks Extent Start Block Block count 0 129 202752 Example 3: Trans Metadevice The following example shows the output of the metastat command after creating a trans metadevice. # metastat d2: Concat/Stripe Size: 204800 blocks Stripe 0: Device Start Block Dbase State Hot Spare d0 0 No Okay d0: Soft Partition Component: c0t3d0s0 Status: Okay Size: 204800 blocks Extent Start Block Block count 0 129 204800 d3: Soft Partition Component: d2 Status: Okay Size: 202752 blocks Extent Start Block Block count 0 129 202752 Example 4: Multi-owner disk set The following example shows the output of the metastat command with a multi-owner disk set and application-based mirror resynchronization option. Application-based resynchronization is set automatically if needed. # metastat -s oban oban/d100: Mirror Submirror 0: oban/d10 State: Okay Submirror 1: oban/d11 State: Okay Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Resync option: application based Owner: None Size: 1027216 blocks (501 MB) oban/d10: Submirror of oban/d100 State: Okay Size: 1027216 blocks (501 MB) Stripe 0: Device Start Block Dbase State Reloc Hot Spare c1t3d0s0 0 No Okay oban/d11: Submirror of oban/d100 State: Okay Size: 1027216 blocks (501 MB) Stripe 0: Device Start Block Dbase State Reloc Hot Spare c1t4d0s0 0 No Okay WARNINGS
metastat displays states as of the time the command is entered. It is unwise to use the output of the metastat -p command to create a md.tab(4) file for a number of reasons: o The output of metastat -p might show hot spares being used. o It might show mirrors with multiple submirrors. See metainit(1M) for instructions for creating multi-way mirrors using metainit and metattach. o A slice may go into an error state after metastat -p is issued. The following exit values are returned: 0 Successful completion. >0 An error occurred. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWmdr | +-----------------------------+-----------------------------+ |Stability |Evolving | +-----------------------------+-----------------------------+ mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M), metarecover(1M), metarename(1M), metareplace(1M), metaroot(1M), metaset(1M), metassist(1M), metasync(1M), metattach(1M), md.tab(4), md.cf(4), mddb.cf(4), md.tab(4), attributes(5), md(7D) Trans metadevices have been replaced by UFS logging. Existing trans devices are not logging--they pass data directly through to the under- lying device. See mount_ufs(1M) for more information about UFS logging. 30 Mar 2005 metastat(1M)
All times are GMT -4. The time now is 04:04 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy