[clue-tech] Re: kernel drivers (linux kernel: hde: drive_cmd:

[Hex Star]

hmm...actually the manufactures diagnostics is a seperate program and
*may* see the drive OK with the current setup, will try it out
tomorrow after school and if it sees the drive normally I'll run the
extended test and report back the results...with the way tests have
gone it should and I hope it will, pass

On 1/4/06, Hex Star <hexstar at gmail.com> wrote:
> As I've mentioned before here (I think), I can't use the manufactures
> diagnostics because with the drive connected to the ATA card it thinks
> the drive is a cd rom drive although I have the ATA drivers loaded in
> Windows and Windows sees the drive normally :-/, doing it with the
> drive connected to the motherboard directly is not a option either
> anymore since I'd have to install a dynamic drive overlay which uses
> the MBR and lilo is currently in the MBR (multibooting suse 9.1 pro
> and xp pro sp2) since the bios only supports a max of 60GB and even
> the latest BIOS update (which costs $60 so I decided to buy a $50 ATA
> card which can detect the whole HD itself) can only see half of the
> drive, 150GB, however as I've pointed out I've done a fsck on the
> drive which returned no errors, I've done a quick SMART test and a 2
> hour SMART test, both of which also passed and were done on the
> drive...so is there anything more I should do? Thanks guys for your
> help and sorry about all the replies, I'll do my best to keep them to
> a minimum. :-)
>
> On 1/4/06, David L. Anselmi <anselmi at anselmi.us> wrote:
> > Hex Star wrote:
> > > mm, well after the installation of linux it turns out that the IDE
> > > cable connection to the ATA controller was actually half out for some
> > > reason, it's now completely in...do you think this could be the cause
> > > of these errors and thus they could be ignored (perhaps some minor
> > > corruption occured due to that but it can be ignored)? Or do you think
> > > it'd be worth trying a reinstall since this may mean there's major
> > > corruption? Thanks for your reply and help! :-)
> >
> > I think the cable is a likely cause for your errors on both drives.  If
> > it were my drive I'd do whatever seemed easy to verify the files on it
> > and then not worry about it.
> >
> > The only time I've seen these errors is when the drive was failing.  You
> > can use badblocks to help diagnose that but you'd be best off verifying
> > the drive with the manufacturer's diagnostics.
> >
> > Although gmail may make it convenient for you to reply to yourself over
> > and over you'll get better answers if your posts are convenient for your
> > readers.  That means complete but concise.
> >
> > Dave
> > _______________________________________________
> > CLUE-tech mailing list
> > CLUE-tech at cluedenver.org
> > http://cluedenver.org/mailman/listinfo/clue-tech
> >
>
_______________________________________________
CLUE-tech mailing list
CLUE-tech at cluedenver.org
http://cluedenver.org/mailman/listinfo/clue-tech