From owner-freebsd-bugs Thu Aug 12 15:32:25 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id C6FB414C89 for ; Thu, 12 Aug 1999 15:32:22 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id PAA60815; Thu, 12 Aug 1999 15:30:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Thu, 12 Aug 1999 15:30:03 -0700 (PDT) Message-Id: <199908122230.PAA60815@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Nick Hibma Subject: Re: i386/12981: Bad *.flp files and and raw write program Reply-To: Nick Hibma Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR i386/12981; it has been noted by GNATS. From: Nick Hibma To: dvditto@yahoo.com Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: i386/12981: Bad *.flp files and and raw write program Date: Thu, 12 Aug 1999 22:12:46 +0000 (GMT) > When I use the raw write program you supplied with your boot images > it actually creates bad sectors on my floppy disk. When I use > annoter version of raw write with you boot images, raw write stops > part way though and reports that there is a bad sector, however > there is aren't any bad boot on the disk. >How-To-Repeat: How did you verify that the floppy is ok? Did you try another floppy? It is impossible for a normal utility to create bad blocks on a floppy. If you want to check whether you have bad blocks try the following command: dd if=/dev/rfd0 of=/dev/null bs=1024 count=1440 That should produce an error on reading the floppy. Nick -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message