11-02-2008
Try removing the hard disks. Then boot it it. That pretty much has to send you to the ok prompt. Once there do:
setenv auto-boot? false
Then power it off, replace the drives, and turn it back on. You should return to the ok prompt. You can set auto-boot? back to true after you get the os installed if you want.
10 More Discussions You Might Find Interesting
1. Solaris
Hey All
Thanks in Advance.
Iam facing a problem with Netra T1 105 Ram issuse.I have 1 gb ram in the server but when it boots up in ok prompt or in banner it shows 768 mb Ram , if i put 512 mb Ram it show 368 mb Ram but this all ram if i connect in anthore netra server its shows 1 gb and... (1 Reply)
Discussion started by: solaris8in
1 Replies
2. Solaris
Hello,
I wrote a script which monitor the keyswitch state repeatedly each 10 minutes.
I'm extracting the keyswitch status by using prtdiag.
The script works fine for Netra v440 , but I found that prtdiag under Netra 1290 don't give keyswitch status.
unlike Netra 440 server , I found that... (2 Replies)
Discussion started by: Alalush
2 Replies
3. Solaris
Hi,
I have Sun SPARC Enterprise T5140 and I can't access it via serial port using preconfigured administrator account, as described in Sun Integrated Lights Out Manager 2.0 User's Guide: I'm always receive "Login incorrect" message. I'm really confused! Does anyone experience such circumstances?... (12 Replies)
Discussion started by: Sapfeer
12 Replies
4. Debian
Comments/Problems:
Machine boots from CDROM, starts SILO Version 1.4.13,
display welcome message (welcome to Debian GNU/Linux lenny!
built on 20081218-10:06 ).
boot:
Allocated 8 Megs of memory at 0x40000000 for kernel
Loaded kernel version 2.6.26
Loading initial ramdisk... (3 Replies)
Discussion started by: mtk
3 Replies
5. Solaris
Looking for ideas on why I can't dial into our new Avaya CMS server (Sun Netra 210 - Sol 9) - remotely thru our ASA - site admin software.
Running R3-V13 Avaya CMS software - just did a fresh install of the CMS software - install went perfect.
The Sun supplied DB9 connector is installed... (1 Reply)
Discussion started by: drewmich
1 Replies
6. Solaris
Hi,
I have a netra t2000 running solaris 10. It is fully patched with the latest patch cluster and also patch 118833-36 and 126897-02. The SC sys_event level is set to 3.
I am running a test to show hardware log status, e.g simulating a power supply failure.Hence I unplug one of te... (3 Replies)
Discussion started by: ulemsee
3 Replies
7. Ubuntu
hello guys i bought a SPARC neutra system a couple of months ago and after failing to install solaris onto it (and leaving it as a door stop for a couple of months) decided to stick ubuntu onto it
for starters i dont own a sun keyboard i have a cheap pcline usb keyboard (it works... (3 Replies)
Discussion started by: garethmob
3 Replies
8. Solaris
Newbie question.
I've been running OpenSolaris on an Intel box for some time with great success.
I have just bought an old Sun Blade workstation with a corrupted version of Solaris 5 something on it.
The plan was to install OpenSolaris on it.
However beyond my skills, I see, as no Live CD (or... (10 Replies)
Discussion started by: lewtargett
10 Replies
9. Solaris
Hi All,
I had install the solaris 10 into the SUNFIRE V890 server, after installed, it keep rebooting.
I wish to enter the OK mode again, and install back the Solaris 10.
i had try the "break" button and "stop+A" button, but all fail.
kindly advice... (4 Replies)
Discussion started by: SmartAntz
4 Replies
10. Hardware
Hi guys,
when I power on my sun netra 240 server,
it displays these error messages:
1. Notice: cpu 0 has 2048/2048 MB of memory disabled.
2. Error : The following devices are disabled dimm1.
Please can anyone be kind enough to explain this for me?
Thanks (2 Replies)
Discussion started by: cjashu
2 Replies
LEARN ABOUT POSIX
bootctl
BOOTCTL(1) bootctl BOOTCTL(1)
NAME
bootctl - Control the firmware and boot manager settings
SYNOPSIS
bootctl [OPTIONS...] status
bootctl [OPTIONS...] list
bootctl [OPTIONS...] update
bootctl [OPTIONS...] install
bootctl [OPTIONS...] remove
DESCRIPTION
bootctl checks, updates, installs or removes the boot loader from the current system.
bootctl status checks and prints the currently installed versions of the boot loader binaries and all current EFI boot variables.
bootctl list displays all configured boot loader entries.
bootctl update updates all installed versions of systemd-boot, if the current version is newer than the version installed in the EFI system
partition. This also includes the EFI default/fallback loader at /EFI/BOOT/BOOT*.EFI. A systemd-boot entry in the EFI boot variables is
created if there is no current entry. The created entry will be added to the end of the boot order list.
bootctl install installs systemd-boot into the EFI system partition. A copy of systemd-boot will be stored as the EFI default/fallback
loader at /EFI/BOOT/BOOT*.EFI. A systemd-boot entry in the EFI boot variables is created and added to the top of the boot order list.
bootctl remove removes all installed versions of systemd-boot from the EFI system partition, and removes systemd-boot from the EFI boot
variables.
If no command is passed, status is implied.
OPTIONS
The following options are understood:
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
--path=
Path to the EFI System Partition (ESP). If not specified, /efi, /boot, and /boot/efi are checked in turn. It is recommended to mount
the ESP to /boot, if possible.
-p, --print-path
This option modifies the behaviour of status. Just print the path to the EFI System Partition (ESP) to standard output and exit.
--no-variables
Do not touch the EFI boot variables.
EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise.
SEE ALSO
Boot loader specification[1] systemd boot loader interface[2]
NOTES
1. Boot loader specification
https://www.freedesktop.org/wiki/Specifications/BootLoaderSpec
2. systemd boot loader interface
https://www.freedesktop.org/wiki/Software/systemd/BootLoaderInterface
systemd 237 BOOTCTL(1)