|
|
"Jim" <jim@xxxxxxxxxxx> wrote in message
news:p07n74holdltq8cue64sg2lacmge5ena4h@xxxxxxxxxx
> On Mon, 7 Jul 2008 13:21:00 +0100, "Mortimer" <me@xxxxxxxxxxx> wrote:
>
>>Over the past couple of months I've been called to three customers whose
>>PCs
>>have failed to boot. When I put the HDD in a second computer, Windows
>>CHDSKs
>>it, corrects a few filesystem errors and leaves the disk in a state where
>>it
>>will boot the original PC perfectly.
>>
>>In all three cases, the PCs have had SATA drives. I've never seen this
>>symptom with IDE disks. Is there something about SATA drives which makes
>>them more vulnerable to filesystem corruption than IDE ones, assuming the
>>same filesystem (NTFS) and OS (XP) in both cases?
>
> You may find that if you change the offending drive to another
> SATA slot it may clear this problem, the failing to boot part if
> not the filesystem corruption. It worked for me.
I'll try that if I encounter another PC that displays this symptom: it's
quicker to change the SATA lead to another socket on the customer's PC that
to bring the PC back to base to connect the disk into a different PC. I
suppose the latter is an extreme case of what you are recommending - the
disk in connected to a different SATA connector *on a different PC* ;-)
Assuming that the PC will boot, there is every chance the Windows will check
and repair any filesystem corruption if it deems this to be necessary.
|
|