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.
Code:
exec(/sbin/init) file not found
press any key to restart
I tried to search for this error but couldn't find any solution. Hope someone can help
I want to get my telnetd to run on startup and was wondering where it was? im used to having it in /etc/init.d/rc.d but it is not the same in hp-ux :(
thanks all (4 Replies)
My Solaris10 cannot boot after I made an error when apending the vfstab to:
dev to mount======/dev/dsk/c0d0p1:1
device to fsck====== <blank>
mount pt=========/Data
FS Type==========pcfs
fsck pass=========-
mount at boot=====yes
mount options===== <blank>
My 'Data' partition is a... (3 Replies)
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... (1 Reply)
Hello.
system fails on reboot this AM.
received message about not possible for kernel to find process that caused crash.
system does memory dump succesfully, then tries to boot again.
looking further at messages during this time, i'm getting 'init died with return value 256'...system panic... (12 Replies)
Good evening all,I'm new to your site, so please bear any infringements or transgressions on my part.I'm new to the whole Solaris boot install over the net scenario, but here's where I'm stuck:I have an M5000 with 2 domains (running unimode). Domain 0 is configured and running Solaris 10. Domain 1... (9 Replies)
Hi Experts,
I am doing PXE boot for my GNU/Linux device and pxelinux.0 loads the kernel as well as initrd images I have mentioned in the config file but it looks like it is not considering the init= option. Instead it starts the default INIT program.
I wanted my customized init program to be... (3 Replies)
Hello all,
Fairly simple question here. I know that in Solaris 10 there is a way to tell a system running solaris 10 to init 0 and then boot disk1 all in the same command line from a SSH window. That way once you hit enter it then performs the init 0 and then does the boot disk1. ... (2 Replies)
I have a command in init that trys to start a daemon and open a log, but a get an error error that the file access permissions do not allow the specified action. My permissions on the log file are:
-rw-r--r-- 1 root system 4434 Mar 22 15:13 dsmerror.log
The logfile is written to... (2 Replies)
I am running the gxemul software under cygwin,
Just when installing the .iso image, I got the error shown in
the picture. Any ideas what's happening?
Thanks
Jack (1 Reply)
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
LEARN ABOUT SUNOS
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)