Re: [caiman-discuss] X3-2L in UEFI mode with 3Tb disks on s11-u1-24a

Thu, 20 Sep 2012 09:49:13 -0700 

Niall,
About the ai_manifest builder, see below .....obviously the gpt_partition is not implemented yet ;-) 

On 09/19/12 05:42 PM, Niall Power wrote:

On 20/09/2012 08:01, Paul de Nijs wrote:

Niall,


Oops, I missed the gpt_partition, I guess I have to read every 
*.dtd.x file in the future when there is a new build ;-)


Until more friendly manifest editing tools than vi come along ;-)



Ha, well I'm trying to do so, and even trying to catch up with all new 
requirements. Here is the one we use:


http://onager.us.oracle.com/asterix/cgi-bin/s11ai_manifest.pl


on the other hand, I think this is an option that should NOT exist at 
all.

What option specifically are you referring to?

the gpt_partition of course ...





If the install detects a disk >2TB it should install a GPT label, 
especially if you use:

<disk whole_disk="true">

It does exactly that, regardless of disk capacity. The only exception 
is those SPARC OBP firmwares that

do not yet have GPT boot capability (which is most of them at this point)

Duh, I just tried the gpt_partition, it really seems that I have to 
specify the <size> element. I never had to do that with <partition>


And then how come that 'format' still whines about the 2TB limit ?
should 'format -e' not solve this ?



The "-e" is expert mode according to format(1M). I suspect you want 
the '-L efi' argument to specify label type
as efi (just FYI, EFI is the same thing as GPT in terms of partition 
formats, but the solaris terminology is a

bit inconsistent)



Anyway, thanks for the help


No problem


Paul

On 09/19/12 04:36 PM, Niall Power wrote:

Hi Paul,


The problem is that you are not using GPT partitions in your 
manifest. Legacy DOS/MBR partitions and VTOC slices are limited to 
2TiB. If you want to lay out the disk manually yourself you should 
be using the <gpt_partition> element instead of 
<partition><slice/></partition> to use a disk and partitions > 2TiB



The error message is not all that useful I would admit - looks like 
it tripped over if anything.



Alternatively you can just remove the partition layout from the 
manifest and AI will layout the disk with a GPT partition table for 
you automatically



One other thing to note is that with GRUB2, Solaris can boot from 
disk (GTP) partitions > 2 TiB even on BIOS X86 systems, and so we 
now use GPT by default on all X86 and GPT capable SPARC systems.


Hope this helps,
Niall


On 20/09/2012 07:01, Paul de Nijs wrote:

All,


I wanted to test the UEFI capabilities for partitions > 2Tb on a 
X3-2L server, however I get this error when tyinstalling:



2012-09-19 16:35:37,136   InstallationLogger CRITICAL   Failed 
Checkpoints:

2012-09-19 16:35:37,186   InstallationLogger ERROR

2012-09-19 16:35:37,236   InstallationLogger ERROR              
target-selection

2012-09-19 16:35:37,286   InstallationLogger ERROR

2012-09-19 16:35:37,336   InstallationLogger ERROR      Checkpoint 
execution error:

2012-09-19 16:35:37,387   InstallationLogger ERROR

2012-09-19 16:35:37,437   InstallationLogger ERROR              
list index out of range

2012-09-19 16:35:37,487   InstallationLogger ERROR

2012-09-19 16:35:37,537   InstallationLogger INFO       Automated 
Installation Failed.  See install log at /system/volatile//install_log
2012-09-19 16:35:37,587   InstallationLogger DEBUG      Shutting 
down Progress Handler


my manifest looks like:

<?xml version="1.0" encoding="UTF-8"?>
<!--
Generated by: Asterix 2.4.3 for host: sbm-4270m3-01 on 2012-09-19 16:25

Source:  
sbm-ai:/install/AI/Jumpstart_data/hdd00_hdd01_zfs_mirrored.s11_x86_ai.xml

Profile: hdd00_hdd01_zfs_mirrored
AI_SERVICE=http://10.80.182.6:10101
-->
<!DOCTYPE auto_install SYSTEM "file:///usr/share/install/ai.dtd.1">
<auto_install>
<ai_instance name="default" auto_reboot="true">
<target>
<disk whole_disk="true">
<disk_name name="HDD00" name_type="receptacle"/>
<partition name="1" action="create" part_type="191">
<slice name="6" action="create" force="true">
<size val="100mb"/>
</slice>
<slice name="7" action="create" force="true">
<size val="100mb"/>
</slice>

<slice name="0" action="create" in_vdev="rpoolmirrored" 
in_zpool="rpool"/>

</partition>
</disk>
<disk whole_disk="true">
<disk_name name="HDD01" name_type="receptacle"/>
<partition name="1" action="create" part_type="191">
<slice name="6" action="create" force="true">
<size val="100mb"/>
</slice>
<slice name="7" action="create" force="true">
<size val="100mb"/>
</slice>

<slice name="0" action="create" in_vdev="rpoolmirrored" 
in_zpool="rpool"/>

</partition>
</disk>
<logical noswap="false" nodump="false">
<zpool name="rpool" action="create" is_root="true">
<vdev name="rpoolmirrored" redundancy="mirror"/>
<filesystem name="export" action="create" mountpoint="/export"/>
<filesystem name="export/home" action="create"/>
</zpool>
</logical>
</target>
<software type="IPS">
<source>
<publisher name="solaris">
<origin name="http://sbm-ai.us.oracle.com/s11_1-24a"/>
</publisher>
<publisher name="sae">
<origin name="http://sbm-ai.us.oracle.com/sae"/>
</publisher>
</source>
<software_data action="install">
<name>pkg://solaris/entire</name>
<name>pkg://solaris/group/system/solaris-large-server</name>
<name>pkg://solaris/storage/svm</name>
<name>pkg://solaris/storage/metassist</name>
<name>pkg://sae/AIPostAsterix</name>
</software_data>
</software>
</ai_instance>
</auto_install>


I think I booted in UEFI (well the system is set to do uefi in the 
bios screen).


my dhcp-entry (yes it's solaris dhcp)

root@sbm-ai:~# dhtadm -P | grep sbm-4270m3-01

sbm-4270m3-01           Macro           
:BootSrvA=10.80.182.6:BootFile="x86_s11_1-24a-x86/boot/grub/grub2netx64.efi":Include=10.80.182.0:


and 'format -e' still whines:

root@sbm-4270m3-01:/system/volatile#  format -e
Searching for disks...done

c0t5000CCA01A212F4Cd0: configured with capacity of 2047.90GB
c0t5000CCA01A212C90d0: configured with capacity of 2047.90GB
c0t5000CCA01A322B10d0: configured with capacity of 2047.90GB
c0t5000C50034E0E513d0: configured with capacity of 2047.90GB
c0t5000CCA01A20671Cd0: configured with capacity of 2047.90GB
c0t5000CCA01A3FC780d0: configured with capacity of 2047.90GB
c0t5000CCA01A35EAFCd0: configured with capacity of 2047.90GB
c0t5000C50040D1C6F7d0: configured with capacity of 2047.90GB
c0t5000C50034E0E3E3d0: configured with capacity of 2047.90GB
c0t5000CCA01A35EB1Cd0: configured with capacity of 2047.90GB
c0t5000C50034E0E40Fd0: configured with capacity of 2047.90GB
c0t5000C50034E0E4BBd0: configured with capacity of 2047.90GB
c0t5000C5003C121463d0: configured with capacity of 279.38GB
c7t0d0: configured with capacity of 3.61GB


AVAILABLE DISK SELECTIONS:

       0. c0t5000CCA01A212F4Cd0 <HITACHI-H7230AS60SUN3.0T-A120 cyl 
44556 alt 2 hd 255 sec 378>

          /scsi_vhci/disk@g5000cca01a212f4c
          /dev/chassis/CONCORD.1201FM5013/HDD00/disk

       1. c0t5000CCA01A212C90d0 <HITACHI-H7230AS60SUN3.0T-A120 cyl 
44556 alt 2 hd 255 sec 378>

          /scsi_vhci/disk@g5000cca01a212c90
          /dev/chassis/CONCORD.1201FM5013/HDD01/disk

       2. c0t5000CCA01A322B10d0 <HITACHI-H7230AS60SUN3.0T-A120 cyl 
44556 alt 2 hd 255 sec 378>

          /scsi_vhci/disk@g5000cca01a322b10
          /dev/chassis/CONCORD.1201FM5013/HDD02/disk

       3. c0t5000C50034E0E513d0 <SEAGATE-ST33000SSSUN3.0T-064A cyl 
44556 alt 2 hd 255 sec 378>

          /scsi_vhci/disk@g5000c50034e0e513
          /dev/chassis/CONCORD.1201FM5013/HDD03/disk

       4. c0t5000CCA01A20671Cd0 <HITACHI-H7230AS60SUN3.0T-A120 cyl 
44556 alt 2 hd 255 sec 378>

          /scsi_vhci/disk@g5000cca01a20671c
          /dev/chassis/CONCORD.1201FM5013/HDD04/disk

       5. c0t5000CCA01A3FC780d0 <HITACHI-H7230AS60SUN3.0T-A120 cyl 
44556 alt 2 hd 255 sec 378>

          /scsi_vhci/disk@g5000cca01a3fc780
          /dev/chassis/CONCORD.1201FM5013/HDD05/disk

       6. c0t5000CCA01A35EAFCd0 <HITACHI-H7230AS60SUN3.0T-A120 cyl 
44556 alt 2 hd 255 sec 378>

          /scsi_vhci/disk@g5000cca01a35eafc
          /dev/chassis/CONCORD.1201FM5013/HDD06/disk

       7. c0t5000C50040D1C6F7d0 <SEAGATE-ST33000SSSUN3.0T-064A cyl 
44556 alt 2 hd 255 sec 378>

          /scsi_vhci/disk@g5000c50040d1c6f7
          /dev/chassis/CONCORD.1201FM5013/HDD07/disk

       8. c0t5000C50034E0E3E3d0 <SEAGATE-ST33000SSSUN3.0T-064A cyl 
44556 alt 2 hd 255 sec 378>

          /scsi_vhci/disk@g5000c50034e0e3e3
          /dev/chassis/CONCORD.1201FM5013/HDD08/disk

       9. c0t5000CCA01A35EB1Cd0 <HITACHI-H7230AS60SUN3.0T-A120 cyl 
44556 alt 2 hd 255 sec 378>

          /scsi_vhci/disk@g5000cca01a35eb1c
          /dev/chassis/CONCORD.1201FM5013/HDD09/disk

      10. c0t5000C50034E0E40Fd0 <SEAGATE-ST33000SSSUN3.0T-064A cyl 
44556 alt 2 hd 255 sec 378>

          /scsi_vhci/disk@g5000c50034e0e40f
          /dev/chassis/CONCORD.1201FM5013/HDD10/disk

      11. c0t5000C50034E0E4BBd0 <SEAGATE-ST33000SSSUN3.0T-064A cyl 
44556 alt 2 hd 255 sec 378>

          /scsi_vhci/disk@g5000c50034e0e4bb
          /dev/chassis/CONCORD.1201FM5013/HDD11/disk

      12. c0t5000C5003C121463d0 <SEAGATE-ST930003SSUN300G-0B70 cyl 
46873 alt 2 hd 20 sec 625>

          /scsi_vhci/disk@g5000c5003c121463
          /dev/chassis/CONCORD.1201FM5013/HDD12/disk

      13. c0t5000C5000C942F03d0 <SEAGATE-ST914602SSUN146G-0603 cyl 
17846 alt 2 hd 255 sec 63>

          /scsi_vhci/disk@g5000c5000c942f03
          /dev/chassis/CONCORD.1201FM5013/HDD13/disk
      14. c7t0d0 <ORACLE-SSM-PMAP cyl 1848 alt 2 hd 128 sec 32>
          /pci@0,0/pci108e,484e@1a/hub@1/storage@2/disk@0,0
Specify disk (enter its number): 11
selecting c0t5000C50034E0E4BBd0
[disk formatted]
No Solaris fdisk partition found.


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 disk ID
        scsi       - independent SCSI mode selects
        cache      - enable, disable or query SCSI disk cache
        volname    - set 8-character volume name
        !<cmd>     - execute <cmd>, then return
        quit
format> fdisk
No fdisk table exists. The default partition for the disk is:

  a 100% "SOLARIS System" partition


Type "y" to accept the default partition,  otherwise type "n" to 
edit the

 partition table.

WARNING: Disk is larger than 2TB. Solaris partition will be limited 
to 2 TB.


grub menu:

root@sbm-ai:/tftpboot# cat grub.cfg.sbm-4270m3-01
default=0
timeout=30
menuentry " s11_1-24a-x86 Jumpstart Install" {
        echo ""
        echo "Loading /platform/i86pc/kernel/amd64/unix ..."

        multiboot2 
/x86_s11_1-24a-x86/platform/i86pc/kernel/amd64/unix 
/platform/i86pc/kernel/amd64/unix -v -B 
console=ttya,livemode=text,livessh=enable,install=true,install_debug=enable,install_media=http://10.80.182.6/OS/solaris11_x86/s11_1-24a-x86,install_boot=http://10.80.182.6/OS/solaris11_x86/s11_1-24a-x86/boot,install_service=default,install_svc_address=10.80.182.6:10101

        echo "Loading /platform/i86pc/amd64/boot_archive ..."
        module2 /x86_s11_1-24a-x86/platform/i86pc/amd64/boot_archive
}
menuentry " s11_1-24a-x86 Boot image ONLY" {
        echo ""
        echo "Loading /platform/i86pc/kernel/amd64/unix ..."

        multiboot2 
/x86_s11_1-24a-x86/platform/i86pc/kernel/amd64/unix 
/platform/i86pc/kernel/amd64/unix -v -B 
console=ttya,livemode=text,livessh=enable,install_debug=enable,install_media=http://10.80.182.6/OS/solaris11_x86/s11_1-24a-x86,install_boot=http://10.80.182.6/OS/solaris11_x86/s11_1-24a-x86/boot,install_service=default,install_svc_address=10.80.182.6:10101

        echo "Loading /platform/i86pc/amd64/boot_archive ..."
        module2 /x86_s11_1-24a-x86/platform/i86pc/amd64/boot_archive
}


what am I missing here ? I expected to make a partition >2TB. While 
this is obviously not possible, why is the install failing with the 
above error ? (oh, and this happens also in s12_0_0_4 BTW)


Thanks

Paul


--




Paul de Nijs | Principal Software Engineer | Performance 
Technologies | +1.503.495.7882

Oracle Strategic Applications Engineering (SAE)
3295 NW 211th Terrace | Hillsboro, OR 97124-7110




_______________________________________________
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


--




Paul de Nijs | Principal Software Engineer | Performance Technologies 
| +1.503.495.7882

Oracle Strategic Applications Engineering (SAE)
3295 NW 211th Terrace | Hillsboro, OR 97124-7110






--




Paul de Nijs | Principal Software Engineer | Performance Technologies | 
+1.503.495.7882

Oracle Strategic Applications Engineering (SAE)
3295 NW 211th Terrace | Hillsboro, OR 97124-7110



_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss






















					Reply via email to