Discussion Locked

SCSI???????????

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Help I need a SCSI pro..........

I have a client that has a SCSI controler going to a seagate HDD. I built the system out a few years ago and everything was fine. I got a call a few weeks ago saying the system was dead. Well after finding whathappened. The user was loading HP printer software and some how nuked the system. I have no idea how it happened but now the system will not boot. During the boot process it waits and waits at chaA di0 and then says found seagate, and that the drive is connected but not ready??? I am by no means a SCSI pro. I've tried booting with a boot disk but it say the disk is not configed correctly. I'm sure I have the ARC wrong. Durning boot it says the SCSI bios is not loaded. I've also tried reloading NT but it fails tring to find a disk to load onto. The disk light flashed so I know I've got connectivity but that's it. I guess the question is what is the methodical steps in trying to recover a SCSI disk? Are there any utilitys out there that can help me find out what the problem is. Any help is going to be great. Thanks

7 replies

by mckaytech

My first thought is that the printer driver install and the failure might just be co-incidence. Not that it helps, but this sounds to me like a hardware drive failure rather than simply a trashed OS.

Your best bet for diagnosis is going to be toidentify the SCSI controller and then look for the manufacturer's diagnostic utilities. Adaptec is particularly well supported in that regard.

If you can post with the make and model of your controller, I'll see what I have in the way of diagnostic information.

But if you have another SCSI drive to try, I would try that first since the controller appears to find the drive but it then times out waiting for the drive to get ready. That is normally indicative of a hardware drive failure but you should probably also look for misplaced terminator packs, bad cables, things like that.

paul

by freetech

my best guess is that your hard drive is bad. as for the booting with a floppy, check to see if the boot order has the floppy before the scsi.
anyway, if the scsi bios doesn't load, that means that the card does not detect the disk.
best guess, bad disk.

by estebandelatorre

A very good start will be to install the controller AND it's disk on a machine with the same os instaled as the dead one.
Once the machine boots, you may be able to configure the scsi drivers onto the new OS, and then you will inmediatly see the HD (if it is not dead. Windows will help you to identify if your SCSI card or disk are damaged.
Also, first try under bios setup of the machine, the startup boot order!, it must be a:, scsi,...
Another try will be to inspect disk & partitions, active partitions with fdisk.exe

Hope it helps

This discussion is closed to new replies.