From owner-freebsd-questions Tue Aug 11 04:55:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA19868 for freebsd-questions-outgoing; Tue, 11 Aug 1998 04:55:05 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from lucy.bedford.net (lucy.bedford.net [206.99.145.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA19857 for ; Tue, 11 Aug 1998 04:54:59 -0700 (PDT) (envelope-from listread@lucy.bedford.net) Received: (from listread@localhost) by lucy.bedford.net (8.8.8/8.8.8) id HAA16828; Tue, 11 Aug 1998 07:36:46 -0400 (EDT) (envelope-from listread) Message-Id: <199808111136.HAA16828@lucy.bedford.net> Subject: Re: couldn't set disk in "badscan" mode: Inappropriate ioctl for device In-Reply-To: <35CFC245.BC43AD4F@turkey.ispro.net.tr> from Evren Yurtesen at "Aug 11, 98 07:02:13 am" To: yurtesen@turkey.ispro.net.tr (Evren Yurtesen) Date: Tue, 11 Aug 1998 07:36:46 -0400 (EDT) Cc: freebsd-questions@FreeBSD.ORG X-no-archive: yes Reply-to: djv@bedford.net From: CyberPeasant X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Evren Yurtesen wrote: > hello, > I am having trouble when I am using bad144 > does anybody know what does this mean? > I think that I should correct this problem but how? > > cyl: 526, tracks: 255, secs: 63, sec/cyl: 16065, start: 0, end: 8466003 > bad144: couldn't set disk in "badscan" mode: Inappropriate ioctl for > device > I hate to add a "me too" here... so I won't. (Haven't tried bad144 on FBSD, but have used it on NetBSD in the past.) My impression is that bad144 won't work on a disk whose driver does not support it. At least in the past, only the MFM (old, pre-IDE "ST-506" PeeCee drives) and ESDI drivers (and of course old 8"-14" form-factor Vax drives...) supported bad144-style remapping, and this had to be taken into account at the fdisk stage, involving manually entering "known" bad blocks before disklabel and newfs. In this light, I would say that your ioctl error says simply, "This isn't a bad144 compatible disk." I would say that non-MFM/ESDI disks all fit this category (i.e. IDE/SCSI disks are not bad144-able), but I have seen posts here lately that suggest that people are successfully using bad144 on such disks, to my confusion. Could someone give us a thumbnail sketch of bad144 under FreeBSD? Dave -- Bedford County, PA -- 47,000 polite, friendly Appalachians, 4,000 of whom have concealed-carry permits. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message