<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18904"></HEAD>
<BODY
style="WORD-WRAP: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space">
<DIV><FONT color=#0000ff size=2 face=Arial><SPAN class=437094515-13042010>Sounds
crazy but I had luck with sticking the drive in the freezer for 24 hours and
then mounting it.</SPAN></FONT></DIV>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px" dir=ltr>
<DIV dir=ltr class=OutlookMessageHeader align=left><FONT size=2
face=Tahoma>-----Original Message-----<BR><B>From:</B>
tclug-list-bounces@mn-linux.org [mailto:tclug-list-bounces@mn-linux.org]<B>On
Behalf Of </B>Ryan Coleman<BR><B>Sent:</B> Tuesday, April 13, 2010 10:35
AM<BR><B>To:</B> TCLUG Mailing List<BR><B>Subject:</B> Re: [tclug-list]
Mounting a bad NTFS partition<BR><BR></FONT></DIV>I trust that it was not
dropped - the device does not make any abnormal noises that would lead
me to believe that is the case. It spins up normally...
<DIV>
<DIV><BR></DIV>
<DIV>I have the image made ...</DIV>
<DIV>
<DIV><I>[root@server /mount/archive/da-harddrive]# ls -la</I></DIV>
<DIV><I>total 78188872</I></DIV>
<DIV><I>-rw-r--r-- 1 ryan wheel 80026361856 Apr 13 03:46
80gb.drive</I></DIV>
<DIV><I>-rw-r--r-- 1 ryan wheel
425 Apr 13 03:46 80gb.log</I></DIV>
<DIV><BR></DIV></DIV>
<DIV>When I try to mount that with mount_ntfs I get the following (expected)
error:</DIV>
<DIV>
<DIV><I>mount_ntfs: /mount/archive/da-harddrive/80gb.drive: Block device
required</I></DIV>
<DIV><BR></DIV>
<DIV>Is there a way to fake the Block device? I also tried just now to mount
the physical partition with the fusefs NTFS port and got the following
response:</DIV>
<DIV>
<DIV><I>[root@server /mount/archive/da-harddrive]# ntfs-3g /dev/da0
/mount/drive1</I></DIV>
<DIV><I>NTFS signature is missing.</I></DIV>
<DIV><I>Failed to mount '/dev/da0': Invalid argument</I></DIV>
<DIV><I>The device '/dev/da0' doesn't seem to have a valid NTFS.</I></DIV>
<DIV><I>Maybe the wrong device is used? Or the whole disk instead of
a</I></DIV>
<DIV><I>partition (e.g. /dev/sda, not /dev/sda1)? Or the other way
around?</I></DIV>
<DIV><BR></DIV>
<DIV>I'm still planning on testing out TestDisk.</DIV></DIV>
<DIV><BR></DIV></DIV>
<DIV>
<DIV>
<DIV>
<DIV>On Apr 13, 2010, at 10:20 AM, Justin Kremer wrote:</DIV><BR
class=Apple-interchange-newline>
<BLOCKQUOTE type="cite">
<DIV>Just a couple comments from a couple similar experiences I
had...<BR>The first is to figure out the mode of failure of the drive.<BR>Is
it from a laptop that was dropped during use? Is it a drive that<BR>is
having sectors go bad? Did someone do something silly and
start<BR>writing zeros to the wrong device? (not that I've ever done
that...)<BR>Different modes of failure may require different tactics, and
can also<BR>have very different results.<BR><BR>On Tue, Apr 13, 2010 at 9:49
AM, Ryan Coleman <<A
href="mailto:ryanjcole@me.com">ryanjcole@me.com</A>> wrote:<BR>
<BLOCKQUOTE type="cite">I was given leads to using ddrescue and dd but
frankly that is outside of my<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">realm of knowledge and 9 of the 10 NTFS
partitions that refused to mount in<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">Windows have mounted so far in FreeBSD (I'm
running 8.0).<BR></BLOCKQUOTE><BR>ddrescue might be VERY useful in this
situation. If you're not<BR>familiar, it is basically dd, but it is
forced to keep reading (and<BR>writing) on when it encounters bad blocks.
Some of the files will end<BR>up corrupt in the disk image you create,
but if you are fortunate, the<BR>lion's share will be there.<BR>You just
want to start with the failed drive readable to you, and with<BR>a location
you can write the output file to with more space available<BR>than the size
of the partition you are trying to recover.<BR>Both dd and ddrescue use
similar syntax. As I recall there is a<BR>slight difference, but
starting with the basics, you should be able to<BR>figure out the
rest...<BR>I think the command I used was: dd if=(path of the device name
for the<BR>partition to be recovered) of=(path of the file name to create
from<BR>the partition)<BR>Certain other flags may be necessary, and ddrescue
may be the<BR>preferable command. The less times you have to try the
better. If<BR>the drive's condition is getting worse with use, you
want to use it<BR>less if possible!<BR>I would expect it to take a LONG
time.<BR>Once the process is complete, you can try to mount the output file
as<BR>a loopback filesystem. (under Linux, I believe the flag is "-o
loop")<BR>If you're able to mount it, you should be able to copy any
important<BR>files off of it and then weed out what is intact and what is
corrupt<BR>without dealing with i/o errors in the middle of trying to copy
a<BR>batch of files.<BR><BR>
<BLOCKQUOTE type="cite">The drive is presently connected via USB on a SATA
sled.<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">I know that there's something to be had on there
somewhere:<BR></BLOCKQUOTE><BR>Personally, I would try to use the most
direct connection possible.<BR>SATA direct to the motherboard first.
Maybe it's just my dislike for<BR>middlemen...<BR>-
Justin<BR><BR>_______________________________________________<BR>TCLUG
Mailing List - Minneapolis/St. Paul, Minnesota<BR><A
href="mailto:tclug-list@mn-linux.org">tclug-list@mn-linux.org</A><BR>http://mailman.mn-linux.org/mailman/listinfo/tclug-list<BR></DIV></BLOCKQUOTE></DIV><BR></DIV></DIV></DIV></BLOCKQUOTE></BODY></HTML>