Sponsored Content
Full Discussion: Upgrade disk in RAID 1
Operating Systems Solaris Upgrade disk in RAID 1 Post 302213348 by photon on Wednesday 9th of July 2008 11:27:12 PM
Old 07-10-2008
Thanks for replies. Smilie

Nice hints joerg.

This was absolutely needed in procedure

Quote:
to copy the partition table from one to an other disk:
prtvtoc /dev/rdsk/c?t?d?s2 | fmthard -s - /dev/rdsk/c?t?d?s2
but since disks are not identical I might do it manually, not sure yet.

Manually would be
# format
# partition
# print

get partition table from 73Gb drive

then with new 146Gb drive

# format
# partition
# (follow prompts etc.. to create partitions of 73Gb drive)

Quote:
make the disks bootable:
/usr/sbin/installboot /usr/lib/fs/ufs/bootblk /dev/rdsk/c?t?d?s?
It says in the man fmthard "adds boot information to the Solaris fdisk partition"
so I do not think hint 2 is needed and if you partition manually the volume
manager will recreate the boot, swap, and other partitions.

Quote:
Is the replacement of the two 72GB drives w/ two 146GB drives just
because you can get the drives quicker for replacement?
Yes, the drives have reached there max capacity and backups of company
critical info have not been done in a month, it seemed like the best choice but
I wonder if there would have been a better?

Quote:
Because you dont use the additional added space from the step to 146GB drives, I can write a little how-to of doing that if you want..
I think it would be best to partition the drive exactly as mirror of 73Gb for volume
manager to do its thing. When both drives are in sync with 146Gb drives then
partion new space with format -> partition and mount a new file system. If you have
a suggestion or idea, I would like to here it.
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Creating a Mirror RAID With Existing Disk

Hi there, I'm not sure if this is possible, but here is what I'd like to do.. I have an existing 160GB drive in my Redhat 9.0 server that I would like to add an additional 160GB drive to and create a mirrored RAID of the first disk to the new disk. I would like to do this without having to... (2 Replies)
Discussion started by: sysera
2 Replies

2. UNIX for Advanced & Expert Users

disk upgrade

Hi all, this s going to be my 1st time upgrading a disk.I need the ways or steps to migrate data from a 2gb disk to a 4gb disk which sits in the High Availability Disk Array Model 10.the os disk is the internal disk of the K200 system so i dont think i would be meddling around with that.what r... (1 Reply)
Discussion started by: giriplug
1 Replies

3. Filesystems, Disks and Memory

Problem replace disk with RAID-5 volumes

Good morning, I have a problem replacing a disk with raid-5 volumes. An hardware error was occurred from a disk c9t3 so all slices were in maintenace. Every slice is part of a raid-5 volume. Any replica is present. Following Volume manager manual for replacing a disk, I have: - phisically... (0 Replies)
Discussion started by: bonovox
0 Replies

4. Solaris

Configuring RAID using single disk

Hi All, I have a SUN ENTERPRISE 3500 server with solaris 10 on it. I have already mirrored root partition.Now i need to mirror two more partitions with 25GB space. But i have only one disk having 70GB space.Total i have 7 disks but each one is of 18 GB only except one. Please find the output of... (2 Replies)
Discussion started by: Renjesh
2 Replies

5. Ubuntu

Ubunutu 8.04.4 RAID 1 mirror replace disk

Hi, I have an Ubuntu system which I have an faulted mirror. I trying to replace the disk, but I'm stuck on that it boots and only showing GRUB GRUB ## ## End Default Options ## title Ubuntu 8.04.4 LTS, kernel 2.6.24-26-server root (hd0,0) kernel ... (0 Replies)
Discussion started by: jld
0 Replies

6. UNIX for Advanced & Expert Users

Identify failed disk in Linux RAID

Good Evening, 2 years ago, I set up an Ubuntu file-server for a friend, who is a photograph amateur. Basically, the server offers a software RAID-5 that can be accessed remotely from a MAC. Unfortunately, I didn't labeled the hard drives (i.e. which physical drive corresponds to the /dev/sdX... (2 Replies)
Discussion started by: Loic Domaigne
2 Replies

7. Solaris

Hardware RAID not recognize the new disk [Sun T6320]

We have hardware RAID configured on Sun-Blade-T6320 and one of the disk got failed. Hence we replaced the failed disk. But the hot swapped disk not recognized by RAID. Kindly help on fixing this issue. We have 2 LDOM configured on this server and this server running on single disk. #... (8 Replies)
Discussion started by: rock123
8 Replies

8. AIX

SAN DISK raid level in AIX

Hello All, Our servers having emc clarion for the data disks. Is that possible to see those san disks raid level from AIX ? Am having AIX 6.1 and EMC clarion 5.5. Regards, Gowtham.G (3 Replies)
Discussion started by: gowthamakanthan
3 Replies

9. SuSE

/proc/mdstat and cciss not available, how to know your disk is raid

Im issuing a cat /proc/mdstat, dmraid -r, and finding a cciss, to know if my server is software raid and hardware raid. But all of them are missing. What is the other way to know, your disk are raid, your disks is sync, your disk are out of sync, your disk is failed, ASIDE LOOKING AT THEM... (0 Replies)
Discussion started by: invinzin21
0 Replies

10. Solaris

Patching on Raid 0 Disk

Dear All , We need to do patching on one Solaris Server , where we have raid 0 configured. What is the process to patch a Server if RAID 0 (Concat/Stripe) is there. Below is the sample output. # metadb flags first blk block count a m pc luo 16 ... (1 Reply)
Discussion started by: jegaraman
1 Replies
voldiskadm(8)						      System Manager's Manual						     voldiskadm(8)

NAME
voldiskadm - Menu interface for LSM disk administration SYNOPSIS
/usr/sbin/voldiskadm DESCRIPTION
The voldiskadm script is an interactive tool that presents a menu of possible operations to the user. When an operation is selected, the script guides the user through the necessary steps, and prompts for data needed to complete the operation. The voldiskadm interface is intended mainly for beginning users and for those who prefer a simple method for doing common operations. The interface uses query-based prompts to gather input, with defaults supplied when possible. Context-sensitive help is available at every prompt by typing ?. Also, a list option can be used to get information on available target disks for an operation. For operations that require a device name, one or more names can be specified using a space-separated list. Names in the list can have the form dskn or rdskn (for an entire disk) or dsknp or rdsknp (for a specific disk partition). Disk names relate directly to device names in the /dev/disk and /dev/rdisk directories. The file, /etc/vol/disks.exclude, may be used to exclude disks from use by voldiskadm. Each line of the file specifies the name of a disk to exclude (for example, dsk5). The voldiskadm menu includes the following options: Add or initialize one or more disks This option prompts for one or more disk device addresses. The specified disks can be added to an existing disk group, added to a new disk group, added to a disk group as spares, or initialized but not added to a disk group (reserved for use as replacement disks). After specifying the disks, the user is prompted for a disk group (rootdg by default) and a disk name. If no name is specified, a default disk name is assigned (diskn for disks in the rootdg disk group and diskgroupn for disks in other disk groups). The disks are then checked to ensure that there is no information already on them. If there is, the user is given the option of encapsulating the disks. Encapsulate one or more disks This option prompts for one or more disk addresses. It then calls volencap to encapsulate the specified partitions. Remove a disk This option prompts for a disk, by disk media name. The disk is checked to ensure that no subdisks reside on the disk. If the disk is in use, the operation fails with a recommendation to first move all volumes off the disk. If this disk is the last disk in a disk group, the user is prompted for whether the disk group should be removed from the system, as well. The operation proceeds by calling voldg rmdisk to remove the disk from its disk group. If this is the last disk in its disk group, voldg deport is used, instead, to remove the disk group from use. Remove a disk for replacement This option prompts for a disk, by disk media name. The disk is checked for volumes that would lose all mirrors as a result of the operation. If such volumes exist, they are listed and the user is prompted to ensure that the operation should proceed. The operation proceeds by calling voldg -k rmdisk to dissociate the media record from the physical disk. If some formatted disks are under LSM control but not assigned to a disk group, the user is prompted for whether one of these disks should be used as a replacement. Replace a failed or removed disk This option prompts for a disk media name. The named media record must be dissociated from a disk. If the media record is not in the removed state, unused disks are scanned for matching disk IDs. If a disk with a matching disk ID is found, the user is prompted for whether that disk should be reattached. If a matching disk is not used, the user is prompted for a new disk, by device name. If the named replacement disk has a valid disk header, but is not allocated to a disk group, the user is prompted for whether the disk should be reinitialized. If the named replacement disk is listed as allocated to a disk group or to another host, the user is prompted to ensure that the operation should proceed. If the device is to be initialized, a new disk label is written to the disk to reflect its private and public regions. Given an initialized disk, the operation proceeds by replacing the disk in a disk group with voldg -k adddisk. Mirror volumes on a disk This option prompts for a disk, by disk media name. It then prompts for a destination disk within the same disk group, also by disk media name. Specifying no destination disks indicates that any disk is suitable. The operation proceeds by calling volmirror to mirror the volumes. Mirroring volumes from the boot disk will produce a disk that can be used as an alternate boot disk. This is done by calling the volrootmir command. Move volumes from a disk This option prompts for a disk, by disk media name. It then prompts for a possible list of destination disks, also by disk media name. Specifying no destination disks indicates that any disk is suitable. The operation proceeds by calling volevac to move sub- disks off the disk. Enable access to (import) a disk group This option prompts for a disk, by device address. The operation proceeds by calling voldg import to import the disk group stored on that disk. Disable access to (deport) a disk group This option prompts for a disk group name. The prompt display lists alternate disk groups and the disks (media name and access name) that they contain. The operation proceeds by calling voldg deport. Enable (online) a disk device This option prompts for a disk device. The prompt display allows for a display of disks on the system. The operation only func- tions for disks currently in an offline state. It then proceeds to make the disk accessible. Disable (offline) a disk device This option prompts for a disk device. The prompt display allows for a display of disks on the system. The operation only func- tions for disks currently in an online state but not part of any disk group. It then proceeds to mark the disk as offline such that the Logical Storage Manager makes no further attempt at accessing the disk. Mark a disk as a spare for a disk group This option sets up a disk to be used as a spare device for its disk group. A spare disk can be used to automatically replace a disk that has failed. No space can be used on a disk that is marked as a spare. Turn off the spare flag for a disk This option removes a disk from those that can be used as a spare and returns its space to the general pool of available space. Recover plexes and volumes after replacement This operation performs plex attachment, RAID-5 subdisk recovery, and resynchronize operations for the named volumes, or for volumes residing on the named disks (media name). If no media name or volume operands are specified, the operation applies to all volumes (or to all volumes in the specified disk group). ERRORS
See the voldiskadd(8) reference page for a description of errors related to the initialization operation. FILES
A list of disks to exclude from use by voldiskadm. SEE ALSO
disklabel(8), volintro(8), voldg(8), voldisk(8), voldiskadd(8), voldisksetup(8), volrootmir(8) voldiskadm(8)
All times are GMT -4. The time now is 02:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy