<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">The entire disk; Should I re-try the ddrescue with the slice only?<div><br></div><div>As I just sent to the list:</div><div><div>[root@server /]# mount_ntfs -o loop /mount/archive/da-harddrive/80gb.drive /mount/drive1</div><div><i>mount_ntfs: -o loop: option not supported</i></div><div><br></div><div><br></div><div><div><div>On Apr 13, 2010, at 10:48 AM, Sunny wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On Tue, Apr 13, 2010 at 10:34 AM, Ryan Coleman <<a href="mailto:ryanjcole@me.com">ryanjcole@me.com</a>> wrote:<br><blockquote type="cite">I trust that it was not dropped - the device does not make any abnormal<br></blockquote><blockquote type="cite">noises that would lead me to believe that is the case. It spins up<br></blockquote><blockquote type="cite">normally...<br></blockquote><blockquote type="cite">I have the image made ...<br></blockquote><br>Did you make an image of the partition, or the disk itself?<br><br><blockquote type="cite">[root@server /mount/archive/da-harddrive]# ls -la<br></blockquote><blockquote type="cite">total 78188872<br></blockquote><blockquote type="cite">-rw-r--r-- 1 ryan wheel 80026361856 Apr 13 03:46 80gb.drive<br></blockquote><blockquote type="cite">-rw-r--r-- 1 ryan wheel 425 Apr 13 03:46 80gb.log<br></blockquote><blockquote type="cite">When I try to mount that with mount_ntfs I get the following (expected)<br></blockquote><blockquote type="cite">error:<br></blockquote><blockquote type="cite">mount_ntfs: /mount/archive/da-harddrive/80gb.drive: Block device required<br></blockquote><blockquote type="cite">Is there a way to fake the Block device? I also tried just now to mount the<br></blockquote><br>If your image is of the partition, did you used -o loop as mounting option?<br><br><blockquote type="cite">physical partition with the fusefs NTFS port and got the following response:<br></blockquote><blockquote type="cite">[root@server /mount/archive/da-harddrive]# ntfs-3g /dev/da0 /mount/drive1<br></blockquote><blockquote type="cite">NTFS signature is missing.<br></blockquote><blockquote type="cite">Failed to mount '/dev/da0': Invalid argument<br></blockquote><blockquote type="cite">The device '/dev/da0' doesn't seem to have a valid NTFS.<br></blockquote><blockquote type="cite">Maybe the wrong device is used? Or the whole disk instead of a<br></blockquote><blockquote type="cite">partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?<br></blockquote><blockquote type="cite">I'm still planning on testing out TestDisk.<br></blockquote><blockquote type="cite">On Apr 13, 2010, at 10:20 AM, Justin Kremer wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Just a couple comments from a couple similar experiences I had...<br></blockquote><blockquote type="cite">The first is to figure out the mode of failure of the drive.<br></blockquote><blockquote type="cite">Is it from a laptop that was dropped during use? Is it a drive that<br></blockquote><blockquote type="cite">is having sectors go bad? Did someone do something silly and start<br></blockquote><blockquote type="cite">writing zeros to the wrong device? (not that I've ever done that...)<br></blockquote><blockquote type="cite">Different modes of failure may require different tactics, and can also<br></blockquote><blockquote type="cite">have very different results.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On Tue, Apr 13, 2010 at 9:49 AM, Ryan Coleman <<a href="mailto:ryanjcole@me.com">ryanjcole@me.com</a>> wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I was given leads to using ddrescue and dd but frankly that is outside of my<br></blockquote><blockquote type="cite"><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"><br></blockquote><blockquote type="cite">Windows have mounted so far in FreeBSD (I'm running 8.0).<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">ddrescue might be VERY useful in this situation. If you're not<br></blockquote><blockquote type="cite">familiar, it is basically dd, but it is forced to keep reading (and<br></blockquote><blockquote type="cite">writing) on when it encounters bad blocks. Some of the files will end<br></blockquote><blockquote type="cite">up corrupt in the disk image you create, but if you are fortunate, the<br></blockquote><blockquote type="cite">lion's share will be there.<br></blockquote><blockquote type="cite">You just want to start with the failed drive readable to you, and with<br></blockquote><blockquote type="cite">a location you can write the output file to with more space available<br></blockquote><blockquote type="cite">than the size of the partition you are trying to recover.<br></blockquote><blockquote type="cite">Both dd and ddrescue use similar syntax. As I recall there is a<br></blockquote><blockquote type="cite">slight difference, but starting with the basics, you should be able to<br></blockquote><blockquote type="cite">figure out the rest...<br></blockquote><blockquote type="cite">I think the command I used was: dd if=(path of the device name for the<br></blockquote><blockquote type="cite">partition to be recovered) of=(path of the file name to create from<br></blockquote><blockquote type="cite">the partition)<br></blockquote><blockquote type="cite">Certain other flags may be necessary, and ddrescue may be the<br></blockquote><blockquote type="cite">preferable command. The less times you have to try the better. If<br></blockquote><blockquote type="cite">the drive's condition is getting worse with use, you want to use it<br></blockquote><blockquote type="cite">less if possible!<br></blockquote><blockquote type="cite">I would expect it to take a LONG time.<br></blockquote><blockquote type="cite">Once the process is complete, you can try to mount the output file as<br></blockquote><blockquote type="cite">a loopback filesystem. (under Linux, I believe the flag is "-o loop")<br></blockquote><blockquote type="cite">If you're able to mount it, you should be able to copy any important<br></blockquote><blockquote type="cite">files off of it and then weed out what is intact and what is corrupt<br></blockquote><blockquote type="cite">without dealing with i/o errors in the middle of trying to copy a<br></blockquote><blockquote type="cite">batch of files.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">The drive is presently connected via USB on a SATA sled.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I know that there's something to be had on there somewhere:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Personally, I would try to use the most direct connection possible.<br></blockquote><blockquote type="cite">SATA direct to the motherboard first. Maybe it's just my dislike for<br></blockquote><blockquote type="cite">middlemen...<br></blockquote><blockquote type="cite">- Justin<br></blockquote></div></blockquote></div><br></div></div></body></html>