From owner-freebsd-questions@FreeBSD.ORG Fri Mar 21 20:14:56 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F442106566B for ; Fri, 21 Mar 2008 20:14:56 +0000 (UTC) (envelope-from derek@computinginnovations.com) Received: from betty.computinginnovations.com (mail.computinginnovations.com [64.81.227.250]) by mx1.freebsd.org (Postfix) with ESMTP id 042BE8FC21 for ; Fri, 21 Mar 2008 20:14:55 +0000 (UTC) (envelope-from derek@computinginnovations.com) Received: from p28.computinginnovations.com (dhcp-10-20-30-100.computinginnovations.com [10.20.30.100]) (authenticated bits=0) by betty.computinginnovations.com (8.14.2/8.13.8) with ESMTP id m2LKEce4073497; Fri, 21 Mar 2008 15:14:38 -0500 (CDT) (envelope-from derek@computinginnovations.com) Message-Id: <6.0.0.22.2.20080321151543.0272b758@mail.computinginnovations.com> X-Sender: derek@mail.computinginnovations.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Fri, 21 Mar 2008 15:16:31 -0500 To: William Bulley , freebsd-questions@freebsd.org From: Derek Ragona In-Reply-To: <20080321173950.GF26011@dell1> References: <20080321173950.GF26011@dell1> Mime-Version: 1.0 X-Antivirus: avast! (VPS 080321-0, 03/21/2008), Outbound message X-Antivirus-Status: Clean X-ComputingInnovations-MailScanner-Information: Please contact the ISP for more information X-ComputingInnovations-MailScanner: Found to be clean X-ComputingInnovations-MailScanner-From: derek@computinginnovations.com X-Spam-Status: No Content-Type: text/plain; charset="us-ascii"; format=flowed X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: help for a wounded disk drive... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Mar 2008 20:14:56 -0000 At 12:39 PM 3/21/2008, William Bulley wrote: >I damaged a Seagate 80 GB EIDE drive that was attached to a FreeBSD 5.4 >system (as ufs) some time ago, and I would like to recover the data on >this drive - if that is possible. All positive suggestions are welcome. > >The drive is mechanically and electrically good. I just can't mount it >and use it under FreeBSD. It was a dual boot drive with a DOS partition >on the first partition and FreeBSD 5.4 on partition two. I did the normal >sysinstall for FreeBSD 5.5 as I had done many times before. Unfortunately, >I had the older, FreeBSD 5.4 drive cabled up (and powered up) on the second >IDE channel (using cable select) of an i386 motherboard while I did the 5.5 >install on a new, blank drive on the first IDE channel. > >I told sysinstall to add the standard FreeBSD bootloader on the new drive. >I don't recall if I allowed for a DOS partition or just used the entire disk. >The FreeBSD 5.4 disk on the second IDE channel also had the standard FreeBSD >bootloader from my earlier sysinstall of 5.4 on that disk. > >When I completed the install, I figured I could just mount the second (older) >drive manually. When I tried to do this, things went from bad to worse, and >the new system could never recognize the drive. I believe the installation >process attempted to (or succeeded in) putting (an unnecessary) bootloader on >the older drive. Had it not been connected, it would probably be okay today. >I learned an important lesson at that time... > >I don't know what steps to take to recover this drive so I can mount it in a >read-only mode. I just want to recover the files on this drive. It is very >small by today's standards, so I will likely not use the drive in production. > >I am comfortable running any required shell commands (as root), but I don't >want to damage the disk drive any further. I hope I don't have to resort to >using dd(1) on the raw device! Thanks in advance for any pointers. > >Regards, > >web... If the mechanics and other workings are good, try testdisk at: www.testdisk.org -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.