Sponsored Content
Operating Systems Solaris How to destroy hardware raid on T5120 Post 302304478 by netlink on Monday 6th of April 2009 02:21:20 PM
Old 04-06-2009
Here is the output of raidctl -l

# raidctl -l
Controller: 1
Volume:c1t0d0
Volume:c1t2d0
Disk: 0.0.0
Disk: 0.0.0
Disk: 0.0.0
Disk: 0.0.0
......
then this output Disk: 0.0.0 keep printing on screen

Thanks!
 

9 More Discussions You Might Find Interesting

1. Solaris

Hardware RAID

I don't understood why on SPARC-Platforms have not present RAID-Controller ? Sorry for my bad english, but it's crazy always setup software RAID !!! I whanna Hardware RAID and when i can find solution ? (7 Replies)
Discussion started by: jess_t03
7 Replies

2. Solaris

how to hardware RAID 1 on T5120

Hi, I have t5120 sparc and I have 2 146 G drives in the system. I will be installing solaris 10 and also want the system mirrored using Hardware RAID "1" The System did come preinstalled as it comes from sun. I did not do much on it. I booted system using boot cdrom -s gave format... (6 Replies)
Discussion started by: upengan78
6 Replies

3. Solaris

T2000 Hardware RAID

Hi, I have a root with hardware RAID on c0t0d0 and c0t2d0. I would like to set the boot device sequence in OBP for both hdds. I have checked in ls -l /dev/rdsk/ for the path of c0t2d0 but it does not exist. Can anyone shed some lights on this? AVAILABLE DISK SELECTIONS: 0.... (12 Replies)
Discussion started by: honmin
12 Replies

4. Solaris

Sun T5120 hardware RAID question

Hi everyone I've just purchased a Sun T5120 server with 2 internal disks. I've configured hardware RAID (mirror) and as a result the device tree in Solaris only contains 1 hard drive. My question is, how would I know when one of the drives become faulty? Thanks (2 Replies)
Discussion started by: soliberus
2 Replies

5. UNIX for Dummies Questions & Answers

RAID software vs hardware RAID

Hi Can someone tell me what are the differences between software and hardware raid ? thx for help. (2 Replies)
Discussion started by: presul
2 Replies

6. Solaris

Hardware Raid - LiveUpgrade

Hi, I have a question. Do LiveUpgrade supports hardware raid? How to choose the configuration of the system disk for Solaris 10 SPARC? 1st Hardware RAID-1 and UFS 2nd Hardware RAID-1 and ZFS 3rd SVM - UFS and RAID1 4th Software RAID-1 and ZFS I care about this in the future to take... (1 Reply)
Discussion started by: bieszczaders
1 Replies

7. Hardware

Sun T3-1 hardware RAID

Hi all I've just received my T3-1. It has 8 disks and I would like to configure RAID1 on the disks. The Sun documentation states that you can either use the OpenBoot PROMP utility called Fcode or you can use software via the Solaris OS. The documentation doesn't make it clear if: 1. The... (6 Replies)
Discussion started by: soliberus
6 Replies

8. Solaris

Software RAID on top of Hardware RAID

Server Model: T5120 with 146G x4 disks. OS: Solaris 10 - installed on c1t0d0. Plan to use software raid (veritas volume mgr) on c1t2d0 disk. After format and label the disk, still not able to detect using vxdiskadm. Question: Should I remove the hardware raid on c1t2d0 first? My... (4 Replies)
Discussion started by: KhawHL
4 Replies

9. Solaris

Hardware RAID using three disks

Dear All , Pl find the below command , # raidctl -l Controller: 1 Volume:c1t0d0 Disk: 0.0.0 Disk: 0.1.0 Disk: 0.3.0 # raidctl -l c1t0d0 Volume Size Stripe Status Cache RAID Sub Size ... (10 Replies)
Discussion started by: jegaraman
10 Replies
metadevadm(1M)                                            System Administration Commands                                            metadevadm(1M)

NAME
metadevadm - update metadevice information SYNOPSIS
/usr/sbin/metadevadm [-h] [-n] [ [-l]-r] [-s setname] [-u disk_specifier] [-v] DESCRIPTION
The metadevadm command facilitates the administration of device ID entries in Solaris Volume Manager. Use this command when the pathname stored in the metadevice state database no longer correctly addresses the device or when a disk drive has had its device ID changed. This command requires root privileges. OPTIONS
The following options are supported. -h Provide a help display. -l Specify that metadevadm log to syslog(3C). metadevadm logs to the the DAEMON facility at the ERR level by default. See syslog.conf(4) for additional information on changing logging levels. Use this option anytime. It is most useful in startup scripts and less useful interactively. -n Emulate the effect of a command, without making any changes to the system. -r Recompute the pathname and disk specifier (including slice) associated with all devices in the metadevice state database if the device supports device IDs. If a device does not support device IDs or the device is not available, then no action is taken for that device. Use this option when the disk has been moved or readdressed. This option is run automatically at boot time to detect device ID changes and update the state database. -s setname Specify the name of the disk set on which metadevadm works. This option causes the command to perform its adminis- trative function within the specified disk set. Without this option, the command performs its function on devices in the local disk set. -u disk_specifier Obtain the device ID associated with the disk_specifier (for example, c1t2d0) of a device and update the metadevice state database. If the device ID has not changed this option does nothing. Use this option when a disk drive has had its device ID changed during a firmware upgrade or due to changing the controller of a storage subsystem. -v Execute in verbose mode. This option has no effect when used with -u. Verbose is the default. EXAMPLES
Example 1: Updating Device ID of Disk The following example updates the device c2t3d0: # metadevadm -u c2t3d0 Updating SLVM device relocation information for c2t3d0. Old device reloc information: id19280192391293123012012010012012091398 New device reloc information: id19380192391293123012012010012012091398 The following example is a variation of the preceding, using the full pathname. # metadevadm -u /dev/dsk/c2t3d0 The following example uses the -n option, which means that the command is emulated, but does not take effect. Note that when the -v option is used with -u, -v has no effect (verbose is the default). # metadevadm -u -v -n c2t3d0 Updating SLVM device relocation information for c2t3d0. Old device reloc information: id19280192391293123012012010012012091398 New device reloc information: id19380192391293123012012010012012091398 Example 2: Recomputing Pathnames In the following example, all device names are valid. # metadevadm -r Disk movement detected. Updating device names in SLVM. In the following example, once again device names are valid. # metadevadm -r -v Disk movement detected. Updating device names in SLVM. c0t0d0s0 changed to c0t0d1s0 from device relocation information id12098123lkmklsdjaasdkfjadfjakds In the following example, metadevadm detects an invalid device name. # metadevadm -r Invalid device relocation information detected in SLVM. Please check status of following disk(s): c3t0d0 RETURN VALUES
The following exit values are returned: 0 Command was successful. 1 metadevadm encountered an error condition. 2 An invalid device ID was detected when using the -r option. This is for use in the rc2.d script. See init.d(4). ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWmdu | +-----------------------------+-----------------------------+ SEE ALSO
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), metastat(1M), metasync(1M), metattach(1M), md.tab(4), md.cf(4), mddb.cf(4), md.tab(4), attributes(5), md(7D) Solaris Volume Manager Administration Guide SunOS 5.10 13 Sep 2004 metadevadm(1M)
All times are GMT -4. The time now is 10:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy