Sponsored Content
Operating Systems SCO SCO unresponsive after root disk Post 302942679 by jgt on Thursday 30th of April 2015 02:09:08 PM
Old 04-30-2015
I take it that you are booting from the diskettes.
Lets define the hardware.
Adaptec 2940 host adapter, 2gb scsi disk, scsi tape, and scsi cdrom.
130k of memory, intel 100pro network card, digiboard PCIXr 8 port serial card.
I think that this is 5.0.5 based on the kernel date of 97/09/03, and probably a P3 cpu.

I would install a fresh hard drive, install the operating system from scratch.
Add the original disk in as scsi id 1, and put a jumper on the readonly pins.
Then attempt to mount the second (original) drive.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Fortgot root password SCO 5.0.

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

adding hard disk from SCO OpSer in SCO 5.06

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

sco openserver 5.0.0 boot / root disk

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

Expanding the root area on SCO 5.07?

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

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

Mirror the root disk

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

root out of space in sco 5

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

Lost Root Password on VXVM Encapsulated Root Disk

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

SCO Openserver 5 root password and disk full

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
AHA(4)							   BSD Kernel Interfaces Manual 						    AHA(4)

NAME
aha -- Adaptec SCSI host adapter driver SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device scbus device aha Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): aha_load="YES" In /boot/device.hints: hint.aha.0.at="isa" DESCRIPTION
This driver provides access to the SCSI bus connected to the Adaptec AHA-154x and AHA-1640 SCSI host adapters. x is 0 for controllers with- out a floppy drive and 2 for controllers that have them. For optimum performance, Adaptec AHA-174x controllers should be configured in enhanced mode and attached via the ahb(4) driver. One device hint entry for every card to be attached by the system is required. Specific values for the port address, IRQ, and DRQ may be specified. If wildcard values are used, the driver will query the device for its current settings and use those. If the port address is a wildcard, the driver consults an internal table of possible port address locations and attaches to the first unattached card it finds. The possible port addresses for this card are 0x330, 0x334, 0x230, 0x234, 0x130, and 0x134. The AHA-1640 is an MCA bus card. Since the MCA bus is a self-identifying bus, no setting of hints is required. HARDWARE
The aha driver supports the following SCSI host adapters: o Adaptec AHA-154xB o Adaptec AHA-154xC o Adaptec AHA-154xCF o Adaptec AHA-154xCP o Adaptec AHA-1640 o Adaptec AHA-174x in 154x emulation mode o DTC 3290 SCSI controller in 1542 emulation mode o Tekram SCSI controllers in 154x emulation mode SEE ALSO
ahb(4), ahc(4), aic(4), cd(4), da(4), sa(4), scsi(4) AUTHORS
The aha driver was ported by M. Warner Losh from the bt driver written by Justin T. Gibbs. BUGS
The AHA-154xA card does not support residuals on data transfers. As a result, this card is no longer supported. There have been some reports that the AHA-154xB does not work well under heavy load. The AHA-154xCP is a plug and play controller. However, its resources are set using the on-board BIOS and cannot be moved. Failures to attached for this card are often caused when the resources set in the BIOS conflict. BSD
July 4, 2004 BSD
All times are GMT -4. The time now is 01:13 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy