Sponsored Content
Operating Systems SCO Need Help With System Recovery After HD Errors Post 302992313 by spock9458 on Thursday 23rd of February 2017 04:00:42 PM
Old 02-23-2017
OK, I have my new hard drive installed with the IDE / SATA adapter. Installing from the original SCO 5.0.6 boot disk appears to work fine, I am not linking to any particular driver for the HD and it appears to be recognized. However, when I get to the part about selecting my CD device, the installation does not find the CD. I know from the BIOS that it is attached to the Secondary IDE channel as the Master. Is there some kind of problem with having it as the Secondary Master? I did not change that cable at all, so I know this is how it was configured the last time 5.0.6 was installed. Any ideas why it won't find my CD? I know the CD drive has power, because the tray opens and closes. The "working" light comes on when I insert the CD. However when the installation routine says it is checking the CD the light does not come on. I don't know what to do now. Any help is appreciated.
 

8 More Discussions You Might Find Interesting

1. HP-UX

Automatic system recovery?

Hi all! I've a strange problem. I would use the GNU Make tool on HPUX 11.11. To archive this, i have compiled the sourcecode and renamed HP make in /usr/bin from make to make_old. Now i have make a softlink from /usr/local/bin/make (GNU version) to /usr/bin/make. All things here are ok, but... (1 Reply)
Discussion started by: coredump2003
1 Replies

2. UNIX for Advanced & Expert Users

Adapter Errors and Link Errors

$ errpt | more IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION 3074FEB7 0802050205 T H fscsi1 ADAPTER ERROR B8113DD1 0802050205 T H fcs1 LINK ERROR B8113DD1 0802050205 T H fcs1 LINK ERROR 3074FEB7 0802050205 T H fscsi0 ADAPTER ERROR B8113DD1 ... (0 Replies)
Discussion started by: mcastill66
0 Replies

3. AIX

make a recovery CD/DVD - system has no writable devices

Hi, Has anyone please got some advise as to how I can make a CD/DVD on an AIX 5.3 system so that it can be fully recoverd just by inserting the backed up system. The system that I need to recover has no writable devices, not even a tape drive (it wasn't specified by me btw). I am trying to... (0 Replies)
Discussion started by: stevek007
0 Replies

4. AIX

System recovery

Hi everyone I'm green AIX user or rather beginner (light green). Unfortunately I have to restore my system + data from scratch (things happen) and make it up and running. I've never done it before. Can someone of you provide me with link/procedure/instruction how to do it? Now I know only:... (3 Replies)
Discussion started by: fraydey
3 Replies

5. UNIX for Advanced & Expert Users

Data Recovery from file system overwritten with LVM.

Hey peeps, Here is somethin u might find interestin.... Is it possible to recover data from a partition which used to be an ext3 file sytem with some nice forgotten backups, which now is an lvm partion containg root partition of another OS. :) I couldn't create any mess better than this, can... (2 Replies)
Discussion started by: squid04
2 Replies

6. UNIX for Advanced & Expert Users

linux system recovery after overriding connect() by "ld.so.preload"

dear fellows; i have used ld.so.preload file to override connect() function, dynamic library overriding, it did worked really fine ...... but i went on to struck in a situation ... within the overrided connect() i have used printf once to see IP and Port to whom the connect request is being... (1 Reply)
Discussion started by: mzeeshan
1 Replies

7. UNIX for Advanced & Expert Users

fsck.gfs2 outputs "RG recovery impossible; I can't fix this file system"

I have a CentOS release 5.2 (Final)host running kernel 2.6.18-92.el5 with at raid 10 that had two mirrored drives fail. The drives were re-inserted and now the raid shows healthy (for now). I tried to mount but got an Input/output error. I then attempted a fsck: fsck.gfs2 -y /dev/vg_01/uss_vol... (0 Replies)
Discussion started by: king_hippo
0 Replies

8. Red Hat

Linux system hangs giving ntp errors

Hi folks, I am facing issue of my system (host1) getting hanged after throwing following ntpd messages. I am not able to ssh to the server there after. only option is to restart the host: Dec 29 02:58:51 host1 ntpd: time reset -0.207907 s Dec 29 02:58:51 host1 ntpd: synchronisation lost Dec 29... (0 Replies)
Discussion started by: SiddhV
0 Replies
uata(7D)																  uata(7D)

NAME
uata - IDE Host Bus Adapter Driver SYNOPSIS
ide@unit-address The uata host bus adapter driver is a nexus driver that supports the ide interface on SPARC platforms. The driver attempts to set the disk and ATAPI CD-ROM drive to maximum supported speed. The uata driver supports ultra DMA mode-4 (ATA66). Currently, the uata driver supports the CMD646U, Sil680a and Acer Southbridge M5229 IDE controllers. The uata driver supports two channels concurrently with two devices connected per channel. The devices are logically numbered from 0 to 3: 0 Master disk on primary channel. 1 Slave disk on primary channel. 2 Master disk on secondary channel. 3 Slave disk on secondary channel. For ATAPI devices, an ATAPI DRIVE RESET command is issued to facilitate recovery from timeouts and errors. The BSY bit of the drive's sta- tus register is polled to check for the drive reset completion. If the drive reset fails, a warning message is displayed and the recovery process continues. This logic is subject to change. To control the maximum time spent waiting for the ATAPI drive reset to complete, the atapi-device-reset-waittime tunable property is avail- able through the /kernel/drv/uata.conf file. The default and maximum/minimum values are shown below. Please see /kernel/drv/uata.conf for more info. Default value: 3000000 Minimum value: 20 Maximum value: 3000000 The atapi-device-reset-waittime property units are in microseconds. /kernel/drv/uata 32-bit ELF kernel module. /kernel/drv/uata.conf Driver configuration file. prtconf(1M), driver.conf(4), attributes(5) X3T10 ATA-4 specifications In addition to being logged, the following messages may appear on the system console: ddi_get_iblock_cookie failed. The driver could not obtain the interrupt cookie. The attach may fail. Drive not ready before set_features. Indicates a fatal problem. The drives are not ready to be programmed and features cannot be set. (During the driver initialization process, the driver must set the features for the drive, including dma and pio). Error set after issuing Set Feature command. Indicates a fatal problem. The driver's error bit was set after the set feature command was issued. (During the driver initialization process, the driver must set the features for the drive, including dma and pio). Interrupt not seen after set_features. Indicates a fatal problem with the drive. Features cannot be set. ata_controller - set features failed. Indicates a fatal problem with the drive. Features cannot be set. ? target <number> lun 0. Displayed at boot up time to indicate that the target <number> was identified, where <number> is a decimal value. resid Residual number of bytes in data transfer and the I/O operation could not be finished completely. ghd_timer_newstate: HBA reset failed. Generally indicates a fatal condition. I/O operation cannot be completed following reset of the channel. timeout: <message> chno =<number> target=<number>. A timeout occured because of <message> on device (target=<number>) on channel (chno =<number). Where <message> could be either early abort, early timeout, abort request, abort device, reset target or reset bus. ata_controller - Drive not ready before command <number>. The drive did not respond before issuing the command <number> to the controller; command <number> will not be issued to the drive. (<number> is the hexadecimal opcode for the sleep or standby commands, which are issued when the drive transitions between power man- agement states). ATAPI drive reset failed for target: <number>;Continuing the recovery process. If this message is displayed after you modify /kernel/drv/uata.conf, try to increase the atapi-device-reset-waittime property value within the maximum value allowed, otherwise contact Sun support. ata_controller - Command <number> failed. Command <number> failed on the drive. (<number> is the hexadecimal opcode for the sleep or standby commands, which are issued when the drive transitions between power management states). ata_controller - Command <number> returned error. The command returned an error. (<number> is the hexadecimal opcode for the sleep or standby commands, which are issued when the drive transitions between power management states). ata_controller - Cannot take drive <number> to sleep. The disk will not transition to sleep state. (Indicates that the driver could not set the device to sleep mode while performing power management functions). ata_controller - Cannot reset secondary/primary channel. The disk will not transition from sleep to active state. ata_controller - Unsupported Controller Vendor 0x13d0, Device 0x43f1, Revision 0x034. An unsupported ata controller was found on the system and prints <ID>, device id and revision of the controller, where <ID> represents the hexidecimal vendor ID. Changing the mode of targ: <number> to Ultra DMA mode: <number>. For the timedout command, the driver attempts to recover by changing speed to lower values and retrying the command. This message indi- cates to which mode the driver is attempting to re-program the drive, where <number> is a decimal value. Changing the mode of targ: <number> to Multi DMA mode: <number>. For the timedout command, the driver attempts to recover by changing speed to lower values and retrying the command. This message indi- cates to which mode the driver is attempting to re-program the drive, where <number> is a decimal value. These messages are informational and indicate that a timeout occured for a I/O request. The uata driver recovers from these states auto- matically unless there is a fatal error. 20 April 2005 uata(7D)
All times are GMT -4. The time now is 07:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy