Micro Channel Boot diskette Solaris 2.6

Whe can I get this - "Solaris 2.6 (Intel Platform Edition) Device Configuration Assistant Microchannel verion (MCA)"
Thanks,
Richard

The link wasn't active when I went to it, but here's info from their 2.6 Release Notes:
System With a Micro Channel Architecture
The Solaris 2.6 (Intel Platform Edition) distribution CD is accompanied by a boot diskette supporting most systems, including those with ISA, EISA, VLB, and PCI buses. If you have a system with a Micro Channel Architecture (MCA), you may download a boot diskette from Sun's Solaris 2.6 Web site:
� http://access1.sun.com/solaris/distrib2.6
Full instructions for downloading and creating the MCA diskette are on the Web site. You may also obtain the diskette through your Sun Software Support Provider.
You must make certain that the boot diskette is not write-protected because configuration information is saved to the diskette during the initial boot.

Similar Messages

I cant make a boot diskette with lan driver

hello
i am trying to make a boot diskette with lan driver for the 865 chipset and for the pt880 m/b
but i cant find the onboard lan driver for dos anywhere
i want the computer to connect to another and take a ghost image from it
i need the lan driver for dos
please help

This one works perfectly with my onboard Intel Gigabit LAN. I use it all the time to make back-up images across my network.

Help, unable to boot clean Solaris 10 install

I use Solaris at work, but have never done any sysadmin.
I have installed Solaris 10 on a new Intel Core2 Duo machine at home, but when I select Solaris 10 (not failsafe) from GRUB2, my machine reboots right after the "Use is subject to license terms", and goes back to GRUB2.
I can boot to the failsafe prompt, but I don't know how to troubleshoot from there.
What I've been able to find online suggests that I turn off ACPI (tried with no luck) and disable USB legacy mode in bios (again, tried with no luck). I'm using an IDE DVD drive to install, and a SATA drive for the OS, so everything is installed on c1d0, not c0d0.
When I run failsafe, it finds Solaris 10 ... X86 on c1d0s0 and I can attach as read/write, but I'm not sure what to do from there to find out why GRUB can't load the OS.
I've tried the Solaris 0606 Test Check CD, which says there are drivers for my complete system except for the audio (no driver) and the network (third party, I haven't bothered to get yet).
Please help, I'm totally stuck!
Thanks in advance,
Brett

enemix-
Sorry, I meant to say GRUB stage 2, not GRUB 2. I'm using the GRUB that came with solaris 0606. GRUB works fine.
mAbrante -
Tried the halt_on_panic=1, had no effect. I'm really not sure what is causing the problem. I've found that if I boot 32 bit mode by editing the GRUB command to append kernel/unix I can boot into solaris. But I'd sure like to be able to boot into 64 bit mode.
Any more thoughts anyone?
Brett

Custom boot diskette

I have a large number of identical Intel systems for which I want to create a custom boot diskette that launches a jumpstart install across the network. I've been searing for days now on how this might be possible, and although I've found a few messages from people who say they're doing it or who mention the possibility, I have not found any actual documentation on the subject.
Right now I'm going through the painful process of booting from CD and hitting F2 a lot until I get to the point of launching the jumpstart. This does not make me happy ;)
Does anybody know of some hidden documentation that the obvious keyword searches have missed?
Lusty

Do you mean the diskette with NC ? It is a few years ago, but when I
remember well, this message would appear when you reinstall NC. You are
ask for diskette with NC. When you have not this diskette, you must
select four location during installation - two are in answer from lain,
third is usualy c:\novell\client32 (for asked files *.nlm) and fourth
is c:\novell\client32\msg\english for asked files *.msg.
I suggest you run any file manager together with instalation and fill
path to asked files, which you found in file manager.
Jindrich Kovar
Iain McLaren napsal(a):
> Errrm....what's the exact message you're getting?
>
> You will need the Windows 98 install CD for some of the network components
> (unless they're already installed AND you know where they are (C:\Windows or
> C:\Windows\System usually))
>
> Iain
>
> <[email protected]> wrote in message
> news:9VAne.1179$[email protected]..
>
>>When I try to install NC 3.4 on win98, a boot diskette (for NC )is
>>required. Can sb tell me where I can get that?
>>
>>So long
>
>
>

Dual boot with Solaris 8.0 and Windows 98

I am interested in Setting up my pc with with a Dual boot of Solaris 8 and Windows 98. I have a 60 GB hard drive that I am going to make two 30 GB primary Partitions on this hard dive. One with Windows 98 and one with Solaris 8 Intel Platform version. The question that I have, Is this particular Setup doable? And if so can you tell me what order they have to be installed and what partition software I should use for this procedure. Also if i missing procedure please be very detailed in explaining this to me. I read the message board was confused.
If need be please email me at [email protected]

Hey, goto http://math.uwb.edu.pl/~mariusz/dualboot/ and that will answer all your dual boot questions ?
i2l2

Dual booting between Solaris 8 and 10

Hi,
We mostly use Solaris 8 for testing which means I can't uninstall it. How would I be able to dual boot both Solaris 8 and 10 on a SUN SPARC machine? Is there a boot loader available like grub?
Please help.
Thanks alot!
Till later,
Joseph.

SPARC doesn't need a split boot loader like BIOS/x86. The OBP can directly load from any slice. So 'boot disk:a' would boot from slice 0 and 'boot disk:g' would boot from slice 6.
Darren

Problem building Norton Ghost Boot diskettes for K8N Neo4-F motherboard

We recently purchased 25 sets of the following components to build computers for a classroom.
MSI K8N Neo4-F (bios Award ver1.A0)
AMD Athlon 3200+ 939 pin
Kingston DDRRAM 400 512 mg
ATI Saphire
Enlight 300 Watt +3V/25A, +5V/25A and +12V/15A
Western Digital 80 gig 7200 rpm IDE drive
Sony DVD/CD_RW combo drive
Windows XP Pro sp2
The computers work fine, however we have been unsuccessfull in building a Norton Ghost boot diskette for these systems. The motherboard has an onboard Marvell gigbit LAN chip but neither the BIOS or WinXP or the install CD recognize this chip. All three think the motherboard LAN is an Nvidia. The NVIDA drivers work fine in Win XP but when we attempt to build the boot diskette if we use the NDIS drivers supplided on the install CD for the Marvell LAN the boot diskettte can't find the Marvell controller chip. If we use the NVIDIA NDIS drivers the boot diskette finds the controller but gives us the following error "media test failed check cable". The cable is fine because we can go ahead and boot into Win XP and everything works fine.
I know that the Marvell gigibit LAN has a virtual cable tester built in but I could not find any discussion of this chip on either the MSI, Marvell or NVIDIA sites. We added a 3COM PCI LAN card to one of the motherboards and the boot diskette will work fine wit hthis combination. I would like to find a cleaner solution if possible.
Regards,
jdraper

What you need is a compatible NDIS driver. I am not 100% sure about the hardware. I know their site says a Marvell 88E1111 PHY, but you still use nVIDIA drivers. Here is a link to download basic NDIS drivers:
http://nvidia.custhelp.com/cgi-bin/nvidia.cfg/php/enduser/fattach_get.php?p_sid=PaNaTd1i&p_tbl=9&p_id=25&p_created=1141061119&p_olh=0
These drivers will also assist someone trying to use WinPE as well.

Difficulty with SAN boot of solaris 10 (on V245) from HP EVA 4000 -

Hi
This is my first post. I'm trying to get my head around what's preventing me booting a V245 solaris 10 from a LUN presented from an HP EVA 4000.
The machine boots up ok from a local disk. So, i've done the LUN masking (presentation) on the EVA and the Brocade zoning - solaris can see the disk.
I've formated it close to the current internal root disk, and had used ufsdump/ufsrestore and installboot to copy the contents of / onto the new LUN , which i had mounted as /mnt.
My problem is i just can't seem to get at the new disk at the ok prompt - i'm never quite sure that i'm booting from the correct disk.
I believe all the compatibility with o/s qlc card drivers and the EVA are in order.
The qlc HBA is as follows:
Sun SG-XPCI2FC-QF2/x6768A 1077 2312 1077 10A and have suitable patch 119139-33
Here's some output:
root@bwdnbtsl02# uname -a
SunOS bwdnbtsl02 5.10 Generic_137111-01 sun4u sparc SUNW,Sun-Fire-V245
root@bwdnbtsl02#
root@bwdnbtsl02# luxadm probe
No Network Array enclosures found in /dev/es
Found Fibre Channel device(s):
Node WWN:50001fe15009df00 Device Type:Disk device
Logical Path:/dev/rdsk/c4t600508B4001066A60000C00002B50000d0s2
root@bwdnbtsl02#
Now down at ok prompt, probe-scsi-all can see the EVA (HSV) LUNS
(Here's a sample of the output)
ok probe-scsi-all
/pci@1f,700000/pci@0/SUNW,qlc@2,1
************************* Fabric Attached Devices ************************
Adapter portId - 640100
Device PortId 640000 DeviceId 1 WWPN 210000e08b8a3e4f
Device PortId dc0000 DeviceId 2 WWPN 50001fe15009df09
Lun 0 HP HSV200 6220
Lun 1 DISK HP HSV200 6220
Device PortId d20000 DeviceId 3 WWPN 50001fe150092f19
Lun 0 HP HSV200 6220
/pci@1f,700000/pci@0/SUNW,qlc@2
************************* Fabric Attached Devices ************************
Adapter portId - 630100
Device PortId 630000 DeviceId 1 WWPN 210100e08baa3e4f
Device PortId 780000 DeviceId 2 WWPN 50001fe15009df08
Lun 0 HP HSV200 6220
Lun 1 DISK HP HSV200 6220
Device PortId 6e0000 DeviceId 3 WWPN 50001fe150092f18
Lun 0 HP HSV200 6220
So, i attempt to boot with the following:
ok boot /pci@1f,700000/pci@0/SUNW,qlc@2/fp@0,0/disk@w50001fe15009df08,0:a
Boot device: /pci@1f,700000/pci@0/SUNW,qlc@2/fp@0,0/disk@w50001fe15009df08,0:a File and args:
Can't read disk label.
Can't open disk label package
Can't open boot device
{1} ok
If anyone can put me straight here i'd be most grateful.
thanks john

hi,guys:
i am interesting in your question. i have never try it like your experience.
maybe the cause is drive . either the OS is running . the drive can load. or relation with the style of server .
i think you can try it like the following again.
when you install OS , you chocie EVA disk .
remeber . if the test is complete. you must tell me .
the following is my contact: [email protected]
best regards

Intel boot cd Solaris 8

If you have problems creating the bootable cds from the downloadable Solaris 8 free files, you will see in the forum, the image provided for Solaris 8 is already an iso image. You need only burn the file as an image (not as a bootable cd). Have fun.

All of these messages are all quite normal solaris kernel
status messages (because you've booted with verbose "-v"
kernel messages).
Hmm, it has detected your IDE harddisc (SAMSUNG, 6.5GB)
as the slave device on the primary IDE channel (there were
probably more messages before that SAMSUNG hard disc
where it recognized the master device on the primary IDE
channel; there is a device connected as master on the
primary ide channel, right?).
And it has detected your ATAPI CDROM (COMPAQ SCR-3232)
on the secondary IDE channel, as the master device.
Is there a slave device present on the secondary IDE
channel? (probably not, otherwise it would appear
before the "PCI-device: ide@1, ata1" line).
Hmm, the next step is probably that the kernel scans for
SCSI controllers. Do you have any SCSI controllers in that
system? (It might hang probing for some SCSI controller)
Assuming there are no SCSI controllers, the next step
of the kernel would probably to look for disk drives on each
of the disk controllers. (So, it might hang talking to your
IDE hard disc drives)
Is the HDD LED active when the system is frozen?
Perhaps you get some real error messages when you wait a
minute or two?
If you temporarily remove the power connector from both of
the IDE hard discs on the primary IDE channel (so that the
only IDE device is the CDROM), and you boot again with
"b kadb -v", is it still hanging after:
model COMPAQ SCR-3232, stat 50, err 0
cfg 0x85c0, cyl 0, hd 0, sec/trk 0
mul1 0x0, mult2 0x0, dwcap 0x0, cap 0xf00
piomode 0x200, dmamode 0x200, advpiomode 0x3
minpio 120, minpioflow 120
valid 0x2, dwdma 0x407, majver 0x0
PCI-device: ide@1, ata1
ata1 is /pci@0, 0/pci-ide@0,1/ide@1

Slow boot of solaris 11 machine

hi all,
Thanks in advance.
I have Solaris 11 express on Sunfire V250 machine. It has SAN connectivity through fibre channel. I want to configure SAN devices on my own with the help of command devfsadm.
For this I created a .so library and put that library at /usr/lib/devfsadm/linkmod/ directory. In the library I defined a variable for the structure devfsadm_create_t and a function so that it will reconfigure the devices as per my requirement (names of the logical links etc.,). After putting the library I rebooted the Solaris machine with -r option(reconfiguration reboot).
Then at boot time during execution of above said library by devfsadmd(in daemon mode only), /dev/ directory is getting busy so that it is not able to read its contents and hence the machine is taking much time to boot around 45 minutes. However, that library is working fine with Solaris 10 on the same machine.
Please help me out with possible root cause and solution of the problem.
thanks and regards,
kumar

Hi Kumar,
Here's a few pointers that should help you.
1) There's a dedicated area of the Forums for Driver Development. See Driver Development This would be a better place the ask for help.
2) The devfs sub-system underwent several changes in Solaris 11, some of which were back-ported to the S10u10 Kernel. So if you're using private interfaces to devfs that'll be why your new driver doesn't work.
3) Support for sun4u (which your V215 is), has been removed from Solaris 11. The only sun4u systems supported in Solaris 11 are the M-Series systems. All other sun4u systems will be unsupported and therefore not boot. So I'd recommend you save yourself the time and effort developing for an OS you can't run.
4) It's helpful to the community if you provide the code you're using. That way we can review it and understand what you're trying to do and suggest possible alternatives.
5) Please provide the exact message/error you get whilst booting. (boot -m verbose)
6) As already suggested, if you want to debug this during boot, then use DTrace's Anonymous Tracing feature. However it would be better to debug this in multi-user mode using modeload and modunload.
Here's some resources that should help you debug your library:
http://dsc.sun.com/solaris/articles/dtrace_for_dev.html
http://wikis.sun.com/display/DTrace/Anonymous+Tracing
http://developers.sun.com/solaris/driverdev/reference/docs/index.html
Regards,
Steve

Can xhost be added to boot in Solaris

Xhost + is needed for the reports server to function. Up to now we have been manually running this command since our SA says it cannot be run automatically upon boot. This manual approach has caused problems when the server reboots at odd times and the root user is not available to run the xhost, leading to the reports server not working properly.
Is it possible to run the xhost + as part of the boot process? The environment is Solaris 8. -quinn

Hi, I suggest reading this document, it's easy:
http://qwuh.no-ip.com/oracle/index.html
It's contains all you need for this!
Greetings from Palma!

Dual OS system booting issue - Solaris with Windows XP Pro

Hi,
I have installed Windows XP Professional with SP2 on my laptop Dell Inspiron 6400 (Intel Core 2 Duo). I created partition as below,
C: 25GB (Primary : Active) Installed XP
D: 15GB (Primary) - Tried to install Solaris here
F: 10GB (Primary)
G: 20 GB (Logical)
H: 20 GB (Logical)
1. I tried to install Solaris 10, booted up system from DVD and selected Solaris. I got a message related to "License..." and it stopped right there, nothing showed up on screen after the message. I forced it to shutdown.
2. Next, I tried with Solaris Express Developer edition DVD. I was able to proceed until "Install" option. After clicking "Install" button, it reported some account name(no account name found) setting problem and quitted from installation. It asked to remove the DVD manually. But I was not able to eject it, got stuck. I switched off it and removed DVD.
When I bootup the system next time from HDD or CD or USB bootable backup, it showed blank screen and blinking cursor. I am not able to boot system with Win XP or USB Win Xp bootable. I am able to enter BIOS setup.
Please let me know how to boot up Win Xp and install Solaris with it.

with my little experience i find solaris 10 isn't able to install on sata hdd but with solaris express edition 5.11 i was able to install it on my lap top toshiba tecra and now i can boot with xp sp2 and solaris i hope this answer your question .

Problem booting a Solaris 10 x86 after Jumpstart Installation

Hi,
I have a strange problem. I have a working x86 machine with Solaris 10 installed. I have made a flash image of it's hard disk, and I have store thar flar on another machine. I have another Solaris 10 with Jumpstart.
I boot other x86 machine through PXE. The Jumpstart machine gives it a valid IP, and the process of sending the flash image begins. The process finish, and the client machine reboots. And here is the strange problem:
When starting, the Grub men� appears, and shows the two options configured: first, start Solaris in normal mode, and second, failsafe.
If I choose normal start, the screen goes black and the machine restart as if you rebooted it. I can only start in failsafe mode.
Here are the config files in Jumpstart for that machine:
Profile:
install_type flash_install
archive_location nfs 10.95.8.7:/export/backup/platform/alba-ucm/ALBA-UCM-HostID_2b72c461_4x80GbMirror-Prepared_09042008.flar
partitioning explicit
filesys c0t0d0s0 1:2650 /
filesys c0t0d0s1 2651:1600 /var
filesys c0t0d0s3 4251:400 swap
filesys c0t0d0s4 4651:1000 /opt/app
filesys c0t0d0s5 5651:3143 /repositoryCC
filesys c0t0d0s6 8794:100 /tmp
filesys c0t0d0s7 8894:26
filesys c0t2d0s0 1:8093 /datos
filesys c0t2d0s1 8094:800 /DBoracle
filesys c0t2d0s7 8894:26
After Script:
touch /a/etc/notrouter
touch /a/noautoshutdown
sync
echo "Changing and syncing bootenv.rc"
# clear the boot-args property
echo "setprop boot-args ''" >> /a/boot/solaris/bootenv.rc
# set the bootpath property to boot from the hard disk
STRING=`df | grep '^/a '� | sed 's/).*//' | sed 's/^.* (//'`
STRING=`ls -l ${STRING}`
MYROOT=`echo $STRING | sed 's/.*..\/..\/devices//'`
echo "setprop bootpath ${MYROOT}" >> /a/boot/solaris/bootenv.rc
# disable kdmconfig from running after the first reboot
sysidconfig -b /a -r /usr/openwin/bin/kdmconfig
sync
And here is the menu.lst for Grub:
title Solaris 10
root (hd0,0,a)
kernel /platform/i86pc/multiboot
module /platform/i86pc/boot_archive
title Solaris Failsafe
kernel /boot/multiboot kernel/unix -s
module /boot/x86.miniroot-safe
Please, any idea about what may be hapening?

Thanks for your answers.
Yes, both machines have the same hardware exactly. Finally, I could find where the problem was.
The file bootenv.rc, for some reason that I don't know, was corrupted: In it there was a correct line with bootpath variable correctly defined, but, at the end of the file, there was another line setting the bootpath variable to a long and incoherent string of chars. Booting in failsafe, mounting the system in /a, and removing that stupid line from the bootenv.rc, solved the problem.

Error messages during booting of Solaris 8 zone

I have installed a Solaris 8 zone from a flash archive of a Solaris 8 server that is currently in production. I get no errors during the installation of the zone and when I boot the zone I get the following messages on the zone console:
SunOS Release 5.8 Version Generic_Virtual 64-bit
Copyright 1983-2000 Sun Microsystems, Inc. All rights reserved
Hostname: madison1xl
The system is coming up. Please wait.
NIS domainname is eam.rjf.com
operation failed, Not owner
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
operation failed, Not owner
operation failed, Not owner
operation failed, Not owner
operation failed, Not owner
operation failed, Not owner
operation failed, Not owner
operation failed, Not owner
operation failed, Not owner
operation failed, Not owner
operation failed, Not owner
Sun BluePrints network security settings applied.
syslog service starting.
I am not sure what is causing these errors. The zone appears to be running properly, but I am concerned that something is not starting during the boot process. /var/adm/messages file does not show any errors. Thanks for any help you can give me.

Thanks. That helped alot. I found out that all the messages came from a start up script named nddconfig. Since the ngz cannot change anything about devices this was causing a lot of errors. I stopped the script from starting and now do not receive any errors.

Created zone with defaults won't boot completely (Solaris 10, Update 1)

If I create a zone with defaults, i.e. allowing the zone to inherit the typical package dirs, the resulting zone does not boot completely. When I attach to the zone via zlogin, the zone looks to be in an administrative state. It never boots to a point where one would typically enter in the initial configuration info, e.g. timezone and root password.
However if I create the zone after first removing the inherited dirs, the zone boots to a state where it subsequently can be confiured and fully booted.
Looks as if the SMF facilities are not fully initialized when the zone is configured to inherit its packages. This could be a red herring as I'm a newbie who's moved over from Linux and starting to understand SMF specifically and Solaris in general.
I did not have this problem with Solaris 10. I've just installed Solaris 10 Update 1; the problem seems specific to that installation. I reinstalled and the problem persists.

I snipped the output because there were some errors, which on retrospect seems to have been a silly decision. I repeated the process and captured the missing output:
# zoneadm -z foo install
Preparing to install zone <foo>.
Creating list of files to copy from the global zone.
Copying <5913> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <942> packages on the zone.
Initialized <942> packages on zone.
Zone <foo> is initialized.
Installation of <1> packages was skipped.
Installation of these packages generated warnings: <SUNWxwfnt
SUNWxwplt SUNWxwcft SUNWjxmft SUNWxwpls SUNWpmowu
SUNWxilrl SUNWolrte SUNWi13rf SUNWi15rf SUNWi2rf SUNWi5rf
SUNWi7rf SUNWi9rf SUNWtxfnt SUNWdoc SUNWi1of SUNWi4rf
SUNWi8rf SUNW1251f SUNWarrf SUNWxwoft SUNWxwxst
SUNWkoi8f SUNWasu SUNWxrpcrt SUNWasac SUNWasdb
SUNWasut>
The file </zone/foo/root/var/sadm/system/logs/install_log> contains a log of the zone installation.The packages are related to App development and X11. I don't see any that might be related to SMF.
The logfile is too large to post at over 37K lines. However there seemed to be a pattern to the package failures. Hopefully these greps highlight the important messages:
# grep "partially failed" /zone/foo/root/var/sadm/system/logs/install_log
Installation of <SUNWxwfnt> on zone <foo> partially failed.
Installation of <SUNWxwplt> on zone <foo> partially failed.
Installation of <SUNWxwcft> on zone <foo> partially failed.
Installation of <SUNWjxmft> on zone <foo> partially failed.
Installation of <SUNWxwpls> on zone <foo> partially failed.
Installation of <SUNWpmowu> on zone <foo> partially failed.
Installation of <SUNWxilrl> on zone <foo> partially failed.
Installation of <SUNWolrte> on zone <foo> partially failed.
Installation of <SUNWi13rf> on zone <foo> partially failed.
Installation of <SUNWi15rf> on zone <foo> partially failed.
Installation of <SUNWi2rf> on zone <foo> partially failed.
Installation of <SUNWi5rf> on zone <foo> partially failed.
Installation of <SUNWi7rf> on zone <foo> partially failed.
Installation of <SUNWi9rf> on zone <foo> partially failed.
Installation of <SUNWtxfnt> on zone <foo> partially failed.
Installation of <SUNWdoc> on zone <foo> partially failed.
Installation of <SUNWi1of> on zone <foo> partially failed.
Installation of <SUNWi4rf> on zone <foo> partially failed.
Installation of <SUNWi8rf> on zone <foo> partially failed.
Installation of <SUNW1251f> on zone <foo> partially failed.
Installation of <SUNWarrf> on zone <foo> partially failed.
Installation of <SUNWxwoft> on zone <foo> partially failed.
Installation of <SUNWxwxst> on zone <foo> partially failed.
Installation of <SUNWkoi8f> on zone <foo> partially failed.
Installation of <SUNWasu> on zone <foo> partially failed.
Installation of <SUNWxrpcrt> on zone <foo> partially failed.
Installation of <SUNWasac> on zone <foo> partially failed.
Installation of <SUNWasdb> on zone <foo> partially failed.
Installation of <SUNWasut> on zone <foo> partially failed.and# grep "not installed" /zone/foo/root/var/sadm/system/logs/install_log
*** package <SPROmrdwf> was not installed:
*** package <SPROdwrfb> was not installed:
*** package <SPROlang> was not installed:
*** package <SPROlangx> was not installed:
*** package <SPROdwrfx> was not installed:
*** package <SPROsbld> was not installed:
*** package <SPROsbldx> was not installed:
*** package <SPROrdbkb> was not installed:
*** package <SPROrdbkx> was not installed:
*** package <SPROcc> was not installed:
*** package <SPROutool> was not installed:
*** package <SPROmrcc> was not installed:
*** package <SPROmrcom> was not installed:
*** package <SPROmr3m> was not installed:
*** package <SPROmrtcv> was not installed:
*** package <SPROm9xs> was not installed:
*** package <SPROsunms> was not installed:
*** package <SPROsmsx> was not installed:
*** package <SPROsmpx> was not installed:
*** package <SPROmrsbe> was not installed:
*** package <SPROsbe> was not installed:
*** package <SPROpnsn> was not installed:
*** package <SPROfd> was not installed:
*** package <SPROupdck> was not installed:
*** package <SPROcpl> was not installed:
*** package <SPROcplx> was not installed:
*** package <SPROcmpl> was not installed:
*** package <SPROtlbn7> was not installed:
*** package <SPROtll7> was not installed:
*** package <SPROtl7x> was not installed:
*** package <SPROtll7x> was not installed:
*** package <SPROscl> was not installed:
*** package <SPROsclx> was not installed:
*** package <SPROmrstd> was not installed:
*** package <SPROmrcpl> was not installed:
*** package <SPROstl4h> was not installed:
*** package <SPROstl4a> was not installed:
*** package <SPROstl4o> was not installed:
*** package <SPROstl4x> was not installed:
*** package <SPROstl4y> was not installed:
*** package <SPROftool> was not installed:
*** package <SPROl90> was not installed:
*** package <SPROl90x> was not installed:
*** package <SPROl90s> was not installed:
*** package <SPROl90sx> was not installed:
*** package <SPROf90> was not installed:
*** package <SPROmrftn> was not installed:
*** package <SPROgc> was not installed:
*** package <SPROlgc> was not installed:
*** package <SPROgcx> was not installed:
*** package <SPROlgcx> was not installed:
*** package <SPROdbx> was not installed:
*** package <SPROdbxx> was not installed:
*** package <SPROjdbx> was not installed:
*** package <SPROjdbxx> was not installed:
*** package <SPROmrdbx> was not installed:
*** package <SPROdemo> was not installed:
*** package <SPROdmake> was not installed:
*** package <SPROmrdmk> was not installed:
*** package <SPROtdemo> was not installed:
*** package <SPROmride> was not installed:
*** package <SPROdbxui> was not installed:
*** package <SPROsvc> was not installed:
*** package <SPROxdplg> was not installed:
*** package <SPROidext> was not installed:
*** package <SPROjnsnb> was not installed:
*** package <SPROjnsrt> was not installed:
*** package <SPROjnsup> was not installed:
*** package <SPROctags> was not installed:
*** package <SUNWnbide> was not installed:
*** package <SUNWnbcpp> was not installed:
*** package <SUJAnbcpp> was not installed:
*** package <SUZHnbcpp> was not installed:
*** package <SUNWexted> was not installed:
*** package <SUJAexted> was not installed:
*** package <SUZHexted> was not installed:
*** package <SPROnbreg> was not installed:
*** package <SPROfdxd> was not installed:
*** package <SPROmrxd> was not installed:
*** package <SPROgvim> was not installed:
*** package <SPROxmbin> was not installed:
*** package <SPROxmshr> was not installed:
*** package <SPROxmsrc> was not installed:
*** package <SPROmrxm> was not installed:
*** package <SPROprfan> was not installed:
*** package <SPROmrpan> was not installed:
*** package <SPROprfax> was not installed:
*** package <SPROprflb> was not installed:
*** package <SPROprflx> was not installed:
*** package <SPROprfgn> was not installed:
*** package <SPROmrpgn> was not installed:
*** package <SPROhtbas> was not installed:
*** package <SPROhttl7> was not installed:
*** package <SPROhtstd> was not installed:
*** package <SPROhtxd> was not installed:
*** package <SPROdwrfs> was not installed:
*** package <SPROrdbks> was not installed:
*** package <SPROctsrc> was not installed:
*** package <SPROplg> was not installed:
*** package <SPROpl> was not installed:
*** package <SPROplx> was not installed:
*** package <SPROpls> was not installed:
*** package <SPROplsx> was not installed:
*** package <SPROmrpl> was not installed:These messages seem to be inline with the general output captured from the zone install itself.
> What does "svcadm list -vc" give you when you started the zone ?
I took that as a typo, instead using "zoneadm?"
# zoneadm list -vc
ID NAME             STATUS         PATH
   0 global           running        /
   7 foo              running        /zone/fooThe zone is not on its own slice, however "/zone" is mounted as a loopback from /export/zone. I don't think that's a problem since the zone install seems to work if I don't inherit packages. Unless perhaps its a nesting level of lofs's.
FWIW,
# mount |grep zone
/zone on /export/zone read/write/setuid/devices/dev=1540000 on Fri Feb 24 16:10:55 2006
/zone/foo/root/dev on /zone/foo/dev read/write/setuid/devices/zonedevfs/dev=4640007 on Tue Feb 28 13:13:03 2006
/zone/foo/root/lib on /lib read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/platform on /platform read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/sbin on /sbin read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/usr on /usr read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/proc on proc read/write/setuid/nodevices/zone=foo/dev=4400007 on Tue Feb 28 13:13:06 2006
/zone/foo/root/system/contract on ctfs read/write/setuid/nodevices/zone=foo/dev=43c0008 on Tue Feb 28 13:13:06 2006
/zone/foo/root/etc/svc/volatile on swap read/write/setuid/nodevices/xattr/zone=foo/dev=448000e on Tue Feb 28 13:13:06 2006
/zone/foo/root/etc/mnttab on mnttab read/write/setuid/nodevices/zone=foo/dev=4440008 on Tue Feb 28 13:13:06 2006

Micro Channel Boot diskette Solaris 2.6

Similar Messages

Maybe you are looking for