From owner-freebsd-hackers@freebsd.org Sat Jul 13 06:36:40 2019 Return-Path: Delivered-To: freebsd-hackers@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 7BE9115E15EB for ; Sat, 13 Jul 2019 06:36:40 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8ACEA7096B for ; Sat, 13 Jul 2019 06:36:39 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.129.235]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 30CE52602EB; Sat, 13 Jul 2019 08:36:29 +0200 (CEST) Subject: Re: 4k sector support (not good?) To: Zaphod Beeblebrox , FreeBSD Hackers References: From: Hans Petter Selasky Message-ID: <13de3cde-185b-a986-cbce-6ad984792952@selasky.org> Date: Sat, 13 Jul 2019 08:35:50 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 8ACEA7096B X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of hps@selasky.org designates 88.99.82.50 as permitted sender) smtp.mailfrom=hps@selasky.org X-Spamd-Result: default: False [-6.28 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+a:mail.turbocat.net]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[selasky.org]; SUBJECT_HAS_QUESTION(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: mail.turbocat.net]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.78)[-0.780,0]; IP_SCORE(-3.19)[ip: (-9.39), ipnet: 88.99.0.0/16(-4.74), asn: 24940(-1.80), country: DE(-0.01)]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:88.99.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jul 2019 06:36:40 -0000 On 2019-07-13 06:56, Zaphod Beeblebrox wrote: > Replying to my own message to add data. Attaching the drives to a SAS > controller that probes up with mps, they attach without complaint, but read > and write give: > > (da1:mps0:0:12:0): SCSI status: Check Condition > (da1:mps0:0:12:0): SCSI sense: ILLEGAL REQUEST asc:74,79 (Security conflict > in translated device) > (da1:mps0:0:12:0): Error 13, Unretryable error > (da1:mps0:0:12:0): READ(10). CDB: 28 00 00 00 00 00 00 00 01 00 > (da1:mps0:0:12:0): CAM status: SCSI Status Error > (da1:mps0:0:12:0): SCSI status: Check Condition > (da1:mps0:0:12:0): SCSI sense: ILLEGAL REQUEST asc:74,79 (Security conflict > in translated device) > (da1:mps0:0:12:0): Error 13, Unretryable error > (da1:mps0:0:12:0): WRITE(10). CDB: 2a 00 00 00 00 00 00 00 01 00 > (da1:mps0:0:12:0): CAM status: SCSI Status Error > (da1:mps0:0:12:0): SCSI status: Check Condition > (da1:mps0:0:12:0): SCSI sense: ILLEGAL REQUEST asc:74,79 (Security conflict > in translated device) > (da1:mps0:0:12:0): Error 13, Unretryable error > > ... now this drive is a ST2000NX0243. The ST2000NX0248 is an encrypted > drive, but the 243 is not. > > ... so what's this error. Also... I'm no SCSI speaker, but reading the > manual for the drive, 28 and 2a are not commands it lists. 20 and 24 (for > read and read extended) and 30 and 34 (for write and write extended). > > Help? > > > On Fri, Jul 12, 2019 at 7:33 PM Zaphod Beeblebrox wrote: > >> So I have 6 drives that have 4k sectors. They are: >> >> ST2000NX0243 >> >> I first tried talking to them with an old MFI passthru controller. I >> think that is not FreeBSD's fault --- the MFI didn't want them. >> >> Now on the motherboard, I have >> >> ahci2: port >> 0xa050-0xa057,0xa040-0xa043,0xa030-0xa037,0xa020-0xa023,0xa000-0xa01f mem >> 0xfe610000-0xfe6107ff irq 40 at device 0.0 on pci7 >> ahci2: AHCI v1.20 with 8 6Gbps ports, Port Multiplier not supported >> >> ... which will attach the drives, but kick out all kinds of probe errors. >> Smartctl can read the drives on this controller. >> >> In a PCIe slot I have: >> >> ahci3@pci0:0:17:0: class=0x010601 card=0x84dd1043 chip=0x43911002 >> rev=0x40 hdr=0x00 >> vendor = 'Advanced Micro Devices, Inc. [AMD/ATI]' >> device = 'SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode]' >> >> which attaches the devices, kicks out a lot of errors and smartctl can't >> read the drives on this controller. >> >> now... on the motherboard controller, I can say: >> If you want to boot from a 4K disk you need this patch at least: https://reviews.freebsd.org/D19245 --HPS