Re: C:\ partition with a interemittent bad sector

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

IMO if a hd shows bad sectors it should be dumped, or only used for stuff
you dont mind losing.
Having said that, any iffy psu can cause 'odd' hd problems such as this

"jbclem" <jbclem1@xxxxxxxxxxx> wrote in message
news:VUE8j.83$v43.0@xxxxxxxxxxxxxxx
My WIn2000 PIII computer has 2 hard drives and 2 Win2000 installations (C:
ands E:). So I can always boot up in E: when this intermittent problem
happens. There seems to be a bad hard drive sector near or at the
beginning
of the C: and when it's bad I can't boot up in C: . I can run Partition
Table Doctor's surface test(from E:) and spot the bad sector, and today
when
it happened I couldn't access anything on C:, and My Computer was showing
zero bytes on C:. I could still access other partitions on that hard
drive,
D: and E:. Usually when this happens I can't boot up in C: but I can
access
files in that partition so I assumed that the problem was only in the area
where the boot record was. But today all of C: was inaccessible.

I have a new hard drive coming in the mail...but I'd like to know if there
is a program that might help me fix this problem if it's just a bad
sector.
I've run Chkdsk, I've run SpinRite, I've run the Maxtor diagnostics disk.
Neither Spinrite nor the Maxtor disk find anything wrong, but that might
just be the fact that it's an intermittent problem. Partition Table
Doctor
was finding 4 bad sectors (surface test) but today only found one. Chkdsk
finds problems and presumably fixes them. But that doesn't stop them from
reoccuring. I know that there are sectors marked as B (bad) because I see
them on of the surface tests I've conducted. But the problem is still
there. Should I try rebuilding the MBR, or rebuilding the partition
(using
Partition Table Doctor)...will I destroy something if this isn't the
problem?

This is a weird problem and I'd like some advice and suggestions for
handling it. I think most of the hard drive is ok, just this area with
the
problem. What can I do to try to fix it.

Thanks in advance...

John




.

Relevant Pages

  • FC3/XP dual boot: "invalid boot sector" after each FC3 boot
    ... I boot FC3, the ... Extended partition with the following logical partitions: ... Begin C,H,S values were large drive placeholders. ... Sectors per Cluster: 8 ...
    (Fedora)
  • FC3/XP dual boot: "invalid boot sector" after each FC3 boot
    ... I boot FC3, the ... Extended partition with the following logical partitions: ... Begin C,H,S values were large drive placeholders. ... Sectors per Cluster: 8 ...
    (linux.redhat)
  • FC3/XP dual boot: "invalid boot sector" after each FC3 boot
    ... I boot FC3, the ... Extended partition with the following logical partitions: ... Begin C,H,S values were large drive placeholders. ... Sectors per Cluster: 8 ...
    (linux.redhat.install)
  • Re: repairing HDD partition
    ... >> this is the output I got from findpart when I booted it from a DOS boot ... >> can be not easy repairable FAT sectors. ... >> Partition Status Type Vol. Label Mbytes System Usage ... >>> That's why the RAID BIOS mangled FAT's boot sector. ...
    (comp.sys.ibm.pc.hardware.storage)
  • Re: CRC Errors
    ... I have been running a surface scan with Scandisk on the drive to copy the data from the bad sectors to good ones so I can backup the drive to a second hard drive with Drive Image. ... when I run drive image on a disk to disk cloning operation it copies about 72% of the drive and then halts with a CRC error. ... Boot from a floppy disk and run fdisk to mark the partition as active. ... The second hard drive has two partitions on it, one for the C: partition drive Drive Image clone and the second one for the D: partition clone. ...
    (microsoft.public.windowsxp.help_and_support)