Re: S.M.A.R.T. command failure. BIOS issue after security update
From: Fred (anonymous_at_discussions.microsoft.com)
Date: 03/09/04
- Next message: Pegasus \(MVP\): "Re: xp client can't add in 2000 domain"
- Previous message: Chris Palmer: "RE: basic help"
- In reply to: Bruce Chambers: "Re: S.M.A.R.T. command failure. BIOS issue after security update"
- Next in thread: Bruce Chambers: "Re: S.M.A.R.T. command failure. BIOS issue after security update"
- Reply: Bruce Chambers: "Re: S.M.A.R.T. command failure. BIOS issue after security update"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 9 Mar 2004 04:06:32 -0800
Thanks. Good advice, and I'll do those backups now. Odd
that this occurred immediately after the patch
installation. I realized that the error message was being
generated between the HDD and BIOS, but it wouldn't be the
first time I've seen software updates change the MBR or
BIOS settings. I'm new to XP tho, and not quite sure what
to expect with it's updates.
I've run the latest Maxtor Diagnostics and it reports no
errors on the drive. But I'll contact Maxtor as well.
Was 'hoping' somebody else might have experienced this
upon install of the patch and it wasn't *just* my system
bombing :)
>-----Original Message-----
>Greetings --
>
>>From whatis.com (http://whatis.techtarget.com/):
>
> "Self-Monitoring Analysis and Reporting Technology
(S.M.A.R.T.) is
>an interface between a computer's start-up program or
BIOS (basic
>input/output system) and the computer hard disk. It is a
feature of
>the Enhanced Integrated Drive Electronics (EIDE)
technology that
>controls access to the hard drive. If S.M.A.R.T is
enabled when a
>computer is set up, the BIOS can receive analytical
information from
>the hard drive and determine whether to send the user a
warning
>message about possible future failure of the hard drive. "
>
> As you can see, this is purely a function of the PC's
>hardware/firmware and the hard drive; it has nothing to
do with WinXP,
>or any other operating system.
>
> Having seen the same error, I can only say: "Back up
your data
>daily until you replace that drive."
>
> On those machines I on which I've seen those
S.M.A.R.T. warnings,
>catastrophic hard drive failures invariably followed.
Some hard
>drives lasted for a few days after the warnings first
appeared, one
>lasted months, and some lasted only minutes. I suppose
the one that
>lasted months could be considered a false alarm, as
months hardly
>translate to "imminent," but, on the whole, I'd suggest
you take the
>warnings seriously.
>
>
>Bruce Chambers
>--
>Help us help you:
>http://dts-l.org/goodpost.htm
>http://www.catb.org/~esr/faqs/smart-questions.html
>
>You can have peace. Or you can have freedom. Don't ever
count on
>having both at once. -- RAH
>
- Next message: Pegasus \(MVP\): "Re: xp client can't add in 2000 domain"
- Previous message: Chris Palmer: "RE: basic help"
- In reply to: Bruce Chambers: "Re: S.M.A.R.T. command failure. BIOS issue after security update"
- Next in thread: Bruce Chambers: "Re: S.M.A.R.T. command failure. BIOS issue after security update"
- Reply: Bruce Chambers: "Re: S.M.A.R.T. command failure. BIOS issue after security update"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
