Sponsored Content
Operating Systems Solaris Jumpstart Error: Unsupported version (3.0). Post 302549603 by Siralos on Tuesday 23rd of August 2011 11:16:37 AM
Old 08-23-2011
[SOLVED] Jumpstart Error: Unsupported version (3.0).

Hello,

The OS version of the ZFS flar is Solaris 10 U9 .

Here is the screen output from my attempted jumpstart:

Code:
System identification is completed.
System identification complete.
Starting Solaris installation program...
Searching for JumpStart directory...
Using rules.ok from JumpServer:/opt/SUNWjet.
Checking rules.ok file...
Using begin script: Utils/begin
Using derived profile: Utils/begin
Using finish script: Utils/finish
Executing JumpStart preinstall phase...
Executing begin script "Utils/begin"...
Installation of ClientNew at 07:48 on 23-Aug-2011
Loading JumpStart Server variables
Loading Client configuration file
BASE_CONFIG: Running base_config begin script....
FLASH: Running flash begin script....
Begin script Utils/begin execution completed.
Searching for SolStart directory...
Checking rules.ok file...
Using begin script: install_begin
Using finish script: patch_finish
Executing SolStart preinstall phase...
Executing begin script "install_begin"...
Begin script install_begin execution completed.

Processing profile
        - Opening Flash archive

ERROR: Unsupported version (3.0).

ERROR: Flash installation failed
Solaris installation program exited.

Moderator's Comments:
Mod Comment Please use [CODE] tags when posting console output, ...


Thanks for the assistance ( Kinda new to forums) ...

I was thinking that the error might be referencing the version of JET installed on the Server..

Code:
 
The following package is currently installed:
   SUNWjet  Sun JumpStart Enterprise Toolkit
            (sparc,i386) 4.7


Last edited by Siralos; 08-29-2011 at 03:09 PM.. Reason: Solved
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

unsupported characters

Hi I am new to unix - can anyone give me an idea of the characters i should NOT be using in unix filenames - ie: i know not to use spaces and backslashes but not much else. Thanks John (1 Reply)
Discussion started by: jmalpas
1 Replies

2. Solaris

Jumpstart Error

I 've configured jumpstart and everything is fine but the installation starts asking human intervention and go till NFS conifugration .. Setting up Java. Please wait... Serial console, reverting to text install Beginning system identification... Searching for configuration file(s)... Using... (3 Replies)
Discussion started by: fugitive
3 Replies

3. Solaris

Error after Jumpstart

I have a Solaris 10 U6 flash nothing has changed on my Jumpstart expect for some finish files and profiles. after I jump either a client or a server I always get the same error the following files in / differ from the boot archive changed /kernel/drv/md.conf then I enter in the root... (4 Replies)
Discussion started by: deaconf19
4 Replies

4. Solaris

error in jumpstart while cretaing rules.ok with ./check

Hi Gurus, When i am running the ./check and i am getting below error Error in files "rules", line 92 hostname sample_host - host_class set_root_pw Error: Finish script missing: set_root_pw i do not have any begin or finish define in my rules file it just marked as - , the content... (2 Replies)
Discussion started by: kumarmani
2 Replies

5. Solaris

boot Error for jumpstart

Hi community, I am installing Solaris 10 using a jumpstart installation. Both Server and Client are in the same netmask. When I perform the "boot net - install" command, I receive the following error: Timeout waiting for ARP/RARP packets Timeout waiting for ARP/RARP packets Timeout... (1 Reply)
Discussion started by: Sunb3
1 Replies

6. Solaris

Jumpstart client flash archive error....

Hi , I am facing this issue while restoring flash archive from jumpstart server.The image was aroung 9 gb (5.9 release) and we have restored the other images successfully bigger than this size to other machines we have never faced this issue .Please advice me on this issue . Extracted 100 %... (0 Replies)
Discussion started by: knl.sundeep
0 Replies

7. Solaris

help me! jumpstart installation error

Hi actualy my two machines are sun sparc ultra 60. Both are same configuration. I am trying jumpstart Installation in my two machines, i got no errors in server side but in the client side actually it detects the server machine with correct hostname and domainname but after showed that it will... (2 Replies)
Discussion started by: Grovestreet
2 Replies

8. Solaris

Solaris 10 Jumpstart Error

Hey All, I'm trying to jump start a new Sun Server from an existing jump start server, but this last machine is giving me driver errors :s It doesn't make sense as we've built a few of these exact same servers just recently, but this last one displays: "No driver (or driver binding)... (2 Replies)
Discussion started by: UnxAdm1101
2 Replies

9. Red Hat

Unsupported hardware detected error for SSD hard drive

Hi, I am trying to install Oracle Linux 6.5 on vmware workstation 9, but during the installation i am getting popup box with below message. unsupported hardware detected The hardware ( or a combination thereof) is not supported by Oracle Linux) ....... My laptop is having SSD SM871... (1 Reply)
Discussion started by: suren424
1 Replies
rc0(8)							      System Manager's Manual							    rc0(8)

NAME
rc0 - Runs command script executed when stopping the system SYNOPSIS
rc0 DESCRIPTION
The rc0 script contains run commands that enable a smooth shutdown and bring the system to a single-user state; run levels 0 and s. In addition to commands listed in within the script itself, rc0 contains instructions to run commands found in the /sbin/rc0.d directory. The script defines the conditions under which the commands execute; some commands run if the system is being shut down while others run if the system is being shut down and rebooted to single user. By convention, files in the /sbin/rc0.d directory begin with either the letter "K" or the letter "S" and are followed by a two-digit number and a filename, for example: K00enlogin K05lpd K60cron K30nfs In general, the system starts commands that begin with the letter "S" and stops commands that begin with the letter "K." The numbering of commands in the /sbin/rc0.d directory is important since the numbers are sorted and the commands are run in ascending order. Files in the /sbin/rc0.d directory are normally links to files in the /etc/init.d directory. An entry in the inittab file causes the system to execute the rc0 script, for example: ss:Ss:wait:/sbin/rc0 shutdown < /dev/console > /dev/console 2>&1 s0:0:wait:/sbin/rc0 off < /dev/console > /dev/console 2>&1 The following operations are typical of those that result from executing the rc0 script and the commands located in the /sbin/rc0.d direc- tory: Notify users that the system is shutting down. Sync the disks Stop system services and daemons Stop processes Kill processes Unmount file systems Invoke init if the system is being shut down to single user The killall command sends a SIGTERM signal to stop running processes; SIGKILL follows to kill all processes except the process which initi- ated the call. The umount -a command unmounts all file systems except the root file system. FILES
Specifies the command path Specifies the directory of commands that corresponds to the run level RELATED INFORMATION
Commands: init(8), killall(8), rc2(8), rc3(8), shutdown(8) delim off rc0(8)
All times are GMT -4. The time now is 04:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy