Sponsored Content
Operating Systems Solaris V490 Failed To Boot After ALOM poweron Post 302240753 by quetzalcoatl on Friday 26th of September 2008 12:54:42 PM
Old 09-26-2008
eeprom command

Hi
I wonder if maybe itīs a good practice to store the OK variables in a text file
for futures references.

into OS should you use the eeprom command

root@ultra # eeprom
asr-policy=normal
test-args: data not available.
diag-passes=1
local-mac-address?=true
fcode-debug?=false
scsi-initiator-id=7
oem-logo: data not available.
oem-logo?=false
oem-banner: data not available.
oem-banner?=false
ansi-terminal?=true
screen-#columns=80
screen-#rows=34
ttyb-rts-dtr-off=false
ttyb-ignore-cd=true
ttya-rts-dtr-off=false
ttya-ignore-cd=true
ttyb-mode=9600,8,n,1,-
ttya-mode=9600,8,n,1,-
output-device=screen
input-device=keyboard
auto-boot-on-error?=false
error-reset-recovery=sync
load-base=16384
auto-boot?=true
network-boot-arguments: data not available.
boot-command=boot
diag-file: data not available.
diag-device=disk net
boot-file: data not available.
boot-device=disk net
use-nvramrc?=false
nvramrc=." ChassisSerialNumber ######### " cr
security-mode=none
security-password: data not available.
security-#badlogins=0
verbosity=min
diag-trigger=none
service-mode?=false
diag-script=none
diag-level=max
diag-switch?=false
 

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
HALT(8) 						Linux System Administrator's Manual						   HALT(8)

NAME
halt, reboot, poweroff - stop the system. SYNOPSIS
/sbin/halt [-n] [-w] [-d] [-f] [-i] [-p] [-h] /sbin/reboot [-n] [-w] [-d] [-f] [-i] /sbin/poweroff [-n] [-w] [-d] [-f] [-i] [-h] DESCRIPTION
Halt notes that the system is being brought down in the file /var/log/wtmp, and then either tells the kernel to halt, reboot or poweroff the system. If halt or reboot is called when the system is not in runlevel 0 or 6, in other words when it's running normally, shutdown will be invoked instead (with the -h or -r flag). For more info see the shutdown(8) manpage. The rest of this manpage describes the behaviour in runlevels 0 and 6, that is when the systems shutdown scripts are being run. OPTIONS
-n Don't sync before reboot or halt. -w Don't actually reboot or halt but only write the wtmp record (in the /var/log/wtmp file). -d Don't write the wtmp record. The -n flag implies -d. -f Force halt or reboot, don't call shutdown(8). -i Shut down all network interfaces just before halt or reboot. -h Put all harddrives on the system in standby mode just before halt or poweroff. -p When halting the system, do a poweroff. This is the default when halt is called as poweroff. DIAGNOSTICS
If you're not the superuser, you will get the message `must be superuser'. NOTES
Under older sysvinit releases , reboot and halt should never be called directly. From release 2.74 on halt and reboot invoke shutdown(8) if the system is not in runlevel 0 or 6. This means that if halt or reboot cannot find out the current runlevel (for example, when /var/run/utmp hasn't been initialized correctly) shutdown will be called, which might not be what you want. Use the -f flag if you want to do a hard halt or reboot. The -h flag puts all harddisks in standby mode just before halt or poweroff. Right now this is only implemented for IDE drives. A side effect of putting the drive in standby mode is that the write cache on the disk is flushed. This is important for IDE drives, since the kernel doesn't flush the write-cache itself before poweroff. The halt program uses /proc/ide/hd* to find all IDE disk devices, which means that /proc needs to be mounted when halt or poweroff is called or the -h switch will do nothing. AUTHOR
Miquel van Smoorenburg, miquels@cistron.nl SEE ALSO
shutdown(8), init(8) Nov 6, 2001 HALT(8)
All times are GMT -4. The time now is 10:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy