Sponsored Content
Operating Systems SCO SCO OpenServer 5.0.7 Installation problem Post 302129499 by hafizurr on Tuesday 31st of July 2007 08:57:48 AM
Old 07-31-2007
SCO OpenServer 5.0.7 Installation problem

we are installing Openserver 5.0.7, system have SAS controller (Hard Disk Attached) as well as Adaptec ultra 320 controller (Tape Drive Attached).

At the time of installation we link both driver BTLD

Boot: Defbootstr link=accraid ad320

Aftes succesfully installation of accraid btld which is SAS controller when system ask AD320 Driver machine was hangs and we have to reset the machine.

but when we install ad320 btld first

Boot: Defbootstr link=ad320 accraid

It will install both Driver succesfully as well as OS but after complete installation when we reboot the machine it will stop at Boot: when we press enter it will give followinf error

hd(40) not found.

can any one please help us to solve this issue.

Regards

hafeez
 

10 More Discussions You Might Find Interesting

1. IP Networking

Installation Problem in Unix Openserver

I have certain problems while Installing UNIX OPENSERVER.Could anyone solve that if I provide that problem. (3 Replies)
Discussion started by: Rajraius
3 Replies

2. Filesystems, Disks and Memory

SCO openserver 5 install problem

Hello all, I'm trying to install SCO openserver 5 on a 2.5 Gig hard drive, and I tried fdisk and a low-level format of the drive. When I insert the boot diskette all seems fine, and it asks me to set the cd-rom and it sees it and reads from it. Well, I'm thinking all is well until right after I... (1 Reply)
Discussion started by: immulett
1 Replies

3. UNIX for Dummies Questions & Answers

SCO OpenServer Booting Problem

My company has a Compaq NeoServer running SCO OpenServer Release 5 (vintage late 1998) that we inherited from another small company. This has been a very reliable file server for our small company. We recently installed a new Linux server and would like to convert the NeoServer to other functions... (1 Reply)
Discussion started by: Jeff Boyce
1 Replies

4. UNIX for Dummies Questions & Answers

RE: login problem with SCO openserver

I am running the beta version of Openserver by SCO and the Graphical login only gives me the option of logging into the system v xwindows and I know that this build included KDE 3.3 I have tried the kde kdm command at shell prompt: command not found. Any ideas anyone? (0 Replies)
Discussion started by: coreykirk
0 Replies

5. SCO

sco openserver 5.07 installation problem

Hi everyone, We r installing sco openserver 5.07 on dell poweredge 2800 but we are facing problem when installing SCSI-raid drivers. Dell provide Perc4 raid card and we dont found raid drivers for this specific raid card. So we r stuck up on primary stage and we also dont know the... (2 Replies)
Discussion started by: mineshkoli
2 Replies

6. SCO

SCO OpenServer 5.0.7 Installation problem on HP ML310 G4

can not for the life of me workout which BTLD to load allways shows no HDD available can any one give me a clue tried hpsas aacraid lsil a160 a320 server is a ML310 G4 ?????:confused::confused: (7 Replies)
Discussion started by: wildginger
7 Replies

7. SCO

sco openserver release 5.0.5 installation problems on notebook

hello, i want to install release 5.0.5 on my notebook but the system hangs when extracing files from source media in fact after configuration all of setting please help me:confused: (1 Reply)
Discussion started by: hossein
1 Replies

8. SCO

SCO OpenServer 5.0.5 Problem

I am currently having a problem with my SCO OpenServer 5.0.5 / 3.2v5.0.5 system. Running smoothly for the past 3 years, at random on March 16, 2010 the system crashes. I reboot it. Everything is normal again. 9 hours later it crashes again. This cycle has repeated itself ever since then. System... (2 Replies)
Discussion started by: jesmith
2 Replies

9. UNIX for Advanced & Expert Users

Installation of Sco Openserver 5.0.7 on HP DC 7600

Hi All , I wanted to install SCO Open server 5.0.7 on HP DC7600 Desktop Machine, is there any bootloader and which site i can find it to enable me install it because the system is not recognizing the Hard disk just like the ML G Series machine installations. Please help if you have done this... (4 Replies)
Discussion started by: davosky
4 Replies

10. SCO

Installation on SCO Openserver 5.0.5

Hello all, First off- great forum! I have learned a lot just by reading some of the questions and answers. Good to see there are good people out there still willing to help! Here is my dilemma- I have a fairly new server running an Activant product on it, which runs SCO openserver 5.0.5... (9 Replies)
Discussion started by: crt001
9 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 05:46 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy