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.
10 More Discussions You Might Find Interesting
1. SCO
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
2. Programming
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
3. Solaris
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
4. SCO
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
5. Solaris
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
6. SCO
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
7. SCO
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
8. SCO
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
9. HP-UX
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
10. SCO
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) BSD General Commands Manual EJECT(1)
NAME
eject -- eject a floppy disk, cdrom or tape
SYNOPSIS
eject [-fv] [-l | -L | -U] [-t device-type] [-d] device
eject -n
DESCRIPTION
The eject program ejects a medium from the specified device. It can also load a cdrom in the drive if this operation is supported by the
hardware. The device argument specifies a device either by its full path name (identified by a /dev/ prefix), or by one of the built-in
nicknames. If the medium contains a file system that is currently mounted, eject will attempt to unmount the file system before ejecting.
The following options are available:
-d Deprecated.
-f Force the eject operation without attempting to unmount any file systems first.
-l Load media in the drive (only supported for the cdrom device type).
-L Lock the media into the drive (but see BUGS below).
-n List the built-in nicknames on standard output.
-t device-type
Specify the device type. The argument must be one of diskette, floppy, cdrom, disk, or tape. This option is necessary when ejecting a
device for which no built-in knowledge is available.
-U Unlock the media from the drive.
-v Display some of the actions taken on standard output.
BUGS
Most disk drivers automatically lock the media on the first open and unlock it on the last close, making 'eject -L' almost useless, since
when it closes the device, it gets unlocked again.
BSD
October 6, 2001 BSD