02-02-2005
I now know what's wrong, but I do not know how to fix it.
I made the following discoveries:
In the "intepreter" mode, I type "set" and can see all the variables. def_bootfile was set to 'now', which explains why I get the error message "can't run now".
I can boot the CDROM, and when I do, it's def_bootfile is 'kernel/unix'
So I changed the def_bootfile to 'kernel/unix' and I am able to boot.
However, every time I reboot, def_bootfile gets reset to 'now'. How to I make it permanent?
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I couldnt get my hands on my solaris 2.6 cd soo i used solaris 7 cd to boot to single user mode. I typed
boot cdrom -s
it bought me to my root prompt , but when i typed fsck.....nothing happened. It was as though it couldnt go ahead with fscking. it just bought up the prompt again,... (1 Reply)
Discussion started by: lealyz
1 Replies
2. Solaris
Hello everybody,
I installed sun solaris i86 , the programme installation install the
"Mini Root" and after that he doing shutdown.
the camputer coming up and he can't boot.
how i can to resuled this problem ???
Thenk you in advence..... (2 Replies)
Discussion started by: yanly
2 Replies
3. Solaris
When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error.
cannot find mis/krtld
boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies
4. UNIX for Advanced & Expert Users
Our V480 w/ Solaris 9 would not boot properly. After recreating the LUNs on our StorEdge A1000, and then performing a reboot, the machine just keep cycling through the boot process. No error messages, it keeps trying to reboot over and over again.
Any ideas?
We managed to do a stop+a and... (6 Replies)
Discussion started by: xnightcrawl
6 Replies
5. Solaris
Hi All,
I am newbie in solaris, please guide me.
A week before i installed solaris10 on my x86 system, it was working fine i always used "init 5" to shutdown my system as per my collegue advice.
But yesterday when i started my system it gave me following message
... (6 Replies)
Discussion started by: imrankhan.in
6 Replies
6. 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
7. Solaris
Hi All,
I have an x86 system which I have just installed Solaris 10 on, I intend to use this as a database server for Oracle, I tried to patch the server with the latest updates from SUN in preparation for the Oracle installation as I wanted to make sure that I was running the latest patches.
... (0 Replies)
Discussion started by: platforminc
0 Replies
8. Solaris
Hi All
We have the Sun Solaris server ... Got a power cut suddenly .... Crash happened to the system almost
You can access through Termnl .. But it seems he did not boot ... How to Make the process of the boot correctly without losing information
Thanks for all (3 Replies)
Discussion started by: gogo888
3 Replies
9. Solaris
Hello,
We have a T5140 server with Solaris 10 and its suddenly throwing "segmentation core" when I login into the server and not showing any output for commands like df, mount etc. so I had to reboot the server to fix this issue. Please note that there's no boot disk mirroring.
But... (2 Replies)
Discussion started by: prvnrk
2 Replies
10. Solaris
Hi
I have a problem on a server, when he boot I have this type of message loop, do you know what it corresponds to ?
( requesting internet Adress for 0:3:ba:fa:33:91 )
Regards
Sun Fire V240, No Keyboard
Copyright 2007 Sun Microsystems, INC. All rights reserved.
openboot 4.22.33,... (10 Replies)
Discussion started by: yoyo-tns
10 Replies
LEARN ABOUT FREEBSD
fasthalt
REBOOT(8) BSD System Manager's Manual REBOOT(8)
NAME
reboot, halt, fastboot, fasthalt -- stopping and restarting the system
SYNOPSIS
halt [-lnpq] [-k kernel]
reboot [-dlnpq] [-k kernel]
fasthalt [-lnpq] [-k kernel]
fastboot [-dlnpq] [-k kernel]
DESCRIPTION
The halt and reboot utilities flush the file system cache to disk, send all running processes a SIGTERM (and subsequently a SIGKILL) and,
respectively, halt or restart the system. The action is logged, including entering a shutdown record into the user accounting database.
The options are as follows:
-d The system is requested to create a crash dump. This option is supported only when rebooting, and it has no effect unless a dump
device has previously been specified with dumpon(8).
-k kernel
Boot the specified kernel on the next system boot. If the kernel boots successfully, the default kernel will be booted on successive
boots, this is a one-shot option. If the boot fails, the system will continue attempting to boot kernel until the boot process is
interrupted and a valid kernel booted. This may change in the future.
-l The halt or reboot is not logged to the system log. This option is intended for applications such as shutdown(8), that call reboot
or halt and log this themselves.
-n The file system cache is not flushed. This option should probably not be used.
-p The system will turn off the power if it can. If the power down action fails, the system will halt or reboot normally, depending on
whether halt or reboot was called.
-q The system is halted or restarted quickly and ungracefully, and only the flushing of the file system cache is performed (if the -n
option is not specified). This option should probably not be used.
The fasthalt and fastboot utilities are nothing more than aliases for the halt and reboot utilities.
Normally, the shutdown(8) utility is used when the system needs to be halted or restarted, giving users advance warning of their impending
doom and cleanly terminating specific programs.
SEE ALSO
getutxent(3), boot(8), dumpon(8), nextboot(8), savecore(8), shutdown(8), sync(8)
HISTORY
A reboot utility appeared in Version 6 AT&T UNIX.
BSD
October 11, 2010 BSD