Sponsored Content
Full Discussion: RAID1 and LDoms
Operating Systems Solaris RAID1 and LDoms Post 302283999 by StarSol on Wednesday 4th of February 2009 01:28:24 PM
Old 02-04-2009
RAID1 and LDoms

I have a Netra T5220 Solaris 10 server with LDoms installed and enabled. RAID1 is enabled in the control domain with the following slices:

d50 -m d51 d52 1
d51 1 1 c1t0d0s5
d52 1 1 c1t1d0s5
d10 -m d11 d12 1
d11 1 1 c1t0d0s0
d12 1 1 c1t1d0s0
d20 -m d21 d22 1
d21 1 1 c1t0d0s1
d22 1 1 c1t1d0s1
d40 -m d41 d42 1
d41 1 1 c1t0d0s4
d42 1 1 c1t1d0s4
d60 -m d61 d62 1
d61 1 1 c1t0d0s6
d62 1 1 c1t1d0s6
d70 -m d71 d72 1
d71 1 1 c1t0d0s7
d72 1 1 c1t1d0s7

Each slice has a guest domain built. In other words, when the guest domain is built, something similar to /dev/md/dsk/d30 is assigned; the commands look like:

# ldm add-vdsdev /dev/md/dsk/d70 vol7@primary-vds0
# ldm add-vdisk vdisk1 vol7@primary-vds0 ldg1

My question is whether there is an issue with having LDoms and RAID1 at the same time? The reason I am asking is, after I am done with the control domain and guest domains cofguration, and metast looks good, once I reboot the control domain I get an error:

Hostname: control_dom
/dev/md/rdsk/d40 is clean
/dev/md/rdsk/d70 is clean
checking ufs filesystems
/dev/md/rdsk/d50: PARTIALLY ALLOCATED INODE I=2
/dev/md/rdsk/d50: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
/dev/md/rdsk/d60: NEGATIVE SIZE -5476372287601639394 I=2
/dev/md/rdsk/d60: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
THE FOLLOWING FILE SYSTEM(S) HAD AN UNEXPECTED INCONSISTENCY: /dev/md/rdsk/d50 (/exp ort/home/sgw), /dev/md/rdsk/d60 (/export/home/mrf)
fsckall failed with exit code 1.
WARNING - Unable to repair one or more filesystems.
Run fsck manually (fsck filesystem...).
mount: Please run fsck and try again
mount: Please run fsck and try again
svc:/system/filesystem/local:default: WARNING: /sbin/mountall -l failed: exit status 1
Reading ZFS config: done.
Feb 4 09:52:41 svc.startd[7]: svc:/system/filesystem/local:default: Method "/lib/svc/method/fs-local" failed with exit status 95.
Feb 4 09:52:42 svc.startd[7]: system/filesystem/local:default failed fatally: transitioned to maintenance (see 'svcs -xv' for details)

After that, ldm commands returns "Failed to connect to logical domain manager: Connection refused". Running fsck does not help; it even makes thing worse. Appreciate your help...
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How can i set up Software disk mirroring(Raid1) in SCO 5.0.5 with two SCSI harddisk ?

thank u very much, (1 Reply)
Discussion started by: coralsea
1 Replies

2. Filesystems, Disks and Memory

Pulling a drive on RAID1 hangs system

I'm setting up a server with software RAID1, and everything is working perfectly, except that when I pull either of the drives, the system completely hangs and has to be rebooted. The computer is a Tyan Transport GX28, which is alleged to have hot-swappable SATA. I can fail a drive and the system... (1 Reply)
Discussion started by: vertigo23
1 Replies

3. AIX

rootvg and hardware raid1

Good Morning, We have a JS22 blade that we will be loading AIX5.3 onto it. We just discovered that the JS22 will only support one drive, so we are planning on booting this blade from the Fiber Channel SAN. Orginally we used 2 physical drives and set up RAID 1 and presented the logical drive... (0 Replies)
Discussion started by: brachinus
0 Replies

4. UNIX for Advanced & Expert Users

how to create multiple-boot system with disks mirrored(RAID1+0) and disk alone

I have a HP proliant ML 570 G3 with two 146GB disk drives mirrored(RAID1+0) windows server 2003 was installed on that disk. I will add a disk.(scsi 300GB) I will install Linux on that additional disk. I want to create multiple-boot system. Is it possible? I wanna know how to create... (0 Replies)
Discussion started by: lifegeek
0 Replies

5. Filesystems, Disks and Memory

Solaris 10 Raid1

does anyone k ow the answer to this? OS solaris 10 using the command raidctl -c c1t0d0 c1t1d0, this took about 4 mins to return to the prompt with "Volume c1t0d0 is created successfully!" then using format I saw AVAILABLE DISK SELECTIONS: 0. c1t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>... (1 Reply)
Discussion started by: powerrack
1 Replies

6. Linux

SPARC, Linux, RAID1, SILO

Hi, I've been searching for answers for two days and didn't find any definite answers on building RAID1 on SPARC. The main problem was with SILO (Sparc Improved boot LOader): can it boot from RAID partition or not. So I just tried it and it works. I've done this on Debian, but it should be... (0 Replies)
Discussion started by: Luka
0 Replies

7. Linux

raid1 (dmraid) - bad sectors - mount - smartd - complicated!

Hello, i'm running a server with two disks in raid1.. it seems that some bad sectors have recently appeared on one of the disks. Aug 9 08:26:19 linux smartd: Device: /dev/sda, FAILED SMART self-check. BACK UP DATA NOW! Aug 9 08:26:19 linux smartd: Device: /dev/sda, 2 Currently... (0 Replies)
Discussion started by: TehOne
0 Replies

8. Solaris

Moving to RAID1

Is there an easy, safe way to move the system to RAID1 on sparc solaris 10? (without reinstalling). thanks. (6 Replies)
Discussion started by: orange47
6 Replies

9. Ubuntu

Ubuntu desktop RAID1 boot problem.

Hello, I installed ubuntu desktop just recently in aim to create a RAID1 configuration using software RAID MDADM. I have the following configuration as fdisk -l reports: Disk /dev/sda: 223,6 GiB, 240057409536 bytes, 468862128 sectors Units: sectors of 1 * 512 = 512 bytes Sector size... (5 Replies)
Discussion started by: Reol
5 Replies

10. Ubuntu

Samba share on software raid1

Hello! i am having a ubuntu server with two empty disks and connected software raid1 to it. I am having /mnt/raid folder which i created to mount it. SO should i now make a share folder inside that or what? I ama bit confused when a raid is present. (27 Replies)
Discussion started by: tomislav91
27 Replies
vntsd(1M)						  System Administration Commands						 vntsd(1M)

NAME
vntsd - virtual network terminal server daemon for Logical Domains SYNOPSIS
/usr/lib/ldoms/vntsd DESCRIPTION
The vntsd daemon is a server that supports connections to the Logical Domains (LDoms) console by using telnet(1). When a telnet session starts, vntsd sends telnet options to the client indicating a willingness to remotely echo characters and to suppress go ahead. Consoles are organized into groups by the LDoms Manager. Each console group is assigned a unique group name and TCP port number. vntsd uses the group's port number to export access to the consoles within that group. To establish a connection with a console or console group, a user starts a telnet(1) session with the corresponding group's port number. Depending on the number of consoles within that group, vntsd does one of two things: o If there is only one console in the group, vntsd connects a session to that LDoms console. o If there are multiple consoles in the group, vntsd prompts the user to select the console to which they would like to connect, as shown in "Multiple-Console Options," below. For each console, vntsd provides write access only to the first user connecting to the console. Subsequent users connecting to the console are allowed only to read from the console and wait for write access. When the first user disconnects, write privileges are transferred to the next user waiting in the queue. If a user who does not have write privileges attempts to write to a console, the vntsd displays the following message: You do not have write access A user who has no write access can acquire write access forcibly by using the ~w special console command, described in "Special Console Commands," below. vntsd can be invoked only with superuser privileges or by someone in the Primary Administrator role. OPTIONS
The options for vntsd are divided into multiple-console options and console commands. Multiple-Console Options The options listed below are supported when there are multiple LDoms consoles in a group. The syntax for the use of these options is: <hostname>-vnts-<group-name>: <option> For example: myhost-vnts-salesgroup: h The h option invokes help, as described below. h Display the following help text: h -- this help l -- list of consoles q -- quit c{id}, n{name} -- connect to console of domain {id} or domain name l List all consoles in the group. For example: DOMAIN ID DOMAIN NAME DOMAIN STATE 0 ldg1 online 1 ldg2 connected ... ... ... The two domain states and their meanings are: online No one is connected to the console. connected At least one user is already connected to the console. q Disconnect from vntsd. c{id}, n{name} Connect to specified console. Upon connection, the following message is displayed: Connecting to console <domain-name> in group <group-name> Press ~? for control options .... Special Console Commands A tilde (~) appearing as the first character of a line is an escape signal that directs vntsd to perform a special console command. The tilde-tilde (~~) sequence outputs a tilde. In conjunction with the initial tilde, vntsd accepts the following special console commands: ~. Disconnect from the console or console group. ~w Force write access to the console. ~p Disconnect from this console, and connect to the console that precedes this console in the list of consoles. ~n Disconnect from this console, and connect to the console that follows this console in the list of consoles. ~# Send break. ~? Display vntsd help, as follows: ~# - Send break ~. - Exit from this console ~w - Force write access ~n - Console next ~p - Console previous ~? - Help FILES
/usr/lib/ldoms/vntsd Binary executable vntsd file. /usr/lib/ldoms/vntsd.xml Service management facility (smf(5)) manifest file for vntsd. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWldoms | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
telnet(1), svccfg(1M), usermod(1M), auth_attr(4), attributes(5), smf(5) NOTES
The vntsd is managed by the service management facility, smf(5), under the service identifier: svc:/ldoms/vntsd You can change the following properties using the svccfg(1M) command: vntsd/vcc_device Set an instance of the virtual console concentrator (vcc) driver to which vntsd is connected. vntsd/listen_addr Set the IP address to which vntsd listens, using the following syntax: vntsd/listen_addr:"xxx.xxx.xxx.xxx" ...where xxx.xxx.xxx.xxx is a valid IP address. The default value of this property is to listen on IP address 127.0.0.1. Users can con- nect to a guest console over a network if the value is set to the IP address of the control domain. Note - Enabling network access to a console has security implications. Any user can connect to a console and for this reason it is disabled by default. vntsd/timeout_minutes Set timeout in minutes. vntsd will timeout (close) telnet connection if there is no activity (input or output) on the console. The default value is 0, which disables timeout. vntsd/authorization Enable the authorization checking of users and roles for the domain console or consoles that are being accessed. The default value of this property is false to maintain backward compatibility. To enable authorization checking, use the svccfg(1M) command to set the property value to true. While this option is enabled, vntsd listens and accepts connections on localhost. If the listen_addr property specifies an alternate IP address when this option is enabled, vntsd ignores the alternate IP address and continues to listen on local- host. Connections that are initiated from other hosts will also fail. Authorizations are available to access all consoles or console groups, or to access specific consoles or console groups. When the vntsd service is enabled, the following authorization is added to the authorization description database, auth_attr(4): solaris.vntsd.consoles:::Access All LDoms Guest Consoles:: Add any fine-grained authorizations based on the name of the console group. For example, if the name of the console group to be autho- rized is ldg1, add the following entry to the auth_attr(4) file: solaris.vntsd.console-ldg1:::Access Specific LDoms Guest Console:: By default, the authorization to access all consoles is assigned to the root user or role. The Primary Administrator (superuser) can use the usermod(1M) command to assign the required authorization or authorizations to other users or roles. The following example gives user user1 the authorization to access all domain consoles: # usermod -A "solaris.vntsd.consoles" user1 The following example gives user user1 the authorization to access the console group named ldg1: # usermod -A "solaris.vntsd.console-ldg1" user1 SunOS 5.11 13 Feb 2009 vntsd(1M)
All times are GMT -4. The time now is 10:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy