Sponsored Content
Full Discussion: M5000 Question
Operating Systems Solaris M5000 Question Post 302320141 by DukeNuke2 on Wednesday 27th of May 2009 06:59:07 AM
Old 05-27-2009
the internal disks can only be used by two domains. if you'll create 4 domains, you'll need external storage for minimum two of the domains.
 

10 More Discussions You Might Find Interesting

1. Solaris

M5000 servers - XSCF functions

Hi all A couple of new M5000 servers will be arriving soon and I need to work out how to configure the underlying domains. It will come with 4 x CPUS, 32 Gb of memory, 4 x HD, 2 x IOtrays. Reading the XSCF manual, I can configure the item into 2 domains, something about uni / quad xsb.... (9 Replies)
Discussion started by: sbk1972
9 Replies

2. Solaris

M5000 Question

Hi i 've a M5000 running 2 domains in my Lab with following hardconf SPARC Enterprise M5000; Memory_Size:128 GB; +-----------------------------------+------------+ | FRU | Quantity | +-----------------------------------+------------+ | MBU_B... (3 Replies)
Discussion started by: fugitive
3 Replies

3. Solaris

Unable to start SunVTS on M5000

Please advise. Thank you bash-3.00# cd /usr/sunvts/bin/ bash-3.00# ls bios.bin iobushangscript.sh stopsunvts vtsprobe cmos.bin javabridge.jar sunlink vtsreportgenerate dispatcher loadVtsServer svmVolDiskList vtstalk env6test... (6 Replies)
Discussion started by: incredible
6 Replies

4. Hardware

Sun/Oracle M5000 Question

I have an M5K with disk issues I'm trying to troubleshoot, and it's causing me some confusion. I know the host has four on-board HDDs, but the format command's output shows c0t0d0, c0t1d0, c3t0d0, and c3t1d0. cfgadm -al shows c0t3d0 as the DVD-ROM drive, and c1 and c2 as SAN disks. Confused yet? ... (2 Replies)
Discussion started by: desertdenizen
2 Replies

5. Solaris

M5000 splitting existing domain

Hi We have an M5000 with one domain running Sun Cluster on it. We would like to split the domain into two domains. One with the existing Sun Cluster and one with a fresh install. We have 2 CPU Boards (8 CPU) / 4 Mem Boards (64 gb memory) and 2 IOU as well as 4 disks Is it possible to have... (9 Replies)
Discussion started by: sanc
9 Replies

6. Solaris

Mounting USB in XSCF on M5000

Trying to update my M5000 firmware. trying to mount my USB to upload firmware and getting the following message. XSCF> getflashimage -v file:///media/usb_msd/FFXCP1115.tar.gz Free space: 97MB Making sure mount point is clear umount: /media/usb_msd is not mounted (according to mtab) Trying... (2 Replies)
Discussion started by: soupbone38
2 Replies

7. Solaris

M5000 showhardconf is showing everything is Deconfigured

Hi Forum please help me to fix M5000 Server which we were not using. now i logged to serve and foung that everything is showing as Deconfigured. XSCF> showhardconf SPARC Enterprise M5000; + Serial:BDF1051F30; Operator_Panel_Switch:Locked; + Power_Supply_System:Single;... (4 Replies)
Discussion started by: bentech4u
4 Replies

8. IP Networking

M5000 Xscf

I took over an M5000 and have a jumper server with a nic to connect to the console IP of an M5000. access via ssh user@ip. it was working fine, another person can connect remotely on the subnet, but when I ssh,it just hangs and then times out. so my question is, any ideas of what I might... (4 Replies)
Discussion started by: rrodgers
4 Replies

9. Solaris

M5000 fails to boot

I have an m5000 that Is down. I have access to XSCF> and was able to get to the ok prompt. However, on >ok boot it failed to boot. erred with : svc.startd: svc:/system/device/fc-fabric:default: Method "/lib/svc/method/fc-fabric" failed due to signal KILL. Nov 29... (3 Replies)
Discussion started by: goya
3 Replies

10. Hardware

M5000 won't power up

on an m5000 , I can not power it up, system failure. XSCF> poweron -a DomainIDs to power on:00,01 Continue? :y 00 :Not powering on :Poweron canceled due to missing component. 01 :Not powering on :Poweron canceled due to missing component. the only fault that I can see is: ... (4 Replies)
Discussion started by: goya
4 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 03:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy