From owner-freebsd-scsi@freebsd.org Thu May 23 06:34:27 2019 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6BB26159E6C9 for ; Thu, 23 May 2019 06:34:27 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id F3BD785A06 for ; Thu, 23 May 2019 06:34:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id B3C31159E6C8; Thu, 23 May 2019 06:34:26 +0000 (UTC) Delivered-To: scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 76526159E6C7 for ; Thu, 23 May 2019 06:34:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0C84385A01 for ; Thu, 23 May 2019 06:34:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 32BDE64DE for ; Thu, 23 May 2019 06:34:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x4N6YPRG068598 for ; Thu, 23 May 2019 06:34:25 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x4N6YPhc068591 for scsi@FreeBSD.org; Thu, 23 May 2019 06:34:25 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: scsi@FreeBSD.org Subject: [Bug 202712] [cam] [ata] System doesn't recognize older hdd after boot Date: Thu, 23 May 2019 06:34:23 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.2-RELEASE X-Bugzilla-Keywords: patch, regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: scottl@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: scsi@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2019 06:34:27 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D202712 Scott Long changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |scottl@FreeBSD.org --- Comment #39 from Scott Long --- The code in sys/cam/ata is generic protocol and transport support for all devices. The code in sys/dev/ata is controller-specific drivers. In simple terms, adding CHS support would happen in sys/cam/ata. I have mixed feelings on adding CHS support. As others have mentioned, it's ancient, and it's nearly impossible for people to test. It would exist as a poorly tested codepath that would be prone to accidental breakage. The cos= t of keeping it working, in terms of equipment procurement and operation, would likely outweigh the benefit. It looks like Amazon has a PCIe add-in card for ATA/IDE, but I haven't owne= d a working ATA drive in almost 10 years, and I probably haven't owned a functi= onal CHS-only drive in at least 20 years. I have no idea where I'd get one, ot= her than to buy batches of them off of Ebay and hope to find some that work. 2= 0+ years is a long time for a hard drive, even in the best of circumstances.=20 Moisture will invade the platter cavity through the breather hole. Lubrica= tion will slowly evaporate off of spindle and armature joints and redeposit itse= lf onto the platters and heads. Capacitors on the circuit board will slowly l= eak, and copper and aluminum connectors and traces will corrode. I'm impressed = that you have a working 400MiB drive, that's a 25 year old drive at this point. = I'd worry that it would stop working in the near future. If I were to build a rig to operate a CHS-era IDE drive (or any ATA/IDE dri= ve for that matter), it would be solely to recover and archive the drive data = to modern storage. For that, I'd use software that supported the use-case. If that means using an older version of FreeBSD, or using Linux, I'd do that.= =20 It's such a niche use case that I'd spend considerably more time resurrecti= ng and testing CHS code than I'd spend actually recovering the data, and that's just not an interesting use of my time. If there's community interest in supporting CHS long-term in FreeBSD, my recommendation is to create a IDE-CHS specific transport in CAM that lives alongside the ATA/SATA support, but does not rely on it. This probably mea= ns copying sys/cam/ata/ata_xpt.c to sys/cam/ata/ide_xpt.c, removing the SATA-specific logic in it, and adding in the IDE and CHS specific logic. N= ice, clean, and isolated so that it's less likely to be accidentally broken, and people working on SATA aren't likely to trip on it. This would probably be= a week of work at most, assuming that test hardware is available. --=20 You are receiving this mail because: You are the assignee for the bug.=