Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!uwvax!oddjob!gargoyle!ihnp4!homxb!homxc!rps From: rps@homxc.UUCP (R.SHARPLES) Newsgroups: comp.sys.att,comp.sys.ibm.pc Subject: Re: Help needed with AT&T 6300 hard disk problem!! Message-ID: <2306@homxc.UUCP> Date: Mon, 30-Nov-87 07:57:31 EST Article-I.D.: homxc.2306 Posted: Mon Nov 30 07:57:31 1987 Date-Received: Thu, 3-Dec-87 04:53:34 EST References: <2225@killer.UUCP> Distribution: na Organization: AT&T Bell Laboratories, Holmdel Lines: 47 Xref: mnetor comp.sys.att:1921 comp.sys.ibm.pc:10624 In article <2225@killer.UUCP>, strianta@killer.UUCP (Spiros Trianta) writes: ... > Then one day it really hit the fan. Could not do anyththing with drive C, > without getting TONS of said errors. Diagnostics said DISK & DRIVE CONTROLLER > TIME OUT (?). I low- and high- level formatted the drive with no avail. > Format went thrui once and said not ready, immediately after said OK. Still > same problem. > > Now that I use the system from floppyu only, after half an hour or so of use the > system (drive) makes funny seeking noises, but without me referencing it. The > seek light does not come on. The noises are similar to the ones done while tryiotrying to reboot. > > A friendly technician said that probably the controller is shot. What is > your opinion, Oh Net? AT&T won't sell me the advanced diagnostics, at least the few authorized dealers in the Indy area won't. > > I would like some opinions or educated guesses before taking the box to service. > Any help will be appreciated, and as usual, I will summarize if interesting > facts arise. Remember, it is an AT&T 6300 with its original 20 MB hard disk > and controller from AT&T. I think the controller is an RLL western digital, > while the drive is a seagate. > > Thanks much! > > Spiros > -- > > Spiros Trianta > ...!ihnp4!killer!strianta It is probably not an RLL controller, just your basic Western Digital PCXT controller. I would call the hotline about the diagnostic disk (800-922-0354) they have sent me several disks of specialized software to solve various problems. Second, I would try swapping the controller with one from work, assuming that someone at work has a PC6300 and wouldn't mind you borrowing the controller overnight. If that doesn't fix it, try your controller with a known good harddisk (after backing it up!). Russ Sharples homxc!rps NOTE: The above in NO WAY reflects the opinions of AT&T. These opinions are my own and the results of un-scientific and highly irregular analysis methods.