01-11-2008
boot load failed
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 to why this happens?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi
i have both Linux and Windows XP on my PC.
i used to use grub as a boot loader and everything was perfect, until
i reinstalled Windows.
apparently, Windows installer installed its own bootloader, that
doesn't recognize Linux.
i tried using a tool called GrubInstaller for Windows, and now... (4 Replies)
Discussion started by: shx2
4 Replies
2. HP-UX
Hi There,
Does anyone knows what could be the problem if my apache server is running but unable to load JK2 module into the server. My HTTPS is running on Apache Server 2.0.49 with ssl enabled and compiled with Mod_ssl on HPUX-11.11i.
In fact we have try out the following parameter,
... (4 Replies)
Discussion started by: e_jeffhang
4 Replies
3. UNIX for Dummies Questions & Answers
zero experience Unix user here. Cannot boot our Sparc10.
Running:
SunOS release 5.3 Version Generic_Patch
message says:
(Can't load swapgeneric)
Program terminated
Tried to 'boot -s' , but this looks like a problem w/ Generic_Patch maybe?
At bootup, the devices come up fine and it... (0 Replies)
Discussion started by: man_of_action
0 Replies
4. Solaris
After issuing reboot command (and disconnected from PuTTY), server is not even rebooted because ping test is succesful. So I connect to ALOM and issue poweroff command. After a minute, I did poweron and get this message (only).
rsc> poweron
Are you sure you want to turn your system power on... (10 Replies)
Discussion started by: Olli.Lang
10 Replies
5. Solaris
My solaris 8 server messages log recored error
"Sep 30 21:35:00 bkp1 cron: open_module: /usr/lib/security/pam_unix_cred.so.1 failed: ld.so.1: cron: fatal: libproject.so.1: open failed: No such file or directory"
Any idea what is this related to and how to stop?
thanks in advance. (2 Replies)
Discussion started by: admin@solaris
2 Replies
6. SuSE
Hi All,
I got the following errors when i was trying to restart Infiniband service.
Loading cxgb3 driver :
Loading HCA driver and Access Layer :
The command managed to bring up the services, but without RDMA modules loaded from /etc/init.d/openibd status output. Is the missing of RDMA... (0 Replies)
Discussion started by: dchm
0 Replies
7. AIX
In my AIX 7.1 , jre is not working. I have attempted reinstalling but not succeeded to get rid of the error. Following error I am getting (jvm.dll failed to load: global entrypoints not found)
bash-4.2# cd /usr/java6/jre/bin/
bash-4.2# java -version
jvm.dll failed to load: global entrypoints... (4 Replies)
Discussion started by: George47
4 Replies
8. SCO
I'm under huge pressure to recover data from an old server that only gets booted very infrequently. The data on it is urgently required - isn't always??!
..
Server is an HP DL380G5 which is running SCO Unixware 7.11
..
It has 3 partitions in a RAID 5 Configuration: 1 of 10GB (I assume it... (19 Replies)
Discussion started by: BernP
19 Replies
9. Solaris
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)
Discussion started by: krishna001
3 Replies
10. Solaris
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
REBOOT(8) System Manager's Manual REBOOT(8)
NAME
reboot - stopping and restarting the system
SYNOPSIS
/sbin/reboot [ -lqnhdarsfRD ]
/sbin/halt [ -lqndars ]
/sbin/fastboot [ -lqndarsRD ]
DESCRIPTION
2.11BSD is started by placing it in memory at location zero and transferring to its entry point. Since the system is not reentrant, it is
necessary to read it in from disk or tape each time it is to be boot strapped.
Rebooting a running system: When the system is running and a reboot is desired, shutdown(8) is normally used to stop time sharing and put
the system into single user mode. If there are no users then /sbin/reboot can be used without shutting the system down first.
Reboot normally causes the disks to be synced and allows the system to perform other shutdown activities such as resynchronizing hardware
time-of-day clocks. A multi-user reboot (as described below) is then initiated. This causes a system to be booted and an automatic disk
check to be performed. If all this succeeds without incident, the system is then brought up for multi-user operation.
Options to reboot are:
-l Don't try to tell syslogd(8) what's about to happen.
-q Reboot quickly and ungracefully, without shutting down running processes first.
-n Don't sync before rebooting. This can be used if a disk or the processor is on fire.
-h Don't reboot, simply halt the processor.
-d Dump memory onto the dump device, usually part of swap, before rebooting. The dump is done in the same way as after a panic.
-a Have the system booter ask for the name of the system to be booted, rather than immediately booting the default system (/unix).
-r Mount the root file system as read only when the system reboots. This is not supported by the kernel in 2.11BSD.
-s Don't enter multi-user mode after system has rebooted - stay in single user mode.
-f Fast reboot. Omit the automatic file system consistency check when the system reboots and goes multi-user. This is accomplished by
passing a fast reboot flag on to the rebooting kernel. This currently prevents the use of -f flag in conjunction with the -h (halt)
flag.
-D Set the autoconfig(8) debug flag. This is normally not used unless one is debugging the autoconfig program.
-R Tells the kernel to use the compiled in root device. Normally the system uses the device from which it was booted as the
root/swap/pipe/dump device.
Reboot normally places a shutdown record in the login accounting file /usr/adm/wtmp. This is inhibited if the -q or -n options are
present. Note that the -f (fast reboot) and -n (don't sync) options are contradictory; the request for a fast reboot is ignored in this
case.
Halt and fastboot are synonymous with ``reboot -h'' and ``reboot -f'', respectively.
Power fail and crash recovery: Normally, the system will reboot itself at power-up or after crashes if the contents of low memory are
intact. An automatic consistency check of the file systems will be performed, and unless this fails, the system will resume multi-user
operations.
SEE ALSO
autoconfig(8), sync(2), utmp(8), shutdown(8), syslogd(8)
3rd Berkeley Distribution May 24, 1996 REBOOT(8)