this error occured while processing Inode 115146 (max 230448)

[redmike]

Hi,

When I run using "D:\Program Files\jk defragmentor\JkDefrag.exe"  -a 3 -d 2 -q c: d: g:

I get ...

this error occured while processing Inode 115146 (max 230448)

Any info would be appreciated.

Thanks,

Mike

[jeroen]

There should be another message just before it. The message can be a temporary message caused by the MFT being changed while it is being analyzed, but if the message is repeated the next time you run JkDefrag then it indicates something is wrong in the MFT. Try running chkdsk on the volume (open the properties of the volume, tools tab, run the error checking).

[redmike]

the only message before the warning one is 'Phase1 analyzing'

I have three partitions and I just ran chkdsk on all three of them and I got no error messages.

JKdefrag still shows the same error however.

I ran chkdsk a couple of days ago (after I had run JKdefrag a few times) because I wanted to resize a partition and there was a message, "unallocated space, showing as used" or something very similar and chkdsk fixed the problem.

thanks,

Mike

[jeroen]

the only message before the warning one is 'Phase1 analyzing'

I think you are talking about what you see on the screen. Please check the JkDefrag.log file, there MUST be an extra message just before it.

JKdefrag still shows the same error however.

Perhaps it is caused by the 941715 bug? See the "known problems" chapter on the JkDefrag homepage.

[redmike]

I have got a a SATA external but it's only used for back ups and is not connected when doing the defrag.

08:38:37   VolumeSerialNumber: E6B89C65B89C35D1
08:38:39 This is not a valid MFT record, it does not begin with FILE (maybe trying to read past the end?).

above is from the log file,

Mike

[Myriades]

Hi redmike. plz post the log

[redmike]

Hi redmike. plz post the log

Thanks for all the help,

Mike

[jeroen]

08:38:39 This is not a valid MFT record, it does not begin with FILE (maybe trying to read past the end?).

Your harddisk is definitely corrupted, there is some junk in the middle of your MFT (Master File Table). NTFS is quite robust and simply ignores the junk. After this message in the JkDefrag logfile there should be a hex dump of the data, which might give you a clue as to which program has corrupted your harddisk. It may be a hardware problem, but I think it is more likely software. My advise is to copy everything of from the disk and format the disk.

[redmike]

08:38:39 This is not a valid MFT record, it does not begin with FILE (maybe trying to read past the end?).

Your harddisk is definitely corrupted, there is some junk in the middle of your MFT (Master File Table). NTFS is quite robust and simply ignores the junk. After this message in the JkDefrag logfile there should be a hex dump of the data, which might give you a clue as to which program has corrupted your harddisk. It may be a hardware problem, but I think it is more likely software. My advise is to copy everything of from the disk and format the disk.

If by 'copy everything off from the disk and format the disk' you're talking about just 'data' then sorry I wouldn't even consider it. I have around 40 programs on my system which never gives me any problems and even JKdefrag works well.

"If it works then don't fix it".

Why would I spend 3-4 days of time and lost income just to fix an error message?

Where would the hex dump be?

and

Perhaps there is a better program for fixing the MFT ?

thanks,

Mike

[jeroen]

"If it works then don't fix it".

If you believe that, then why are you using JkDefrag? My car needs regular service after so-and-so many miles, even though it's running perfectly. I'm sure it will soon break down if I don't have a mechanic change the oilfilters, and all that. I'm not saying that your disk will explode in your face in the next three hours, but my advise is not to take any risks and to format the disk as a precautionary measure. How valuable is your data to you?

Where would the hex dump be?

Just after the error message, in the JkDefrag logfile.

[schitzn]

maybe preform a CHKDSK C: /R on the disk.  This would test for bad sectors.  Damaged MFT's in my experience can be a sign of a HDD that is pending more serious issues down the track.

[redmike]

"If it works then don't fix it".

If you believe that, then why are you using JkDefrag? My car needs regular service after so-and-so many miles, even though it's running perfectly. I'm sure it will soon break down if I don't have a mechanic change the oilfilters, and all that. I'm not saying that your disk will explode in your face in the next three hours, but my advise is not to take any risks and to format the disk as a precautionary measure. How valuable is your data to you?

Where would the hex dump be?

Just after the error message, in the JkDefrag logfile.

I very much appreciate your help but don't really see the logic in you post.

All my data is already backed up and my computer 'on the surface' is working fine.

If it crashes in the future then I will format, and spend three days putting my system back together again.

I could do all of the above now and then have a similar problem in two weeks time and then start all over again.

Why do it now?

Maybe I missing something here?

What is the value in going through all the agro now.

All my programs are functioning well - including yours - which I like very much!

Is there a better program than CHKDSK that my repair the 'minor' damage to my MFT?

thanks,

Mike

[redmike]

maybe preform a CHKDSK C: /R on the disk.  This would test for bad sectors.  Damaged MFT's in my experience can be a sign of a HDD that is pending more serious issues down the track.

I tried that earlier today and tonight include a deep scan.

I do believe that there is a problem with my MFT or something else because Acronis won't verify clones.

thanks,

Mike

[jeroen]

I very much appreciate your help but don't really see the logic in you post.

That's a pity. I wish you all the best with your disk.

[Maleko]

maybe preform a CHKDSK C: /R on the disk.  This would test for bad sectors.  Damaged MFT's in my experience can be a sign of a HDD that is pending more serious issues down the track.

why not chkdsk c: /f /r ?