Sponsored Content
Full Discussion: Disk needs replacing?
Operating Systems Solaris Disk needs replacing? Post 302185549 by BrewDudeBob on Tuesday 15th of April 2008 09:11:20 AM
Old 04-15-2008
If your disk is part of a two disk mirror you can lay out the partitions on the new disk with a one line command:

prtvtoc -s /dev/rdsk/good_disk_s2 | fmthard -s - /dev/rdsk/new_disk_s2

Here is an example:

# prtvtoc -s /dev/rdsk/c0t1d0s2 | fmthard -s - /dev/rdsk/c3t0d0s2
fmthard: New volume table of contents now in place.

Of course it is a good idea to do a prtvtoc -s on each drive before you pipe the prtvtoc command to the fmthard so you can see the layouts of each disk before you copy the info.

Last edited by BrewDudeBob; 04-15-2008 at 10:13 AM.. Reason: I screwed up the italic formatting
 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Replacing Boot Disk in Solaris

Hi, I have the situaiton in which primary boot disk has bad sectors in Solaris 9. The other hard disk is mirrored using Solstice DiskSuite 4.2. I can reboot system with the other disk. My question is, when I replaced the boot disk with a new one, how can I create meta db and finally make it... (2 Replies)
Discussion started by: s_aamir
2 Replies

2. Solaris

replacing root disk SunFire 280R

Hi, We had a disk go bad in this SunFire 280R, running Solaris 8 - Generic_117350-46. We replaced the disk and partitioned it. We metadetached all the metadevices but for some reason the new disk is showing up in the metadb as Concat/Stripe and it won't let us re-sync the mirror. We are not... (2 Replies)
Discussion started by: mgb
2 Replies

3. Solaris

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... (0 Replies)
Discussion started by: aji1729
0 Replies

4. AIX

replacing mirror disk

Hi Admins, I am new into aix.I was surfing aix pages and reading how to replace failed mirror disks.I read in one of the posts that we have to reboot the server to replace the disk. actually i was a HPUX admin and many times replaced root mirror disk online.Ofcourse it was hot swappable. ... (2 Replies)
Discussion started by: newaix
2 Replies

5. AIX

Regarding AIX volume manager & replacing a disk

First a little background: I'm working with an AIX 6.1 TL05 running two mirrored SAS disks (rootvg) and four SSDs (appvg) All four SSDs belong to appvg and are setup to mirror as follows: hdisk4 --> hdisk6 (containing application fs) hdisk5 --> hdisk7 (containing database fs) A few days... (1 Reply)
Discussion started by: Michael Mullig
1 Replies

6. Solaris

Need help replacing a mirrored boot disk

I have a v480 with a mirrored boot disk c1t0 and c1t1. The drives themselves don't show a failure but the mirror's need maintenance. This is my plan for replacing the drive. I would love feedback to point out what I"m missing or where my steps are incorrect. Two things I believe I'm... (3 Replies)
Discussion started by: pcoffey
3 Replies

7. 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

8. 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
fmthard(1M)															       fmthard(1M)

NAME
fmthard - populate label on hard disks SYNOPSIS
SPARC fmthard -d data | -n volume_name | -s datafile [-i] /dev/rdsk/c? [t?] d?s2 fmthard -d data | -n volume_name | -s datafile [-i] /dev/rdsk/c? [t?] d?s2 The fmthard command updates the VTOC (Volume Table of Contents) on hard disks and, on systems, adds boot information to the Solaris fdisk partition. One or more of the options -s datafile, -d data, or -n volume_name must be used to request modifications to the disk label. To print disk label contents, see prtvtoc(1M). The /dev/rdsk/c?[t?]d?s2 file must be the character special file of the device where the new label is to be installed. On systems, fdisk(1M) must be run on the drive before fmthard. If you are using an system, note that the term ``partition'' in this page refers to slices within the fdisk partition on machines. Do not confuse the partitions created by fmthard with the partitions created by fdisk. The following options are supported: -d data The data argument of this option is a string representing the information for a particular partition in the current VTOC. The string must be of the format part:tag:flag:start:size where part is the partition number, tag is the ID TAG of the partition, flag is the set of permission flags, start is the starting sector number of the partition, and size is the number of sectors in the partition. See the description of the datafile below for more information on these fields. -i This option allows the command to create the desired VTOC table, but prints the information to standard output instead of modifying the VTOC on the disk. -n volume_name This option is used to give the disk a volume_name up to 8 characters long. -s datafile This option is used to populate the VTOC according to a datafile created by the user. If the datafile is "-", fmthard reads from standard input. The datafile format is described below. This option causes all of the disk par- tition timestamp fields to be set to zero. Every VTOC generated by fmthard will also have partition 2, by convention, that corresponds to the whole disk. If the input in datafile does not specify an entry for partition 2, a default partition 2 entry will be created auto- matically in VTOC with the tag V_BACKUP and size equal to the full size of the disk. The datafile contains one specification line for each partition, starting with partition 0. Each line is delimited by a new-line character ( ). If the first character of a line is an asterisk (*), the line is treated as a com- ment. Each line is composed of entries that are position-dependent, separated by "white space" and having the fol- lowing format: partition tag flag starting_sector size_in_sectors where the entries have the following values: partition The partition number. Currently, for Solaris SPARC, a disk can have up to 8 partitions, 0-7. Even though the partition field has 4 bits, only 3 bits are currently used. For , all 4 bits are used to allow slices 0-15. Each Solaris fdisk partition can have up to 16 slices. tag The partition tag: a decimal number. The following are reserved codes: 0 (V_UNASSIGNED), 1 (V_BOOT), 2 (V_ROOT), 3 (V_SWAP), 4 (V_USR), 5 (V_BACKUP), 6 (V_STAND), 7 (V_VAR), and 8 (V_HOME). flag The flag allows a partition to be flagged as unmountable or read only, the masks being: V_UNMNT 0x01, and V_RONLY 0x10. For mountable partitions use 0x00. starting_sector The sector number (decimal) on which the partition starts. size_in_sectors The number (decimal) of sectors occupied by the partition. You can save the output of a prtvtoc command to a file, edit the file, and use it as the datafile argument to the -s option. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ uname(1), format(1M), prtvtoc(1M), attributes(5) Only fdisk(1M), installgrub(1M) Special care should be exercised when overwriting an existing VTOC, as incorrect entries could result in current data being inaccessible. As a precaution, save the old VTOC. For disks under one terabyte, fmthard cannot write a VTOC on an unlabeled disk. Use format(1M) for this purpose. 11 Apr 2005 fmthard(1M)
All times are GMT -4. The time now is 01:26 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy