Sponsored Content
Operating Systems SCO SCO 5.0.7 driver for HP SmartArray P410i Controller on Proliant DL380 G7? Post 303037342 by Stuart1946 on Tuesday 30th of July 2019 05:01:02 AM
Old 07-30-2019
Hi Everyone. First of all many thanks for your contributions in trying to resolve my problem.


Second, it would appear that there's no resolution. There doesn't appear to be a SCO driver for the the P410i in the G7. I tried hpsas (thanks jgt) without success.



Some points for anyone else trying to load SCO on a server without a floppy drive but with a SATA CD ROM.


1) The USB floppy must be attached to the server with a disc loaded when the server is booted or the floppy disc won't be read properly.


2) Similarly the usb CD ROM must be attached at boot time. Swap the CD from the SATA drive to the usb drive after boot but before the installation starts.


2a) Alternatively load BTLD wd (version 3) during the process. The SATA drive will then be recognised and installation will proceed from it if you select IDE CD ROM.


Thanks again, everyone.
This User Gave Thanks to Stuart1946 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
EJECT(1)							   User Commands							  EJECT(1)

NAME
eject - eject removable media SYNOPSIS
eject [options] device|mountpoint DESCRIPTION
Eject allows removable media (typically a CD-ROM, floppy disk, tape, JAZ, ZIP or USB disk) to be ejected under software control. The com- mand can also control some multi-disc CD-ROM changers, the auto-eject feature supported by some devices, and close the disc tray of some CD-ROM drives. The device corresponding to device or mountpoint is ejected. If no name is specified, the default name /dev/cdrom is used. The device may be addressed by device name (e.g. 'sda'), device path (e.g. '/dev/sda'), UUID=<uuid> or LABEL=<label> tags. There are four different methods of ejecting, depending on whether the device is a CD-ROM, SCSI device, removable floppy, or tape. By default eject tries all four methods in order until it succeeds. If device partition is specified, the whole-disk device is used. If the device or a device partition is currently mounted, it is unmounted before ejecting. OPTIONS
-a, --auto on|off This option controls the auto-eject mode, supported by some devices. When enabled, the drive automatically ejects when the device is closed. -c, --changerslot slot With this option a CD slot can be selected from an ATAPI/IDE CD-ROM changer. Linux 2.0 or higher is required to use this feature. The CD-ROM drive can not be in use (mounted data CD or playing a music CD) for a change request to work. Please also note that the first slot of the changer is referred to as 0, not 1. -d, --default List the default device name. -f, --floppy This option specifies that the drive should be ejected using a removable floppy disk eject command. -F, --force Force eject, don't check device type. -h, --help Print a help text and exit. -i, --manualeject on|off This option controls locking of the hardware eject button. When enabled, the drive will not be ejected when the button is pressed. This is useful when you are carrying a laptop in a bag or case and don't want it to eject if the button is inadvertently pressed. -p, --proc This option allow you to use /proc/mounts instead /etc/mtab. It also passes the -n option to umount(1). -q, --tape This option specifies that the drive should be ejected using a tape drive offline command. -m, --no-unmount The option tells eject to not try to unmount at all. -M, --no-partitions-unmount The option tells eject to not try to unmount another partitions on partitioned devices. If another partition is mounted the program will not attempt to eject the media. It will attempt to unmount only mountpoint or mounted device given on eject command line. -n, --noop With this option the selected device is displayed but no action is performed. -t, --trayclose With this option the drive is given a CD-ROM tray close command. Not all devices support this command. -T, --traytoggle With this option the drive is given a CD-ROM tray close command if it's opened, and a CD-ROM tray eject command if it's closed. Not all devices support this command, because it uses the above CD-ROM tray close command. -r, --cdrom This option specifies that the drive should be ejected using a CDROM eject command. -s, --scsi This option specifies that the drive should be ejected using SCSI commands. -v, --verbose Run in verbose mode; more information is displayed about what the command is doing. -V, --version Display program version and exit. -x, --cdspeed <speed> With this option the drive is given a CD-ROM select speed command. The speed argument is a number indicating the desired speed (e.g. 8 for 8X speed), or 0 for maximum data rate. Not all devices support this command and you can only specify speeds that the drive is capable of. Every time the media is changed this option is cleared. This option can be used alone, or with the -t and -c options. -X, --listspeed With this option the CD-ROM drive will be probed to detect the available speeds. The output is a list of speeds which can be used as an argument of the -x option. This only works with Linux 2.6.13 or higher, on previous versions solely the maximum speed will be reported. Also note that some drive may not correctly report the speed and therefore this option does not work with them. EXIT STATUS
Returns 0 if operation was successful, 1 if operation failed or command syntax was not valid. NOTES
Eject only works with devices that support one or more of the four methods of ejecting. This includes most CD-ROM drives (IDE, SCSI, and proprietary), some SCSI tape drives, JAZ drives, ZIP drives (parallel port, SCSI, and IDE versions), and LS120 removable floppies. Users have also reported success with floppy drives on Sun SPARC and Apple Macintosh systems. If eject does not work, it is most likely a limi- tation of the kernel driver for the device and not the eject program itself. The -r, -s, -f, and -q options allow controlling which methods are used to eject. More than one method can be specified. If none of these options are specified, it tries all four (this works fine in most cases). Eject may not always be able to determine if the device is mounted (e.g. if it has several names). If the device name is a symbolic link, eject will follow the link and use the device that it points to. If eject determines that the device can have multiple partitions, it will attempt to unmount all mounted partitions of the device before ejecting (see --no-partitions-unmount). If an unmount fails, the program will not attempt to eject the media. You can eject an audio CD. Some CD-ROM drives will refuse to open the tray if the drive is empty. Some devices do not support the tray close command. If the auto-eject feature is enabled, then the drive will always be ejected after running this command. Not all Linux kernel CD-ROM driv- ers support the auto-eject mode. There is no way to find out the state of the auto-eject mode. You need appropriate privileges to access the device files. Running as root is required to eject some devices (e.g. SCSI devices). AUTHORS
Jeff Tranter <tranter@pobox.com> - original author. Karel Zak <kzak@redhat.com> and Michal Luscon <mluscon@redhat.com> - util-linux version. SEE ALSO
lsblk(8), findmnt(8), mount(8), umount(8) AVAILABILITY
The eject command is part of the util-linux package and is available from Linux Kernel Archive <ftp://ftp.kernel.org/pub/linux/utils/util- linux/>. Linux April 2012 EJECT(1)
All times are GMT -4. The time now is 07:50 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy