<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>$MFTMirr on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/mftmirr/</link><description>Recent content in $MFTMirr on Karpoke - Just Another Blog</description><generator>Hugo -- 0.159.0</generator><language>es</language><lastBuildDate>Thu, 06 Sep 2012 12:46:00 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/mftmirr/index.xml" rel="self" type="application/rss+xml"/><item><title>Solucionado el error "$MFTMirr does not match $MFT (record 0)." al montar una partición NTFS</title><link>http://karpoke.ignaciocano.com/2012/09/06/solucionado-el-error-mftmirr-does-not-match-mft-record-0-al-montar-una-particion-ntfs/</link><pubDate>Thu, 06 Sep 2012 12:46:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2012/09/06/solucionado-el-error-mftmirr-does-not-match-mft-record-0-al-montar-una-particion-ntfs/</guid><description>&lt;p&gt;Si intentamos montar un disco o partición en NTFS, el formato que
utiliza Windows, que no ha sido desconectada &amp;ldquo;de forma segura&amp;rdquo;, es
posible que no podamos montarla y que recibamos el siguiente error:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;$ sudo mount -t ntfs-3g /dev/sdb1 /media/ntfs
$MFTMirr does not match $MFT (record 0).
Failed to mount &amp;#39;/dev/sdb1&amp;#39;: Error de entrada/salida
NTFS is either inconsistent, or there is a hardware fault, or it’s a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the &amp;#39;dmraid&amp;#39; documentation
for more details.
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Incluso si utilizamos el parámetro &lt;code&gt;-o force&lt;/code&gt; nos sigue devolviendo el
mismo error.&lt;/p&gt;</description></item></channel></rss>