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
NEXTBOOT(8)						    BSD System Manager's Manual 					       NEXTBOOT(8)

NAME
nextboot -- specify an alternate kernel and boot flags for the next reboot SYNOPSIS
nextboot [-e variable=value] [-f] [-k kernel] [-o options] nextboot -D DESCRIPTION
The nextboot utility allows specifying some combination of an alternate kernel, boot flags and kernel environment for the next time the machine is booted. Once the loader(8) loads in the new kernel information, it is deleted so in case the new kernel hangs the machine, once it is rebooted, the machine will automatically revert to its previous configuration. The options are as follows: -D Invoking nextboot with this option removes an existing nextboot configuration. -e variable=value This option adds the provided variable and value to the kernel environment. The value is quoted when written to the nextboot configuration. -f This option disables the sanity checking which checks if the kernel really exists before writing the nextboot configuration. -k kernel This option specifies a kernel directory relative to /boot to load the kernel and any modules from. -o options This option allows the passing of kernel flags for the next boot. FILES
/boot/nextboot.conf The configuration file that the nextboot configuration is written into. EXAMPLES
To boot the GENERIC kernel with the nextboot command: nextboot -k GENERIC To enable into single user mode with the normal kernel: nextboot -o "-s" -k kernel To remove an existing nextboot configuration: nextboot -D SEE ALSO
boot(8), loader(8) HISTORY
The original nextboot manual page first appeared in FreeBSD 2.2. It used a very different interface to achieve similar results. The current incarnation of nextboot appeared in FreeBSD 5.0. AUTHORS
This manual page was written by Gordon Tetlow <gordon@FreeBSD.org>. BUGS
The nextboot code is implemented in the loader(8). It is not the most thoroughly tested code. It is also my first attempt to write in Forth. Finally, it does some evil things like writing to the file system before it has been checked. If it scrambles your file system, do not blame me. BSD
January 31, 2012 BSD
All times are GMT -4. The time now is 01:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy