how to make x86.miniroot to select "Custom Jumpstart" by default
I am trying to perform an unattended install for solaris x86 using pxe, tftp and dhcp setup. The tftp server send the x86.miniroot image all right and the stage 1 of the boot goes through. However at the next stage i am presented with the following menu:
Solaris Interactive (default)
Custom JumpStart
Solaris Interactive Text (Desktop session)
Solaris Interactive Text (Console session)
Apply driver updates
Single user shell
And it defaults to Solaris interactive. How can i cause it to default to custom jumpstart and do a completely unattended install?
Thanks,
Atul
[636 byte] By [
AtulVGore] at [2007-11-26 11:28:29]
# 1
You need to hack /tftpboot/boot/grub/menu.lst
Here is an example, its what i use in my jumpstart environment, basically it gives the user a chance to choose between an automatic installation and a single-user shell.
The automatic jumpstart is selected after 5 minutes (so far no machine have been accidentally reinstalled, touch wood).
Note that you'll have to replace the IP's and paths accordingly, also, it will do a text-based installation since i didn't wanted a window based one.
bash-3.00# cat /tftpboot/boot/grub/menu.lst
default=0
timeout=300
title Solaris_10 6_06 Hands Off Installation a'la Magnus
kernel /I86PC.Solaris_10-1/multiboot kernel/unix -B install_config=10.91.1.140:/export/install/config,input-device=keyboard,output- device=screen,install_media=10.91.1.140:/export/install/Solaris/i386/10/6_06,sys id_config=10.91.1.140:/export/install/sysidcfg,install_boot=10.91.1.140:/export/ install/Solaris/i386/10/6_06/Solaris_10/Tools/Boot -m install w
module /I86PC.Solaris_10-1/x86.miniroot
title Solaris_10 6/06 Single User
kernel /I86PC.Solaris_10-1/multiboot kernel/unix -s
module /I86PC.Solaris_10-1/x86.miniroot
bash-3.00#
hope this helps, it took me a while to find out.
.7/M.
# 2
hmm, this forum messes up the line breaks and things at times. The original file have one line which starts with "kernel", then the next line starts with "module", don't know if it actually matters, but its probably good to know. .7/M.
# 3
my menu.lst looks like:
default=0
timeout=30
title Solaris_10 Jumpstart
kernel /I86PC.Solaris_10-1/multiboot kernel/unix -B
install_config=10.20.26.201:/space/jumpstart/config,
install_media=10.20.26.201:/space/jumpstart/solaris10/Solaris_10_x86/install/x8 6_10,
install_boot=10.20.26.201:/space/jumpstart/solaris10/Solaris_10_x86/boot/boot
(don't mind the new lines, i put them for readability)
I don't have the sysidconfig clause that you have in your configuration.
Also what does the
"-m install w" switches do?
Is that what is causing the install to show the menu instead of directly trying to install ?
-Atul
> You need to hack /tftpboot/boot/grub/menu.lst
>
> Here is an example, its what i use in my jumpstart
> environment, basically it gives the user a chance to
> choose between an automatic installation and a
> single-user shell.
>
> The automatic jumpstart is selected after 5 minutes
> (so far no machine have been accidentally
> reinstalled, touch wood).
>
> Note that you'll have to replace the IP's and paths
> accordingly, also, it will do a text-based
> installation since i didn't wanted a window based
> one.
>
> bash-3.00# cat /tftpboot/boot/grub/menu.lst
> default=0
> timeout=300
> title Solaris_10 6_06 Hands Off Installation a'la
> Magnus
> kernel /I86PC.Solaris_10-1/multiboot
> kernel/unix -B
> install_config=10.91.1.140:/export/install/config,inp
> t-device=keyboard,output-device=screen,install_media=1
> 0.91.1.140:/export/install/Solaris/i386/10/6_06,sysid_
> config=10.91.1.140:/export/install/sysidcfg,install_bo
> ot=10.91.1.140:/export/install/Solaris/i386/10/6_06/So
> laris_10/Tools/Boot -m install w
>module /I86PC.Solaris_10-1/x86.miniroot
> e Solaris_10 6/06 Single User
> kernel /I86PC.Solaris_10-1/multiboot
> kernel/unix -s
>module /I86PC.Solaris_10-1/x86.miniroot
> 00#
>
> hope this helps, it took me a while to find out.
>
> .7/M.
# 4
the 'install' in -m install w tells the system to install it self, w is a short form of 'nowin' which prevents the jumpstart from attempting to configure the X-server.. .7/M.
# 5
I tried using the menu.lst entry that you mention, with one difference.I did not provide sysidconfig=.... clause.What is this clause? and is it absolutely necessary for an automated install?Please advice.Thanks,Atul
# 6
I use the sysidcfg file to set things like:
timezone
netmask
timeserver (which i set to localhost, which prevents the installation from asking about the time).
locale
root password
Its also the place where you can prevent the system from asking you about kerberos by setting:
security_policy=none
You are also supposed to be able to set the monitor/keyboard/mouse types for X86 systems, but i never got that to work.
.7/M.
# 7
When I add the '-m install' after the -B switch in the menu.lst
I get the following error after rebooting:
File not executable.
panic: no entry point in
Press any key to reboot
Any idea why i would get this?
my menu.lst looks like:
title Solaris_10 Jumpstart
kernel /I86PC.Solaris_10-2/multiboot kernel/unix -B -m install install_config=10.20.26.201:/space/jumpstart/config,sysid_config=10.20.26.201:/ space/jumpstart/BladeLogic/sysidconfig,install_media=10.20.26.201:/space/jumpsta rt/solaris10/Solaris_10_x86/install/x86_10,install_boot=10.20.26.201:/space/jump start/solaris10/Solaris_10_x86/install/x86_10/boot
module /I86PC.Solaris_10-2/x86.miniroot
# 8
The earlier example had it not on the unix line but on the install_boot= line.-- Darren
# 9
> The earlier example had it not on the unix line but
> on the install_boot= line.
>
> --
> Darren
Did not really help putting those arguments in the correct place.
It now gives me rpcbind errors !
I am really stuck at this problem now.
# 10
Hmm, do you mean that you actually get problems with rpcbind, or that rpcbind is the last things printed on the screen before the installation hangs?Try and snoop the jumpstart client from the jumpstart server and see if there is any ongoing communication between the two.
