Hi, Sundar and Ethan,
I think I had same issue with Praveen, slice 0 is not big enough to hold
AI. After made
slice 0 larger(8GB instead of 4.0), the installation passed.
Following is slice info output:
partition> p
Current partition table (original):
Total disk cylinders available: 60797 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks
0 root wm 1 - 173 3.98GB (173/0/0)
8337735
1 unassigned wm 0 0 (0/0/0)
0
2 backup wu 0 - 60796 1.36TB (60797/0/0)
2930111415
3 unassigned wm 0 0 (0/0/0)
0
4 unassigned wm 0 0 (0/0/0)
0
5 unassigned wm 0 0 (0/0/0)
0
6 unassigned wm 0 0 (0/0/0)
0
7 unassigned wm 0 0 (0/0/0)
0
8 boot wu 0 - 0 23.53MB (1/0/0)
48195
9 unassigned wm 0 0 (0/0/0)
0
root at opensolaris:~/export/Install/ws-ai-engine/src/suites/ai-manifest#
prtvtoc /dev/rdsk/c8t1d0s2
* /dev/rdsk/c8t1d0s2 partition map
*
* Dimensions:
* 512 bytes/sector
* 189 sectors/track
* 255 tracks/cylinder
* 48195 sectors/cylinder
* 60799 cylinders
* 60797 accessible cylinders
*
* Flags:
* 1: unmountable
* 10: read-only
*
* Unallocated space:
* First Sector Last
* Sector Count Sector
* 0 48195 48194
* 8434125 2921677290 2930111414
*
* First Sector Last
* Partition Tag Flags Sector Count Sector Mount Directory
0 2 00 48195 8337735 8385929
2 5 01 0 2930111415 2930111414
8 1 01 0 48195 48194
I am running into this issue when executing my test suite.
In my suite, in order to test on VirtualBox(which usually has limited
space), the previous test case
created a 4GB slice 0, then the following one
continue using this slice 0, so caused the installation failed.
And as AI grow bigger, seems 4GB is not enough. (That's may explained
why same test suite,
but my previous execution prior to 111a could succeed).
I changed my test case to create 8GB slice, no problem right now.
partition> p
Current partition table (original):
Total disk cylinders available: 60797 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks
0 root wm 1 - 347 7.97GB (347/0/0)
16723665
1 unassigned wm 0 0 (0/0/0)
0
2 backup wu 0 - 60796 1.36TB (60797/0/0)
2930111415
Here which needs to improve is the error message, "not enough space"
should be
reported instead of "missing package" in /tmp/install_log.
Sundar Yamunachari ??:
> Jeffrey,
>
> Did you see this problem while using a manifest that doesn't have any
> slice operations (create/delete)? What is the size of slice 0 on the
> failed systems. Send the output of the format command with slice
> information.
>
> Thanks,
> Sundar
>
> Jeffrey Huang wrote:
>> Hi, Sarah,
>>
>> Sure, we can try that.
>> It happens only when running the full set of test suite. I will try to
>> get the result back
>> after our long weekend holiday.
>>
>> So when install_debug=enable, there will be more detail info goes in
>> to /tmp/install_log,
>> right? Or any other further info I need to capture?
>>
>> Regards
>> Jeffrey
>>
>>
>> Sarah Jelinek ??:
>>> Hi Jeffrey,
>>>
>>> I wonder if enabling debug would get us more data about which pkg is
>>> not found.
>>>
>>> Can you set install_debug=enable at the end, on the kernel line in
>>> the grub menu and run install?
>>>
>>> thanks,
>>> sarah
>>> ***
>>>> Hi, Ethan,
>>>>
>>>> We also met the same issue in our automated test suite. But things
>>>> uncertain for me is:
>>>> 1. It is new in 111a
>>>> 2. Only happening on x86
>>>> 3. Not reproduced every time: Run a bunch of test cases it happened,
>>>> run individual test case,
>>>> it passed.
>>>>
>>>> == The manifest ==
>>>> <ai_manifest name="ai_test_manifest">
>>>> <ai_target_device>
>>>> <target_device_name>c8t1d0</target_device_name>
>>>>
>>>> <target_device_use_solaris_partition>true</target_device_use_solaris_partition
>>>>
>>>>
>>>> >
>>>>
>>>> <target_device_overwrite_root_zfs_pool>true</target_device_overwrite_root_zfs_
>>>>
>>>>
>>>> pool>
>>>> </ai_target_device>
>>>> <ai_pkg_repo_default_authority>
>>>> <main url="http://10.13.28.40:10000"
>>>> authname="opensolaris.org"/>
>>>> <mirror url=""/>
>>>> </ai_pkg_repo_default_authority>
>>>> <ai_install_packages>
>>>> <pkg name="entire"/>
>>>> <pkg name="SUNWcsd"/>
>>>> <pkg name="SUNWcs"/>
>>>> <pkg name="babel_install"/>
>>>> <pkg name="SUNWmercurial"/>
>>>> </ai_install_packages>
>>>> </ai_manifest>
>>>> == The install_log ==
>>>> opensolaris 12:32:15 +++ /tmp/install_log +++
>>>> opensolaris 12:32:15 <AI Apr 28 19:09:23> /root/ai_my_manifest.xml
>>>> is a valid manifest
>>>> opensolaris 12:32:15 <AI Apr 28 19:09:23> Manifest indicates that
>>>> Solaris fdisk partition must
>>>> opensolaris 12:32:15 be on the target disk prior to installation.
>>>> opensolaris 12:32:15 <AI Apr 28 19:09:33> Disk = c8t1d0 found on the
>>>> system
>>>> opensolaris 12:32:15 <AI Apr 28 19:09:33> Disk name selected for
>>>> installation is c8t1d0
>>>> opensolaris 12:32:15 <AI Apr 28 19:09:33> no manifest partition
>>>> information found
>>>> opensolaris 12:32:15 <OM Apr 28 19:09:33> disk partition info not
>>>> changed
>>>> opensolaris 12:32:15 <AI Apr 28 19:09:33> no manifest slice
>>>> information found
>>>> opensolaris 12:32:15 <OM Apr 28 19:09:33> System reports enough
>>>> physical memory for installation, swap is optional
>>>> opensolaris 12:32:15 <OM Apr 28 19:09:34> Timezone setting will be
>>>> TZ=US/Pacific
>>>> opensolaris 12:32:15 <OM Apr 28 19:09:34> Set timezone
>>>> opensolaris 12:32:15 <AI Apr 28 19:09:34> installation will be
>>>> performed from http://10.13.28.40:10000 (opensolaris.org)
>>>> opensolaris 12:32:15 <AI Apr 28 19:09:34> installation will be
>>>> performed from http://10.13.28.40:10000 (opensolaris.org)
>>>> opensolaris 12:32:15 <AI Apr 28 19:09:34> list of packages to be
>>>> installed is:
>>>> opensolaris 12:32:15 <AI Apr 28 19:09:34> SUNWmercurial
>>>> opensolaris 12:32:15 <AI Apr 28 19:09:34> entire
>>>> opensolaris 12:32:15 <AI Apr 28 19:09:34> SUNWcsd
>>>> opensolaris 12:32:15 <AI Apr 28 19:09:34> SUNWcs
>>>> opensolaris 12:32:15 <AI Apr 28 19:09:34> babel_install
>>>> opensolaris 12:32:15 <AI Apr 28 19:09:34> No packages specified to
>>>> be removed from installed system
>>>> opensolaris 12:32:15 <OM Apr 28 19:09:34> Disk was changed
>>>> opensolaris 12:32:15 <OM Apr 28 19:09:34> Disk contains valid
>>>> Solaris partition
>>>> opensolaris 12:32:15 <OM Apr 28 19:09:34> whole_disk = 0
>>>> opensolaris 12:32:15 <OM Apr 28 19:09:34> diskname set = c8t1d0
>>>> opensolaris 12:32:15 <OM Apr 28 19:09:34> Set fdisk attrs
>>>> opensolaris 12:32:15 <OM Apr 28 19:09:34> Set zfs root pool device
>>>> opensolaris 12:32:15 <OM Apr 28 19:09:34> creating zpool
>>>> opensolaris 12:32:15 <OM Apr 28 19:09:34> /usr/sbin/zfs get -Hp -o
>>>> value available rpool
>>>> opensolaris 12:32:15 <OM Apr 28 19:09:34> Creating swap and dump on
>>>> ZFS volumes
>>>> opensolaris 12:32:15 <OM Apr 28 19:09:37> TI process completed
>>>> successfully
>>>> opensolaris 12:32:15 <OM Apr 28 19:09:37> Transfer process initiated
>>>> opensolaris 12:32:15 <OM Apr 28 19:09:37> IPS transfer mechanism
>>>> selected
>>>> opensolaris 12:32:16 <OM Apr 28 19:09:37> IPS transfer phase initiated
>>>> opensolaris 12:32:16 <OM Apr 28 19:09:56> IPS initialization phase 1
>>>> succeeded
>>>> opensolaris 12:32:16 <TRANSFER_MOD Apr 28 19:32:11> pkg missing
>>>> opensolaris 12:32:16 <OM Apr 28 19:32:11> Installation of packages
>>>> failed
>>>> opensolaris 12:32:16 <OM Apr 28 19:32:11> Transfer failed with error -1
>>>> opensolaris 12:32:16 <AI Apr 28 19:32:15> om_perform_install failed
>>>> with error 114
>>>> opensolaris 12:32:16 <AI Apr 28 19:32:15> Auto install failed
>>>> opensolaris 12:32:16 +++ end +++
>>>>
>>>>
>>>> Ethan Quach ??:
>>>>>
>>>>>
>>>>> Praveen Shivasharan wrote:
>>>>>> Hi,
>>>>>>
>>>>>> Installation of osol_111a is failing on x4250 system. Didn't find
>>>>>> any matching bugs in Bugzilla.
>>>>>> Please let me know if you are aware of this issue and how to fix
>>>>>> it. In process of reproducing the
>>>>>> issue
>>>>>>
>>>>>> root at opensolaris:~# tail -20 /tmp/install_log
>>>>>> <OM Apr 30 19:41:34> Disk was changed
>>>>>> <OM Apr 30 19:41:34> Disk contains valid Solaris partition
>>>>>> <OM Apr 30 19:41:34> whole_disk = 0
>>>>>> <OM Apr 30 19:41:34> diskname set = c8t0d0
>>>>>> <OM Apr 30 19:41:34> Set fdisk attrs
>>>>>> <OM Apr 30 19:41:34> Set zfs root pool device
>>>>>> <OM Apr 30 19:41:34> creating zpool
>>>>>> <OM Apr 30 19:41:39> /usr/sbin/zfs get -Hp -o value available rpool
>>>>>> <OM Apr 30 19:41:39> Creating swap and dump on ZFS volumes
>>>>>> <OM Apr 30 19:42:00> TI process completed successfully
>>>>>> <OM Apr 30 19:42:00> Transfer process initiated
>>>>>> <OM Apr 30 19:42:00> IPS transfer mechanism selected
>>>>>> <OM Apr 30 19:42:00> IPS transfer phase initiated
>>>>>> <OM Apr 30 19:42:12> IPS initialization phase 1 succeeded
>>>>>> <OM Apr 30 19:42:13> IPS initialization phase 2 succeeded
>>>>>> <TRANSFER_MOD Apr 30 19:59:33> pkg missing
>>>>>
>>>>> Looks like one of the packages in the list couldn't be found. Can
>>>>> you send the manifest file that was used with this installation.
>>>>> If you don't know where that is on the server, you can get it from
>>>>> the client after the failed install at:
>>>>>
>>>>> /tmp/ai_combined_manifest.xml
>>>>>
>>>>>
>>>>> thanks,
>>>>> -ethan
>>>>>
>>>>>
>>>>>> <OM Apr 30 19:59:33> Installation of packages failed
>>>>>> <OM Apr 30 19:59:33> Transfer failed with error -1
>>>>>> <AI Apr 30 19:59:35> om_perform_install failed with error 114
>>>>>> <AI Apr 30 19:59:35> Auto install failed
>>>>>> root at opensolaris:~#
>>>>>>
>>>>> _______________________________________________
>>>>> caiman-discuss mailing list
>>>>> caiman-discuss at opensolaris.org
>>>>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
>>>>
>>>
>>
>
--
Great Thanks & Best Regards
---
Jeffrey Huang SWAN: x51683, Ext: 0086-10-62673683
Solaris QE Group Email: jeffrey.huang at sun.com
China Engineering & Research Institute, Sun Microsystems
7/F Chuang Xin Plaza, Tsinghua Science Park, Beijing China