Sponsored Content
Operating Systems Solaris Solaris Re-installation failure Post 302671907 by mystition on Sunday 15th of July 2012 04:01:33 AM
Old 07-15-2012
CPU & Memory Solaris Re-installation failure

Hello Community.

I had installed solaris 5.10 OS on an X86 server using a custom-jumpstart installation program and it was performed successfully.

Due to some issues, i had to go for reinstallation using the same jumpstart but this time it failed giving below error.

Code:
Starting Solaris installation program...
Searching for JumpStart directory...
 <<< using DVD install_config >>>
not found
Checking rules.ok file...
c1t0d2 doesn't have a VTOC label
c1t0d3 doesn't have a VTOC label
c1t0d5 doesn't have a VTOC label
c1t0d6 doesn't have a VTOC label
c2t0d0 doesn't have a VTOC label
c2t0d1 doesn't have a VTOC label
c2t0d4 doesn't have a VTOC label
c2t0d6 doesn't have a VTOC label
Using begin script: local.begin
Using derived profile: local.begin
Using finish script: local.finish
Executing JumpStart preinstall phase...
Executing begin script "local.begin"...

Using /cdrom/1_19089-CXP9024789_1.L.flar
Begin script local.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.
WARNING: The firmware on this machine cannot be set for automatic rebooting

Processing default locales
- Specifying default locale (en_US.ISO8859-1)

Processing profile
- Opening Flash archive
- Validating Flash archive
- Selecting all disks
- Configuring boot device
- Using disk (c0t5000CCA0253DB69Dd0) for "rootdisk"
- Creating "maxfree" Solaris fdisk partition (c0t5000CCA0253DB69Dd0)
- Using existing Solaris fdisk partition (c0t5000CCA0253DB69Dd0)

ERROR: fdisk partition table invalid (c0t5000CCA02536A475d0)

ERROR: Flash installation failed
Solaris installation program exited.
#

I tried checking the fdisk of disk-0 on which the installation is failing and it has below output:

Code:
format>fdisk
             Total disk size is 36472 cylinders
             Cylinder size is 16065 (512 byte) blocks

                                               Cylinders
      Partition   Status    Type          Start   End   Length    %
      =========   ======    ============  =====   ===   ======   ===
          1       Active    Solaris2          1  36350    36350    100

Please help in resolving this. Smilie
 

9 More Discussions You Might Find Interesting

1. Solaris

installation of Solaris: installation bypasses network config.

hello solaris friends, I've tried installing Sun Solaris 10.0, but everytime it seems to bypass the network config. screen that looks similar to this...here's the url: http://www.hup.hu/old/images/hup/Solaris/Sol10beta7/9.png I'm able to install it all the way through but I get no... (2 Replies)
Discussion started by: cadmiumgreen
2 Replies

2. OS X (Apple)

GRUB Error and Installation Failure

...I haven't been here in along time! Anyways, I didn't know where I should put this, as this involves practically three OSes, so if this is in the wrong place, feel free to move it. Recently, I thought about this: installing OpenSUSE 10.1 on my Mac Mini's (Intel Core Duo) external hard... (0 Replies)
Discussion started by: Danny_10
0 Replies

3. Solaris

t2000 Sol10 installation failure

Hi folks, I've searched as much as possible with regards to the installation of Solaris 10 and this error that I keep getting no matter which arguments I use. sol-10-u9-ga-sparc-dvd.iso sc> showhost Sun-Fire-T2000 System Firmware 6.7.12 2011/07/06 20:03 Host flash versions: OBP... (3 Replies)
Discussion started by: dnetcrawler
3 Replies

4. SuSE

Failure of Vmware Server 2 installation on SLES 11 SP2

Issue: I am trying to install Vmware Server 2(VMware-server-2.0.2-203138.x86_64) installation on SUSE Linux Enterprise Server 11 (x86_64) SP2 and it fails with error: None of the pre-built vmmon modules for VMware Server is suitable for your running kernel. Do you want this program to try... (3 Replies)
Discussion started by: rupeshkp728
3 Replies

5. Solaris

Solaris 10 flash installation - fatal error. Solaris installation program exited.

Not very helpful to say the least. Seems to read the flar file and go through the upgrade and then come up with this error. Any ideas? (1 Reply)
Discussion started by: psychocandy
1 Replies

6. SuSE

Wine Installation Failure

When I try to install wine either through yast or zypper it fails with below message: zypper in wine Refreshing service 'nu_novell_com'. Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides libOSMesa.so.8()(64bit) needed by... (0 Replies)
Discussion started by: rupeshkp728
0 Replies

7. Post Here to Contact Site Administrators and Moderators

EEM Installation failure

I am trying to install EEM on Linux but found with below issue 27 Sep 2013 01:10:41 INFO iGateway - Check if we can upgrade from Linux 2.4 to 2.6 installer 27 Sep 2013 01:10:41 INFO iGateway - iGateway components conf, Spin.conf] Please suggest, If any further information is required... (1 Reply)
Discussion started by: rakesh_411
1 Replies

8. HP-UX

Sudo installation failure

Dear Guru, I want to install sudo in my HPUX 11.11 and i also already downloading the software from website sudo, and already install the depot using swinstall -c .... , after finish still can not find sudo . something wrong with my installation ? thank you # ls... (6 Replies)
Discussion started by: trisno
6 Replies

9. Shell Programming and Scripting

Gamit installation error: showing Failure in make_gamit -- install_software terminated

what i should to do next? read full query first please!! harshbhu@harshbhu:/usr/local/gg/10.6/updates/Source$ sudo ./install_software sudo: unable to resolve host harshbhu install_software version 2017/06/29 GAMIT and GLOBK to be installed into /usr/local/gg/10.6/updates/Source If... (0 Replies)
Discussion started by: ankit lohar
0 Replies
fmthard(1M)                                                                                                                            fmthard(1M)

NAME
fmthard - populate label on hard disks SYNOPSIS
SPARC fmthard -d data | -n volume_name | -s datafile [-i] /dev/rdsk/c? [t?] d?s2 fmthard -d data | -n volume_name | -s datafile [-i] /dev/rdsk/c? [t?] d?s2 The fmthard command updates the VTOC (Volume Table of Contents) on hard disks and, on systems, adds boot information to the Solaris fdisk partition. One or more of the options -s datafile, -d data, or -n volume_name must be used to request modifications to the disk label. To print disk label contents, see prtvtoc(1M). The /dev/rdsk/c?[t?]d?s2 file must be the character special file of the device where the new label is to be installed. On systems, fdisk(1M) must be run on the drive before fmthard. If you are using an system, note that the term ``partition'' in this page refers to slices within the fdisk partition on machines. Do not confuse the partitions created by fmthard with the partitions created by fdisk. The following options are supported: -d data The data argument of this option is a string representing the information for a particular partition in the current VTOC. The string must be of the format part:tag:flag:start:size where part is the partition number, tag is the ID TAG of the partition, flag is the set of permission flags, start is the starting sector number of the partition, and size is the number of sectors in the partition. See the description of the datafile below for more information on these fields. -i This option allows the command to create the desired VTOC table, but prints the information to standard output instead of modifying the VTOC on the disk. -n volume_name This option is used to give the disk a volume_name up to 8 characters long. -s datafile This option is used to populate the VTOC according to a datafile created by the user. If the datafile is "-", fmthard reads from standard input. The datafile format is described below. This option causes all of the disk par- tition timestamp fields to be set to zero. Every VTOC generated by fmthard will also have partition 2, by convention, that corresponds to the whole disk. If the input in datafile does not specify an entry for partition 2, a default partition 2 entry will be created auto- matically in VTOC with the tag V_BACKUP and size equal to the full size of the disk. The datafile contains one specification line for each partition, starting with partition 0. Each line is delimited by a new-line character ( ). If the first character of a line is an asterisk (*), the line is treated as a com- ment. Each line is composed of entries that are position-dependent, separated by "white space" and having the fol- lowing format: partition tag flag starting_sector size_in_sectors where the entries have the following values: partition The partition number. Currently, for Solaris SPARC, a disk can have up to 8 partitions, 0-7. Even though the partition field has 4 bits, only 3 bits are currently used. For , all 4 bits are used to allow slices 0-15. Each Solaris fdisk partition can have up to 16 slices. tag The partition tag: a decimal number. The following are reserved codes: 0 (V_UNASSIGNED), 1 (V_BOOT), 2 (V_ROOT), 3 (V_SWAP), 4 (V_USR), 5 (V_BACKUP), 6 (V_STAND), 7 (V_VAR), and 8 (V_HOME). flag The flag allows a partition to be flagged as unmountable or read only, the masks being: V_UNMNT 0x01, and V_RONLY 0x10. For mountable partitions use 0x00. starting_sector The sector number (decimal) on which the partition starts. size_in_sectors The number (decimal) of sectors occupied by the partition. You can save the output of a prtvtoc command to a file, edit the file, and use it as the datafile argument to the -s option. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ uname(1), format(1M), prtvtoc(1M), attributes(5) Only fdisk(1M), installgrub(1M) Special care should be exercised when overwriting an existing VTOC, as incorrect entries could result in current data being inaccessible. As a precaution, save the old VTOC. For disks under one terabyte, fmthard cannot write a VTOC on an unlabeled disk. Use format(1M) for this purpose. 11 Apr 2005 fmthard(1M)
All times are GMT -4. The time now is 11:42 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy