10-08-2009
Quote:
Originally Posted by
rhfrommn
I'm not sure what caused this error, but the first thing to do to fix it is to look at /var/sadm/system/data/packages_to_be_added and see exactly which package(s) are missing. Then check the BE you copied to see if they are there. If not you have your answer, add them to the BE and do your copy again. If they are there then it's a matter of figuring out why they didn't copy to the new BE correctly.
Hi rhfrommn,
I did check the " /var/sadm/system/data/packages_to_be_added " file but it was a huge list - about 700 packages. In the original BE they are not there. I wonder why luactivate demands those packages.
Now let me tell you what I did next,
Quote:
ludelete Solaris10_lu
lucreate -c c0t0d0 -n Solaris10_lu -m /:/dev/dsk/c0t2d0s0:ufs -m -:/dev/dsk/c0t2d0s1:swap -m /export/home:/dev/dsk/c0t2dufs7
Mount solaris cd /mnt/cdrom
luupgrade -u -n Solaris10_lu -s /mnt/cdrom/
last command got executed successfully,
this command now worked and it did activate Solaris10_lu BE. However it did show an error for only 1 package. I did not careto check which package because new BE is active.
Quote:
init 6 and there you go my new BE came up fine..
Now funny thing is when I wanted to go back to original BE- c0t0d0, I ran
luactivate c0t0d0 and I still see 700 package list and activation failed
then I went to ok prompt and did
Quote:
ok setenv boot-device /pci@1f,0/ide@d/disk@0,0:a
boot
it brought up original BE - c0t0d0, so this means that 700 packages which luactivate complains about is a bug and this 700 package requirement should not be mandatory if BE can boot anyways if you do setenv, so I am sure if I had setenv for Solaris10_lu BE then it would have booted just fine..
Last edited by upengan78; 10-08-2009 at 03:18 PM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hey guys, need some help. Running AIX Version 5.2 and one of our cron jobs is writing errors to a log file. Any ideas on the following error message.
Error: Internal system error: Unable to initialize standard output file
I'm guessing more info might be needed, so let me know.
Thanks (2 Replies)
Discussion started by: firkus
2 Replies
2. UNIX for Dummies Questions & Answers
hi there
i write one awk script file in shell programing
the code is related to dd/mm/yy to month, day year format
but i get an error
please can anybody help me out in this problem ??????
i give my code here including error
awk `
# date-month -- convert mm/dd/yy to month day,... (2 Replies)
Discussion started by: Herry
2 Replies
3. AIX
--------------------------------------------------------------------------------
Hello, help me please.
I am trying to create a mksysb bakup using nim. I am geting this error, how to correct it ? :
Command : failed stdout: yes stderr: no... (9 Replies)
Discussion started by: astjen
9 Replies
4. Solaris
Earlier live upgrade from solaris 8 to solaris 10 5/08 was not permitted . Later by document 250526 dated Feb 2009 , it permitted and fllowing s8p7zip.tar and following solution 206844 .
While installing SUNWluu,SUNWlur,SUNWlucfg , I had a partial failure . But pkginfo shows the information... (5 Replies)
Discussion started by: Hitesh Shah
5 Replies
5. Solaris
Hi,
I currently have one BE and would like to create an ABE.
# lustatus
BE_name Complete Active ActiveOnReboot CopyStatus
------------------------------------------------------------------------
coolthreads yes yes yes - But... (3 Replies)
Discussion started by: pgarousi
3 Replies
6. UNIX for Dummies Questions & Answers
im kinda new to shell scripting so i need some help
i try to run this script and get the error code
> 5 ")syntax error: operand expected (error token is "
the code for the script is
#!/bin/sh
#
# script to see if the given value is correct
#
# Define errors
ER_AF=86 # Var is... (4 Replies)
Discussion started by: metal005
4 Replies
7. Solaris
Got server that I want to have an 'image' of disk to keep in case of failure. What I want to be able to do is, in the event of disk failure, remove system disk replace with cloned disk (same slot) and reboot.
Trouble is I cant take this server down to single user.
Is dd still a viable... (6 Replies)
Discussion started by: psychocandy
6 Replies
8. Solaris
I have two servers with a fresh install of Solaris 11, and having problems when doing rpcinfo between them. There is no firewall involved, so everything should theoretically be getting through. Does anyone have any ideas? I did a lot of Google searches, and haven't found a working solution yet.
... (2 Replies)
Discussion started by: christr
2 Replies
9. 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
10. UNIX for Beginners Questions & Answers
I am writing a shell script with 2 run time arguments. During the execution if i got any error, then it needs to redirected to a error file and in console. Also both error and output to be redirected to a log file. But i am facing the below error.
#! /bin/sh
errExit ()
{
errMsg=`cat... (1 Reply)
Discussion started by: sarathy_a35
1 Replies
LEARN ABOUT SUNOS
lufslist
lufslist(1M) lufslist(1M)
NAME
lufslist - list configuration of a boot environment
SYNOPSIS
/usr/sbin/lufslist [-l error_log] [-o outfile] BE_name [-X]
DESCRIPTION
The lufslist 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 lufslist command lists the configuration of a boot environment (BE). The output contains the disk slice (file system), file system
type, and file system size for each BE mount point.
The following is an example of lufslist output.
# lufslist BE_name
Filesystem fstype size(Mb) Mounted on
------------------------------------------------------------------
/dev/dsk/c0t0d0s1 swap 512.11 -
/dev/dsk/c0t4d0s3 ufs 3738.29 /
/dev/dsk/c0t4d0s4 ufs 510.24 /opt
File system type can be ufs, swap, or vxfs, for a Veritas file system. Under the Filesystem heading can be a disk slice or a logical
device, such as a disk metadevice used by volume management software.
The lufslist command requires root privileges.
OPTIONS
The lufslist 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.
-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.
OPERANDS
BE_name
Name of the BE for which file systems are to be reported. You cannot specify a BE that is involved in another Live Upgrade operation.
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), lucurr(1M), ludelete(1M), ludesc(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 lufslist(1M)