Bugzilla – Bug 8575
AI should verify slice/pool size is big enough before going on with installation.
Last modified: 2009-11-04 02:10:30 UTC
You need to log in before you can comment on or make changes to this bug.
Installation of open solaris build 111a is failing on x4250 system due to "om_perform_install failed with error 114"The problem is reproducible. It complains about not having enough space left. o/p's from various files /tmp/ai_combined_manifest.xml file root@opensolaris:/tmp# more ai_combined_manifest.xml <ai_criteria_manifest> <ai_embedded_manifest> <ai_manifest name="ai_d53c_111a.xml"> <ai_target_device> <target_device_name>c8t0d0</target_device_name> </ai_target_device> <ai_pkg_repo_default_authority> <main url="http://ipkg.sfbay/dev" authname="ipkg.sfbay"/> </ai_pkg_repo_default_authority> <ai_pkg_repo_addl_authority> <main url="http://pkg.opensolaris.org/dev" authname="opensolaris.org"/> </ai_pkg_repo_addl_authority> <ai_packages> <package_name>entire@0.5.11,5.11-0.111:20090418T200225Z</package_name> <package_name>SUNWcsd</package_name> <package_name>SUNWcs</package_name> <package_name>babel_install</package_name> </ai_packages> <ai_auto_reboot>true</ai_auto_reboot> </ai_manifest> </ai_embedded_manifest> <sc_embedded_manifest name = "AI"> <!-- <?xml version='1.0'?> <!DOCTYPE service_bundle SYSTEM "/usr/share/lib/xml/dtd/service_bundle.dtd.1"> <service_bundle type="profile" name="name"> <service name="ai_properties" version="1" type="service"> <instance name="default" enabled="true"> <property_group name="ai" type="application"> <propval name="rootpass" type="astring" value="$5$bh8iAJNq$B.hzKao4NVmZF.VQ9GRzo2yBbs9pBZU7PzBrinNx9D6"/> <propval name="timezone" type="astring" value="US/Pacific"/> </property_group> </instance> </service> </service_bundle> --> </sc_embedded_manifest> </ai_criteria_manifest> root@opensolaris:/tmp# root@opensolaris:/tmp# more /var/svc/log/application-auto-installer:default.log [ Apr 30 08:24:01 Executing start method ("/lib/svc/method/auto-installer"). ] Service discovery phase initiated Service name to look up: x86-111a-default <AISD_I 04/30 15:24:02> Service file: /tmp/service_list.261 <AISD_I 04/30 15:24:02> Service to look up: x86-111a-default._OSInstall._tcp.local <AISD_I 04/30 15:24:02> cmd: /usr/bin/dns-sd -L x86-111a-default _OSInstall._tcp local <AISD_I 04/30 15:24:02> dns-sd pid: 319 <AISD_I 04/30 15:24:03> Svc: Lookup x86-111a-default._OSInstall._tcp.local <AISD_I 04/30 15:24:03> Svc: 8:24:03.510 x86-111a-default._OSInstall._tcp.local. can be reached at mpk1200-ai.local.:46506 <AISD_I 04/30 15:24:03> TXT: aiwebserver=172.21.254.7:46506 <AISD_I 04/30 15:24:03> x86-111a-default service found <AISD_I 04/30 15:24:03> dns-sd (pid=319) is running, will be terminated <AISD_I 04/30 15:24:03> Valid service found: svc: 8:24:03.510 x86-111a-default._OSInstall._tcp.local. can be reached at mpk1200-ai.local.:46506 TXT: aiwebserver=172.21.254.7:46506 <AISD_I 04/30 15:24:03> x86-111a-default._OSInstall._tcp.local can be reached at: 172.21.254.7:46506 <AISD_I 04/30 15:24:03> Storing service list into /tmp/service_list.261 Service discovery finished successfully Process of obtaining configuration manifest initiated <AISC_I 04/30 15:24:03> Service list: /tmp/service_list.261 <AISC_I 04/30 15:24:03> Manifest file: /tmp/ai_combined_manifest.xml <AISC_I 04/30 15:24:03> cmd:/usr/sbin/ifconfig -au | /usr/bin/grep '[0-9]:' | /usr/bin/grep -v 'LOOPBACK' <AISC_I 04/30 15:24:03> Network interface obtained: e1000g0 <AISC_I 04/30 15:24:03> cmd:/usr/sbin/ifconfig e1000g0 <AISC_I 04/30 15:24:03> Client IP address: 172021239045 <AISC_I 04/30 15:24:03> Mask: FFFFFF00, IP: AC15EF2D, Network: AC15EF00 <AISC_I 04/30 15:24:03> Client net: 172021239000 <AISC_I 04/30 15:24:03> cmd:/usr/sbin/prtconf -vp | /usr/bin/grep '^Memory size: ' <AISC_I 04/30 15:24:03> prtconf(1M) reported: 8192 Megabytes <AISC_I 04/30 15:24:03> cmd:/usr/bin/uname -i <AISC_I 04/30 15:24:03> Client MAC address: 001e6849b79c <AISC_I 04/30 15:24:03> cmd:/usr/bin/uname -m <AISC_I 04/30 15:24:03> cmd:/usr/bin/uname -p <AISC_I 04/30 15:24:03> Client can supply following criteria <AISC_I 04/30 15:24:03> network=172021239000, 'Client network address' <AISC_I 04/30 15:24:03> mem=8192, 'Physical memory size' <AISC_I 04/30 15:24:03> hostname=opensolaris, 'Client hostname' <AISC_I 04/30 15:24:03> platform=i86pc, 'Client platform' <AISC_I 04/30 15:24:03> mac=001e6849b79c, 'Client MAC address' <AISC_I 04/30 15:24:03> ipv4=172021239045, 'Client IP address' <AISC_I 04/30 15:24:03> arch=i86pc, 'Client machine architecture' <AISC_I 04/30 15:24:03> cpu=i386, 'Client processor type' <AISC_I 04/30 15:24:03> Starting to contact AI services provided by /tmp/service_list.261 <AISC_I 04/30 15:24:03> AI service: 172.21.254.7:46506 <AISC_I 04/30 15:24:03> Asking for criteria list: <AISC_I 04/30 15:24:03> HTTP GET 172.21.254.7:46506/manifest.xml <AISC_I 04/30 15:24:03> Required criteria 1: mac <AISC_I 04/30 15:24:03> Required criteria 2: ipv4 <AISC_I 04/30 15:24:03> List of criteria to be sent: <AISC_I 04/30 15:24:03> mac=001e6849b79c <AISC_I 04/30 15:24:03> ipv4=172021239045 <AISC_I 04/30 15:24:03> Sending list of criteria, asking for manifest: <AISC_I 04/30 15:24:03> HTTP POST {'mac': '001e6849b79c', 'ipv4': '172021239045'} 172.21.254.7:46506 <AISC_I 04/30 15:24:03> postData=mac=001e6849b79c%3Bipv4=172021239045 <AISC_I 04/30 15:24:03> 172.21.254.7:46506 AI service provided valid manifest <AISC_I 04/30 15:24:03> Saving manifest to /tmp/ai_combined_manifest.xml Configuration manifest obtained Automated Installation started The progress of the Automated Installation can be followed by viewing the logfile at /tmp/install_log /tmp/ai_manifest.defval.xml validates /tmp/ai_manifest_temp_380.xml validates /tmp/ai_combined_manifest.xml is a valid manifest Auto reboot enabled Disk = c8t0d0 found on the system Disk name selected for installation is c8t0d0 no manifest partition information found no manifest slice information found installation will be performed from http://ipkg.sfbay/dev (ipkg.sfbay) installation will be performed from http://ipkg.sfbay/dev (ipkg.sfbay) alternate IPS authority will be http://pkg.opensolaris.org/dev (opensolaris.org)list of packages to be installed is: entire@0.5.11,5.11-0.111:20090418T200225Z SUNWcsd SUNWcs babel_install No packages specified to be removed from installed system Error in atexit._run_exitfuncs: Traceback (most recent call last): File "/usr/lib/python2.4/atexit.py", line 24, in _run_exitfuncs func(*targs, **kargs) File "/usr/lib/python2.4/threading.py", line 638, in __exitfunc self._Thread__delete() File "/usr/lib/python2.4/threading.py", line 522, in __delete del _active[_get_ident()] KeyError: 8 Error in sys.exitfunc: Traceback (most recent call last): File "/usr/lib/python2.4/atexit.py", line 24, in _run_exitfuncs func(*targs, **kargs) File "/usr/lib/python2.4/threading.py", line 638, in __exitfunc self._Thread__delete() File "/usr/lib/python2.4/threading.py", line 522, in __delete del _active[_get_ident()] KeyError: 8 Install Phase ... Done Reading Existing Index ... Done Indexing Packages ... Done Download: SUNWcsd ... Done Install Phase ... Done Reading Existing Index ... Done Indexing Packages ... Done Download: SUNWcs ... Done Download: SUNWcsl ... Done Download: SUNWlibsasl ... Done Download: SUNWlibms ... Done Download: SUNWpr ... Done Download: SUNWtls ... Done Download: SUNWlxml ... Done .... ..... .... <<< Deleted lines to shorten the message>>.. .... Download: SUNWlang-sr ... Done Download: SUNWlang-es ... Done Download: SUNWlang-tr ... Done Download: SUNWlang-hr ... Done Download: SUNWlang-et ... Done Download: SUNWlang-sv ... Done Download: SUNWlang-el ... Done Download: SUNWlang-en ... Done Download: SUNWgnome-l10nmessages-extra ... Done Download: SUNWlang-sh ... Done The Boot Environment opensolaris failed to be updated. A snapshot was taken before the failed attempt and has been restored so no changes have been made to opensolaris. pkg: An unexpected error happened during installation: [Errno 28] No space left on device Traceback (most recent call last): File "/usr/bin/pkg", line 2563, in ? __ret = main_func() File "/usr/bin/pkg", line 2506, in main_func return install(mydir, pargs) File "/usr/bin/pkg", line 780, in install api_inst.execute_plan() File "/usr/lib/python2.4/vendor-packages/pkg/client/api.py", line 526, in execute_plan self.img.imageplan.execute() File "/usr/lib/python2.4/vendor-packages/pkg/client/imageplan.py", line 719, in execute p.execute_install(src, dest) File "/usr/lib/python2.4/vendor-packages/pkg/client/pkgplan.py", line 260, in execute_install dest.install(self, src) File "/usr/lib/python2.4/vendor-packages/pkg/actions/file.py", line 165, in install shasum = misc.gunzip_from_stream(stream, tfile) File "/usr/lib/python2.4/vendor-packages/pkg/misc.py", line 309, in gunzip_from_stream outfile.write(ubuf) IOError: [Errno 28] No space left on device pkg: This is an internal error. Please let the developers know about this problem by filing a bug at http://defect.opensolaris.org and including the above traceback and this message. The version of pkg(5) is '02ad3f8f9c38'. close failed: [Errno 5] I/O error Install Phase ... Action install failed for 'usr/lib/libmlib/amd64/libmlib_sse2.so.2' (pkg:/SUNWmlib): IOError: [Errno 28] No space left on device Unable to install babel_install in /a om_perform_install failed with error 114 Auto install failed Automated Installation failed Please refer to /tmp/install_log file for details [ Apr 30 15:57:35 Method "start" exited with status 95. ] root@opensolaris:/tmp# root@opensolaris:/tmp# root@opensolaris:/tmp# more install_log <AI Apr 30 15:24:04> /tmp/ai_combined_manifest.xml is a valid manifest <AI Apr 30 15:24:04> Auto reboot enabled <AI Apr 30 15:41:55> Disk = c8t0d0 found on the system <AI Apr 30 15:41:55> Disk name selected for installation is c8t0d0 <AI Apr 30 15:41:55> no manifest partition information found <OM Apr 30 15:41:55> disk partition info not changed <AI Apr 30 15:41:55> no manifest slice information found <OM Apr 30 15:41:55> System reports enough physical memory for installation, swap is optional <OM Apr 30 22:41:55> Timezone setting will be TZ=US/Pacific <OM Apr 30 22:41:55> Set timezone <AI Apr 30 22:41:55> installation will be performed from http://ipkg.sfbay/dev (ipkg.sfbay) <AI Apr 30 22:41:55> installation will be performed from http://ipkg.sfbay/dev (ipkg.sfbay) <AI Apr 30 22:41:55> alternate IPS authority will be http://pkg.opensolaris.org/dev (opensolaris.org) <AI Apr 30 22:41:55> list of packages to be installed is: <AI Apr 30 22:41:55> entire@0.5.11,5.11-0.111:20090418T200225Z <AI Apr 30 22:41:55> SUNWcsd <AI Apr 30 22:41:55> SUNWcs <AI Apr 30 22:41:55> babel_install <AI Apr 30 22:41:55> No packages specified to be removed from installed system <OM Apr 30 22:41:55> User name not specified <OM Apr 30 22:41:55> User login name not specified <OM Apr 30 22:41:55> Disk was changed <OM Apr 30 22:41:55> Disk contains valid Solaris partition <OM Apr 30 22:41:55> whole_disk = 0 <OM Apr 30 22:41:55> diskname set = c8t0d0 <OM Apr 30 22:41:55> Set fdisk attrs <OM Apr 30 22:41:55> Set zfs root pool device <OM Apr 30 22:41:55> creating zpool <OM Apr 30 22:41:59> /usr/sbin/zfs get -Hp -o value available rpool <OM Apr 30 22:41:59> Creating swap and dump on ZFS volumes <OM Apr 30 22:42:21> TI process completed successfully <OM Apr 30 22:42:21> Transfer process initiated <OM Apr 30 22:42:21> IPS transfer mechanism selected <OM Apr 30 22:42:21> IPS transfer phase initiated <OM Apr 30 22:42:33> IPS initialization phase 1 succeeded <OM Apr 30 22:42:34> IPS initialization phase 2 succeeded <TRANSFER_MOD Apr 30 22:57:34> pkg missing <OM Apr 30 22:57:34> Installation of packages failed <OM Apr 30 22:57:34> Transfer failed with error -1 <AI Apr 30 22:57:35> om_perform_install failed with error 114 <AI Apr 30 22:57:35> Auto install failed root@opensolaris:/tmp#
(In reply to comment #0) > Download: SUNWlang-hr ... Done > Download: SUNWlang-et ... Done > Download: SUNWlang-sv ... Done > Download: SUNWlang-el ... Done > Download: SUNWlang-en ... Done > Download: SUNWgnome-l10nmessages-extra ... Done > Download: SUNWlang-sh ... Done > The Boot Environment opensolaris failed to be updated. A snapshot was taken > before the failed attempt and has been restored so no changes have been made to > opensolaris. > pkg: An unexpected error happened during installation: [Errno 28] No space left > on device > Traceback (most recent call last): > File "/usr/bin/pkg", line 2563, in ? > __ret = main_func() > File "/usr/bin/pkg", line 2506, in main_func > return install(mydir, pargs) > File "/usr/bin/pkg", line 780, in install > api_inst.execute_plan() > File "/usr/lib/python2.4/vendor-packages/pkg/client/api.py", line 526, in > execute_plan > self.img.imageplan.execute() > File "/usr/lib/python2.4/vendor-packages/pkg/client/imageplan.py", line 719, > in execute > p.execute_install(src, dest) > File "/usr/lib/python2.4/vendor-packages/pkg/client/pkgplan.py", line 260, in > execute_install > dest.install(self, src) > File "/usr/lib/python2.4/vendor-packages/pkg/actions/file.py", line 165, in > install > shasum = misc.gunzip_from_stream(stream, tfile) > File "/usr/lib/python2.4/vendor-packages/pkg/misc.py", line 309, in > gunzip_from_stream > outfile.write(ubuf) > IOError: [Errno 28] No space left on device > > > pkg: This is an internal error. Please let the developers know about this > problem by filing a bug at http://defect.opensolaris.org and including the > above traceback and this message. The version of pkg(5) is '02ad3f8f9c38'. > close failed: [Errno 5] I/O error > Install Phase ... Action install failed for > 'usr/lib/libmlib/amd64/libmlib_sse2.so.2' (pkg:/SUNWmlib): > IOError: [Errno 28] No space left on device > Unable to install babel_install in /a > om_perform_install failed with error 114 > Auto install failed > Automated Installation failed Moving over to pkg for someone to take a look at this traceback. This system 8G of memory so its seems odd that its failing for space reasons.
Please reset the default assignee and QA contact when transferring bugs. It looks like you ran out of space on the device during the install. Is this really a P1 bug? Can you show us a df(1M) or similar output for the device that has run out of space?
Te boot disk that I'm using (c8t0d0) has capacity of ~136GB. Here are some details root@opensolaris:/tmp# format Searching for disks... AVAILABLE DISK SELECTIONS: 0. c7t8d0 <DEFAULT cyl 17845 alt 2 hd 255 sec 63> /pci@0,0/pci8086,25e2@2/pci8086,3500@0/pci8086,3510@0/pci111d,801c@0/pci111d,801c@2/pci10b5,8114@0/pci1000,10b0@8,1/sd@8,0 1. c7t9d0 <DEFAULT cyl 17845 alt 2 hd 255 sec 63> /pci@0,0/pci8086,25e2@2/pci8086,3500@0/pci8086,3510@0/pci111d,801c@0/pci111d,801c@2/pci10b5,8114@0/pci1000,10b0@8,1/sd@9,0 2. c7t10d0 <DEFAULT cyl 17845 alt 2 hd 255 sec 63> /pci@0,0/pci8086,25e2@2/pci8086,3500@0/pci8086,3510@0/pci111d,801c@0/pci111d,801c@2/pci10b5,8114@0/pci1000,10b0@8,1/sd@a,0 3. c7t11d0 <DEFAULT cyl 4424 alt 2 hd 255 sec 63> /pci@0,0/pci8086,25e2@2/pci8086,3500@0/pci8086,3510@0/pci111d,801c@0/pci111d,801c@2/pci10b5,8114@0/pci1000,10b0@8,1/sd@b,0 4. c8t0d0 <DEFAULT cyl 17824 alt 2 hd 255 sec 63> <--- BOOT DISK /pci@0,0/pci8086,25e2@2/pci8086,3500@0/pci8086,3510@0/pci111d,801c@0/pci111d,801c@4/pci108e,286@0/disk@0,0 5. c8t1d0 <Sun-STK RAID INT-V1.0-136.61GB> /pci@0,0/pci8086,25e2@2/pci8086,3500@0/pci8086,3510@0/pci111d,801c@0/pci111d,801c@4/pci108e,286@0/disk@1,0 6. c8t2d0 <Sun-STK RAID INT-V1.0-136.61GB> /pci@0,0/pci8086,25e2@2/pci8086,3500@0/pci8086,3510@0/pci111d,801c@0/pci111d,801c@4/pci108e,286@0/disk@2,0 7. c8t3d0 <Sun-STK RAID INT-V1.0-136.61GB> /pci@0,0/pci8086,25e2@2/pci8086,3500@0/pci8086,3510@0/pci111d,801c@0/pci111d,801c@4/pci108e,286@0/disk@3,0 8. c9t4d0 <drive type unknown> /pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci1000,3150@0/sd@4,0 9. c9t4d1 <drive type unknown> /pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci1000,3150@0/sd@4,1 10. c9t4d2 <drive type unknown> /pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci1000,3150@0/sd@4,2 11. c9t4d3 <drive type unknown> /pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci1000,3150@0/sd@4,3 12. c9t4d4 <drive type unknown> /pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci1000,3150@0/sd@4,4 13. c9t4d5 <drive type unknown> /pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci1000,3150@0/sd@4,5 14. c9t5d0 <DEFAULT cyl 2607 alt 2 hd 255 sec 63> /pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci1000,3150@0/sd@5,0 15. c9t5d1 <DEFAULT cyl 2607 alt 2 hd 255 sec 63> /pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci1000,3150@0/sd@5,1 16. c9t5d2 <DEFAULT cyl 2607 alt 2 hd 255 sec 63> /pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci1000,3150@0/sd@5,2 17. c9t5d3 <DEFAULT cyl 2607 alt 2 hd 255 sec 63> /pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci1000,3150@0/sd@5,3 18. c9t5d4 <DEFAULT cyl 2607 alt 2 hd 255 sec 63> /pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci1000,3150@0/sd@5,4 19. c9t5d5 <DEFAULT cyl 2607 alt 2 hd 255 sec 63> /pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci1000,3150@0/sd@5,5 Specify disk (enter its number): 4 selecting c8t0d0 [disk formatted] /dev/dsk/c8t0d0s0 is part of active ZFS pool rpool. Please see zpool(1M). FORMAT MENU: disk - select a disk type - select (define) a disk type partition - select (define) a partition table current - describe the current disk format - format and analyze the disk fdisk - run the fdisk program repair - repair a defective sector label - write label to the disk analyze - surface analysis defect - defect list management backup - search for backup labels verify - read and display labels save - save new disk/partition definitions inquiry - show vendor, product and revision volname - set 8-character volume name !<cmd> - execute <cmd>, then return quit format> p PARTITION MENU: 0 - change `0' partition 1 - change `1' partition 2 - change `2' partition 3 - change `3' partition 4 - change `4' partition 5 - change `5' partition 6 - change `6' partition 7 - change `7' partition select - select a predefined table modify - modify a predefined partition table name - name the current table print - display the current table label - write partition map and label to the disk !<cmd> - execute <cmd>, then return quit partition> p Current partition table (original): Total disk cylinders available: 17824 + 2 (reserved cylinders) Part Tag Flag Cylinders Size Blocks 0 swap wu 1 - 319 2.44GB (319/0/0) 5124735 1 root wm 320 - 17823 134.09GB (17504/0/0) 281201760 2 backup wm 0 - 17823 136.54GB (17824/0/0) 286342560 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 7.84MB (1/0/0) 16065 9 unassigned wm 0 0 (0/0/0) 0 partition> root@opensolaris:/tmp# df -k Filesystem kbytes used avail capacity Mounted on /devices/ramdisk:a 177143 171641 5502 97% / /devices 0 0 0 0% /devices /dev 0 0 0 0% /dev ctfs 0 0 0 0% /system/contract proc 0 0 0 0% /proc mnttab 0 0 0 0% /etc/mnttab swap 4771192 688 4770504 1% /etc/svc/volatile objfs 0 0 0 0% /system/object sharefs 0 0 0 0% /etc/dfs/sharetab swap 4852484 81980 4770504 2% /tmp /dev/lofi/1 226962 226962 0 100% /usr /tmp/solarismisc.zlib 27440 27440 0 100% /mnt/misc /usr/lib/libc/libc_hwcap1.so.1 226962 226962 0 100% /lib/libc.so.1 /mnt/misc/opt 27440 27440 0 100% /mnt/misc/opt fd 0 0 0 0% /dev/fd swap 4770520 16 4770504 1% /var/run rpool 2515968 22 444225 1% /rpool rpool/ROOT/opensolaris 2515968 1284492 444225 75% /a rpool/export 2515968 21 444225 1% /a/export rpool/export/home 2515968 19 444225 1% /a/export/home
(In reply to comment #3) > Te boot disk that I'm using (c8t0d0) has capacity of ~136GB. Here are > some details > > Part Tag Flag Cylinders Size Blocks > 0 swap wu 1 - 319 2.44GB (319/0/0) 5124735 > 1 root wm 320 - 17823 134.09GB (17504/0/0) 281201760 > 2 backup wm 0 - 17823 136.54GB (17824/0/0) 286342560 > 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 7.84MB (1/0/0) 16065 > 9 unassigned wm 0 0 (0/0/0) 0 ... > rpool/ROOT/opensolaris > 2515968 1284492 444225 75% /a > rpool/export 2515968 21 444225 1% /a/export > rpool/export/home 2515968 19 444225 1% /a/export/home That's interesting. Slice 0 is only 2.44 GB. Did the installer automatically preserve s1? Moving back over the installer component for further investigation.
By default, automated installer uses slice 0 for installation. As a workaround, you can change the slice to slice 1 in the AI manifest.
You can specify the slice in the AI manifest as follows <ai_target_device> <target_device_name>c0t0d0</target_device_name> <target_device_install_slice_number>1</target_device_install_slice_number> </ai_target_device> Refer to the AI document at http://dlc.sun.com/osol/docs/content/dev/AIinstall/customai.html#ievtoc
If by default AI uses slice 0 for installation then I would expect AI to check size of slice 0 (if exist) to see if that's enough to proceed the installation. In this case it continues the installation and when it rans out of space it complains which IMO is comprising the quality of AI. Another thing I would like to add here, if the administrator has provided whole disk (<c8t0d0>) information in the manifest file and has not provided any slice specific information then AI should automatically wipe out all the unnecessary slices first (especially Slice 0) and create the required ones with appropriate sizes.
Agreed with the comments #7 that AI should check the size of the slice to make sure that it is big enough to complete the installation. AI does it for X86 partitions. About the second comment, I don't think it is right to use the whole disk if the user has provided the target device and no slice information. AI could add one more field to specify whether whole disk can be used for installation.
Adding to the potential blocker list so we're sure to have this evaluated for 2009.06.
I think I had same issue, slice 0 is not big enough to hold AI. 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@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.
This will be release noted for 2009.06 release
(In reply to comment #8) > Agreed with the comments #7 that AI should check the size of the slice to make > sure that it is big enough to complete the installation. AI does it for X86 > partitions. Updating the bug synopsis to reflect this issue. > > About the second comment, I don't think it is right to use the whole disk if > the user has provided the target device and no slice information. AI could add > one more field to specify whether whole disk can be used for installation. This second issue is tracked by bug 6488.
*** Bug 12337 has been marked as a duplicate of this bug. ***