Both drive's directorys corupt and unreadable after copying
I added a new drive to replace a smaller drive to my box and now after copying the old active drive to the new active drive both the orginal drive and now the new drive shows that the directory is corupt and unreadable when I try to run System Suite Jet Defrag.
I added a new drive to replace a smaller drive to my box and now after copying the old active drive to the new active drive both the orginal drive and now the new drive shows that the directory is corupt and unreadable when I try to run System Suite Jet Defrag. Chkntfs shows it is dirty.
The box has 2 drives both partitioned that I can switch between the 2 and boot from either one via a toggle switch on the front panel.
All 4 partitions were FAT32 that I converted to NTFS using the convert utility within 2k.
I used Partition Magic to partition and format the new drive. I used Drive Image to copy the active partition from the larger of the 2 orginal drives that were in the system to the new drive's active partition.
When I finished using DI, the orginal active drive's partition was hidden (no idea why, I didn't choose that option) I unhide it and then had to make it active again.
Both active partitions and the 2nd partition of both drivers are accessible. I'm typing this from the copyied drive right now.
I'm new to NTFS and have no idea what happened and how to fix it. I did run chkdisk twice, but it comes up clean.
The box has 2 drives both partitioned that I can switch between the 2 and boot from either one via a toggle switch on the front panel.
All 4 partitions were FAT32 that I converted to NTFS using the convert utility within 2k.
I used Partition Magic to partition and format the new drive. I used Drive Image to copy the active partition from the larger of the 2 orginal drives that were in the system to the new drive's active partition.
When I finished using DI, the orginal active drive's partition was hidden (no idea why, I didn't choose that option) I unhide it and then had to make it active again.
Both active partitions and the 2nd partition of both drivers are accessible. I'm typing this from the copyied drive right now.
I'm new to NTFS and have no idea what happened and how to fix it. I did run chkdisk twice, but it comes up clean.
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
I think you misunderstand..........Chkdisc doesn't show any errors!
I don't want chkdisk to stop running when it has to, it's not running on every reboot/boot anyway.
It's the error from chkntfs and the error within Jet Defrag (Fix It Utilities from vCom formerly Ontrack) that is the problem!
Bottom line something is wrong when chkntfs says the directory is dirty.
I did make a image of the drive also and I tried that route, but the same thing after it was restored!
I ran the drfrag problem on the 2nd partition and it worked fine.
I don't want chkdisk to stop running when it has to, it's not running on every reboot/boot anyway.
It's the error from chkntfs and the error within Jet Defrag (Fix It Utilities from vCom formerly Ontrack) that is the problem!
Bottom line something is wrong when chkntfs says the directory is dirty.
I did make a image of the drive also and I tried that route, but the same thing after it was restored!
I ran the drfrag problem on the 2nd partition and it worked fine.
Quote:Au contrare mon frereBoy.........I love it when you talk dirty...........
Quote: if it sees thru strcomp type function calls that autochk * is not that, but set to a SPECIFIC disk, it will leave that disk alone rather than risk MFT$ or FAT corruption as well as file data loss. Ok, I'm lost. What is "strcomp" and what does "autochk * is not that, but set to a SPECIFIC disk" mean?
Thats for all the other info, though alot of it is over my head. I don't want to skirt the issue since it is a smoking gun. Is there something I might of done wrong with PM or DI? I did use the default cluster size BTW.
One more deal; I noticed that the cluster size on the 2nd partition (69GB) is 4096k and all the other cluster sizes are 512k on this and the other drive. Is it just that the 69GB partition is larger than that 32GB limit it uses a larger cluster size?
Someone else suggested bad memory in this forum:
http://www.tech-report.com/forums/viewtopic.php?p=67618#67618
Quote: if it sees thru strcomp type function calls that autochk * is not that, but set to a SPECIFIC disk, it will leave that disk alone rather than risk MFT$ or FAT corruption as well as file data loss. Ok, I'm lost. What is "strcomp" and what does "autochk * is not that, but set to a SPECIFIC disk" mean?
Thats for all the other info, though alot of it is over my head. I don't want to skirt the issue since it is a smoking gun. Is there something I might of done wrong with PM or DI? I did use the default cluster size BTW.
One more deal; I noticed that the cluster size on the 2nd partition (69GB) is 4096k and all the other cluster sizes are 512k on this and the other drive. Is it just that the 69GB partition is larger than that 32GB limit it uses a larger cluster size?
Someone else suggested bad memory in this forum:
http://www.tech-report.com/forums/viewtopic.php?p=67618#67618
To keep things more interesting I wiped the drive using the Maxtor MaxBlast (write zero's to drive) though after 2 hours doing a complete job I canceled it and did a fast job which was done as soon as I clicked start.
Then I just used Drive Image (no PM this time), set the partition size to 8300MB instead of the 5800MB of the image to be restored (don't know if that is a issue itself) and ran it checking bad sectors check and verify contents and all went good.
BTW, the other times no error was reported in eith PM or DI!
I rebooted and ran chkntfs and it showed the active partition as "not dirty"!!
Then I ran Je tDefrag and after 8% it gave the same error at the same spot that the drive's directory was "corupt and unreadable!
I went back to chkntfs and it reported that the drive was "dirty" again!
WTF?
Any idea what is happening? I can only guess it was the conversion process from FAT32 to NTFS. The image I used was after I coneveted to NTFS. I also have a FAT32 image (before I converted) that I haven't tried.
Then I just used Drive Image (no PM this time), set the partition size to 8300MB instead of the 5800MB of the image to be restored (don't know if that is a issue itself) and ran it checking bad sectors check and verify contents and all went good.
BTW, the other times no error was reported in eith PM or DI!
I rebooted and ran chkntfs and it showed the active partition as "not dirty"!!
Then I ran Je tDefrag and after 8% it gave the same error at the same spot that the drive's directory was "corupt and unreadable!
I went back to chkntfs and it reported that the drive was "dirty" again!
WTF?
Any idea what is happening? I can only guess it was the conversion process from FAT32 to NTFS. The image I used was after I coneveted to NTFS. I also have a FAT32 image (before I converted) that I haven't tried.
Any one else can input something?
I tried it again and the first pass of JetDefrag stops at the same 8% complete as before with the same error.
Chkntfs reports it again as "dirty"
I ran chkdsk and it reported no errors, ran chkntfs and it reported it as "not dirty" again!
I haven't tried Norton's Speed Disk yet which I will to see if it is a bug in SS.
I tried it again and the first pass of JetDefrag stops at the same 8% complete as before with the same error.
Chkntfs reports it again as "dirty"
I ran chkdsk and it reported no errors, ran chkntfs and it reported it as "not dirty" again!
I haven't tried Norton's Speed Disk yet which I will to see if it is a bug in SS.
I took the FAT32 image and used that, then coneverted it to NTFS and all seems fine. I guess it was something with the conversion to NTFS DI didn't like.
Now, the MFT Zone is a issue I think, but I guess I will live with that. It seems larger than it should (varies up to 2.5 GB on certain partitions). On various drives it varies alot.
Now, the MFT Zone is a issue I think, but I guess I will live with that. It seems larger than it should (varies up to 2.5 GB on certain partitions). On various drives it varies alot.
