From: "Geo" 

Besides the obvious problems with the drive hardware or cabling or even a
wrong driver, it could also be memory going flakey. Typically that will
appear to be bad blocks in the swap file or something along those lines.

Anything in the event log look related?

Geo.

"Scott"  wrote in message
news:43133185$1{at}w3.nls.net...
> Scott wrote:
>
> Odd, still getting directory errors although I reformatted the disk and
> then restored it with all files replaced (wasn't the recommended method
> according to ntbackup; it wanted to keep files, newer I think).
>
> Could it be an odd corruption in the OS files?
>
> > Good morning all!
> >
> > My problem, to get to it, is a hard drive issue/
> >
> > I Ghosted a copy of my previous drive (80 gig) to a newer 100 gig.
> >
> > The previous drive has already been retasked.
> >
> > But now, I'm getting a drive geometry error:
> >
> > CHKDSK discovered free space marked as allocated in the
> > master file table (MFT) bitmap.
> > CHKDSK discovered free space marked as allocated in the volume bitmap.
> > Windows found problems with the file system.
> > Run CHKDSK with the /F (fix) option to correct these.
> >
> >
> > I have run chkdsk multiple times both in /f and /r modes; no joy.
> >
> > Also, on occasion, I get "Orphaned file" and
"Truncating extents"
> > errors. This is obviously serious.
> >
> > So... I've done an NTBACKUP of the drive. I'd like to know what the
> > proper restore should be. Also, was there something I should have done
> > in the backup to ensure (besides verify which I did, no errors) it's
> > proper restore?
> >
> > Scott/SpiritWolf

--- BBBS/NT v4.01 Flag-5