07-29-2011
Just thought I'd give an update on this issue to say that i've successfully used the boot -L workaround to boot to an old BE.
Oracle have been able to reproduce this behaviour in their lab. They said that this is a known bug addressed in:
Bug 6996301 : s10u9 zfs root PBE/ABE in same pool on-screen luactivate instructions don't work
and
Bug 6923286 : luactivate fails in single user mode during fallback activation
There's no official fix available currently.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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. SCO
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 Replies)
Discussion started by: pacctono
3 Replies
3. Solaris
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... (1 Reply)
Discussion started by: sx3v1l_1n51de
1 Replies
4. UNIX for Dummies Questions & Answers
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
5. Solaris
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
6. Solaris
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... (0 Replies)
Discussion started by: faberarnold
0 Replies
7. Solaris
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
8. UNIX for Beginners Questions & Answers
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
9. Solaris
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... (1 Reply)
Discussion started by: samthewildone
1 Replies
lutab(4) lutab(4)
NAME
lutab - list of boot environments
SYNOPSIS
/etc/lutab
DESCRIPTION
The file /etc/lutab is a list of the boot environments (BEs) configured on a system. There are two entries for each BE. These entries have
the following form:
BE_id:BE_name:completion_flag:0
BE_id:root_slice:root_device:1
The fields in the lutab entries are described as follows:
BE_id A unique, internally generated id for a BE.
BE_name The user-assigned name of a BE.
completion_flag Indicates whether the BE is complete (C) or incomplete (NC). A complete BE is one that is not involved in any copy or
upgrade operation. A BE can be activated or compared only when it is complete.
0 Indicates first of two lines.
BE_id As described above.
root_slice Designation of the root slice.
root_device Device on which the root slice is mounted.
1 Indicates second of two lines.
The lutab file must not be edited by hand. Any user modification to this file will result in the incorrect operation of live upgrade.
SEE ALSO
lu(1M), luactivate(1M), lucreate(1M), lucurr(1M), lufslist(1M), lustatus(1M), luupgrade(1M), attributes(5), live_upgrade(5)
WARNINGS
The lutab file is not a public interface. The format and contents of lutab are subject to change. Use lufslist(1M) and lustatus(1M) to
obtain information about BEs.
SunOS 5.10 8 Jun 2001 lutab(4)