BigAdmin System Administration Portal
XPerts

BigAdmin XPerts

XPert Transcript: Solaris 10 OS Installation
Sundar Yamunachari - Sun Microsystems, Inc.

XPerts Home
Last Updated June 2005
 
 
Page 4 (31-41 of 41 results) Pages:  Previous « | 1 - 2 - 3 - 4
  1. Can I run the Solaris 10 OS on an x86 computer with 128 MB of memory?
  2. Is there a tool available to verify the syntax of a file containing a "sysidcfg" set of entries?
  3. During install, the installer fails to create the root file system... The installer fails to "newfs" *any* slice on this disk.
  4. How can I create/configure a container/zone to use DHCP?
  5. Can I install the Sun OS on a PC running Windows XP Home edition? If so, then how?
  6. I have a Sun Ultra 5/10, and I want to install the Solaris 10 OS. I got this message: "NOTE: Not enough memory for graphical installation."
  7. I can't boot up or install software (Blade 100 - Solaris 10 OS).
  8. I just finished configuring our JumpStart server to handle x86 clients, but for some reason the output is getting sent to a dtterm window running inside a windowing environment.
  9. Are there any limitations to using DHCP instead of bootparams for network installations?
  10. Are there any flags or values that can be used to debug the x86 Solaris JumpStart process? We have seen some weird issues, and would love to get some detailed debugging information during the network installation.
  11. I have a Solaris 10 laptop screen resolution problem, limited to 640x480 on HP zv5000. SunSolve document 74551 says use 'sax2', but there's no such command in distribution.

Q: I have an x86 computer with 128 Mbyte of memory. Is this sufficient for running Solaris 10 x86? What features of the Solaris 10 OS can I turn off to free up more memory?

A: The Solaris 10 OS can be installed with 128 Mbyte of memory. Running Solaris 10 with a graphical desktop with 128 Mbyte will be extremely slow. With 128 Mbyte, it will be difficult to take advantage of all the new and exciting features of the Solaris 10 OS.

Back to top


Q: Regarding your example of a "minimum sysidcfg", are all the entries on a single line, or will the sysidcfg you've presented here work correctly *exactly* as it is written? Is there a tool available to verify the syntax of a file containing a sysidcfg set of entries?

A: Referring to my answer to question 6, sysidcfg is a name of the text file to be placed in the directory where your installation is configured to look using add_install_client. The entries are not in a single line. Each entry is of the form name=value and is on a separate line. If the value extends beyond a single line, it is enclosed by curly brackets.

The minimum sysidcfg refers to the set of configuration parameters represented by the left-hand side of the name-value pair. The value part of the entry will be different for your situation. If you set up the value part correctly, the jumpstart install will not ask any questions during the installation process.

Unfortunately, no tools are available to verify the syntax of the sysidcfg file as of now. Since the sysidcfg entries are becoming complex, it may be a good idea to create one.

Back to top


Q: Machine is Sun Fire v20z; disk is Fujitsu MAT3147NC; disk size is 146 Gb. During install, the installer fails to create the root file system. Popping up a terminal I ran format and saw that the disk had been fdisk-ed and partitioned successfully. So I did the following:
newfs /dev/rdsk/c1t0d0s0
And I got the following error message:
 With 5825 sectors per cylinder, minimum cylinder per group is 16.
 This requires the fragment size to be changed from 1024 to 2048
 Please re-run mkfs with corrected parameters.
So I did:
newfs -f 2048 /dev/rdsk/c1t0d0s0
And it runs successfully to completion and I can mount and write to the newfs-ed slice. In this case, the desired size for c1t0d0s0 is 18 Gb. Thinking this might be an issue because of the size of the slice, I tried to newfs a smaller, 8 Gb slice: same error message. So the installer will fail to newfs *any* slice on this disk! How do I get past this situation? How can I "tell" the installer to use -f 2048 while creating file systems during installation?

A: This is a known problem in the Solaris 10 FCS release and will be fixed in Solaris 10 update 1 release. In the meantime, there is a patch available to resolve this problem. The patch id is 119375-01 and you can download from sunsolve.sun.com. Please follow the special install instructions to clear the Solaris label from the disk.

Back to top


Q: How can I create/configure a container/zone to use DHCP?

A: Solaris 10 doesn't support using DHCP to configure non-global zones. But this is on the roadmap and is scheduled to be available in Solaris 10 update releases.

Back to top


Q: Can I install the Sun OS on a PC running Windows XP Home edition? If so, then how?

A: It depends on the type of PC. If it is supported to run the Solaris 10 OS, you can install and run that OS. Please visit the HCL (http://www.sun.com/bigadmin/hcl) for more information. Also check the document Multi-booting Solaris and other operating systems for setting up multiple operating systems on your PC.

Back to top


Q: I have a Sun Ultra 5/10, and I want to install the Solaris 10 OS. I got this message: "NOTE: Not enough memory for graphical installation."

A: The Solaris 10 installation program automatically chooses the mode (text or graphical) of install based on the amount of memory on the system. The installation requires at least 384 MB physical memory to use the wizard-based graphical installer. The text- or console-based installer will be used if the physical memory is less than 384 MB. The system should have at least 128 MB memory for the Solaris install program to run. The install program checks both the system memory and available memory at the time of install and decides which mode to use. This note is letting the user know that the text method is selected.

Back to top


Q: I can't boot up (Blade 100 - Solaris 10 OS). Also, I can't install software -- the PC doesn't recognize the hardware (DVD drive) which I just replaced.

A: I need more information than given in the question about the Blade 100. For the PC, you need to find out whether the DVD drive you are using is supported by the Solaris 10 OS. Go to the HCL web site (http://www.sun.com/bigadmin/hcl) to see whether your configuration is supported.

Back to top


Q: I just finished configuring our JumpStart server to handle x86 clients, but for some reason the output is getting sent to a dtterm window running inside a windowing environment. The Xserver fires up directly after the following messages are displayed:
Using sysid configuration file  /sysidcfg
Search complete

Proposed  Window System Configuration For Installation:

[ ... ]

Discovering additional network configurations...

[ Xserver starts and displays the status in a dtterm ]
Is there a bootenv.rc or sysidcfg parameter to force output to the console? I checked the documentation on docs.sun.com, and reviewed the x86 client JumpStart BluePrints doc., but have been unable to find a setting to change this behavior.

A: By default the input device is set to keyboard and the output device is set to screen. You can change this while setting up the client by using the -b option in add_install_client. To set the input device, use the property name input-device, and for the output device use the property name output-device. You can only use this option for the x86 client that uses DHCP. You should only use this option in conjunction with the -d and -e options. For example, the following command on the install server sets up the client with Ethernet address 0:11:22:33:44:ee to use ttya for input and output.

# ./add_install_client -d -c jumpstart_server:/export/profiles \
-p config_server:/export/config  -b "input-device=ttya" \
-b "output-device=ttya" -e 0:11:22:33:44:ee i86pc

For more information refer to the Solaris 10 man pages for add_install_client(1M) and eeprom(1M).

Back to top


Q: Are there any limitations to using DHCP instead of bootparams for network installations?

A: There are more positives using DHCP compared to bootparams. The only limitation I could think of is that you need to configure the DHCP server after configuring the client using add_install_client. Given that most of the new PCs and laptops use PXE to configure, DHCP is the way to go.

Back to top


Q: Are there any flags or values that can be used to debug the x86 Solaris JumpStart process? We have seen some weird issues, and would love to get some detailed debugging information during the network installation.

A: If your Solaris JumpStart install fails or display error messages, you can run the JumpStart program pfinstall in dryrun mode. To create a temporary Solaris install environment, boot a system from a Solaris CD/DVD/network image (just as you would to install), answer any system identification questions, choose the Solaris Interactive Installation program, and exit out of the first screen that is presented. Then, from the shell, you can execute the pfinstall command.

You can create the profile in the /tmp directory and use the following command:

# /usr/sbin/install.d/pfinstall -D /tmp/prpfile

Running pfinstall in dryrun mode will not actually make any changes to your system. Instead it will check your profile and make sure that the system can be installed using the profile. See the man page for pfinstall(1M) for more information.

Back to top


Q: I have a Solaris 10 laptop screen resolution problem, limited to 640x480 on HP zv5000. SunSolve document 74551 says use 'sax2', but there's no such command in distribution.

A: SunSolve document 74551 is for Linux and not for the Solaris OS. You can use /usr/sbin/kdmconfig to configure or unconfigure keyboard, display, and mouse options for the Solaris 10 OS. Please see the man page kdmconfig(1M) for more information.

Back to top


BigAdmin