Sponsored Content
Operating Systems SCO Sco 5.0.7 installation question Post 302908429 by juan.navarrete on Monday 7th of July 2014 08:56:03 PM
Old 07-07-2014
It is a HP Proliant ML350 G5. The controller is a E200i. I have been able to boot from the CD all the wy to start installing but, without installing the driver, it doesn't see the HD.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

SCO 5.0.6 installation problem

I tryed to install SCO 5.0.6 OpenServer on P4 2.0 GHz 384 MB ram 40 GB HDD. It booted from the floppy disk, and when it comes to hd_config I got this error: unexpected trap in kernel mode: PANIC: K_trap - kernel mode trap 0x0000000E ** Safe to power off ** Please, what should I do? (1 Reply)
Discussion started by: Guest07
1 Replies

2. SCO

SCO 5.0.7 Installation Problems

Happy new year guys. I have a inspiron 5100 laptop "Dell" When i'm trying to install SCO openserver 5.0.7 i get this error right after it goes thru the hardware bootup stage. The error is (PANIC: wdsetparam: no device info for ctlr 1 drive 0 is ctlr 0 , drive 0 not... (0 Replies)
Discussion started by: josramon
0 Replies

3. SCO

Sco.5.0.5 Installation

Hi Am kind of new in Unix. I am used to installing SCO Unix 5.0.5 (very old i guess) on a server with SCSI RAID 0. at the boot prompt during installation I type restart link=ipsraid Srom=wd(0,0,0,0). But the problem now is that i want to install on a server with no RAID SCSI disk. what command do... (3 Replies)
Discussion started by: okonkwouz
3 Replies

4. SCO

SCO UnixWare 7.1.3 Installation problem

I am trying to install SCO Unixware7 on compaq DL380 Server with bootable CD but it was stuck at ..... It was not going to further I have given the following unix Sco UnixWare7 .... It was giving errror "unrecogonized command", Can any one please help to completed the installation.... (4 Replies)
Discussion started by: visu101
4 Replies

5. SCO

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... (6 Replies)
Discussion started by: hafizurr
6 Replies

6. UNIX for Advanced & Expert Users

SCO 5.0.5 installation on 80GB HDD

Hello, I have a P4, 2.4GHz, 256MB ASROCK mainboard: I am trying to install sco 5.0.5 on an 80gb hdd IDE . I have tried the following techniques: 1. using the updated wd btld image- no success 2. defbootstr biosgeom 3. use interactive divvy, make adjustments using dkinit/dparam during... (0 Replies)
Discussion started by: pude
0 Replies

7. 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

8. SCO

Need installation media for SCO 5.0.4

I need to reinstall SCO 5.0.4 onto another server as the customer does mnot want to pay for another license. Does anoine have the installation media for this? I'm willing to trade as I have every other installation CD. Let me download the 5.0.4 media from you and I'll give you any OS you want. I... (2 Replies)
Discussion started by: buffbiker23
2 Replies

9. SCO

SCO 5.0.2 Installation Media

We recently started having problems with our SCO OpenServer 5.0.2 Server. I know it is VERY outdated but we are unable to move off of it yet due to an application that is still used daily. We have a new software replacement that will be implemented Q3 2016. I was looking for some installation... (0 Replies)
Discussion started by: AOC
0 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
HPSA(4) 						     Linux Programmer's Manual							   HPSA(4)

NAME
hpsa - HP Smart Array SCSI driver SYNOPSIS
modprobe hpsa [ hpsa_allow_any=1 ] DESCRIPTION
hpsa is a SCSI driver for HP Smart Array RAID controllers. Options hpsa_allow_any=1: This option allows the driver to attempt to operate on any HP Smart Array hardware RAID controller, even if it is not explicitly known to the driver. This allows newer hardware to work with older drivers. Typically this is used to allow installation of operating systems from media that predates the RAID controller, though it may also be used to enable hpsa to drive older controllers that would normally be handled by the cciss(4) driver. These older boards have not been tested and are not supported with hpsa, and cciss(4) should still be used for these. Supported hardware The hpsa driver supports the following Smart Array boards: Smart Array P700M Smart Array P212 Smart Array P410 Smart Array P410i Smart Array P411 Smart Array P812 Smart Array P712m Smart Array P711m StorageWorks P1210m Since Linux 4.14, the following Smart Array boards are also supported: Smart Array 5300 Smart Array 5312 Smart Array 532 Smart Array 5i Smart Array 6400 Smart Array 6400 EM Smart Array 641 Smart Array 642 Smart Array 6i Smart Array E200 Smart Array E200i Smart Array E200i Smart Array E200i Smart Array E200i Smart Array E500 Smart Array P400 Smart Array P400i Smart Array P600 Smart Array P700m Smart Array P800 Configuration details To configure HP Smart Array controllers, use the HP Array Configuration Utility (either hpacuxe(8) or hpacucli(8)) or the Offline ROM-based Configuration Utility (ORCA) run from the Smart Array's option ROM at boot time. FILES
Device nodes Logical drives are accessed via the SCSI disk driver (sd(4)), tape drives via the SCSI tape driver (st(4)), and the RAID controller via the SCSI generic driver (sg(4)), with device nodes named /dev/sd*, /dev/st*, and /dev/sg*, respectively. HPSA-specific host attribute files in /sys /sys/class/scsi_host/host*/rescan This is a write-only attribute. Writing to this attribute will cause the driver to scan for new, changed, or removed devices (e.g., hot-plugged tape drives, or newly configured or deleted logical drives, etc.) and notify the SCSI midlayer of any changes detected. Normally a rescan is triggered automatically by HP's Array Configuration Utility (either the GUI or the command-line variety); thus, for logical drive changes, the user should not normally have to use this attribute. This attribute may be useful when hot plugging devices like tape drives, or entire storage boxes containing preconfigured logical drives. /sys/class/scsi_host/host*/firmware_revision This attribute contains the firmware version of the Smart Array. For example: # cd /sys/class/scsi_host/host4 # cat firmware_revision 7.14 HPSA-specific disk attribute files in /sys /sys/class/scsi_disk/c:b:t:l/device/unique_id This attribute contains a 32 hex-digit unique ID for each logical drive. For example: # cd /sys/class/scsi_disk/4:0:0:0/device # cat unique_id 600508B1001044395355323037570F77 /sys/class/scsi_disk/c:b:t:l/device/raid_level This attribute contains the RAID level of each logical drive. For example: # cd /sys/class/scsi_disk/4:0:0:0/device # cat raid_level RAID 0 /sys/class/scsi_disk/c:b:t:l/device/lunid This attribute contains the 16 hex-digit (8 byte) LUN ID by which a logical drive or physical device can be addressed. c:b:t:l are the controller, bus, target, and lun of the device. For example: # cd /sys/class/scsi_disk/4:0:0:0/device # cat lunid 0x0000004000000000 Supported ioctl() operations For compatibility with applications written for the cciss(4) driver, many, but not all of the ioctls supported by the cciss(4) driver are also supported by the hpsa driver. The data structures used by these ioctls are described in the Linux kernel source file include/linux/cciss_ioctl.h. CCISS_DEREGDISK, CCISS_REGNEWDISK, CCISS_REGNEWD These three ioctls all do exactly the same thing, which is to cause the driver to rescan for new devices. This does exactly the same thing as writing to the hpsa-specific host "rescan" attribute. CCISS_GETPCIINFO Returns PCI domain, bus, device and function and "board ID" (PCI subsystem ID). CCISS_GETDRIVVER Returns driver version in three bytes encoded as: (major_version << 16) | (minor_version << 8) | (subminor_version) CCISS_PASSTHRU, CCISS_BIG_PASSTHRU Allows "BMIC" and "CISS" commands to be passed through to the Smart Array. These are used extensively by the HP Array Configuration Utility, SNMP storage agents, and so on. See cciss_vol_status at <http://cciss.sf.net> for some examples. SEE ALSO
cciss(4), sd(4), st(4), cciss_vol_status(8), hpacucli(8), hpacuxe(8), <http://cciss.sf.net>, and Documentation/scsi/hpsa.txt and Documentation/ABI/testing/sysfs-bus-pci-devices-cciss in the Linux kernel source tree COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. Linux 2017-09-15 HPSA(4)
All times are GMT -4. The time now is 04:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy