From owner-freebsd-questions@FreeBSD.ORG Mon Apr 21 11:03:56 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7489D37B432 for ; Mon, 21 Apr 2003 11:03:54 -0700 (PDT) Received: from sumax.dyndns.org (212-100-182-29.adsl.easynet.be [212.100.182.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 794F843F3F for ; Mon, 21 Apr 2003 11:03:52 -0700 (PDT) (envelope-from chrisp@belgacom.net) Received: by sumax.dyndns.org (Postfix, from userid 1001) id 5D2F7225A; Mon, 21 Apr 2003 19:59:50 +0200 (CEST) Date: Mon, 21 Apr 2003 19:59:50 +0200 From: Chris Pockele To: nkinkade@fastmail.fm, freebsd-questions@freebsd.org Message-ID: <20030421175950.GA23481@freedaemon.home.lan> Mail-Followup-To: Chris Pockele , nkinkade@fastmail.fm, freebsd-questions@freebsd.org References: <20030421170801.GA23306@freedaemon.home.lan> <20030421175150.GB92029@sub21-156.member.dsl-only.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <20030421175150.GB92029@sub21-156.member.dsl-only.net> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 4.8-STABLE i386 Subject: Re: floppy drive problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Apr 2003 18:03:57 -0000 On Mon, Apr 21, 2003 at 10:51:51AM -0700, Nathan Kinkade wrote: > > Notwithstanding apparent problems with your entire floppy subsystem, > your dd command is incorrect. The syntax should be something like: > # dd if=/dev/fd0 of=image.flp > I know my dd command didn't do anything useful, it was just for testing. Using of=/tmp/image results in similar errors. > Take a look at dd's manpage. > > You can usually get dd to copy data off a damaged disk with the > following command: > # dd if=/dev/fd0 of=image.flp conv=noerror > Logically, that shows even more error messages... : fd0c: hard error reading fsbn 0 (ST0 40 ST1 10 ST2 0 cyl 0 hd 0 sec 1) fd0c: hard error reading fsbn 1 (ST0 40 ST1 10 ST2 0 cyl 0 hd 0 sec 2) fd0c: hard error reading fsbn 2 (ST0 40 ST1 10 ST2 0 cyl 0 hd 0 sec 3) fd0c: hard error reading fsbn 3 (ST0 40 ST1 10 ST2 0 cyl 0 hd 0 sec 4) fd0c: hard error reading fsbn 4 (ST0 40 ST1 10 ST2 0 cyl 0 hd 0 sec 5) .... (skipped some) fd0c: hard error reading fsbn 60 (ST0 44 ST1 10 ST2 0 cyl 1 hd 1 sec 7) fd0c: hard error reading fsbn 61 (ST0 44 ST1 10 ST2 0 cyl 1 hd 1 sec 8) fd0c: hard error reading fsbn 62 (ST0 44 ST1 10 ST2 0 cyl 1 hd 1 sec 9) fd0c: hard error reading fsbn 63 (ST0 44 ST1 10 ST2 0 cyl 1 hd 1 sec 10) fd0c: hard error reading fsbn 64 (ST0 44 ST1 10 ST2 0 cyl 1 hd 1 sec 11) fd0c: hard error reading fsbn 65 (ST0 44 ST1 10 ST2 0 cyl 1 hd 1 sec 12) ... and so on (alternating and (hd 0 and hd 1)) > Note that this won't prevent data loss. It may allow you to recover > good blocks off failing media, though. How confident are you about the > cable and the drive itself? > Well, it can read disks under dos/windows and linux, without I/O errors or retries. > Nathan