I have installed Solaris 10 OS in Sun Virtual Box that uses x86 32 bit system. After an abnormal shutdown i'm getting the following message on the console when i try to boot.
Code:
SunOS Release 5.10 Version Generic_127128_11 32-bit
Copyright 1983-200 Sun Microsystems, Inc. All rights reserrved.
Use is subject to license terms.
WARNING: The following files in / differ from the boot archive:
changed /kernel/drv/md.conf
The recommended action is to reboot and select the "Solaris failsafe" option from the boot menu. Then follow the prompts to update the boot archive. To continue booting at your own risk, you may clear the service by running" "svcadm clear system/boot-archive"
May 17 15:53:47 svc.startd[7]: svc:/system/boot-archive:default: Method "/lib/svc/method/boot-archive" failed with exit status 95.
May 17 15:53:48 svc.startd[7]: system/boot-archive:default failed fatally: transitioned to maintenance (see 'svcs -xv' for details)
Requesting System Maintenance Mode
(See lib/svc/share/README for more information.)
Console login service(s) cannot run
Root password for system maintenance (control-d to bypass):****
single-user privilege assigned to /dev/console.
Entering System Maintenance Mode
May 17 16:05:04 su: 'su root' succeeded for root on /dev/console
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
#
When i reboot and select the "solaris failsafe" option as mentioned on the console, i'm getting the following message.
Code:
SunOS Release 5.10 Version Generic_127128_11 32-bit
Copyright 1983-200 Sun Microsystems, Inc. All rights reserrved.
Use is subject to license terms.
panic[cpu0]/thread=fec1ec20: boot_mapin(): No pp for pfnum = 0
Nothing is displayed after this. Can any one of you suggest me that, What should i need to do to overcome this panic situation?
Last edited by pludi; 05-17-2010 at 08:50 AM..
Reason: code tags, please...
hello guys.
I just installed SCO 5.0.6 OpenServer it went all the way to the end of the installation and the first boot try it gave me this message.
not a directory
boot not found
cannot open
stage 1 boot failure: error loading hd (40)/boot (2 Replies)
Hello.
System is a HP Visualize C3600 running X11 and after a power failure machine will not boot (see error messages below)
From what I've read, this may be caused by a corrupted etc/inittab file. Solution suggested on other websites is to boot in single user mode and edit file inittab... (2 Replies)
Hi all
I used a dual boot operating system and it works fine for me. Now , i install a Ati radeon 9250 Agp card on my system and this results in boot failure of fedora 6. The graphics card is working fine with windows XP , i.e i have no compatibility issues.The system also refuses to boot when i... (2 Replies)
I installed solaris virtually and tried to format the partitions .. I dont know what went wrong, It got rebooted and hangs in the screen "No partitions" and after pressing Enter button it goes to "INT18 boot failure" and hangs there once again . Could any one of you suggest why this has happened... (3 Replies)
hi
SCO Unix 5.0.6 doesn't boot due to this problem:
not a directory
boot not found
cannot open
stage 1 boot failure: error loading hd (40)/boot
Knows someone howto solve it? (16 Replies)
I'm trying to run clusterKnoppix live cd from a couple machines but it only works from one computer. The other three, my toshiba laptop, emachine, and hp machine can't find the filesystem.. the live cd stops booting and gives me a error saying it couldn't find knoppix filesystem and then gives me a... (0 Replies)
Hi Guys,
I have a small problem with a v445 which I have been informed will only boot with the reconfigure option enabled.
It is attached to HP SAN storage using qla2300 FCA's with a Veritas encapsulated rootvoldg (No Laughing here please) when I try a reboot I get the following error.
... (5 Replies)
When I login to the live console of my server and go to the console, I am getting the below message
Processor is booting from the first available device.
To discontinue, press any key within 10 seconds.
10 seconds expired.
Proceeding...
Trying Primary Boot Path... (11 Replies)
Discussion started by: chacko193
11 Replies
LEARN ABOUT X11R4
reboot
reboot(1M)reboot(1M)NAME
reboot - restart the operating system
SYNOPSIS
/usr/sbin/reboot [-dlnq] [boot_arguments]
The reboot utility restarts the kernel. The kernel is loaded into memory by the PROM monitor, which transfers control to the loaded kernel.
Although reboot can be run by the super-user at any time, shutdown(1M) is normally used first to warn all users logged in of the impending
loss of service. See shutdown(1M) for details.
The reboot utility performs a sync(1M) operation on the disks, and then a multi-user reboot is initiated. See init(1M) for details. On
systems, reboot may also update the boot archive as needed to ensure a successful reboot.
The reboot utility normally logs the reboot to the system log daemon, syslogd(1M), and places a shutdown record in the login accounting
file /var/adm/wtmpx. These actions are inhibited if the -n or -q options are present.
Normally, the system reboots itself at power-up or after crashes.
The following options are supported:
-d Force a system crash dump before rebooting. See dumpadm(1M) for information on configuring system crash dumps.
-l Suppress sending a message to the system log daemon, syslogd(1M) about who executed reboot.
-n Avoid calling sync(2) and do not log the reboot to syslogd(1M) or to /var/adm/wtmpx. The kernel still attempts to sync
filesystems prior to reboot, except if the -d option is also present. If -d is used with -n, the kernel does not attempt to
sync filesystems.
-q Quick. Reboot quickly and ungracefully, without shutting down running processes first.
The following operands are supported:
boot_arguments An optional boot_arguments specifies arguments to the uadmin(2) function that are passed to the boot program and kernel
upon restart. The form and list of arguments is described in the boot(1M) and kernel(1M) man pages.. If the arguments are
specified, whitespace between them is replaced by single spaces unless the whitespace is quoted for the shell. If the
boot_arguments begin with a hyphen, they must be preceded by the -- delimiter (two hyphens) to denote the end of the reboot
argument list.
Example 1: Passing the -r and -v Arguments to boot
In the following example, the delimiter -- (two hyphens) must be used to separate the options of reboot from the arguments of boot(1M).
example# reboot -dl -- -rv
Example 2: Rebooting Using a Specific Disk and Kernel
The following example reboots using a specific disk and kernel.
example# reboot disk1 kernel.test/unix
/var/adm/wtmpx login accounting file
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
mdb(1), boot(1M), dumpadm(1M), fsck(1M), halt(1M), init(1M), kernel(1M), shutdown(1M), sync(1M), syslogd(1M), sync(2), uadmin(2),
reboot(3C), attributes(5)
The reboot utility does not execute the scripts in /etc/rcnum.d or execute shutdown actions in inittab(4). To ensure a complete shutdown
of system services, use shutdown(1M) or init(1M) to reboot a Solaris system.
11 Apr 2005 reboot(1M)