Sponsored Content
Operating Systems Solaris Solaris can not boot and restart Post 302982554 by mammut3d on Friday 30th of September 2016 12:25:51 AM
Old 09-30-2016
No, it is original disk. For some reasons i decide to restart machine, i execute init 6 command and after restarting, the system shows that lines and restart automatically.
Do you think that executing below command in failsafe is helpful?
Code:
#bootadm update-archive -f -R /a

P.S. The system has 2 hard disk with 160G capacity. I don't know why?!. The unix base systems are very strange to me.

Last edited by mammut3d; 09-30-2016 at 01:30 AM.. Reason: Writing P.S. for more information.
 

9 More Discussions You Might Find Interesting

1. Solaris

shutting down/restarting oracle with the solaris server restart

How can I make sure that all the database instances are shut down and brought up when the server is restarted. Krishan (3 Replies)
Discussion started by: krishan
3 Replies

2. Solaris

solaris boot problem boot error loading interpreter(misc/krtld)

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

3. Solaris

Restart/Shutdown the Solaris from SC>

Hi Experts, I am running solris 9. Sun-Fire 880. How do i shutdowon the whole server using ALOM i.e sc> console. If the server is down or somehow hang How do i Restart from sc> //purple (6 Replies)
Discussion started by: thepurple
6 Replies

4. Solaris

cant boot from solaris CD

Hi all , I am trying to isntallsolaris 10 using a DVD , But when i try to boot from the OB Prompt i am getting this error : Rebooting with command: boot cdrom -install Boot device: /pci@1f,700000/pci@0/pci@1/pci@0/ide@1f/cdrom@0,0:f File and args: -install Can't read disk label. Can't open... (2 Replies)
Discussion started by: ppass
2 Replies

5. Solaris

solaris 10 mysql no longer able to restart

Came in tonight, and some people started getting this error message note: users were getting this error in IE6 and in firefox, pages seemed to process fine in Chrome. :confused: anyway... So I decided to restart the MySQL service, now it will not restart. First tried: root@bender:/>... (2 Replies)
Discussion started by: ippy98
2 Replies

6. Solaris

Doubt, sshd restart kills the session on Solaris 8,9,10

Hi Everyone, I am just curious, if sshd service is restarted on these OS Solaris 8,9,10 remotely will the session expires?? . I knew we can restart sshd in solaris 10 that will no effect any current session please suggest for 8,9 Thanks, (2 Replies)
Discussion started by: bobby320
2 Replies

7. Solaris

Solaris x86 installation using jumpstart does not local boot ( boot from hdd)

I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Discussion started by: hemalsid
9 Replies

8. Solaris

dual boot solaris/solaris zfs file system

Hi, I am running into a some problems creating a dual boot system of 2 solaris instances using ZFS file system and I was wondering if someone can help me out. First some back ground. I have been asked to change the file system of our server from UFS to ZFS. Currently we are using Solaris... (3 Replies)
Discussion started by: estammis
3 Replies

9. Solaris

Solaris stuck during boot after reconfigure boot

Hello, I have a problem with my machine that won't boot properly. The story is that I installed a software called apcupsd, which is a control application for my APC battery UPS. I have used version 3.14.10 earlier, but as part of restoring my previously crashed os harddrive I wanted to... (18 Replies)
Discussion started by: Zorken
18 Replies
bootadm(1M)															       bootadm(1M)

NAME
bootadm - manage bootability of GRUB-enabled operating system SYNOPSIS
/sbin/bootadm update-archive [-vn] [-R altroot] /sbin/bootadm list-archive [-vn] [-R altroot] only /sbin/bootadm set-menu [-R altroot] key=value /sbin/bootadm list-menu [-R altroot] The bootadm command manages the boot archive and GRUB (GRand Unified Bootloader) menu. The update-archive option provides a way for user to update the boot archive as a preventative measure or as part of the recovery procedure. The set-menu subcommand allows you to switch the auto-boot timeout and default boot entry in the GRUB menu. The list-menu subcommand displays the location of the GRUB menu and the current GRUB menu entries. While the typical location of the GRUB menu is /boot/grub/menu.lst, depending on the install method used the active GRUB menu might be located somewhere else. Use the list-menu subcommand to locate the active GRUB menu. For example, if a system was installed using Live Upgrade, the GRUB menu might not be located in the current boot environment. See the section for typical output from the list-menu option. Note that a SPARC system does not have the concept of a boot archive. The bootadm command on a SPARC system is intended for managing disk- less clients. SUBCOMMANDS
The bootadm command has the following subcommands: update-archive Updates current boot archive if required. Applies to both SPARC and platforms. list-archive Lists the files and directories to be included in the boot archive. Applies to both SPARC and platforms. set-menu Maintain the GRUB menu. The current GRUB menu is boot/grub/menu.lst, relative to root. Do not depend on this location, because it is subject to change. Applies to platforms only. list-menu Lists the location of the active GRUB menu, as well as the current GRUB menu entries. This includes the autoboot-timeout, the default entry number, and the title of each entry. Applies to platforms only. The bootadm command has the following options: -v In an update-archive operation, stale files are displayed on stderr. -n In an update-archive operation, archive content is checked but not updated. -R altroot Operation is applied to an alternate root path. Note - The root file system of any non-global zones must not be referenced with the -R option. Doing so might damage the global zone's file system, might compromise the security of the global zone, and might damage the non-global zone's file system. See zones(5). key=value Possible values are: default=entrynum The item number (for example, 0, 1, or 2) in the GRUB menu designating the operating system to boot when the timer expires. timeout=seconds The number of seconds before the operating system designated by the default item number is booted. If the value is -1, auto boot is disabled. Example 1: Updating the Current Boot Archive The following command updates the current boot archive: # bootadm update-archive Example 2: Updating the Boot Archive on an Alternate Root The following command updates the boot archive on an alternate root: # bootadm update-archive -R /a Example 3: Listing Installed OS Instances The following command lists the installed operating system instances in a GRUB menu: # bootadm list-menu default=0 timeout=10(0) Solaris10(1) Solaris10 Failsafe(2) Linux Example 4: Switching Default Boot Entry The following command refers to the menu displayed in the previous example. The user selects Linux (item 2). # bootadm set-menu default=2 Example 5: Listing GRUB Menu Entries and Location of GRUB Menu The following command lists the GRUB menu entries and the location of the GRUB menu: # bootadm list-menu The location for the active GRUB menu is: /stubboot/boot/grub/menu.lst default 0 timeout 10 0 Solaris10 1 Solaris10 failsafe 2 Linux Example 6: Displaying Location of GRUB Menu The following command displays the location of the GRUB menu: # bootadm list-menu The location for the active GRUB menu is: /dev/dsk/c0t1d0s0 (not mounted) The filesystem type of the menu device is <ufs> default 2 timeout 10 0 c0t1d0s3 1 c0t1d0s3 failsafe 2 Solaris10 3 Solaris10 failsafe In this example, the active GRUB menu is located on a device which is not mounted. To access the GRUB menu, mount the device and access the GRUB menu at <mountpoint>/boot/grub/menu.lst. The following exit values are returned: 0 The command completed successfully. 1 The command exited due to an error. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ boot(1M), installgrub(1M), attributes(5) The GRUB home page: http://www.gnu.org/software/grub/ 10 Oct 2005 bootadm(1M)
All times are GMT -4. The time now is 08:55 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy