Sponsored Content
Operating Systems Solaris T5-4 Bootloop with 11.4 Boot Environment Post 303036902 by samthewildone on Tuesday 16th of July 2019 07:05:49 PM
Old 07-16-2019
The problem was figured out.

The original boot environment was not clean itself. When a new boot environment was created,
it came with all the previous issues with the original. We've got a lot of work to do.
 

8 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... (1 Reply)
Discussion started by: DreamWarrior
1 Replies

2. 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... (3 Replies)
Discussion started by: Garball
3 Replies

3. 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... (3 Replies)
Discussion started by: fugitive
3 Replies

4. Solaris

Solaris live upgrade on Active boot environment

Hi, Is it possible to perform an luupgrade on the active boot environment in Solaris? I want to perform this on BEAlpha - the disk that has BEOmega will be unavailable whilst performing the upgrade but I still want to install the patches using luupgrade. Boot Environment Is... (4 Replies)
Discussion started by: Mr_Webster
4 Replies

5. Solaris

Restoring to previous Boot Environment

Hi all, I'm fairly new to Solaris and am just getting to grips with using LU (Live Upgrade) for OS patching purposes. worcester#uname -a SunOS worcester 5.10 Generic_144488-12 sun4v sparc SUNW,SPARC-Enterprise-T5220I have successfully created and patched a new BE (boot environment) using the... (5 Replies)
Discussion started by: polo_mint4
5 Replies

6. 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... (3 Replies)
Discussion started by: os2mac
3 Replies

7. 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... (0 Replies)
Discussion started by: zbest1966
0 Replies

8. Solaris

How to remove pkg from zone in newly created boot environment?

fyi, I already have SR opened with Oracle. We are looking to upgrade from S11.3 to S11.4 with the latest SRU. Create new BE; success Mount new BE; success pkg -R /mnt update the updating of the global went fine until it touched local zone. pkg: update failed (linked image... (2 Replies)
Discussion started by: samthewildone
2 Replies
COLOR.4TH(8)						    BSD System Manager's Manual 					      COLOR.4TH(8)

NAME
color.4th -- FreeBSD color-detection boot module DESCRIPTION
The file that goes by the name of color.4th is a set of commands designed to simplify color logic. The commands of color.4th by themselves are not enough for most uses. Please refer to the examples below for the most common situations, and to loader(8) for additional commands. Before using any of the commands provided in color.4th, it must be included through the command: include color.4th This line is present in /boot/loader.4th file, so it is not needed (and should not be re-issued) in a normal setup. The commands provided by it are: loader_color? Returns FALSE if the loader_color environment variable is set to ``NO'' (case-insensitive) or ``0''. Otherwise returns TRUE (unless booting serial). The environment variables that effect its behavior are: loader_color If set to ``NO'' (case-insensitive) or ``0'', causes loader_color? to return FALSE, indicating to many modules that color should not be used. FILES
/boot/loader The loader(8). /boot/color.4th color.4th itself. /boot/loader.rc loader(8) bootstrapping script. EXAMPLES
Standard i386 /boot/loader.rc: Use color where applicable: loader_color="YES" SEE ALSO
loader.conf(5), loader(8), loader.4th(8) HISTORY
The color.4th set of commands first appeared in FreeBSD 9.0. AUTHORS
The color.4th set of commands was written by Devin Teske <dteske@FreeBSD.org>. BSD
August 6, 2013 BSD
All times are GMT -4. The time now is 06:05 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy