| Author |
Message |
   
Anonymous
| | Posted on Saturday, Jul 19, 2003 - 23:01: | |
During the check for errors on my NTFS disk the system brings up the message that there is a bad system file name number 9 and 11. The disk is working properly and have no problems with reading and writing, but reorganizing partitions is not working. Is there any solution how to repair those filenames with WinHex or any other software. (chkdsk does not repair this). Thanx for any help. bEEnHeX |
   
Stefan Fleischmann (Admin)
| | Posted on Saturday, Jul 19, 2003 - 23:08: | |
Is this the exact error message? Maybe it means that the system files number 9 and 11 in the master file table have invalid names. If so, you could change them back to their original names ($Quota and $UpCase, in Unicode) manually, e. g. by copying the names entries from the FILE records 9 and 11 of a different NTFS-formatted drive. How to find these entries in the master file table is explained here. |
   
Michael Niemand
Username: minimalniemand
Registered: N/A
| | Posted on Wednesday, Oct 24, 2007 - 23:16: | |
I received the same error while using Partition Magic. I read about that a few times on the net. Seems it only occurs on external drives, connected via Firewire (and USB?). I believe it's caused by switching of the HD before unmounting it or havin it on, when shutting down windows and having it off, when starting Win up again ... Then an error message appears like: "Data Loss while writing bla $Mft bla" as bubble above the system tray. I never cared about that, until i tried to re-partition that drive with PM ... |
   
Alfons Kramer
Username: admin3
Registered: 4-2004
| | Posted on Thursday, Oct 25, 2007 - 10:20: | |
This is definitely the case. NTFS is not designed for removable drives. FAT can tolerate such usage, NTFS not. Turning off the drive before dismount will cause write behind errors, as you reported. Nevertheless, theoretically there should only be a data loss, no inconsistent NTFS structures. After all, NTFS is a journaling FS and makes use of transactions to make sure that at least all FS structures are consistent, under all circumstances. So you should consider to report this problem to the NTFS folkes. |
|