Sponsored Content
Full Discussion: Problems insalling aix 4.3
Operating Systems AIX Problems insalling aix 4.3 Post 302112522 by subotai on Wednesday 28th of March 2007 05:42:18 PM
Old 03-28-2007
Thanks for all the input so far. I have tried to boot from just the cdrom without the hard drive attached and from the hard drive without the cdrom attached, and I have talked to a tech as well.

Everything points to a failed cdrom drive. When it is not attached, there is no error message, the hard drive boots up the OS I originally installed (which I still will overwrite eventually), and a diag test of the system shows everything is fine.

When I reattached the cdrom but did not have it in the boot list, the error message comes up, but the hard drive still can boot the OS. When I run diag with the cdrom connected, it shows the same error code that is displayed when the server first comes up, 21f00001.

I will get this cdrom replaced, and then most likely I can do all the installs I want without further incident. Kind of a rough way to learn aix installs, but oh well...

Thanks again for all the advice posted here.

Scott
 

10 More Discussions You Might Find Interesting

1. Programming

recv() problems using AIX 4.33

I am opening a server socket on one of our machines and connection to it on the other machine. After making the connection if ether one of the systems does a recv() and ther is no data to receive then the buffer is filled with spaces and returns. I have no way of knowing if it is valid or not. ... (1 Reply)
Discussion started by: hazard0007
1 Replies

2. AIX

AIX 4.3.3.0 routing problems

Hello guys. I have a AIX running an ip of 128.2.1.85 255.255.255.0, Main office router is 128.2.1.2 .we just got an t1 line point to point for a remote office with to pcs. My question. I'm not able to ping those pcs one of them is using this ip 128.2.2.128 255.255.255.0 Remote router ip... (2 Replies)
Discussion started by: josramon
2 Replies

3. AIX

Problems with scp in AIX-5.2

I am using ssh version OpenSSH_3.8p1, SSH protocols 1.5/2.0, OpenSSL 0.9.6l When i ssh to this server its working fine ,sftp is also fine ,but when i use scp to copy files to it i am prompted for the password and on entering it throws up the following error stty: tcgetattr: A... (1 Reply)
Discussion started by: arnab
1 Replies

4. AIX

Problems install Aix 5.3

Hello I have a server that I want to install Aix 5.3, first I change on the sms to install device from the cdrom, when I boot the server on the display hangs up on the message E443 and nothing happens. Who Can I resolve this. Thanks in advance for your comments. (3 Replies)
Discussion started by: lo-lp-kl
3 Replies

5. AIX

Problems AIX and SAN.

Sorry for my english. We have a IBM BLADES JS21. AIX 5.3 update to 6. Our JS21 has 2 FC (fcs0 and fcs1). We have one DS4072, one Disk system with 2 controllers and 2 FC by controllers. This means, all AIX FC see all Disk systems controllers by 2 FC switchs. (one fc two roads) FC AIX... (4 Replies)
Discussion started by: fjgonzalez
4 Replies

6. AIX

problems with gcc on AIX 4.33

I just installed gcc on AIX 4.33, and I am having some problems with compiling a simple hello world program. See output below for the issue. The "standards.h" file is not on my system and I don't know where to get it. Thanks in advance for your help! # gcc -v Reading specs from... (2 Replies)
Discussion started by: jhall
2 Replies

7. AIX

Problems with sendmail on AIX

hi, i got this error, i have no idea where to start.. anyone please??? Warning: .cf file is out of date: sendmail AIX5.3/8.13.4 supports version 10, .c f file is version 9 WARNING: local host name (BAANPRO) is not qualified; see cf/README: WHO AM I? Running /var/spool/mqueue/o3CBj3np1138768... (3 Replies)
Discussion started by: fdeivis
3 Replies

8. AIX

NFS mount problems on AIX

Hi, I have two machines (AIX) each on a different VLAN. Need to mount a filesystem using nfs on the other one. When I export the nfs file system its a breeze. But when I try to mount it on the other machine the smitty command hangs on "running" and i get an OK from smitty but with this... (6 Replies)
Discussion started by: aixromeo
6 Replies

9. AIX

various problems in aix

I have some doubts 1. Count the number for fields in a file, being separated by "space" 2. Reverse the order of fields in a file 3. Show the date after 10 days from the current date. (DD-MM-YYYY) 4. Convert GMT to IST (User Gives GMT and IST must be displayed) 5. Delete Duplicate... (1 Reply)
Discussion started by: tsurendra
1 Replies

10. AIX

AIX 5.3 performance problems

Hello, I encounter some performance issues on my AIX 5.3 server running in a LPAR on a P520. How do I investigate performance issues in AIX. Is there any kind of procedure that takes me to the steps to investigate my server and find the sub systems that is causing the issues? The performance... (1 Reply)
Discussion started by: petervg
1 Replies
re-preinstall(1M)					  System Administration Commands					 re-preinstall(1M)

NAME
re-preinstall - installs the JumpStart software on a system SYNOPSIS
cdrom-mnt-pt/Solaris_XX/Tools/Boot/usr/sbin/install.d/re-preinstall [-m Solaris_boot_dir] [-k platform_name] target-slice DESCRIPTION
re-preinstall installs the JumpStart software (preinstall boot image) on a system, so you can power-on the system and have it automatically install the Solaris software (perform a JumpStart installation on the system). When you turn on a re-preinstalled system, the system looks for the JumpStart software on the system's default boot disk. All new SPARC systems have the JumpStart software already preinstalled. The XX in Solaris_XX is the version number of the Solaris release being used. You can use the re-preinstall command in several ways. The most common way is to run re-preinstall on a system to install the JumpStart software on its own default boot disk. This is useful if you want to restore a system to its original factory conditions. (See the first procedure described in EXAMPLES.) You can also run re-preinstall on a system to install JumpStart software on any attached disk (non-boot disk). After you install the Jump- Start software on a disk, you can move the disk to a different system and perform a JumpStart installation on the different system. (See the second procedure described in EXAMPLES.) re-preinstall creates a standard file system on the specified target-slice (usually slice 0), and re-preinstall makes sure there is enough space on the target-slice for the JumpStart software. If sufficient space is not available, re-preinstall fails with the following message: re-preinstall: target-slice too small xx Megabytes required You can use the format(1M) command to create sufficient space on the target-slice for the JumpStart software. OPTIONS
The following options are supported: -k platform_name Platform name of the system that will use the disk with the JumpStart software. The default is the platform name of the system running re-preinstall. (Use the uname(1) command (-i option) to determine a system's platform name.) -m Solaris_boot_dir Absolute path to the Solaris_XX/Tools/Boot subdirectory of a mounted Solaris CD or a Solaris CD copied to disk that re-preinstall uses to install the JumpStart software. The default is root (/), which is where the Solaris CD is mounted in single-user mode. OPERANDS
The following operands are supported: target-slice Device name of the disk slice where the JumpStart software will be installed (usually slice 0), for example, c0t3d0s0. EXAMPLES
Example 1: Installing the JumpStart Software on a System's Own Default Boot Disk The following procedure installs the JumpStart software on a system's own default boot disk: 1. From the ok prompt, boot the system from the Solaris media CD or DVD in single-user mode: ok boot cdrom -s 2. The following command installs the Jumpstart software on the System default boot disk, c0t0d0s0 on a Solaris 9 system: example# /usr/sbin/install.d/re-preinstall c0t0d0s1 3. Reboot the slice: example# reboot disk:b Example 2: Installing the JumpStart Software on a System's Attached (non-boot) Disk The following procedure installs the JumpStart software on a system's attached (non-boot) disk: 1. Mount the Solaris CD or DVD if vold(1M) is not running or CD or DVD is not mounted. 2. Use the format(1M) command to determine the target-slice where JumpStart will be installed. 3. Use the uname(1) command (-i option) to determine the platform name of the system that will use the re-preinstalled disk 4. Run re-preinstall with the -m Solaris_boot_dir option if the Solaris CD or DVD is not mounted on /cdrom. The following command installs the JumpStart software on the system's attached disk for a system with a Sun4u kernel architecture, and it uses the Solaris CD or DVD mounted with vold(1M) on a Solaris 9 system: example# /cdrom/cdrom/s1/usr/bin/install.d/re-preinstall -m /cdrom/cdrom/s1 -k sun4u c0t2d0s0 EXIT STATUS
The following exit values are returned: 0 Successful completion. 1 An error has occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcdrom (Solaris CD, | | |SPARC Platform Edition) | +-----------------------------+-----------------------------+ SEE ALSO
uname(1), eeprom(1M), format(1M), mount(1M), vold(1M), attributes(5) Solaris 10 Installation Guide: Basic Installations SunOS 5.10 9 Apr 2002 re-preinstall(1M)
All times are GMT -4. The time now is 08:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy