12-22-2005
V480 w/ Solaris 9 boot problem
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 get into the ok prompt. Once we got into ok prompt, we did a test-all to check if all devices are okay.
Next step is to try to boot to single user mode from ok prompt:
boot -s
or
boot cdrom -s (if we need to)
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
I had this working before. I have a 120GB disk with Solaris on the first primary partition, Fedore Core 3 on the second, Slackware on the third, And FreeBSD 5.3 on the 4th. Booting was handled by grub, and everything was working fine.
I decided to wipe everything out and start from scratch... (6 Replies)
Discussion started by: lyonsd
6 Replies
4. 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
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,
Can any kind soul please answer this? I want to boot a SunFire v490 with a dvd image we use to boot v480's. Is this possible? Are there caveats to doing this?
Thanks muchly,
mgb (1 Reply)
Discussion started by: mgb
1 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
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)