Unable to mount Elements(external HD) [duplicate]

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
1
down vote

favorite













This question already has an answer here:



  • Cannot mount USB stick - errors out with “$MFTMirr does not match $MFT”

    2 answers



I have inserted my MD Elements Hard Drive.I can not mount it,this is the first time that I have a problem like this.



Error mounting /dev/sdc1 at /media/milenko/Elements: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000" "/dev/sdc1" "/media/milenko/Elements"' exited with non-zero exit status 13: $MFTMirr does not match $MFT (record 0)


I am confused with this.What does MFTMirr stand for?
How to solve this?







share|improve this question












marked as duplicate by pomsky, Eliah Kagan, karel, Community♦ Apr 22 at 12:55


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.














  • ($)MFT = manifest table; part of the directory structure used by NTFS. The mirror (which should be identical) to the main table differs, meaning their are logical errors on the drive. If you write most data on this drive in windoze, i would use windoze to correct it. Yes Ubuntu has tools for it, but given its a NTFS implies to me you use it more with windoze...
    – guiverc
    Apr 22 at 8:58











  • @guiverc No,I have not used Windows for 5-6 months.It surprised me.
    – MikiBelavista
    Apr 22 at 9:49














up vote
1
down vote

favorite













This question already has an answer here:



  • Cannot mount USB stick - errors out with “$MFTMirr does not match $MFT”

    2 answers



I have inserted my MD Elements Hard Drive.I can not mount it,this is the first time that I have a problem like this.



Error mounting /dev/sdc1 at /media/milenko/Elements: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000" "/dev/sdc1" "/media/milenko/Elements"' exited with non-zero exit status 13: $MFTMirr does not match $MFT (record 0)


I am confused with this.What does MFTMirr stand for?
How to solve this?







share|improve this question












marked as duplicate by pomsky, Eliah Kagan, karel, Community♦ Apr 22 at 12:55


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.














  • ($)MFT = manifest table; part of the directory structure used by NTFS. The mirror (which should be identical) to the main table differs, meaning their are logical errors on the drive. If you write most data on this drive in windoze, i would use windoze to correct it. Yes Ubuntu has tools for it, but given its a NTFS implies to me you use it more with windoze...
    – guiverc
    Apr 22 at 8:58











  • @guiverc No,I have not used Windows for 5-6 months.It surprised me.
    – MikiBelavista
    Apr 22 at 9:49












up vote
1
down vote

favorite









up vote
1
down vote

favorite












This question already has an answer here:



  • Cannot mount USB stick - errors out with “$MFTMirr does not match $MFT”

    2 answers



I have inserted my MD Elements Hard Drive.I can not mount it,this is the first time that I have a problem like this.



Error mounting /dev/sdc1 at /media/milenko/Elements: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000" "/dev/sdc1" "/media/milenko/Elements"' exited with non-zero exit status 13: $MFTMirr does not match $MFT (record 0)


I am confused with this.What does MFTMirr stand for?
How to solve this?







share|improve this question













This question already has an answer here:



  • Cannot mount USB stick - errors out with “$MFTMirr does not match $MFT”

    2 answers



I have inserted my MD Elements Hard Drive.I can not mount it,this is the first time that I have a problem like this.



Error mounting /dev/sdc1 at /media/milenko/Elements: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000" "/dev/sdc1" "/media/milenko/Elements"' exited with non-zero exit status 13: $MFTMirr does not match $MFT (record 0)


I am confused with this.What does MFTMirr stand for?
How to solve this?





This question already has an answer here:



  • Cannot mount USB stick - errors out with “$MFTMirr does not match $MFT”

    2 answers









share|improve this question











share|improve this question




share|improve this question










asked Apr 22 at 8:46









MikiBelavista

2412619




2412619




marked as duplicate by pomsky, Eliah Kagan, karel, Community♦ Apr 22 at 12:55


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.






marked as duplicate by pomsky, Eliah Kagan, karel, Community♦ Apr 22 at 12:55


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.













  • ($)MFT = manifest table; part of the directory structure used by NTFS. The mirror (which should be identical) to the main table differs, meaning their are logical errors on the drive. If you write most data on this drive in windoze, i would use windoze to correct it. Yes Ubuntu has tools for it, but given its a NTFS implies to me you use it more with windoze...
    – guiverc
    Apr 22 at 8:58











  • @guiverc No,I have not used Windows for 5-6 months.It surprised me.
    – MikiBelavista
    Apr 22 at 9:49
















  • ($)MFT = manifest table; part of the directory structure used by NTFS. The mirror (which should be identical) to the main table differs, meaning their are logical errors on the drive. If you write most data on this drive in windoze, i would use windoze to correct it. Yes Ubuntu has tools for it, but given its a NTFS implies to me you use it more with windoze...
    – guiverc
    Apr 22 at 8:58











  • @guiverc No,I have not used Windows for 5-6 months.It surprised me.
    – MikiBelavista
    Apr 22 at 9:49















($)MFT = manifest table; part of the directory structure used by NTFS. The mirror (which should be identical) to the main table differs, meaning their are logical errors on the drive. If you write most data on this drive in windoze, i would use windoze to correct it. Yes Ubuntu has tools for it, but given its a NTFS implies to me you use it more with windoze...
– guiverc
Apr 22 at 8:58





($)MFT = manifest table; part of the directory structure used by NTFS. The mirror (which should be identical) to the main table differs, meaning their are logical errors on the drive. If you write most data on this drive in windoze, i would use windoze to correct it. Yes Ubuntu has tools for it, but given its a NTFS implies to me you use it more with windoze...
– guiverc
Apr 22 at 8:58













@guiverc No,I have not used Windows for 5-6 months.It surprised me.
– MikiBelavista
Apr 22 at 9:49




@guiverc No,I have not used Windows for 5-6 months.It surprised me.
– MikiBelavista
Apr 22 at 9:49










1 Answer
1






active

oldest

votes

















up vote
3
down vote



accepted










This answer appears to answer your question. In general it's best to use Windows to fix errors on NTFS hard drives.




But because it is NTFS, the only way to truly repair NTFS is Windows' chkdsk utility. (There is a ntfsfix command, but it is NOT going to be of the same quality of fix as Windows' utilities to check NTFS disks).




My personal experience aligns with this.






share|improve this answer
















  • 2




    Please do not post duplicate answers on different questions. It just creates more work for the moderators. If the questions are so similar that the same answer works on each, then the later of the two is likely a duplicate and should be flagged as such.
    – pomsky
    Apr 22 at 11:56

















1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
3
down vote



accepted










This answer appears to answer your question. In general it's best to use Windows to fix errors on NTFS hard drives.




But because it is NTFS, the only way to truly repair NTFS is Windows' chkdsk utility. (There is a ntfsfix command, but it is NOT going to be of the same quality of fix as Windows' utilities to check NTFS disks).




My personal experience aligns with this.






share|improve this answer
















  • 2




    Please do not post duplicate answers on different questions. It just creates more work for the moderators. If the questions are so similar that the same answer works on each, then the later of the two is likely a duplicate and should be flagged as such.
    – pomsky
    Apr 22 at 11:56














up vote
3
down vote



accepted










This answer appears to answer your question. In general it's best to use Windows to fix errors on NTFS hard drives.




But because it is NTFS, the only way to truly repair NTFS is Windows' chkdsk utility. (There is a ntfsfix command, but it is NOT going to be of the same quality of fix as Windows' utilities to check NTFS disks).




My personal experience aligns with this.






share|improve this answer
















  • 2




    Please do not post duplicate answers on different questions. It just creates more work for the moderators. If the questions are so similar that the same answer works on each, then the later of the two is likely a duplicate and should be flagged as such.
    – pomsky
    Apr 22 at 11:56












up vote
3
down vote



accepted







up vote
3
down vote



accepted






This answer appears to answer your question. In general it's best to use Windows to fix errors on NTFS hard drives.




But because it is NTFS, the only way to truly repair NTFS is Windows' chkdsk utility. (There is a ntfsfix command, but it is NOT going to be of the same quality of fix as Windows' utilities to check NTFS disks).




My personal experience aligns with this.






share|improve this answer












This answer appears to answer your question. In general it's best to use Windows to fix errors on NTFS hard drives.




But because it is NTFS, the only way to truly repair NTFS is Windows' chkdsk utility. (There is a ntfsfix command, but it is NOT going to be of the same quality of fix as Windows' utilities to check NTFS disks).




My personal experience aligns with this.







share|improve this answer












share|improve this answer



share|improve this answer










answered Apr 22 at 10:40









Jeremy

1,43231832




1,43231832







  • 2




    Please do not post duplicate answers on different questions. It just creates more work for the moderators. If the questions are so similar that the same answer works on each, then the later of the two is likely a duplicate and should be flagged as such.
    – pomsky
    Apr 22 at 11:56












  • 2




    Please do not post duplicate answers on different questions. It just creates more work for the moderators. If the questions are so similar that the same answer works on each, then the later of the two is likely a duplicate and should be flagged as such.
    – pomsky
    Apr 22 at 11:56







2




2




Please do not post duplicate answers on different questions. It just creates more work for the moderators. If the questions are so similar that the same answer works on each, then the later of the two is likely a duplicate and should be flagged as such.
– pomsky
Apr 22 at 11:56




Please do not post duplicate answers on different questions. It just creates more work for the moderators. If the questions are so similar that the same answer works on each, then the later of the two is likely a duplicate and should be flagged as such.
– pomsky
Apr 22 at 11:56


Popular posts from this blog

How do so many people here on Academia.SE, and in general, afford lavish higher education programs?

Trouble downloading packages list due to a “Hash sum mismatch” error

How do I move numbers in filenames, in a batch renaming operation?