07-14-2010
Can you get into the service advisor and check? I have never attempted to poweroff from CAM. You can only manually poweroff the array
9 More Discussions You Might Find Interesting
1. Solaris
I have a Sun Sparc T2000 (Solaris 10 05-08) and have installed a PCI-X 4GB Single Port HBA card in it.
I have one StorageTek 2540 array that I would like to connect to the T2000.
For the moment it would be a single path connection, but I've ordered a 2nd HBA, so eventually it would be... (4 Replies)
Discussion started by: soliberus
4 Replies
2. Solaris
We're moving our production 3510FC to development, so we need to replace the production 3510FC. The 6140 is nice, but pricey.
Here's the question: Would two 2540's (RAID 10) be 'faster' than one 3510? (RAID 10) and faster than one 6140 (RAID 10)?
One StoregeTek 6140 (16x72GB 15k rpm fc-al... (12 Replies)
Discussion started by: buddhavelvet
12 Replies
3. Filesystems, Disks and Memory
Hi,
We have 12x1TB SATA disks in our array and I need to create 10TB volume. I defined new storage profile on array and when I tried to add volume, I faced with ~2TB limit for new volumes. I didn't find how to set another limit on my storage profile. Is there is a way to configure one large... (3 Replies)
Discussion started by: Sapfeer
3 Replies
4. Solaris
Hi peeps,
Was wondering if anyone can help me, got a couple of storagetek 2540's that I need to configure. Trouble is I think they were brought as second user as all that came with them was cables.
Does anyone know how to configure them (i.e. create raid sets and map to Luns and present... (1 Reply)
Discussion started by: callmebob
1 Replies
5. Hardware
Hello all !
I am a beginner about system and networking , and after some research on internet , i didn't find any relevant information , so i post here , if someone have an experience with this kind of material or if some documentation about how to connect my storage device on my server.
I... (2 Replies)
Discussion started by: acorradi
2 Replies
6. Hardware
Hi all,
My Sun StorageTek 2540 have redundant batteries, but a battery was failed.
# /opt/SUNWstkcam/bin/sscs list -d MyStorage1 fru
Name FRU Alarm State Status Revision Unique Id
-------------------------- ----------- --------... (2 Replies)
Discussion started by: buyantugs
2 Replies
7. Hardware
Hi Guys and Gals,
Wionder if you could help me, got a problem with a controller on a storagetek 2540, dead when fully powered up but if you reboot, it is ok for a couple of seconds (and you can ping it). Then once the array is fully up, it goes faulty and is un-pingable.
Had anyone... (4 Replies)
Discussion started by: callmebob
4 Replies
8. Solaris
Bought a Sun StorageTek 2540 SAN array a few years ago from a company that was going out of business. When we first set it up, we were able to get all the software (Common Array Manager) and firmware directly from Sun.
We just upgraded the drives, but the array is too large for the firmware. Now... (6 Replies)
Discussion started by: edison303
6 Replies
9. Solaris
Hi Guys,
I have situation here ...
server M4000 server lost connectivity to storagetek 2540
, storagetek 2540 unable to be ping.From DAS URL the storage is undetected.
Any idea why this is happening. Please share.
Thank you.
Raj (1 Reply)
Discussion started by: muralirajah
1 Replies
LEARN ABOUT MOJAVE
systemd-halt.service
SYSTEMD-HALT.SERVICE(8) systemd-halt.service SYSTEMD-HALT.SERVICE(8)
NAME
systemd-halt.service, systemd-poweroff.service, systemd-reboot.service, systemd-kexec.service, systemd-shutdown - System shutdown logic
SYNOPSIS
systemd-halt.service
systemd-poweroff.service
systemd-reboot.service
systemd-kexec.service
/lib/systemd/systemd-shutdown
/lib/systemd/system-shutdown/
DESCRIPTION
systemd-halt.service is a system service that is pulled in by halt.target and is responsible for the actual system halt. Similarly,
systemd-poweroff.service is pulled in by poweroff.target, systemd-reboot.service by reboot.target and systemd-kexec.service by kexec.target
to execute the respective actions.
When these services are run, they ensure that PID 1 is replaced by the /lib/systemd/systemd-shutdown tool which is then responsible for the
actual shutdown. Before shutting down, this binary will try to unmount all remaining file systems, disable all remaining swap devices,
detach all remaining storage devices and kill all remaining processes.
It is necessary to have this code in a separate binary because otherwise rebooting after an upgrade might be broken -- the running PID 1
could still depend on libraries which are not available any more, thus keeping the file system busy, which then cannot be re-mounted
read-only.
Immediately before executing the actual system halt/poweroff/reboot/kexec systemd-shutdown will run all executables in
/lib/systemd/system-shutdown/ and pass one arguments to them: either "halt", "poweroff", "reboot" or "kexec", depending on the chosen
action. All executables in this directory are executed in parallel, and execution of the action is not continued before all executables
finished.
Note that systemd-halt.service (and the related units) should never be executed directly. Instead, trigger system shutdown with a command
such as "systemctl halt" or suchlike.
SEE ALSO
systemd(1), systemctl(1), systemd.special(7), reboot(2), systemd-suspend.service(8)
systemd 237 SYSTEMD-HALT.SERVICE(8)