Sponsored Content
Full Discussion: Re-using disks
Operating Systems Solaris Re-using disks Post 302236417 by Chains on Monday 15th of September 2008 12:56:54 PM
Old 09-15-2008
Re-using disks

I would like to know if I can move the disks from a V240 chassis into a V440 chassis to use the increased resources (CPU & Memory) to boost performance. I know you can move disks between V210/240 chassis's, but I'm not sure if this would work between 240s & 440s. Any help would be much appreciated.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

how many disks do I have?

Hi How do I check how many disks do I have in Solaris & HP-UX? Also what does this mean c9t1d5 in /dev/dsk what is c, t, d etc cheers (8 Replies)
Discussion started by: g-e-n-o
8 Replies

2. UNIX for Dummies Questions & Answers

Disks on AIX

Hello I've been working on AIX 5.3 ML3 on IBM pSeries520. That server has 6 HDD drives in 3 volume groups (1+mirror in each group). I must check which phisical disk is which disk in the system. For ex. I want to know that disk in 4th slot in the machine is marked as hdisk5 on AIX. Does anybody... (2 Replies)
Discussion started by: piooooter
2 Replies

3. AIX

SCSI Disks

Hi Is it possible to install in p5 and pSeries SCSI Disks from SUN on DELL? Will they work? Regards, Pit (0 Replies)
Discussion started by: piooooter
0 Replies

4. Solaris

New Array of disks

I was just curious if anyone has a good tutorial or some info about how I can create and add an array of disks to solaris 8 (11 Replies)
Discussion started by: BRaider
11 Replies

5. Solaris

What do you use to wipe your disks?

What are y'all using to wipe your solaris disks? I am being question by IT Security, what I am using to wipe disk. Is anyone using a 3rd party utility? I have used the format utility in solaris previously. But they are looking for something commercial that I can use. Anyone have... (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies

6. AIX

disks broke?

hay I'm new in the AIX-environment. Right now i'm testing some stuff out. But i can't test the LVM-part which is (to me) very important. I have 2 disks in my testmachine but it seems only 1 is working wel. I'll show you the output below of the disks... hdisk0 = in good condition hdisk2 =... (8 Replies)
Discussion started by: kvanelshocht
8 Replies

7. Solaris

disks in solaris

whats the command to find name of all disks. Is it iostat -En ? (1 Reply)
Discussion started by: vikashtulsiyan
1 Replies

8. Solaris

host cannot see FC disks

Have a V440 server which we need to connect up to a SE6140. Did the zoning on the 3900 brocade silkworm and did mapping from the array to the host manually host initiator did not autodetect the wwn and had to key in manually. probe-scsi-all cannot show the fc disks. What is the problem here? (7 Replies)
Discussion started by: incredible
7 Replies

9. Filesystems, Disks and Memory

FC related disks

Dear Friends, I would like know what are FC related disks and how it will be viewed by generic OSes (Unix, Unix like, Windows & etc.) AFAIK it is viewed by generic OS as SCSI. Can we have FC related disks as internal storage(physically) of general purpose machine (Server / PC /... (1 Reply)
Discussion started by: Tlogine
1 Replies

10. Solaris

How to tell what disks are used for a zpool?

Hello, Does anyone know how I can tell what disk are being not being used by a zpool? For example in Veritas Volume manager, I can run a "vxdisk list" and disks that are marked as "online invalid" are disk that are not used. I'm looking for a similar command in ZFS which will easily show... (5 Replies)
Discussion started by: robertinoau
5 Replies
voldiskadd(8)						      System Manager's Manual						     voldiskadd(8)

NAME
voldiskadd - Adds one or more disks for use with the Logical Storage Manager SYNOPSIS
/usr/sbin/voldiskadd disk-address-list DESCRIPTION
The voldiskadd utility sets up new disks that are added to the system after the initial system installation and configures the disks for use by the Logical Storage Manager. A valid disk label must exist on the disk before using the voldiskadd utility. One or more disks may be specified using a disk-address-list. Disk addresses in the list have the form dskn (for the entire disk) or dsknp (for a specific partition). When specifying multiple disks, use a space between entries. Disk address names relate directly to device names in the /dev/disk directory. For example, here are some valid voldiskadd disk-address-list specifications: # voldiskadd dsk1 # voldiskadd dsk2 dsk3a The file, /etc/vol/disks.exclude, may be used to exclude disks from use by voldiskadd. Each line of the file specifies the name of a disk to exclude (for example, dsk5). The voldiskadd utility prompts the user for a disk group name and disk media name for the disks. If a new disk group name is specified, that disk group is created for the new disks. If no disk group name is specified, the disks are left as unassigned replacement disks for future use. If an existing disk group name is specified, the user is prompted for whether the disks should be designated as spares for the disk group. If a disk is found to already contain non-Logical Storage Manager partitioning, the user is asked whether the disk should be encapsulated. Encapsulation turns each partition of the disk into a volume. A disk should be encapsulated if it contains file systems or data that should not be overwritten. If encapsulation is not desired for a disk, the disk can be initialized as a new disk for use by the Logical Storage Manager. For new disks, all space on the disk becomes free space in the disk's disk group. 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. The voldiskadd utility supports the following general classes of actions: Initializing a disk with reserved regions and partitions. Disk initialization is performed by calling voldisksetup command. Adding a disk to an existing disk group. This operation can be performed independently of the initialization of the disk drive to add a disk's storage space to a disk group's free space pool. The volassist command may subsequently allocate from that free space. The disk can also be added as a hot spare device. Creating new disk groups in which to import new disks. If no disk group exists for importing disks, the option of creating the disk group is offered. Encapsulating disks that have exist- ing contents. This is the default action for disks that do not have a valid, existing Logical Storage Manager private region, but that do have a disk label. Encapsulation is performed by calling volencap. Reconnecting a drive that was temporarily inaccessible. This situation is detected automatically, by noting that the specified drive has a disk ID that matches a disk media record with no currently associated physical disk. After reconnection, any stale plexes referring the disk are reattached, and any stopped volumes referring the disk are restarted. This reattach action is performed by calling the volrecover script. ERRORS
You may receive the following messages when using the voldiskadd command: Initialization of disk device special-device failed. Error: special-device or an overlapping partition is open. This message indicates that the partition you specified or an overlapping partition on the disk is actively in use. The partition could be a mounted UFS or AdvFS filesystem, initialized as an LSM disk or used as a swap device. special-device is marked in use for fstype in the disklabel. If you continue with the operation you can possibly destroy existing data. Would you like to continue?? [y,n,q,?] (default: n) This message indicates that the fstype of a partition or an overlapping partition is set in the disk label. The voldiskadd command prints this message to warn that a disk partition may have valid data which could be destroyed. If you are sure that the disk partition does not have valid data and that the partition can be added to LSM, you can ignore the warning message by entering y at the prompt. The voldiskadd command will proceed to initialize the disk partition and add it to LSM. FILES
A list of disks to exclude from use by voldiskadd. SEE ALSO
disklabel(8), volassist(8), voldisk(8), voldiskadm(8), voldisksetup(8), voldg(8), volintro(8) voldiskadd(8)
All times are GMT -4. The time now is 01:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy