Sponsored Content
Operating Systems Solaris How to find missing disks on Sun x4150 without reboot? Post 302520035 by sboots on Thursday 5th of May 2011 04:09:55 PM
Old 05-05-2011
Im pretty sure the X4150's have internal raid controllers. If you do and you are using it, you have to go into that at boot and add the volumes.
This User Gave Thanks to sboots For This Post:
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Sun internal disks and HBA card

I have a V490 that has couple internal disks attached to the same dual-port HBA card that I'm planning attach to the SAN for additional storage. Would I sacrifice performance if I use the same HBA? Is it better to throw in a new HBA instead? (1 Reply)
Discussion started by: kiem
1 Replies

2. Solaris

disks - Sun Enterprise 220R and SF 280R

Hi, I have SE 220R with 2 disks mirrored using SVM and running OS - solaris 9. Because of performance issues on 220R I'd like to move the OS/application data to SF 280R. Having found that SF280R will only support Fiber channel disks, I am now wondering how to move complete data from SCSI... (3 Replies)
Discussion started by: upengan78
3 Replies

3. Red Hat

missing raid array after reboot

Dear all , i ve configured raid 0 in redhat machine(VM ware), by following steps: #mdadm -C /dev/md0 -l 0 -n 2 /dev/sdb1 /dev/sdc1 #mkfs.ext3 /dev/md0 #mdadm --detail --scan --config=mdadm.conf >/etc/mdadm.conf then mounted the/dev/md0 device and also added a entry in fstab. how... (2 Replies)
Discussion started by: sriniv666
2 Replies

4. Solaris

Reboot causes disks in Resync State

Dear Team, This time i am facing some new problems which is beyond my thinking. I need some expert advice. We are having 4 Servers ( 2 nos Sun SPARC Enterprise T5220 & 2 nos of SF e2900 Servers ). Both the T5220 Servers are Termed as Node A and Node B . The same things are followed with... (1 Reply)
Discussion started by: sudhansu
1 Replies

5. Solaris

Upgrade Sun x4150 ELOM issue

Hi, I was trying to upgrade firmware for this Sun x4150 from ELOM to ILOM. I did it under GUI ELOM Manager > Maintenance > Firmware Upgrade. It then showed 'Someone is upgrading firmware' and took forever. I believe its hung due to unknown reason (wrong file used?). I poweroff and poweron the... (4 Replies)
Discussion started by: aixlover
4 Replies

6. Fedora

Missing entries in log files just before/after reboot

Hello world, One of the servers, a Fedora one,rebooted today (Luckily, a testbox). I tried to get the reason the server rebooted. After going through the messages, I think that the log entries just before and after reboot are missing. Please below: (****** is the server name, for privacy... (0 Replies)
Discussion started by: satish51392111
0 Replies

7. Solaris

Solaris 10 Installation - Disks missing, and Raid

Hey everyone. First, let me start by saying I'm primarily focused on linux boxes, and just happened to get pulled into building two T5220's. I'm not super educated on sun boxes. Both T5220's have 8 146GB 15k SAS drives. Inside the service processor, I can run SHOW /SYS/HDD{0-7} and they all come... (2 Replies)
Discussion started by: msarro
2 Replies

8. Solaris

Disks missing from /devices folder. Not sure why.

Help Please! I picked up a V440 and it has 4 disks. I installed Solaris fine to disk 3, but I cannot see the other disks in Solaris. I have run probe-scsi-all from OBP and I see the other disks and they have names in devalias AFAIK. It's just in Solaris they do not appear. I have run... (6 Replies)
Discussion started by: greg1975
6 Replies

9. Solaris

Missing ASM Disks in Solaris 11.3 LDOM

Hi Guys, Just a quick question hopefully someone will have seen this before and will be able to enlighten me. I have been doing some Infrastructure Verification Testing and one of the tests was booting the primary domain from alternate disks, this all went well - however on restarting one of... (7 Replies)
Discussion started by: gull04
7 Replies
metaimport(1M)															    metaimport(1M)

NAME
metaimport - imports disk sets into existing Solaris Volume Manager configurations SYNOPSIS
metaimport -s setname [-n] [-v] [-f] [disks...] metaimport -r [disks...] metaimport -V metaimport -? The metaimport command allows the importing of disk sets, including replicated disk sets, into an existing Solaris Volume Manager configu- ration. Replicated disk sets are disk sets created using remote replication software. The default Solaris Volume Manager configuration specifies a maximum number of disk sets that can be configured. The metaimport command fails if importing the disk set would result in exceeding the number of disk sets configured on the system. To increase the number of disk sets allowed on a system, see the . Use metaset(1M) or metastat(1M) to view the configuration of the imported set. You must run metaimport as root. metaimport requires a functional Solaris Volume Manager configuration before it runs. The following options are supported: -f Force the import, even if a quorum of replicas from the imported disk set is not available. This option could result in corrupt configurations and should only be used when metaimport fails with the "Insufficient quorum detected; exiting" error. If only a partial disk set is available, this option might be necessary to successfully import. Some or all data could be corrupted or unavailable when importing a partial set or a set lacking a replica quorum. -n Does not actually perform the operation, but shows the output or errors that would have resulted from the opera- tion, had it been run. -r Report on the non-configured disk sets found on the system. If no disk device or LUN is specified, metaimport reports on all non-configured disk sets attached to the system. When the name of one disk is specified, metaimport reports on the disk set (or virtual LUN) containing the specified disk. If two or more disks are specified, metaim- port reports on the set (or sets, if they belong to different disk sets) containing the specified disks. If two or more disks are specified, metaimport reports on the set (or sets, if they belong to different disk sets) containing the specified disks. -s setname Specify the disk set name to use when importing. The imported disk set will be called setname, without regard to the name it may have had on a different system. -v Verbose. Provides detailed information about the metadb replica location and status. -V Version information. -? Display a help message. Example 1: Importing a Disk Set The following example creates a disk set called blue and identifies c1t5d0 as a disk containing a state database replica from the disk set being imported. # metaimport -s blue c1t5d0 Example 2: Reporting Disk Sets to Import The following example scans all disks and LUNs attached to the system and configured as part of the system. It scans for disks that could be part of a disk set to be imported. Components that are already part of the Solaris Volume Manager configuration are ignored. This use of metaimport provides suggested forms of the metaimport command to use to actually import the disk sets that have been found. You can specify a component on the command line to reduce the scope of the scan and generate results more quickly. # metaimport -r 0 Successful completion. >0 An error occurred. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWmdu | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M), metarecover(1M), metareplace(1M), metaroot(1M), metaset(1M), metasync(1M), metattach(1M), md.tab(4), md.cf(4), mddb.cf(4), attributes(5) 16 May 2005 metaimport(1M)
All times are GMT -4. The time now is 07:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy