Restoring to previous Boot Environment Post: 302542955

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Adding to boot-up environment

During the boot-up process *nix runs scripts linked into the runlevel directories rc#.d. What I'm wondering is, how do I control the environment that those scripts see? I need to set a couple environment variables, and I can NOT do it from within the scripts because it poses a maintenance nightmare...

2. SCO

Wanting to boot from a previous kernel

I tried to add ppp on a serial line tty1b and I relink the kernel. Now, I would like to boot from the previous kernel because I lost the connexion for the others terminal (serial lines) too. I would appreciate any help.

3. Solaris

Restoring Boot Manager after Windows Install

Hi everyone, so i have a 40Gb disk with Windows XP and Solaris 10 Installed... windows has once again become unoperable for virus and stufff, and i need to reinstall it, but when i do that the MBR will be overwriten right? and i wont be able to access solaris10 anymore, is there a way, like a...

4. UNIX for Dummies Questions & Answers

Messed up my boot environment or root profile

Ok, a couple weeks ago I was fixing a cron report about perl not happy with 'locale' info (LANG and LC not set). As a result, I was experimenting with setting the correct 'locale' in several areas (like /etc/sysconfig/i18n and who knows where). Somehow after a reboot, as soon as the OS starts...

5. Solaris

Update single zone in alternate boot environment.

I 'm having a weired situation my system has 8 zones, running fine on solaris x86_u4. I installed the live upgrade bundle patch and did a live upgrade. The new BE was created but it missed one of the zone and now if i mount the new BE i do not see that zone in the environment so my question is how...

6. Solaris

unable to boot afer restoring root partion manages by veritas

Hi all, After restoring the / FS on a netra 240. It is unable to boot the system. The message displayed is the following: "The file just loaded does not appear to be executable" Bellow, the content of /etc/vfstab before restoring: #more /etc/vfstab...

7. Solaris

Automating old Boot Environment Cleanup Solaris 11

I'm trying to automate the patching process using scripts and cronjobs in Solaris 11. one of the things I'd like to do is cleanup the old boot environments. unfortunately beadm destroy requires a response :~$ pfexec beadm destroy -f solaris-13 Are you sure you want to destroy...

8. UNIX for Beginners Questions & Answers

Lucreate Fails to Create Boot Environment;

My OS solarius 5.10 Generic_147148-2 i86 Error: please review new boots environments using options 1. Solution - show me the commands Partition is full, try to remove some unneeded files, then try to compress some other unneeded files. man command creates a temp file under...

9. Solaris

T5-4 Bootloop with 11.4 Boot Environment

TLDR: Patched a separate boot environment to 11.4. Activated and rebooted the system only to have it boot loop and show 11.3 on the patched boot environment. Bootloop process: The system went down, came up showing 11.3 then spewed bunch of errors and resetted. SEE BELOW FOR THE FINAL MSG...

LEARN ABOUT LINUX

lucurr

lucurr(1M)																lucurr(1M)

NAME

       lucurr - display the name of the active boot environment

SYNOPSIS

       /usr/sbin/lucurr [-l error_log] [-m mount_point] [-o outfile] [-X]

DESCRIPTION

       The  lucurr  command  is  part  of  a  suite  of  commands  that make up the Live Upgrade feature of the Solaris operating environment. See
       live_upgrade(5) for a description of the Live Upgrade feature.

       The lucurr command displays the name of the currently running boot environment (BE). If no BEs are configured on the  system,  lucurr  dis-
       plays  the  message  "No  Boot Environments are defined". Note that lucurr reports only the name of the current BE, not the BE that will be
       active upon the next reboot. Use lustatus(1M) or luactivate(1M) for this information.

       The lucurr command requires root privileges.

OPTIONS

       The lucurr command has the following options:

       -l error_log

	   Error and status messages are sent to error_log, in addition to where they are sent in your current environment.

       -m mount_point

	   Returns the name of the BE that owns mount_point, where mount_point is the mount point of a BE's root file system. This can be a  mount
	   point  of  the current BE or the mount point of a BE other than the current BE. If the latter, the file system of the BE must have been
	   mounted with lumount(1M) or mount(1M) before entering this option.

       -o outfile

	   All command output is sent to outfile, in addition to where it is sent in your current environment.

       -X

	   Enable XML output. Characteristics of XML are defined in DTD, in /usr/share/lib/xml/dtd/lu_cli.dtd.<num>, where <num>  is  the  version
	   number of the DTD file.

EXIT STATUS

       The following exit values are returned:

       0	Successful completion.

       >0	An error occurred.

FILES

       /etc/lutab

	   list of BEs on the system

       /usr/share/lib/xml/dtd/lu_cli.dtd.<num>

	   Live Upgrade DTD (see -X option)

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWluu			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       lu(1M),	luactivate(1M),  lucancel(1M), lucompare(1M), lucreate(1M), ludelete(1M), ludesc(1M), lufslist(1M), lumake(1M), lumount(1M), lure-
       name(1M), lustatus(1M), luupgrade(1M), lutab(4), attributes(5), live_upgrade(5)

SunOS 5.10							    24 Jan 2002 							lucurr(1M)