Sponsored Content
Operating Systems Solaris Virtual disks are not showing up in LDom Post 302897073 by unblockable on Thursday 10th of April 2014 07:22:20 PM
Old 04-10-2014
Quote:
Originally Posted by Peasant
I see you are using slice0 of the disk.

You will need to specify the option for it :
Code:
ldm add-vdsdev options=slice /dev/dsk/c0t5000CCA015354CB4d0s0 vol5@primary-vds0

Or use the entire disk without the slice option :
Code:
ldm add-vdsdev /dev/dsk/c0t5000CCA015354CB4d0s2 vol5@primary-vds0

Hm I'm curious, is the options=slice required? Because I was able to add the first disk (or first slice rather?) successfully without it.

Quote:
I would also advice to create vds for every ldom, not use primary for everything.
Ah yes, this is probably good advice. I am a novice administrator, and I was just learning as I read the instructions. Moving forward I shall try to keep this in mind.

Quote:
The third disk with 'weird' partition table is actualy entire disk added (s2) and during the creation of the zpool inside of ldom no slice as used (c2d0 for instance).

This enables you to import the zpool on both architectures (x86 or sparc).
Ah, interesting. I wasn't aware of this, and I just used the format -e option to write an SMI label to disk to it matched the formatting of my other disks. I am not sure the purpose of this, I was simply trying to match the layout of my other disks...

After I labeled "c0t5000CCA0153596A4d0" with an SMI label, I was able to add slice 0 "c0t5000CCA0153596A4d0s0" as a virtual disk to my VM, and it showed up as a third disk. I am still unsure why my "c0t5000CCA0153542A4d0s0" did not show up properly as a virtual disk inside my VM, I will investigate later. But as for now it looks like my task is complete.

Thank you.
 

8 More Discussions You Might Find Interesting

1. Linux

LVM (volume manager) and virtual disks

:eek: Hi guys, I'm pulling my hair out over this one. I am trying to set up a virtual server environment. ( I am using VirtualBox, but I think this is irrelevant to this problem.) I have downloaded a pre-packaged Linux virtual disk, with which I have successfully started a virtual instance of a... (4 Replies)
Discussion started by: otheus
4 Replies

2. Solaris

How to create virtual disks in solaris

Hi, I have installed oracle 10g release 2 on solaris 10 Zone. I want to configure ASM in local Zone using virtual disks in place of real disks. I have configured ASM using virtual disks in place real disk in Solaris 10 Global zone. How i can do in local Zone Kindly guid me with proper... (1 Reply)
Discussion started by: malikshahid85
1 Replies

3. Solaris

Disks aren't showing up in Solaris/OBP

(Disclaimer: I put this in the "dummies" section because I am a UNIX noob and I'm not really sure what I'm doing so I felt like it belonged here. If it belongs in the Solaris section I can delete this and post it there:b:) I was handed over an Oracle SPARC T3-1 machine at work, with 8 physical... (15 Replies)
Discussion started by: bstring
15 Replies

4. Red Hat

Java process showing high virtual memory

Hi All, I have a java process which is showing high virtual memory utilization in client server. But the same process is showing comparitively lesser virtual memory consumption. I understand that virtual memory shown is not of much importance for the general user in normal condition, my client... (2 Replies)
Discussion started by: mritusmoi
2 Replies

5. Solaris

Virtual Switch in Solaris LDOM

Hi, Our existing environment is having primary domain and 3 guest domains are running over it. See the attached image. Now we want to add a new primary virtual switch and move LDOM3 to be connected with new primary switch. So, I am not sure how to achieve this because. If I remove the... (7 Replies)
Discussion started by: praveensharma21
7 Replies

6. Solaris

LDOM Solaris 11 add Network vsw (Virtual switch)

hello, I have a problem when configuring the network at the LDOM level, on a SPARC-Enterprise-T5120 machine The network goes through VLAN 503 (level, network tagget) And I need to give network to the guest domain: madarrwebsol10 I hope someone can bring some light .... Excuse my English ... ... (4 Replies)
Discussion started by: Wittman
4 Replies

7. Solaris

Missing ASM Disks in Solaris 11.3 LDOM

Hi Guys, Just a quick question hopefully someone will have seen this before and will be able to enlighten me. I have been doing some Infrastructure Verification Testing and one of the tests was booting the primary domain from alternate disks, this all went well - however on restarting one of... (7 Replies)
Discussion started by: gull04
7 Replies

8. Solaris

Virtual Terminal (Console) showing non-global zone?

Hope that everyone is doing well today. Happy Friday. I am running an illumos (opensolaris) based system which is like SmartOS, OmniOS, and OpenIndiana I have been searching all over the Internet into various documents and forms that have to do with Solaris, Opensolaris, Illumos, and SmartOS... (3 Replies)
Discussion started by: LonnieTC
3 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 12:46 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy