Sponsored Content
Operating Systems Solaris V490 Failed To Boot After ALOM poweron Post 302240514 by DukeNuke2 on Friday 26th of September 2008 02:51:13 AM
Old 09-26-2008
go to console from the rsc card with "console" and have a look if the "ok" prompt is visible... if so, have a look at the output of "printenv". i think "auto-boot?" is set to "false".
now you can do a "boot" to boot your 490 or you do a "setenv auto-boot? true" and then a "reset-all" and have a look if the new settings work.

hth,
DN2
 

10 More Discussions You Might Find Interesting

1. Solaris

Boot problem: failed to mount /usr

My Solaris10 cannot boot after I made an error when apending the vfstab to: dev to mount======/dev/dsk/c0d0p1:1 device to fsck====== <blank> mount pt=========/Data FS Type==========pcfs fsck pass=========- mount at boot=====yes mount options===== <blank> My 'Data' partition is a... (3 Replies)
Discussion started by: maag
3 Replies

2. Solaris

boot load failed

I modified the partitions on my Solaris 10 disk using format command in "boot cdrom -s" mode and then tried rebooting with "reboot". It said "Boot load failed". Why does this happen? I have faced this error before:( and I went in for a fresh installation of the OS.Can anyone tell me the reason as... (1 Reply)
Discussion started by: lydiaEd
1 Replies

3. UNIX and Linux Applications

debian boot failed on IBM RS6000 7025 F80

Hi everybody. I have an old IBM RS6000 Model 7025 F80 with AIX 4.3.3 installed with 2 primary scsi disks. I want to install linux (any flavor) on it. I downloaded and burned an iso image of debian (http://cdimage.debian.org/debian-cd/4.0_r4a/powerpc/iso-cd/debian-40r4a-powerpc-netinst.iso),... (3 Replies)
Discussion started by: pitagoras
3 Replies

4. Solaris

V490 - Centerplane failed

Hi all, I'm freshman in this forum. I'm here to ask for your help. A case about Sun Fire V490. But, before starting to ask, I want to tell you the story. Last week, I was told about a failed V490 in Da Nang City (Vietnam). It could NOT boot. After diagnosing it remotely, I found that the... (6 Replies)
Discussion started by: nam.nguyen
6 Replies

5. Solaris

Solaris10..Open boot diagnostic failed

Hi all, when am rebooting the server (SF v890) we are facing "open boot diagnostic failed". Thanks in Adv. (5 Replies)
Discussion started by: arjunreddy3
5 Replies

6. Solaris

Sun Netra T1 won't poweron/no POST

Hi guys. I have an old Netra T1 that I'm hoping to recover here so I can twiddle around with Solaris 10. It's been unable to power on despite issuing the "poweron" command or hitting the switch at the back of the server for some time. The LOM command "env" reports ALARM3 ON and everything else... (8 Replies)
Discussion started by: detach8
8 Replies

7. Solaris

M5000 boot net- install failed

Good evening all,I'm new to your site, so please bear any infringements or transgressions on my part.I'm new to the whole Solaris boot install over the net scenario, but here's where I'm stuck:I have an M5000 with 2 domains (running unimode). Domain 0 is configured and running Solaris 10. Domain 1... (9 Replies)
Discussion started by: RandomSun
9 Replies

8. Solaris

Difference b/n ALOM and ALOM CMT

Hi Everyone. What is the differece b/n ALOM and ALOM CMT Service processor. I am trying reset ALOM login/passwd using scadm utility on T2000, while I am googling I came cross ALOM CMT doesnt support scadm utility, but ALOM supports. Not sure how different are these. Thanks, (0 Replies)
Discussion started by: bobby320
0 Replies

9. Solaris

Solaris 10 boot failed init

Dear all, I have a solaris 10 in my environment (VMware virtual machine). recently I increased the harddisk size from the VMware and reboot my server. after reboot the os is unable to boot and gives the below error message. exec(/sbin/init) file not found press any key to restart ... (3 Replies)
Discussion started by: krishna001
3 Replies

10. Solaris

Fresh Install - Boot Load Failed

I have M10-1. Installation OS 10 from cdrom external. Here message from OK Prompt {0} ok probe-scsi-all /pci@8000/pci@4/pci@0/pci@2/pci@0/usb@4,1/cdrom@1 Unit 0 Removable Read Only device HL-DT-STDVDRAM GP65NB60 PF00 But.. {0} ok boot... (3 Replies)
Discussion started by: mbahjiman
3 Replies
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)
All times are GMT -4. The time now is 10:42 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy