07-24-2008
Sorry, it didn't work.
-format
-label
y
-q
-format
-q
reboot
During boot, it still give the warning.
Any more idea? Thanks.
10 More Discussions You Might Find Interesting
1. Linux
Hi everyone,
OK, I've made a monumental fsck-up of my linux installation AND I did not backup my data properly (idiot!), so I'm really up the proverbial without a paddle here.
Basically the problem is I re-sized my /home partition (hda13) using Partition Magic 8.0, after doing so my mandrake... (0 Replies)
Discussion started by: alarmcall
0 Replies
2. Solaris
I just was given an Ultra 60 that I'm trying to get started so that I can re-load the system with Solaris 10. I can't seem to get the system to boot past the initial memory check. I've tried to do an Stop-A to get to the eeprom, but can't do that. My next step is to try to send a break from the... (0 Replies)
Discussion started by: zosojohnny
0 Replies
3. Solaris
Hi Fellows,
I am trying to mirror 2 identical disks on a SUN Ultra 10 machines (with new installation of Solaris 8). In the process, I found 2 issues:
1. prtvtoc /dev/rdsk/c0t0d0s0 | fmthard -s - /dev/rdsk/c0t1d0s0
Result: Disk partitions between the 2 disks do not match up.
2. manually... (2 Replies)
Discussion started by: o51974
2 Replies
4. Solaris
Hi,
I have a Sun X4200, when I try to reboot the machine it's not detecting the drive and it shows the following error when I try to rebuilt it. I am not sure whether its a bad HD or something else.
Label says 983040 blocks: Drive says 983039 blocks
WARNING:... (1 Reply)
Discussion started by: gunnervarma
1 Replies
5. Solaris
I have created 1 LUN.
1)LUN 00BB 200GB /dev/rdsk/c1t3d44
/dev/rdsk/c2t28d44
/dev/rdsk/c3t19d44
/dev/rdsk/c4t12d44
2) Already added the new entry into sd.conf and rebooted.
3) Already done these:
powercf –q
power config
4) power display dev=all
I can see the new Symmetrix device.... (1 Reply)
Discussion started by: sirius20d
1 Replies
6. UNIX for Advanced & Expert Users
We have an issue here:
The libc.so.6 file (link) is corrupted and it causes the system unbootable. It even doesn't boot to single user mode. How can we boot the system to fix the library file? Or is there any other solutions for this issue?
Here are some boot messages:... (6 Replies)
Discussion started by: aixlover
6 Replies
7. Filesystems, Disks and Memory
I've seen several posts that are similar to what I'm trying to do but no dice. I have a server (SunFire V215) that went belly up. I've set up a new one. I'm getting a corrupt label: wrong magic number error. Everything I'm seeing says label the drives, but if I do I'm afraid I'll lose the data... (0 Replies)
Discussion started by: tnelson
0 Replies
8. Emergency UNIX and Linux Support
Need help/advice urgently.:wall:
I really shot myself in the foot this time. Here is the scenario
Have a Solaris server Solaris 10 x86 Update 8.
Installed an LSI MegaRaid 9280 raid controller and attached a 16 bay JBOD box to it, created a RAID6 virtual drive with 1 hot spare.
Created a... (2 Replies)
Discussion started by: ccj4467
2 Replies
9. Solaris
I am trying to get an old Ultra 45 to boot and it is stuck in a loop. I cannot get anything to come up on a monitor, so when I hook up a serial connection to the TTYa interface I see the following output:
@(#)OBP 4.21.2 2005/12/22 17:17 Sun Ultra 45 Workstation
Clearing TLBs
Loading... (0 Replies)
Discussion started by: Madrox72
0 Replies
10. Solaris
Hi all,
I've just replaced the eprom battery on my Sun Ultra-30 and having boot issues. For some reason its trying to boot off the network instead of the DISK1. Howe can I change it so the open boot does not default to the boot device: NET
Thanks,
Rob (3 Replies)
Discussion started by: robbo007
3 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)