On 14/07/2011 16:40, David Garcia - ONPIT wrote: > On 07/14/11 16:10, Darren Kenny wrote: >> >> On 14/07/2011 15:53, David Garcia - ONPIT wrote: >>> Hi, >>> >>> I'm trying to install a system with an iscsi target, and I'm getting >>> several errors regarding an incorrect disk configuration. >>> >>> I first tried to set<disk whole_disk="true"> but apparently that's not >>> available with iscsi targets. >>> SelectionError: Invalid request to use whole disk when specifying >>> partitions or slices on disk c0t600144F01569010000004D06060D0004d0 >>> >> This is true, it's either all or nothing on the whole-disk case (for now, >> we're >> working on changing this to be what people seem to expect). >> >> Given what you're doing, why specify the partitions at all, just set >> whole_disk >> to 'true' and let the installer create the layout you want of the whole disk >> being used by the root pool. > Sorry I wasn't clear before, that's what I did. When I set whole_disk to > true I didn't specify any partitions or slices. I got that error message: > SelectionError: Invalid request to use whole disk when specifying > partitions or slices on disk c0t600144F01569010000004D06060D0004d0 >
That's very strange... Never seen this happen before with whole_disk="true" - would be interested to see an install_log from this scenario. >>> I also tried creating a partition with the full size of the disk, but I >>> get the following error: >>> SelectionError: Could not determine the available size in pool 'rpool'. >> It would be useful to see the install_log file for this, but it's most likely >> because you've not allocated any partitions or slices to the root pool. >> >> Try changing the line to be: >> >> <partition action="create" name="1" part_type="191" in_zpool="rpool"/> > > I thought of that too, I tried that and no joy (same error): > SelectionError: Could not determine the available size in pool 'rpool'. > OK, the problem here is that you're both deleting and creating partition 1, try removing the delete of partition 1 - it shouldn't be necessary. A recent fix gone in should avoid this going forward, but for now you will need to remove it. > >>> I'd appreciate if someone could suggest a working manifest that I could >>> use in this case? >> Would be easier with the full install_log - but probably best to not send to >> this list, just send to me. > I sent you and email with the log. Yep, seen it, thanks. Try removing the delete as I say and try again. Thanks, Darren. > > Thanks, > David > >> Thanks, >> >> Darren. >> >>> Thanks, >>> David >>> >>> >>> Manifest used (relevant section): >>> >>> <!DOCTYPE auto_install SYSTEM "file:///usr/share/install/ai.dtd"> >>> <auto_install> >>> <ai_instance name="client" auto_reboot="false"> >>> <target> >>> <disk whole_disk="false"> >>> <iscsi name="iqn.1986-03.com.sun:01:server:client" target_lun="0" >>> target_port="3260"> >>> <ip>x.x.x.x</ip> >>> </iscsi> >>> <partition action="delete" name="1"/> >>> <partition action="delete" name="2"/> >>> <partition action="delete" name="3"/> >>> <partition action="delete" name="4"/> >>> <partition action="create" name="1" part_type="191"/> >>> <logical> >>> <zpool name="rpool" is_root="true"> >>> <filesystem name="export" mountpoint="/export"/> >>> <filesystem name="export/home"/> >>> <be name="solaris"/> >>> </zpool> >>> </logical> >>> </disk> >>> </target> >>> <software type="IPS"> >>> ... >>> > > _______________________________________________ caiman-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
