Sponsored Content
Operating Systems SCO Getting error sco unix 507 from cdrom:no controller for device you chosen Post 302646029 by romanglad112 on Thursday 24th of May 2012 11:49:05 AM
Old 05-24-2012
Thanks for the info jgt. unfortunately the system that is going to rest on the sco calls for 507. however i do have 6.o install disk. problem i have is configuring the hard drive partitions. install instructions i have for 507 (to be compatable) shows different setup screen than 6.0 when i get to the section to setup the drive.
 

10 More Discussions You Might Find Interesting

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

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

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

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

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

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

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

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

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

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
WREN(3) 						     Library Functions Manual							   WREN(3)

NAME
wren, ata - hard disk interface SYNOPSIS
bind #H[drive] /dev bind #w[target[.lun]] /dev /dev/hd0disk /dev/hd0partition /dev/sd0disk /dev/sd0partition ... DESCRIPTION
The hard disk interfaces (wren, #w, is a SCSI disk; ata, #H, is an IDE or ATA disk) serve a one-level directory giving access to the hard disk partitions. The parameter to attach defines the numerical SCSI target and logical unit number or the IDE drive number to access. Both default to zero. Each partition name is prefixed by hd and the numeric drive identifier. The partition always exists and covers the entire disk. The size of each partition as reported by stat(2) is the number of bytes in the partition, so the size of is the size of the entire disk. The partition also always exists; it is the last block on the disk for SCSI, second to last for IDE. If it contains valid partition data, those partitions will be visible as well. Every time the device is bound, the partitions are updated to reflect any changes in the parti- tion file. The format of the partition file is the string plan9 partitions on a line, followed by partition specifications, one per line, consisting of a name and textual strings for the block start and limit for each partition on the disk. The program prep(8) writes the partition table for the disk; its use is preferred to writing it by hand. SEE ALSO
prep(8), scsi(3) SOURCE
/sys/src/9/port/devwren.c /sys/src/9/pc/devata.c WREN(3)
All times are GMT -4. The time now is 12:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy