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


 
Thread Tools Search this Thread
Operating Systems SCO Getting error sco unix 507 from cdrom:no controller for device you chosen
Prev   Next
# 1  
Old 05-23-2012
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 can see the CDROM on device list with id position, etc.
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

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

2. HP-UX

Cdrom device possibly missing?

Hello, I am following the HPUX 11.31 install/update guide and I am trying to install "Update-UX" from the installation media. I put the CD into the drive, and I am trying to mount the device. The instructions state:Find the DVD-ROM device file name: ioscan -C disk -f -n -k | more A typical... (5 Replies)
Discussion started by: bstring
5 Replies

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

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

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

6. Solaris

CDROM will not eject - says device busy

Hi, I've seen similar posts on this board about ejecting CDROMs but I've tried the solutions people suggested but still cannot eject the CD. It's stuck in a production box so I can't reboot it... bash-3.00# eject -f cdrom /vol/dev/dsk/c0t0d0/sol_10_106_sparc/s0: Device busy bash-3.00#... (14 Replies)
Discussion started by: jimmy54321
14 Replies

7. SCO

SCO UNIX DAT Tape Device

Looking for specifically naming convention for a tape device for SCO Unix What full system backup command should I use for SCO UNIX (1 Reply)
Discussion started by: jedimaster
1 Replies

8. Solaris

from where i can find the CDROM device

Hi, I attached the CDROM device in sun 2500 system , Now i want to mount this device. From where i can find the CDROM device. Thnx.. (2 Replies)
Discussion started by: Aamir Sahil
2 Replies

9. Programming

Accessing device with Prolific USB-serial controller.

I am trying to access DG-100 gps logger on Mac OS X with POSIX API. The device uses a Prolific usb-serial controller, and connect to the usb port on my mac. After I install the Prolific driver, it shows up as /dev/tty.usbserial and /dev/cu.usbserial. The vendor has published the data format. So... (1 Reply)
Discussion started by: monkeybiz
1 Replies

10. SCO

sco backup using CDROM

I've installed a CD-RW rom using SCO OSR 5.0.7, but I cannot open the dev to perform backup (6 Replies)
Discussion started by: tsc_hk
6 Replies
Login or Register to Ask a Question
eject(1)							   User Commands							  eject(1)

NAME
eject - eject media such as CD-ROM and floppy from drive SYNOPSIS
eject [-dflqt] [ [device | nickname]] DESCRIPTION
The eject utility is used for those removable media devices that do not have a manual eject button, or for those that might be locked due to, for instance, being mounted. The device may be specified by its name or by a nickname. If no device is specified, the default device is used. Only devices that support eject under program control respond to this command. When eject is used on media that can only be ejected manually, it does everything except remove the media, including unmounting the file system if it is mounted. In this case, eject displays a message that the media can now be manually ejected. Do not physically eject media from a device that contains mounted file systems. eject automatically searches for any mounted file systems that reside on the device, and attempts to umount them prior to ejecting the media. See mount(1M). If the unmount operation fails, eject prints a warning message and exits. The -f option can be used to specify an eject even if the device contains mounted partitions. If you have inserted a floppy diskette, you might need to use volcheck(1) before ejecting the media to inform the system the floppy's pres- ence. OPTIONS
The following options are supported: -d Display the name of the default device to be ejected. -f Force the device to eject even if it is busy. -l Display paths and nicknames of ejectable devices. -q Query to see if the media is present. -t Issues the drive a CD-ROM tray close command. Not all devices support this command. OPERANDS
The following operands are supported: device Specifies which device to eject, by the name it appears in the directory /dev. nickname Specifies which device to eject, by its nickname as known to this command. Volume label or device type (for example, cdrom or floppy0) can be used as a nickname. EXAMPLES
Example 1 Ejecting Media The following example ejects media by its volume label: example> eject 'My Pictures' Example 2 Ejecting a Floppy Disk The following example ejects a floppy disk from the first floppy drive: example> eject floppy0 EXIT STATUS
The following exit codes are returned: 0 The operation was successful or, with the -q option, the media is in the drive. 1 The operation was unsuccessful or, with the -q option, the media is not in the drive. 2 Invalid options were specified. 3 An ioctl() request failed. 4 Manually ejectable media is now okay to remove. FILES
/dev/diskette0 default diskette file /dev/sr0 default CD-ROM file (deprecated) ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
volcheck(1), mount(1M), rmmount(1M), ioctl(2), attributes(5) SunOS 5.11 18 Sep 2006 eject(1)