I've got an X4200 with 2 internal disk drives. The drive in slot 0 currently has an SMI label and is installed with s10u9. The drive in slot 1 has an EFI label and was part of a zpool named 'tank' sometime in the past.

When I try to install build 170 on the box, the installer fails. Here is what I see in the install log:

2011-07-27 12:58:32,890   InstallationLogger DEBUG      Executing 
target-discovery checkpoint
2011-07-27 12:58:32,890   InstallationLogger DEBUG      Executing: 
['/usr/sbin/croinfo', '-h', '-O', 'cAR']
2011-07-27 12:58:32,908   InstallationLogger DEBUG      c1t0d0:SYS:SYS/HD0
c1t1d0:SYS:SYS/HD1
:SYS:SYS/HD2
:SYS:SYS/HD3
2011-07-27 12:58:34,024   InstallationLogger DEBUG      Executing: 
['/usr/sbin/fstyp', '/dev/dsk/c1t1d0s0']
2011-07-27 12:58:34,069   InstallationLogger DEBUG      zfs
2011-07-27 12:58:34,384   InstallationLogger DEBUG      Executing: 
['/usr/sbin/fstyp', '/dev/dsk/c1t1d0s8']
2011-07-27 12:58:34,475   InstallationLogger DEBUG      unknown_fstyp (no 
matches)
2011-07-27 12:58:37,597   InstallationLogger ERROR      Error occurred during 
execution of 'target-discovery' checkpoint.
Traceback (most recent call last):
  File "/usr/lib/python2.6/vendor-packages/solaris_install/engine/__init__.py", 
line 816, in _execute_checkpoints
    checkpoint.execute(dry_run)
  File 
"/usr/lib/python2.6/vendor-packages/solaris_install/target/discovery.py", line 
792, in execute
    self.discover_entire_system()
  File 
"/usr/lib/python2.6/vendor-packages/solaris_install/target/discovery.py", line 
613, in discover_entire_system
    "%s" % new_disk.devpath)
AttributeError: 'NoneType' object has no attribute 'devpath'
2011-07-27 12:58:37,649   InstallationLogger ERROR      Aborting: Internal 
error in InstallEngine
Traceback (most recent call last):
  File "/usr/lib/python2.6/vendor-packages/solaris_install/engine/__init__.py", 
line 816, in _execute_checkpoints
    checkpoint.execute(dry_run)
  File 
"/usr/lib/python2.6/vendor-packages/solaris_install/target/discovery.py", line 
792, in execute
    self.discover_entire_system()
  File 
"/usr/lib/python2.6/vendor-packages/solaris_install/target/discovery.py", line 
613, in discover_entire_system
    "%s" % new_disk.devpath)
AttributeError: 'NoneType' object has no attribute 'devpath'
2011-07-27 12:58:37,705   InstallationLogger DEBUG      Traceback (most recent 
call last):
  File 
"/usr/lib/python2.6/vendor-packages/solaris_install/auto_install/auto_install.py",
 line 791, in execute_checkpoints
    dry_run=dry_run, callback=None)
  File "/usr/lib/python2.6/vendor-packages/solaris_install/engine/__init__.py", 
line 565, in execute_checkpoints
    thread.start()
  File "/usr/lib/python2.6/threading.py", line 477, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib/python2.6/vendor-packages/solaris_install/engine/__init__.py", 
line 816, in _execute_checkpoints
    checkpoint.execute(dry_run)
  File 
"/usr/lib/python2.6/vendor-packages/solaris_install/target/discovery.py", line 
792, in execute
    self.discover_entire_system()
  File 
"/usr/lib/python2.6/vendor-packages/solaris_install/target/discovery.py", line 
613, in discover_entire_system
    "%s" % new_disk.devpath)
AttributeError: 'NoneType' object has no attribute 'devpath'

Here are the contents between the 'target' tags in the manifest:

    <target>
      <disk whole_disk="false">
        <disk_keyword key="boot_disk"/>
        <partition action="use_existing_solaris2" part_type="191">
          <size val="0secs" start_sector="0"/>
        </partition>
      </disk>
      <logical noswap="false" nodump="false">
        <zpool name="rpool" action="create" is_root="true">
          <vdev name="vdev" redundancy="none"/>
          <be name="s11_170"/>
        </zpool>
      </logical>
    </target>

Based on what I see in the install log, '/usr/sbin/fstyp /dev/dsk/c1t1d0s8' fails causing the install to fail. Is this a known issue?

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

Reply via email to