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
Unfortunately I can't test it at the moment because the server is up around an hour ago. I was just been informed by my higher technical guy that auto-boot = false and now he set auto-boot = yes. I guess this is step that I need to do next time (based on ur comment and his email to me).
Now I know that previously system is not starting up automatically after power-on / reset because auto-boot is set to false (and the system stops at OK prompt). Thank you for the insight. You're the best, man !
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)
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)
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)
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)
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)
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)
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)
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)
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
LEARN ABOUT NETBSD
boot
BOOT(8) BSD System Manager's Manual BOOT(8)NAME
boot -- system bootstrapping procedures
DESCRIPTION
This document provides information on using common features in the NetBSD boot loader. Additional information may be found in architecture-
specific boot(8) manual pages.
In the native NetBSD boot protocol, options are passed from the boot loader to the kernel via flag bits in the boothowto variable (see
boothowto(9)).
Interactive mode
In interactive mode, the boot loader will present a prompt, allowing input of these commands:
boot [device:] [filename] [-1234abcdmqsvxz]
The default device will be set to the disk that the boot loader was loaded from. To boot from an alternate disk, the full name of
the device should be given at the prompt. device is of the form xd [N[x]] where xd is the device from which to boot, N is the unit
number, and x is the partition letter.
The following list of supported devices may vary from installation to installation:
hd Hard disks.
fd Floppy drives.
The default filename is netbsd; if the boot loader fails to successfully open that image, it then tries netbsd.gz (expected to be a
kernel image compressed by gzip), followed by netbsd.old, netbsd.old.gz, onetbsd, and finally onetbsd.gz. Alternate system images
can be loaded by just specifying the name of the image.
Options are:
-1 Sets the machine-dependent flag RB_MD1 in boothowto.
-2 Sets the machine-dependent flag RB_MD2 in boothowto.
-3 Sets the machine-dependent flag RB_MD3 in boothowto.
-4 Sets the machine-dependent flag RB_MD4 in boothowto.
-a Sets the RB_ASKNAME flag in boothowto. This causes the kernel to prompt for the root file system device, the system crash
dump device, and the path to init(8).
-b Sets the RB_HALT flag in boothowto. This causes subsequent reboot attempts to halt instead of rebooting.
-c Sets the RB_USERCONF flag in boothowto. This causes the kernel to enter the userconf(4) device configuration manager as soon
as possible during the boot. userconf(4) allows devices to be enabled or disabled, and allows device locators (such as hard-
ware addresses or bus numbers) to be modified before the kernel attempts to attach the devices.
-d Sets the RB_KDB flag in boothowto. Requests the kernel to enter debug mode, in which it waits for a connection from a kernel
debugger; see ddb(4).
-m Sets the RB_MINIROOT flag in boothowto. Informs the kernel that a mini-root file system is present in memory.
-q Sets the AB_QUIET flag in boothowto. Boot the system in quiet mode.
-s Sets the RB_SINGLE flag in boothowto. Boot the system in single-user mode.
-v Sets the AB_VERBOSE flag in boothowto. Boot the system in verbose mode.
-x Sets the AB_DEBUG flag in boothowto. Boot the system with debug messages enabled.
-z Sets the AB_SILENT flag in boothowto. Boot the system in silent mode.
consdev dev
Immediately switch the console to the specified device dev and reprint the banner. dev must be one of pc, com0, com1, com2, com3,
com0kbd, com1kbd, com2kbd, com3kbd, or auto. See Console Selection Policy in boot_console(8).
dev [device]
Set the default drive and partition for subsequent filesystem operations. Without an argument, print the current setting. device
is of the form specified in boot.
help Print an overview about commands and arguments.
ls [path]
Print a directory listing of path, containing inode number, filename, and file type. path can contain a device specification.
quit Reboot the system.
In an emergency, the bootstrap methods described in the NetBSD installation notes for the specific architecture can be used.
FILES
/boot boot program code loaded by the primary bootstrap
/netbsd system code
/netbsd.gz gzip-compressed system code
/usr/mdec/boot master copy of the boot program (copy to /boot)
/usr/mdec/bootxx_fstype primary bootstrap for filesystem type fstype, copied to the start of the NetBSD partition by installboot(8).
SEE ALSO
Architecture-specific boot(8) manual pages, ddb(4), userconf(4), halt(8), installboot(8), reboot(8), rescue(8), shutdown(8), boothowto(9)BUGS
The kernel file name must be specified before, not after, the boot options. Any filename specified after the boot options, e.g.:
boot -d netbsd.test
is ignored, and the default kernel is booted.
BSD September 4, 2009 BSD