Login or Register to Ask a Question and Join Our Community


Solaris

Replacing a hard disk (SVM) with a soft partition?

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems Solaris Replacing a hard disk (SVM) with a soft partition?
# 1  
Old 09-15-2010
Replacing a hard disk (SVM) with a soft partition?
The following is the summarry:-

1) Four disks in server ie (c1t0d0. c1t1d0, c1t2d0, c1t3d0). c1t2d0 is the disk to be replaced.
c1t0d0 and c1t2d0 are mirrors.
c1t1d0 and c1t3d0 are mirrors.

Metadb to be deleted is in c1t2d0s7

a) Mirror d35 has 2 submirrors d38 and d39

d38 is a stripe having 2 members:- stripe 0:- c1t0d0s6
stripe 1:- d36(soft partition), c1t1d0s0


d39 is a stripe having 2 members:- stripe 0:- c1t2d0s6
stripe 1:- d37(soft partition), c1t3d0s0



After deleting metadb and backing up partition table from its mirror,unconfiguring and replacing the disk (c1t2d0), and then configuring it, writing the backed up partition table to it, creating metadb in c1t2d0s7 back.

If i issue metareplace -e d35 c1t3d0s6, would everything be fine? The reason why is asked because c1t2d0s6(failed slice) and a softpartition d37(c1t3d0s0)(its from another disk) forms the submirror d39 which is part of the mirror d39.

Do i have to issue the command metarecover c1t2d0s4 -m -p , or metarecover d36 -m -p ?for re-indexing, please help on this, am really confused.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Replacing a failed disk using SVM

Hi Please can you help me on replacing or removing a faulty disk drive on a SUN NETRA X4250server with 4 internal drives only. the format comand show me the following: format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c0t0d0 <drive type unknown> ... (9 Replies)
Discussion started by: fretagi
9 Replies

2. Solaris

Replacing a Disk in a ODS/SVM Mirror

Hi All BAsed on the below I would like to verifu two things (1) The udnerlying mirroris for '/mnt' na dit onlcy contaisne 1 sub-mirror, with one sliceon is one disk and hence, data loss on the mount point (the mount point, '/mnt' is backed up) (2) the Procedure for renewal # df -kh /mnt... (2 Replies)
Discussion started by: stevie_velvet
2 Replies

3. Filesystems, Disks and Memory

Ask concept soft partition vs hard partition

Hi Experts I would like to know different between soft partition concept and hard partition concept on solaris. Here is little explanation between soft partition concept and hard partition concept on solaris. Soft Partition: 1TB total space available in storage in all mapped to the OS to... (2 Replies)
Discussion started by: edydsuranta
2 Replies

4. Windows & DOS: Issues & Discussions

Hard disk partition on Original windows 7 Home Premium

Respected Members, I am using compaq CQ41, with factory install windows 7, there is three drives namely (local Disk( c: ) 158 GB free of 281 GB), (RECOVERY( D: ) 2.69 GB free of 16.7GB) and (HP_TOOLS( E: ) 92.7 MB free of 99.3 MB). i don't want to lost it,but... (2 Replies)
Discussion started by: Vijay Tyagi
2 Replies

5. Linux

C++ Code to Access Linux Hard Disk Sectors (with a LoopBack Virtual Hard Disk)

Hi all, I'm kind of new to programming in Linux & c/c++. I'm currently writing a FileManager using Ubuntu Linux(10.10) for Learning Purposes. I've got started on this project by creating a loopback device to be used as my virtual hard disk. After creating the loop back hard disk and mounting it... (23 Replies)
Discussion started by: shen747
23 Replies

6. Solaris

SVM Soft partitions in a metaset- how to migrate ?

Hi Friends, I need your assistance, could someone assist.... Scenario:- Solaris 10, with zones and mounted file systems, using SAN. SVM with metasets on it configured soft partitions on the meta device. These soft partitions are mounted and file systems are being accessed. We are now trying... (6 Replies)
Discussion started by: unahb1
6 Replies

7. Solaris

Puzzled over over the relationship between the partition and geometry of hard disk.

Not sure why solaris couldn't detect the geometry of a hard disk which has a working OS of winxp pro. Is it due to the different OS that the partition information is stored in different location? When I type '"format" it is shown as below, c3d1 < drive type unknown>... (5 Replies)
Discussion started by: just.srad
5 Replies

8. Shell Programming and Scripting

Detecting hard or soft disk errors in Solaris

I am looking for some tips or suggestions in how to do the following. 1) From a Solaris server, I run the command iostat -En and receive output that is similiar to the following which shows your disks along with the cdrom/dvdrom: c0t2d0 Soft Errors: 0 Hard Errors: 0 Transport... (1 Reply)
Discussion started by: sunsysadm2003
1 Replies

9. UNIX for Advanced & Expert Users

Hard-disk partition is Full problem?

HI, Currently I am working in One of the webhosting company and I found on one of my server "/home" partition is getting full say 105% usage... But when I actually check the partition size using "du -h", exact partition utilization is only 60-70%. So... (1 Reply)
Discussion started by: jagdish.machhi@
1 Replies

10. UNIX for Dummies Questions & Answers

The hard disk at channel 2, target 1 had a soft error.

Hi there! I received the following error message The hard disk at channel 2, target 1 had a soft error. The output of a system check reveiled the following (see entry <2,1> ): SWXCR xcr0 error counters: RAID Array 200 Controller Family Information Utility V1.03... (1 Reply)
Discussion started by: Ivo
1 Replies
Login or Register to Ask a Question

LEARN ABOUT HPUX

bootconf

bootconf(4)						     Kernel Interfaces Manual						       bootconf(4)

NAME

       bootconf - boot device configuration table

DESCRIPTION

       The file contains the address and disk layout type of the system's boot devices or lif volumes.	It is used by the and HP-UX kernel control
       scripts (fileset to determine how and where to update the initial boot loader.  Normally the kernel's script queries the system's  hardware
       and creates the file.  In rare cases when either the system configuration cannot be automatically determined or additional and/or alternate
       boot devices should be automatically updated, the administrator must edit the file manually.

       There is one line in the file for each boot device.  Each line contains the following blank-separated fields in the order shown:

       disk type   A flag indicating how the file system(s) on the disk are laid out.  The flag must be one of the following:

		   Indicates that the root disk is in LVM or VERITAS Volume Manager
			  (VxVM) format.  If LVM or VxVM mirrors are used, then each of the "mirrors" must have its own line in the file.

		   Indicates that the root disk is in the
			  "whole disk" format with no partitions, but boot and swap space are reserved outside the file system.

       device file The absolute path of the device special file that accesses the physical device where the boot area is located.   For  LVM  root
		   disks,  the	device	special file is the physical volume(s) returned by the command.  For "whole disks" this is the device file
		   that references the entire disk.

       Blank lines are permitted.  Any line beginning with a is considered to be a comment.

DIAGNOSTICS

       The Software Distributor log file contains diagnostic messages under the fileset if the file is incorrect.  Most of the messages are  self-
       explanatory; a few warrant additional explanation:

       If there are no other messages about
	      the  file  is probably empty.  Otherwise, the file is not in the proper format, and the other messages will explain what the problem
	      is.

       The specified device file does not point to a disk where there is a
	      lif which contains the file

       Some character other than
	      or is in the first field of a line.

       As of release 10.0, the boot areas in
	      must all be on the same type of disk layout.

       There are characters after the
	      device file specification.

EXAMPLES

       The boot area is on an LVM root disk:

	      l /dev/disk/disk7_p2

       The boot area is on a whole disk layout:

	      w /dev/disk/disk7

WARNINGS

       All of the boot devices in the file must have the same disk layout.

AUTHOR

       was developed by the Hewlett-Packard Company.

FILES

SEE ALSO

       mediainit(1), hpux(1M), hpux.efi(1M), mkboot(1M), vgdisplay(1M), lif(4), intro(7).

       documentation.

																       bootconf(4)