05-01-2015
I think I would try making a new boot and root set on one of the other 3 machines, verify operation on it, then try it on the machine that is failing. That would eliminate bad boot and root, just in case the supplier duplicated them from a bad original.
More likely, in my experience, that the CD is bad by a factor of at least 20 to 1. Can you swap a CD across.
To answer the previous question, keyboard is generic and shows up as it is booting up.
Assume that the SCSI bios reports all devices correctly on BIOS attachment.
Last edited by edfair; 05-01-2015 at 10:21 PM..
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hello guys The company i work for just got a new client, there old datebase is in Unix SCO openserver 5.0.5.
The manager of this new client can login but not as a root , they forgot there own root password. There old IT company never gave it to them and they have no way of getting a hold of them
... (2 Replies)
Discussion started by: josramon
2 Replies
2. SCO
Hi!
Sorry, but I am'not spesialist in SCO OpenServer. I need to add hard disk from SCO Open Server ( "a") in my SCO OpenServer 5.6. I need data from "a". When I added, I see only swap disk, and didn't see root file system. I need to add IDE and SCSI
Please, help me. How right to add disk?... (0 Replies)
Discussion started by: fedir
0 Replies
3. SCO
Hi,
I have an openserver 5.0.0 machine in the office. The sysad of that machine left years ago without leaving the password to anyone.
I was wondering if someone has a copy of the boot / root diskettes (rescue) for this version? Or perhaps if anyone knows a download link / location in the... (0 Replies)
Discussion started by: marcpascual
0 Replies
4. SCO
I would like to expand the size of the root area, currently 800 kb, to a size of 2000 kb. Is that possible to do without loosing any data in the /u area? There is plenty of space available in the /u area. (2 Replies)
Discussion started by: pschnell
2 Replies
5. 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
6. Solaris
Hi all
I wish to mirror for the root disk, but last time i do, make the server cannot boot up. :p So this time, hope you guys can assist me on it. =)
At the last code, is the step i wish to do. Please help to check and correct me if got any wrong.
root@leo # format </dev/null
Searching for... (17 Replies)
Discussion started by: SmartAntz
17 Replies
7. SCO
DEAR Team,
I need some help in sco open server 5
while booting server beloow message giving server
HTFS no space dev HD 1/42
Thanks
Skb (4 Replies)
Discussion started by: sudhir69
4 Replies
8. Solaris
Hi All
Hope it's okay to post on this sub-forum, couldn't find a better place
I've got a 480R running solaris 8 with veritas volume manager managing all filesystems, including an encapsulated root disk (I believe the root disk is encapsulated as one of the root mirror disks has an entry under... (1 Reply)
Discussion started by: sunnyd76
1 Replies
9. SCO
Hi,
We have an old SCO Openserver 5.0.7 server that I have inherited that currently has two issues that we are trying to resolve.
1. We do not know the root password. I have contacted the old admin, looked for rescue disk and documentation but there appears to be nothing.
I have tried... (1 Reply)
Discussion started by: acerimmer10
1 Replies
socal(7D) Devices socal(7D)
NAME
socal - Serial Optical Controller for Fibre Channel Arbitrated Loop (SOC+) device driver
SYNOPSIS
socal@sbus-slot,0
DESCRIPTION
The Fibre Channel Host Bus Adapter is an SBus card which implements two full duplex Fibre Channel interfaces. Each Fibre Channel interface
can connect to a Fibre Channel Arbitrated Loop (FC-AL).
The socal device driver is a nexus driver and implements portions of the FC-2 and FC-4 layers of FC-AL.
FILES
/kernel/drv/socal ELF Kernel Module
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Architecture |SPARC |
+-----------------------------+-----------------------------+
SEE ALSO
sbus(4), sf(7D), ssd(7D)
Writing Device Drivers
ANSI X3.230-1994, Fibre Channel Physical and Signalling Interface (FC-PH)
ANSI X3.272-1996, Fibre Channel Arbitrated Loop (FC-AL)
Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA)
DIAGNOSTICS
The messages described below may appear on system console in addition to being logged.
On the console, these messages are preceded by:
socal%d: port %a
where %d is the instance number of the socal controller and %a is the port on the host adapter.
Fibre Channel Loop is ONLINE
The Fibre Channel loop is now online.
Fibre Channel Loop is OFFLINE
The Fibre Channel loop is now offline.
attach failed: device in slave-only slot.
Move soc+ card to another slot.
attach failed: bad soft state.
Driver did not attach, devices will be inaccessible.
attach failed: unable to alloc xport struct.
Driver did not attach, devices will be inaccessible.
attach failed: unable to map eeprom
Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to map XRAM
Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to map registers
Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to access status register
Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to install interrupt handler
Driver was not able to add the interrupt routine to the kernel. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to access host adapter XRAM
Driver was unable to access device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to write host adapter XRAM
Driver was unable to write device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: read/write mismatch in XRAM
Driver was unable to verify device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
SunOS 5.10 9 May 1997 socal(7D)