Sponsored Content
Operating Systems SCO SCO 5.0.7 driver for HP SmartArray P410i Controller on Proliant DL380 G7? Post 303037238 by jgt on Friday 26th of July 2019 02:07:01 PM
Old 07-26-2019
Go to the sco site xinuos.com and check the certified hardware list.


According to the hardware list, only the P400 controller is supported, and i am pretty sure that the P410 was never supported.

Last edited by jgt; 07-26-2019 at 05:55 PM..
This User Gave Thanks to jgt For This Post:
 

10 More Discussions You Might Find Interesting

1. SCO

ultra 320 scsi raid controller driver for sco 5.0.6

I am facing a problem to install sco 5.0.6 in Dell Power Edge SC1420 which raid controller is ultra 320 scsi raid controller . how/from where to download the ultra 320 scsi raid controller driver for sco 5.0.6. Plz help with any idea karzon (1 Reply)
Discussion started by: karzon
1 Replies

2. SCO

driver needed for hp smartarry p200i sas raid controller

recently we have purchased hp proliant ml350 g5 server and configured raid 5 with hp smartarray p200i sas controller.but i could not found any sas raid controller hp smartarry p200i driver for sco unix 5.0.7 :(.i searched on hp support site,but no use.any one can help. (3 Replies)
Discussion started by: prakrithi
3 Replies

3. UNIX for Dummies Questions & Answers

SCO Openserver 6.0 Insall on HP DL380 serverl

Trying to install Openserver 6.0 on this server which has an integrated Smart Array P400. Install halts with the message ....... "Incorrect Disk Partitioning .........................." I havent yet got to the "divvy" and disk partitioning section of the install section so I am... (2 Replies)
Discussion started by: farmacy
2 Replies

4. SCO

SCO 5.0.7 no root disk controller found error during install

I'm "attempting" to install SCO 5.0.7 on an HP ML370 G4 server and am ready to bash the keyboard with head now. I keep getting the error message "WARNING hd: no root disk controller found" when running the bootable install cd. I have a raid 5 array with an online spare created using 4 36.3 GB... (2 Replies)
Discussion started by: FrictionBurn
2 Replies

5. SCO

Loading SCO 507 on HP ProLiant ML350 G6

This is my first load of SCO OpenServer v5.0.7 on a HP ProLiant ML350 G6. When it asks me to identify the source media it can't find it no matter how I respond. The SCO compatible page says it used the on board SATA DVD-ROM on Port 2 of the embedded SATA controller with "Legacy IDE emulation (as... (8 Replies)
Discussion started by: farmboy
8 Replies

6. SCO

Change Disk controller in SCO 6.0.0

So today I tried to upgrade a customer from a Proliant with an HPSAS controller to an Intel server with a MEGASAS controller. First, I downloaded the megasas driver from SCO and installed it on the old system. Then I created a new Microlite Edge emergency boot cd with the new driver on it. I... (2 Replies)
Discussion started by: jgt
2 Replies

7. Debian

HP ProLiant DL380 G4 w/ Debian... If your familiar with this machine please help.

Hello, I have a few questions about this server. It has two CPU's 3.20 ghz / 800 mhz / 1MB L2 5120 MB RAM 6 hard disks on HP Smart Array 6i controller (36.4 GB Ultra320 SCSI HD each) RAID set to RAID 5 (5 discs) with one spare (6th disk) USB, 2 Ethernet ports, 1 ILO port, 1 SCSI port ... (2 Replies)
Discussion started by: Marcus Aurelius
2 Replies

8. SCO

Getting error sco unix 507 from cdrom:no controller for device you chosen

Installing SCO UNIX 507 on Dell Poweredge T610. It has no floppy so I downloaded the BTLD onto CD from SCO site to load without floppy drive. BTLD loads ok. when i get to the Media to be used, no matter what option i chose i get the error: No controller for device you have chosen. During bootup you... (9 Replies)
Discussion started by: romanglad112
9 Replies

9. SCO

How to change raid controller driver ? (hardware change)

Hello I'm trying to virtualize an instance of Sco Unix 5.0.5 in VirtualBox (called VM-A) , but sco I have problems set to launch with the new raid controller . The physical machine has a raid controller adaptec (alad driver) but VirtualBox uses buslogic (blc driver) What ... (3 Replies)
Discussion started by: flako
3 Replies

10. SCO

SCO OS 6 Driver for LSIL SAS1064E Raid Controller

Hi all, A client has an SCO OpenServer Server 6.0, that is running on an HP ProLiant Box and they lost the root password. Its equipped with a Doal-Core Intel Pentium Processor. They don't have any media or emergency disk anymore. I tried to boot with the CD Rom, then "Tools", then exit to... (7 Replies)
Discussion started by: thm2222
7 Replies
BIO(4)							   BSD Kernel Interfaces Manual 						    BIO(4)

NAME
bio -- Block IO ioctl tunnel pseudo-device SYNOPSIS
pseudo-device bio DESCRIPTION
The bio driver provides userland applications ioctl(2) access to devices otherwise not found as /dev nodes. The /dev/bio device node oper- ates by delegating ioctl calls to a requested device driver. Only drivers which have registered with the bio device can be accessed via this interface. The following device drivers register with bio for volume management: arcmsr(4) Areca Technology Corporation SATA RAID controller cac(4) Compaq RAID array controller ciss(4) Compaq Smart ARRAY 5/6 SAS/SATA/SCSI RAID controller mfi(4) LSI Logic & Dell MegaRAID SAS RAID controller The following ioctl calls apply to the bio device: BIOCLOCATE Locate a named device and give back a cookie to the application for subsequent ioctl calls. The cookie is used to tunnel further ioctls to the right device. BIOCINQ Retrieve number of volumes and physical disks for a specific device. BIOCDISK Retrieve detailed information for the specified physical disk. Information returned can include status, size, channel, target, lun, vendor name, serial number, and processor device (ses). BIOCDISK_NOVOL Is just the same as BIOCDISK but doesn't require the disks to be in volume sets, so this applies to any physical disk con- nected to the controller. Note: this ioctl might not be supported on all hardware. BIOCVOL Retrieve detailed information for the specified volume. Information returned can include status, size, RAID level, number of disks, device name association (sd?) and vendor name. BIOCALARM Control the alarm beeper on the device. Supported states are: disable alarm, enable alarm, silence alarm, status and test alarm. Note: These options might not be supported on all hardware. BIOCBLINK Blink an LED of the specified physical disk. Supported blink states are: blink LED, unblink LED and blink alarm LED. Note: This option is only supported if the disk is governed by ses(4) and the hardware supports hardware blinking. BIOCSETSTATE Alter the state of specified physical disk. Supported states are: create/remove hot-spare, create/remove pass through disk, start/stop consistency check in a volume, online disk and offline disk. Note: These options might not be supported on all hardware. BIOCVOLOPS For operations in volume sets. It's able to create and remove a volume set in a supported RAID controller. Note: this ioctl might not be supported on all hardware. FILES
/dev/bio ioctl tunnel device SEE ALSO
ioctl(2), bioctl(8) HISTORY
The bio driver first appeared in OpenBSD 3.2 and NetBSD 4.0. AUTHORS
The bio driver was written by Niklas Hallqvist <niklas@openbsd.org>. The API was written by Marco Peereboom <marco@openbsd.org> and was extended even more for NetBSD by Juan Romero Pardines <xtraeme@netbsd.org>. BSD
May 25, 2008 BSD
All times are GMT -4. The time now is 05:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy