Skip Navigation Links | |
Exit Print View | |
Oracle Solaris 10 8/11 Installation Guide: Network-Based Installations Oracle Solaris 10 8/11 Information Library |
Part I Planning to Install Over the Network
1. Where to Find Oracle Solaris Installation Planning Information
2. Preconfiguring System Configuration Information (Tasks)
3. Preconfiguring With a Naming Service or DHCP
Part II Installing Over a Local Area Network
4. Installing From the Network (Overview)
5. Installing From the Network With DVD Media (Tasks)
6. Installing From the Network With CD Media (Tasks)
7. Patching the Miniroot Image (Tasks)
8. Installing Over the Network (Examples)
9. Installing From the Network (Command Reference)
Part III Installing Over a Wide Area Network
11. Preparing to Install With WAN Boot (Planning)
12. Installing With WAN Boot (Tasks)
13. SPARC: Installing With WAN Boot (Tasks)
14. SPARC: Installing With WAN Boot (Examples)
Problems With Setting Up Network Installations
Problems With Booting a System
Booting From Media, Error Messages
Booting From Media, General Problems
Booting From the Network, Error Messages
Booting From the Network, General Problems
Initial Installation of the Oracle Solaris OS
x86: To Check IDE Disk for Bad Blocks
Upgrading the Oracle Solaris OS
System Panics When Upgrading With Live Upgrade Running Veritas VxVM
x86: Service Partition Not Created by Default on Systems With No Existing Service Partition
To Install Software From a Network Installation Image or From the Oracle Solaris DVD
To Install From the Oracle Solaris Software - 1 CD or From a Network Installation Image
The upgrade fails and the system cannot be soft-booted. The failure is for reasons beyond your control, such as a power failure or a network connection failure.
The Oracle Solaris installation program determines if the system has been partially upgraded and continues the upgrade.
The following errors can occur when you use Live Upgrade and the GRUB boot loader on an x86 based system.
ERROR: The media product tools installation directory path-to-installation-directory does not exist.
ERROR: The media dirctory does not contain an operating system upgrade image.
Description: The error messages are seen when using the luupgrade command to upgrade a new boot environment.
Cause: An older version of Live Upgrade is being used. The Live Upgrade packages you have installed on your system are incompatible with the media and the release on that media.
Solution: Always use the Live Upgrade packages from the release you are upgrading to.
Example: In the following example, the error message indicates that the Live Upgrade packages on the system are not the same version as on the media.
# luupgrade -u -n s10u1 -s /mnt Validating the contents of the media </mnt>. The media is a standard Solaris media. ERROR: The media product tools installation directory </mnt/Solaris_10/Tools/Boot/usr/sbin/install.d/install_config> does not exist. ERROR: The media </mnt> does not contain an operating system upgrade image.
ERROR: Cannot find or is not executable: </sbin/biosdev>.
ERROR: One or more patches required by Live Upgrade has not been installed.
Cause: One or more patches required by Live Upgrade are not installed on your system. Beware that this error message does not catch all missing patches.
Solution: Before using Live Upgrade, always install all the required patches. Ensure that you have the most recently updated patch list by consulting (My Oracle Support). Search for the knowledge document 1004881.1 - Solaris Live Upgrade Software Patch Requirements (formerly 206844) on My Oracle Support.
ERROR: Device mapping command </sbin/biosdev> failed. Please reboot and try again.
Cause: Reason 1: Live Upgrade is unable to map devices because of previous administrative tasks.
Solution: Reason 1: Reboot the system and try Live Upgrade again
Cause: Reason 2: If you reboot your system and get the same error message, you have two or more identical disks. The device mapping command is unable to distinguish between them.
Solution: Reason 2: Create a new dummy fdisk partition on one of the disks. See the fdisk(1M) man page. Then reboot the system.
Cannot delete the boot environment that contains the GRUB menu
Cause: Live Upgrade imposes the restriction that a boot environment cannot be deleted if the boot environment contains the GRUB menu.
Solution: Use lumake(1M) or luupgrade(1M) commands to reuse that boot environment.
The file system containing the GRUB menu was accidentally remade. However, the disk has the same slices as before. For example, the disk was not re-sliced.
Cause: The file system that contains the GRUB menu is critical to keeping the system bootable. Live Upgrade commands do not destroy the GRUB menu. But, if you accidentally remake or otherwise destroy the file system containing the GRUB menu with a command other than a Live Upgrade command, the recovery software attempts to reinstall the GRUB menu. The recovery software puts the GRUB menu back in the same file system at the next reboot. For example, you might have used the newfs or mkfs commands on the file system and accidentally destroyed the GRUB menu. To restore the GRUB menu correctly, the slice must adhere to the following conditions:
Contain a mountable file system
Remain a part of the same Live Upgrade boot environment where the slice resided previously
Before rebooting the system, make any necessary corrective actions on the slice.
Solution: Reboot the system. A backup copy of the GRUB menu is automatically installed.
The GRUB menu's menu.lst file was accidentally deleted.
Solution: Reboot the system. A backup copy of the GRUB menu is automatically installed.