07-18-2009
fugitive, i asked above ..
give much more details about your system and how u configured your LDoms.
otherwise i cant say anything, according to behaviour of startup process, something wong with your configuration, certainly with assignment of devices to LDoms.
good luck!
10 More Discussions You Might Find Interesting
1. Linux
Dear Srs,
I have a Linux server (linux01) booting from SAN with a volume in a Nexsan SATAbeast storage array (san01). The disk/volume has four ext3 partitions, total size is near to 400GB, but only 20-30GB are in use.
I need to move this disk/volume to another Nexsan SATAbeast storage array... (0 Replies)
Discussion started by: Santi
0 Replies
2. Red Hat
Hi,
We have 200GB SAN volume mounted on Redhat EL 5. which is working fine. As my SAN supports dynamic resizing of volumes, i unmounted the volume and resized the SAN Volume to 300 GB successfully. Then i mounted again but it shows 200GB only but data is intact.
Now, my requirement is to let... (3 Replies)
Discussion started by: prvnrk
3 Replies
3. AIX
Hello all. I have a perplexing problem
I have an AIX 5.1 system on an EMC SAN.
This system had been on a CX400 SAN for several years. The system was migrated to a CX700 just over a week ago. The migration consisted of utilizing on of the HBAs in the system and connecting to both SANs
... (9 Replies)
Discussion started by: mhenryj
9 Replies
4. Solaris
Is there any way i can mount a zfs volume using snapshot or some other means ? (2 Replies)
Discussion started by: fugitive
2 Replies
5. Solaris
Hi, I need to expand a ZFS volume from 500GB to 800GB. I'd like to ask your help to confirm the following procedure:
Can I do it on the fly without bothering the users working on this volume?
Thank you in advance! (6 Replies)
Discussion started by: aixlover
6 Replies
6. Solaris
I have viewed a few previous posts regarding this, but none of them quite described or worked with my issue.
I am out of local disk space on my LDOM Manager but still have plenty of SAN vCPU and Memory available so I am trying to install a new LDOM OS on SAN.
I have exposed the SAN to the... (0 Replies)
Discussion started by: MobileGSP
0 Replies
7. Solaris
Apologies if this is the wrong forum..
I have some LDOMs running on a Sparc server. I copied the disk0 file from one chassis over to another, stopped the ldom on the source system and started it on the 2nd one. All fine. Shut it down and flipped back. We then did a fair bit of work on the... (4 Replies)
Discussion started by: tommyq
4 Replies
8. Red Hat
I have an IBM blade running RHEL 5.4 server, connected to two Hitachi SANs using common fibre cards & Brocade switches. It has two volume groups made from old SAN LUNs. The old SAN needs to be retired so we allocated LUNs from the new SAN, discovered the LUNs as multipath disks (4 paths) and grew... (4 Replies)
Discussion started by: rbatte1
4 Replies
9. Solaris
Hi all,
I'm using Solaris 11.3.
HBA port connected to SAN disk 3T.
AVAILABLE DISK SELECTIONS:
0. c0t600A0B800033696A0000214B571938F1d0 <SUN-CSM200_R-0760 cyl 44556 alt 2 hd 255 sec 189>
/scsi_vhci/ssd@g600a0b800033696a0000214b571938f1
1. c2t3C58620E0C565100d0... (1 Reply)
Discussion started by: manhte1
1 Replies
10. Solaris
Generally, this is what we do:-
On primary, export 2 LUNs (add-vdsdev).
On primary, assign these disks to the ldom in question (add-vdisk).
On ldom, created mirrored zpool from these two disks.
On one server (which is older) we have:-
On primary, create mirrored zpool from the two LUNs.... (4 Replies)
Discussion started by: psychocandy
4 Replies
LEARN ABOUT LINUX
startup
startup(7) Miscellaneous Information Manual startup(7)
NAME
startup - event signalling system startup
SYNOPSIS
startup [ENV]...
DESCRIPTION
The startup event is generated by the Upstart init(8) daemon after it has completed its own initialisation and is the signal that the rest
of the system may be started.
Typically this will involve checking and mounting the partitions and drives that form the filesystem, loading drivers for connected devices
and starting the X windowing system or other login environment.
In the default Upstart configuration, the primary task run on the startup event is the /etc/init/rc-sysinit.conf job responsible for gener-
ating the System V compatible runlevel(7) event. See that page for a more detailed explanation of this process.
Paradoxically there is currently no corresponding Upstart-native event signifying that the system is to be shutdown, only the System V com-
patible runlevel 0 and runlevel 6 events provide this functionality.
EXAMPLE
A service with no other dependencies run on startup might use:
start on startup
SEE ALSO
runlevel(7) init(8)
Upstart 2009-07-09 startup(7)