Sponsored Content
Full Discussion: boot-archive issue
Operating Systems Solaris boot-archive issue Post 302297666 by pupp on Saturday 14th of March 2009 10:55:59 AM
Old 03-14-2009
you need to boot off the failsafe archive. bring system down to obp. then use
Code:
boot -F failsafe

and follow instructions.

fyi - from the times i remember doing this, i had to perform this several times before it became stable. no clue why. however, if the system comes up and looks stable, make sure you reboot to confirm. also, you may need to remove any metadevices first before hand.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

boot up issue

Could somone please tell me what happened when I reboot my computer, it take too long to pass the part it said "starting sendmail" I only changed the server name and when I reboot the server, all of the services are running except when it got to : starting sendmail it take toooo long to... (1 Reply)
Discussion started by: lapnguyen
1 Replies

2. Shell Programming and Scripting

Tar archive issue

Hi, I make a tar archive: tar -czvf /path_to/cucu.tar.gz /path/dir_to_archive/ In the archive the /path/dir_to_archive/ is maintained for every file. I need that the archive to be made without the /path/dir_to_archive/ to contain only the files in /path/dir_to_archive/. Thanks,... (4 Replies)
Discussion started by: potro
4 Replies

3. HP-UX

hp-ux 10.20 boot issue

Hello, have HP Visualize C3600 workstation. Issue is as follows: When I attempt to boot, unit will not boot successfully and will halt at a menu, the same menu as when during a boot one hits any key within 10 seconds to discontinue. When I attempt to boot with Boot primary, both with IPL... (17 Replies)
Discussion started by: davel1000
17 Replies

4. Solaris

Cannot mount boot archive

hi, I' ve found an error while starting up solaris 10, so I booted in safe mode from grub and modified the menu.lst with vi, to obtain a verbose output of the error. It says failed to readsuperblock diskread reading beyound end of ramdisk start = 0x800 size=0x800 ... ... panic: cannot... (9 Replies)
Discussion started by: freeware
9 Replies

5. Solaris

zfs root flash archive issue

I have created a flash archive from a Ldom on T5220 with zfs root solaris 10_u8. But after creation of flar the info shows the content_architectures=sun4c,sun4d,sun4m,sun4u,sun4us,sun4s but not sun4v due to which i 'm unable to install this flash archive on another Ldom on the same host. Is... (0 Replies)
Discussion started by: fugitive
0 Replies

6. Solaris

Boot-archive Problem

I disabled the boot-archive service by using #svcadm disable svc:/system/boot-archive:default then i rebooted my system but i am unable to boot. It throws the following errors CONSOLE LOGIN SERVICE(S) CANNOT RUN then it automatically asked me for the maintenance mode passwd. i logged... (3 Replies)
Discussion started by: dinu
3 Replies

7. UNIX for Advanced & Expert Users

scp/untar in parallel issue tar : Unexpected EOF in archive

Hi Guys, I am facing a strange issue while doing parallel (using & for background) scp/untar operation from my unix box to multiple unix boxes... I am getting tar : unexpected EOF in archive error the code is as follows.,,, for i in 10 do sh -c "scp <command> ; ssh tar -xf <tar> -C... (1 Reply)
Discussion started by: mihirvora16
1 Replies

8. Solaris

Boot archive file sizes are different on cluster units

Hi experts, I would have a question on boot archive files on solaris10 platform running on T5220 cluster servers. When we check the /platform/sun4v directory , and perform boot archive-list , we see that on both units same files exist. And when we mount the boot archive we see that all files... (0 Replies)
Discussion started by: dyavuzy1
0 Replies

9. Solaris

V100 boot issue

In the server room at my new job, there is a V100 with a problem. When power is turned on, the machine goes to the lom prompt. Entering poweron yields an endless supply of this message with no way to break out of it. ********************************************** PSTATE=0000000000000015... (3 Replies)
Discussion started by: chilinski
3 Replies

10. SCO

Issue during boot

Hi, I am using SCO OpenServer 5 During boot I get this message: PANIC: HTFS: Bad directory ino 2 (offset 0) on HTFS dev hd (1/42) Cannot dump 8095 pages to dumpdev hd (1/41): Space for only 0 pages Dump not completed How can I fix this? I have no boot/root floppy. If it is a "disk... (8 Replies)
Discussion started by: nubian_sundance
8 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)
All times are GMT -4. The time now is 07:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy