Johnny,
I repeated your steps in a native non-global zone and did not see any
problem. Not after finishing installing the packages or after rebooting
the non-global zone.
Those steps alone should not have rendered your system unusable.
Antonello
On 01/24/13 14:33, Johnny Liu wrote:
What I did was
1. download JDK-7 to the system.
2. Untar it
3. pkgadd -d .
4. select all Y no matter what.
5. pkgadd done.
6. console has FMA error (manifest-import) suddently.
7. then I run #svc -xv
8. Then I run #bootadm update-archive
root@x4470a:/opt# bootadm update-archive
sh: /boot/solaris/bin/extract_boot_filelist: not found
root@x4470a:/opt#
-----Original Message-----
From: Mark J. Nelson [mailto:mark.j.nel...@oracle.com]
Sent: Thursday, January 24, 2013 2:23 PM
To: Johnny Liu
Cc: pkg-discuss@opensolaris.org; smf-disc...@opensolaris.org
Subject: Re: [pkg-discuss] [smf-discuss] Oracle smf bootadm gurus please help me
On 01/24/13 12:42 PM, Johnny Liu wrote:
Thanks Casper.
Yes, I tried and Ican import zpool from the broken be. I still need to manually
rebuild my luns etc from these zfs vols.
Apparently some of the old pkg scripts did something bad on the system.
Surprisingly the smf seems to be quite fragile in this respect.
I hate to switch to old be rather than to recover the broken one if I can.
Anybody inside Oracle want to reproduce this issue?
-Johnny
I don't think you've provided any useful information to indict SMF.
Both bootadm and manifest-import failed to find executables that are part of
(or dependencies of) core-os, and pkg failed to find image metadata that should
always be present. Collectively, these problems indicate something much more
fundamentally wrong with your system.
As Shawn suggested separately, pkgadd is almost certainly not the culprit here.
I suspect there are other commands, not mentioned in your notes, that also
affected the root filesystem of the broken BE.
Nonetheless, if you can send a pointer to the allegedly problematic SVr4
package, I can certainly pkgadd it to a recent system and confirm or deny that
portion of my assertions.
--Mark
-----Original Message-----
From: casper....@oracle.com [mailto:casper....@oracle.com]
Sent: Thursday, January 24, 2013 11:27 AM
To: Johnny Liu
Cc: Shawn Walker; pkg-discuss@opensolaris.org;
smf-disc...@opensolaris.org
Subject: Re: [smf-discuss] Oracle smf bootadm gurus please help me
I can boot the system to the older BE without problem, but all my old
configurations (like zfs pools, vols etc) are in the troubled BE.
Is there any ways to recover my old configurations?
If they are all zfs related configuration, then all that configuration is part
of the zpools themselves.
If you created new pools in the broklen be, then you may just be able to import
them. They are not known to the older be.
How come pkgadd -d . have my system image corrupted? I never saw this kind of
problems with IPS pkg cmd which I normally use.
I'm confused about this too. I would be interesting what caused this and
certainly a log of the error message would be useful.
Older pkg tools have install scripts that can do everything, including removing
large parts of the system.
Note that the support repository has jre 7 build 11 (the most current
jre, I think). https://pkg.oracle.com/solaris/support
Casper
________________________________
This message and any attached documents contain information from QLogic
Corporation or its wholly-owned subsidiaries that may be confidential. If you
are not the intended recipient, you may not read, copy, distribute, or use this
information. If you have received this transmission in error, please notify the
sender immediately by reply e-mail and then delete this message.
_______________________________________________
pkg-discuss mailing list
pkg-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
________________________________
This message and any attached documents contain information from QLogic
Corporation or its wholly-owned subsidiaries that may be confidential. If you
are not the intended recipient, you may not read, copy, distribute, or use this
information. If you have received this transmission in error, please notify the
sender immediately by reply e-mail and then delete this message.
_______________________________________________
smf-discuss mailing list
smf-disc...@opensolaris.org
_______________________________________________
pkg-discuss mailing list
pkg-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
