Mark,
Can you get me the core file? (offline)
thanks,
-ethan
On 06/08/10 17:44, Mark Wedel wrote:
Maybe this is a known bug. When trying to install build 140 that
repartitions the disk, the install fails (likely the core dump). The
same manifest works without problems on 139, and an install of 140
also works fine.
/tmp/install_log
<AI Jun 8 16:28:41> /tmp/ai_combined_manifest.xml manifest created
<AI Jun 8 16:28:41> /tmp/ai_combined_manifest.xml manifest setup and
validated
<AI Jun 8 16:28:41> Auto reboot enabled
<AI Jun 8 16:28:41> Initiating Target Discovery...
<AI Jun 8 16:28:49> Target Discovery finished successfully
<AI Jun 8 16:28:49> Searching for a disk target matching the
following criteria<AI Jun 8 16:28:49> Size [MiB]: 10
<AI Jun 8 16:28:49> Disk c1t2d0 selected based on manifest criteria
<AI Jun 8 16:28:49> Disk name selected for installation is c1t2d0
<AI Jun 8 16:28:49> no manifest partition information found
<OM Jun 8 16:28:49> disk partition info not changed
<AI Jun 8 16:28:49> Maximum size requested for new slice. (7)
/var/svc/log/application-auto-installer:default.log
Automated Installation started
The progress of the Automated Installation can be followed by viewing
the logfile at /tmp/install_log
svcprop: Couldn't find property `general/install_debug' for instance
`svc:/application/auto-installer:default'.
/tmp/ai_manifest_temp_902.xml validates
/tmp/ai_manifest.defval.xml validates
/lib/svc/method/auto-installer: line 134: 902: Memory fault(coredump)
Automated Installation failed
Unknown exit code 267 returned
[ Jun 8 16:28:52 Method "start" exited with status 95. ]
r...@opensolaris:~#
Manifest:
<ai_criteria_manifest>
<ai_embedded_manifest>
<!-- This manifest is similar to the default manifest, except
that it removes all the slice information and creates a
new single slice. This is useful when re-installing
systems that have existing UFS filesystems that are
no longer needed.
Note that the manifest control we provide the criteria
and the sc_manifest (root and admin password) for the install.
The root and admin passwords will be set to l1admin.
-->
<ai_manifest name="ai_10.5.235.196">
<!-- Remove all existing slice information -->
<ai_device_vtoc_slices>
<slice_action>delete</slice_action>
<slice_number>0</slice_number>
<slice_size>0</slice_size>
</ai_device_vtoc_slices>
<ai_device_vtoc_slices>
<slice_action>delete</slice_action>
<slice_number>1</slice_number>
<slice_size>0</slice_size>
</ai_device_vtoc_slices>
<!-- Don't delete slice 2 - that needs to stick around -->
<ai_device_vtoc_slices>
<slice_action>delete</slice_action>
<slice_number>3</slice_number>
<slice_size>0</slice_size>
</ai_device_vtoc_slices>
<ai_device_vtoc_slices>
<slice_action>delete</slice_action>
<slice_number>4</slice_number>
<slice_size>0</slice_size>
</ai_device_vtoc_slices>
<ai_device_vtoc_slices>
<slice_action>delete</slice_action>
<slice_number>5</slice_number>
<slice_size>0</slice_size>
</ai_device_vtoc_slices>
<ai_device_vtoc_slices>
<slice_action>delete</slice_action>
<slice_number>6</slice_number>
<slice_size>0</slice_size>
</ai_device_vtoc_slices>
<ai_device_vtoc_slices>
<slice_action>delete</slice_action>
<slice_number>7</slice_number>
<slice_size>0</slice_size>
</ai_device_vtoc_slices>
<!-- Now add a slice -->
<ai_device_vtoc_slices>
<slice_action>create</slice_action>
<slice_number>0</slice_number>
<slice_size>max_size</slice_size>
<slice_size_units>GB</slice_size_units>
</ai_device_vtoc_slices>
<!--
<ai_device_vtoc_slices>
<slice_action>create</slice_action>
<slice_number>1</slice_number>
<slice_size>40</slice_size>
<slice_size_units>GB</slice_size_units>
</ai_device_vtoc_slices>
-->
<ai_target_device>
<target_device_size>20480</target_device_size>
</ai_target_device>
(reset snipped out)
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
