One of your disks needs to be checked ...

[js]

Windows XP gives me this message every few days when I boot up:
"One of your disks needs to be checked for consistency ..."

then CHKDSK starts up and I get messages like ..

"truncating badly linked attribute records"
and
"deleting corrupt attribute record (number) from file record segment ..."

I thought this must have been a faulty hard drive so I bought a new one, but
I still get the same thing happening.
Any ideas please?

 

[Guest]

And just what do you expect? One is not advised, but is it appropriate to
presume that you simply cloned the old drive to the new one and inherited
every faulty bit from the bad drive?

Once you run CHKDSK over the new drive it should remain stable.

 

[js]

No,

I did a clean install on the new drive.

 

[Rick \Nutcase\ Rogers]

Hi,

Have you tried running 'chkdsk <drive> /r' yet?

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

 

[theinvisibleGhost]

I did a really nice reply to this and Google Screwed up, and
FireFox being the clever browser that it is didn't save my response.
So heres the brief version!
If your Disk > 127Gb then Windows 2000/XP + 3rd Party Utils really
have a habit of screwing it up. This is due to 40bit Mode
addressing which only windows actually seems to use.
Most 3rd party utils don't use this and so mess everything up
over 127gb's.
Advice
Use Partition Magic to Create partion over 127Gb threshold.
Label it DangerZone. Only use it as temporary storage.
Not a nice answer I know
2ndly.
Avoid all old Disk utils.
By this I mean even one year is probably out of date :-(
How've i found this out? Lots of bad luck and searching the net!
3rdly GetDataback is a nice utility that gets your data back.
Worth it's wait in Gold, after corruptions
4th CheckDisk does a good job sometimes
5th Be Warned even the windows installer Corrupts the Partitions.
EVEN IF YOU'VE SLIPSTREAMED THE SERVICE PACKS.


Why MS moves between chkdsk and Scandisk every other operating
System beats me.

I hope they get this sorted out for Longhorn.

Regards
TheinvisibleGhost

Hi,

Have you tried running 'chkdsk <drive> /r' yet?

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

LimeWireWin.exe

 

[theinvisibleGhost]

I dunno what the guy is on about with the cloning stuff
You can't clone bad sectors!
If your new hard disk is greater than 127 GB's
then Windows and it's third party utilitys are really poor
at managing it. Basically Windows needs to use 40bit mode addressing
which is turned on as default in Service pack one for XP I believe.
However anything and everything will do it's best to corrupt it.
I have a 160GB disk, and everything over 127gb I think of as unusable
because it's so unreliable.
I'm running 2000, and what I've done is to use Partition Magic
to work out which parts of the disk are safe, and put the rest
of the disk as a DANGERZONE! I only use it for moving things
around. At the moment it's fine cuz i'm no where near using
that much space. But I'm thinking I'll have to upgrade when
Longhorn comes out.

Things that will corrupt over 127GB
-The Windows Setup. Basically Windows doesn't appear
to work in 40bit mode addressing until you've installed it.
Even if you slipstream the servicepacks in.
-Older Defragmenters. I had a version of Diskeeper 9.0 which
set it off last. Thats what made me move over to the Dangerzone
system.

I'd imagine all other Disk tools that write straight to disk also.
If you need a utility to recover data I recommend GetDataBack.
You'll have to pay for it, but it's worth it's wait in Gold!

ChkDsk sometimes fixes sometimes not. I wish I could understand
Microsofts which disk utility shall we use today theory with
Scandisk vs ChkDsk... but there we go.
Hope that helped.

If your using a disk under 127Gb's then it's something else!
I'd then go with a clean install.
But it would mean theres a utility doing the damage, as i said
you definitley can't clone bad sectors (Well not without
dropping the disk several times

 

[js]

The disk is only a 40Gb

When this problem happens and I get the message, CHKDSK starts by itself
and when finished it reports that the problem was fixed.

 

[Rebecca Chen [MSFT]]

Hello,

I would like to jump in and provide some cents here.

I understand you have performed a clean installation on the new 40G hard
disk, however, have you attached the old disk as a secondary IDE disk? If
so, when Windows starts up, it will check the consistency on all disks and
partitions. If the old disk is still attached, the system will bring up
CHKDSK to check the corrupted partition.

Some issues can be fixed by CHKDSK, some cannot, especially due to the
physical failure. I suggest you perform a full check process on the
problematic disk which is indicated CHKDSK by to make identify the problem.

NOTE: When CHKDSK begins to run after you re-start the computer, you will
see CHKDSK intends to check which partition. Please refer to the following
article to perform a full disk scan on this partition. Tick both
"Automatically fix file system errors" and "scan for and attempt recovery
of bad sectors". It is the same in Xp system.

How to Perform Disk Error Checking in Windows XP
http://support.microsoft.com/kb/315265/EN-US/

any update, let us get in touch!

Best regards,

Rebecca Chen

MCSE2000 MCDBA CCNA


Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.