08-27-2002
You are either booting off the wrong device (possible but not likely) or your boot device has died a horrible death.
Boot cdrom -s from the ok prompt (after inserting a Solaris bootable cd into the cdrom drive. You will get a # prompt once it is booted.
You can then check out the drive to insure it is stable (run fsck against it, check that the system 'sees' it, insure the bootblock is installed). If you aren't suppose to be booting c0t0d0s0 as the boot device, then possibly it was changed in the EEPROM to the wrong disk and you only need to change it to the correct one - sometimes it's c0t3d0s0. If you don't know, then you need to check out your /etc/vfstab from booting cdrom single user and mounting your different drives till you find it.
9 More Discussions You Might Find Interesting
1. Solaris
Hi i need help pls ...
Server type sun fire 3800 I need to install solaris 9 .
When i boot the system i recieve the following :
System Controller 'sunfire3800':
Type 0 for Platform Shell
Type 1 for domain A console
Type 2 for domain B console
Type 3 for... (5 Replies)
Discussion started by: tt155
5 Replies
2. Solaris
I have a real emergency. I have a Sun Fire V240 UltraSparc server and am connected via the Serial Mgmnt Port with a Laptop. I have been building an Oracle database on it for the past couple months, not getting very far along with it , when suddenly, the system had a fatal crash. I've lost the... (2 Replies)
Discussion started by: mayewil
2 Replies
3. Solaris
Okay, let me sketch the problem.
I did have a ubuntu / Windows XP dual boot scenario that ran grub as my boot loader. I decided I wanted to try out solaris, so I popped in the opensolaris CD and hit install and told it to format and install over my linux partition.
Of course it did that, and... (2 Replies)
Discussion started by: syndex
2 Replies
4. Solaris
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
5. Solaris
Hi gurus,
I'm beginner with all this unix stuff and I'm trying to install a Solaris 8 but I got this error:
ok
ok
ok boot cdrom
SC Alert: Host System has Reset
Sun Fire V240, No Keyboard
Copyright 1998-2003 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.13.2, 512 MB memory... (9 Replies)
Discussion started by: knight_mare
9 Replies
6. Solaris
Greetings friends,
I would like to 'clone' the system/root hard disk with dd. (Solaris 10 on SPARC).
If I understood correctly, 'OK Prompt' can use dd command?
Can it mount drives? (to avoid any possibility of cloning the wrong drive, I'd like to output dd to file)
thanks. (3 Replies)
Discussion started by: orange47
3 Replies
7. AIX
Hello,
I installed PowerVM IVM Virtual I/O on P-550 but later found out that the machine isn't activated for CoD VET code for virtualization.
So when booted , it goes into OPEN Firmware
I/O Hosting requires a hosting partition boot not permitted exit called
> ok
Panel shows > IO... (3 Replies)
Discussion started by: filosophizer
3 Replies
8. Solaris
I installed a new hard drive completely blank.
sun blade 150
openboot 4.10.6
message:
Boot device: disk:a File and args:
Bad magic number in disk label
Can't open label package
Evaluating:
Can't open boot device (15 Replies)
Discussion started by: janiper
15 Replies
9. Solaris
Hello Forum,
I'm really in a fix now,
I'm getting this error message now, seems like the boot block is damaged?
When I do probe-all the system freezes...
Can any one guide me as what to do next?
System is Solaris 8 running Open Boot PROM 4
System also does not have a cd/dvd rom drive...
... (17 Replies)
Discussion started by: br1an
17 Replies
LEARN ABOUT X11R4
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)