Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type FAB (standard) Sure Solution 1001327.1 : The new PCI+ IB_SSC IO Assembly is not properly supported by any release of Solaris 8.
PreviouslyPublishedAs 201789 Product Sun Fire E2900 Server Sun Fire V1280 Server Bug Id <SUNBUG: 5076027>, <SUNBUG: 6241837>, <SUNBUG: 6243897> Part
Impact While booting Solaris 8 2/04 from the CD or DVD, the boot sequence terminates with the following error messages : {0} ok boot cdrom Rebooting with command: boot cdrom panic[cpu0]/thread=10408000: vfs_mountroot: cannot mount root 0000000010407970 genunix:vfs_mountroot+70 (104b7c00, 0, 0, 104bac88, 10, 14) rebooting... Resetting ... Symptoms Installation or booting Solaris 8 2/04 from DVD or CD will fail on E2900/ V1280 systems that have PCI+ IB_SSC IO Assembly installed. Since no released version of Solaris 8 properly supports the PCI+ IB_SSC IO Assembly, customers cannot install or boot Solaris 8 on systems with the PCI+ IB_SSC IO Assembly via DVD or CD. Systems installing or booting Solaris 8 2/04 via Jumpstart will not recognize the DVD-ROM, will not recognize all of the hardware, and will be likely to eventually panic. Root Cause Full support for the PCI+ IB_SSC was added to Solaris 8 after the Solaris 8 2/04 release. Workaround Support for the new PCI+ IB_SSC IO Assembly was added primarily via Change Requests 5076027, 6241837, and 6243897. Prior driver versions will not recognize all of the components of the new hardware or operate reliably. Resolution Please note that while installing patches 116962-09, 108974-47, 111792-13, and 117000-05 will allow the system to recognize the DVD-ROM device and the PCI+ IB_SCC IO Assembly in general, many other patches are needed to bring the system up to date from the revisions installed in the Solaris 8 2/04 release. In particular, the system will be well behind the current kernel version contained in patch 117350. Use of the Enterprise Installation Standards (EIS) to set up the system is recommended. A) Comprehensive Field Instructions: In order to get the system to recognize the new hardware, the easiest solution is to perform a network based, Jumpstart install, and then patch the system. Option 1 is to add the patch manually. Option 2 is to modify the Jumpstart process to add the patch automatically. Option 3 is to create a Flash Archive of a patched system. Option 4 describes obtaining an alternate DVD0 when necessary. Option 1) Patch the OS installation on the system to recognize the DVD-ROM drive 1b) Install Solaris 8 2/04 via Jumpstart from this image. 1c) After the system boots, install patches 116962-09, 108974-47, 111792-13, and 117000-05 or later, and do a reconfiguration reboot. Option 2) Create a Jumpstart finish script to add patches 116962-09, 108974-47, 111792-13, 117000-05 or later as part of the installation process. 2a) Create a network installation image from the customer's Solaris 8 2/04 Media. - See the "Preparing to Install ... From the Network" chapters of the Solaris 8 Advanced Installation Guide for instructions. 2b) Create a finish script to install patches 116962-09, 108974-47, 111792-13, 117000-05 or later. - See the "Adding Packages or Patches With a Finish Script" section of the "Using Optional Custom JumpStart Features" chapter of the Solaris 8 Advanced Installation Guide. 2c) Install Solaris 8 2/04 via Jumpstart image which will use the the finish script to install the patches. Option 3) Create a Flash Archive of a patched system. 3a) Set up a system as described in option 1. 3b) Use this patched system to create a Flash archive. 3c) Use this archive to install Solaris 8 on the remaining systems as discussed in the "Solaris Flash (Overview and Planning)" chapter of the Solaris 8 Advanced Installation Guide. Option 4) If the installation must be done using the DVD-ROM, then the user must first obtain a copy of an alternate Solaris 8 2/04 DVD0, part number 708-0124-10. They can then boot from this DVD and follow the instructions presented at the console before inserting the standard installation DVD. B) Additional Comments: This issue does not affect booting or installation of Solaris 10 3/05 HW1 on E2900/V1280 systems with the PCI+ IB_SSC IO Assembly. Booting and installation of Solaris 9 9/05 on E2900/V1280 is covered in FIN 102100. Regardless of the installation method chosen, the Enterprise Installation Standards (EIS) are recommended for setting up the system. For reference, the alternative Solaris 8 DVD0 includes the patches needed for proper operation of the PCI+ IB_SSC as well as those required to properly install from the alternative DVD0. This list is explicitly not intended to be a complete listing of all patches recommended for V1280/E2900 systems. 117000-05 C) Special Considerations: Due to changes in the device paths between the PCI and PCI+ IB_SSC IO Assemblies, it not possible to patch or upgrade an existing installation to support the new PCI+ IB_SSC IO Assembly. A new install of Solaris is required. If you want the system to always reboot Solaris from the boot device that you've specified, you may need to change the system's default boot device (OBP boot-device parameter) using the eeprom(1M) command after installing Solaris software. In particular, if the chosen boot device is not the current default boot device, you must update the boot-device parameter. Modification History Date: 12-JUL-2006
Previously Published As 102133 Internal Comments Related Information
Internal Contributor/submitter Chad.Lewis@sun.com Internal Eng Business Unit Group KE Authors Internal Eng Responsible Engineer Patrick.Morrisey@Sun.COM Internal Services Knowledge Engineer sean.hassall@sun.com Internal Resolution Patches 116962-09, 108974-47, 111792-13, 117000-05 Internal Kasp FAB Legacy ID 102133 Internal Sun Alert & FAB Admin Info Critical Category: Significant Change Date: Avoidance: Workaround Responsible Manager: null Original Admin Info: null Product_uuid 63ff680d-0598-11d8-84cb-080020a9ed93|Sun Fire E2900 Server 6a74b2f9-bbd8-4b2c-870d-b6b73d6e224f|Sun Fire V1280 Server Attachments This solution has no attachment |
||||||||||||
|