I suspect you're on the right track, a few weeks ago I ran Maxtor's Powermax
to run a full surface check on both 6Y080L0 80gb hd's because occasionally
XP's chkdsk.exe and/or Norton's Disk Doctor would find an error - sometimes
with the amount of free space reported etc. ..anyway Powermax.exe marked out
on my 2nd hd / drives g: h: i: j: and k:-
1,024 bytes in bad sectors, on drive h: and
160 KB in bad sectors, on drive i:
I gave all drives a good hammering with chkdsk.exe and Norton Diskdoctor
before and after running Powermax.exe surface scan, and then converting all
drives to NTFS
All seems fine but, while I've been rambling, I've just run chkdsk.exe on
all drives and there's no bad sectors anywhere, i.e. the bad sectors that
were on drives' h: and i: seem to have vanished. ....did I read somewhere
that in hd design there is a small pool of storage space to compensate for
surface errors so that the user thinks he's got a perfect hard disk when in
reality they've nearly all got faults ? :-)
I used Alex Nichols CONVERT C:/FS:NTFS command when I finally converted
all drives to NTFS .....now I'm wondering if the procedure has reclaimed my
161 kb's bad clusters ....should I run Powermax again ? ....anyway serves
me right for not checking the switches for xp's "convert" command.
regards, Richard
"CS" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> On Sun, 29 Aug 2004 00:20:59 +0100, "RJK" <(E-Mail Removed)>
> wrote:
>
> >I converted my fat32 drives c: through k: (2 hd's) to NTSF, and was
> >following Alex Nichols advice :-
> >http://aumha.org/win5/a/ntsfcvt.php to "slide," (to ensure that I get 4k
> >clusters ?), my drives when it hiccupped on my I: drive, where I keep
all
> >my programs and most of my data and it took AGES to roll back, because
'it'
> >had found an "error" on the drive. And the same thing happened on my J:
> >drive ...my other drive where I keep a few thousand photos.
> >
> >Interestingly, for me at least, I started to "slide" drive J: for just
two
> >or three seconds and then changed my mind, and it took nearly an hour to
> >roll back !
> >
> >In the end I copied drives I: and J: into folders on hd0 , then deleted
the
> >originals on hd1 - where they normally reside, and then BootitNG "slid"
> >drives I: and J: !! ..which all went okay.
> >
> >....my drives c d e f are on hd0 and g h i j k are on hd1 ..normally.
> >
> >So it seems that BootitNG can't cope with drive with 2 or 3 gigabytes
worth
> >of data on them, (and lots of spare room) ?
> >
> >regards, Richard
>
> That surprises me. I have used BING to align clusters (as Alex has
> advised) several times without a problem whatsoever. Did you run
> chkdsk /f on the drives prior to using BING? It's possible you had
> clusters that were bad or had errors. I don't think the amount of
> data on the drive should make a difference except that it would
> naturally take longer to align the clusters where more data was
> present.
>
Similar Threads
