Date: Sat, 13 Jul 2019 08:35:50 +0200 From: Hans Petter Selasky <hps@selasky.org> To: Zaphod Beeblebrox <zbeeble@gmail.com>, FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: 4k sector support (not good?) Message-ID: <13de3cde-185b-a986-cbce-6ad984792952@selasky.org> In-Reply-To: <CACpH0MeEgMUV-1Q4-Z3hJw87oBn07Yy2ypwjG1RuX=6LWgHKhg@mail.gmail.com> References: <CACpH0McZ50=yoosevUfMSVsHz_nvdQYNY-ozA=BtV-SAaJUjaA@mail.gmail.com> <CACpH0MeEgMUV-1Q4-Z3hJw87oBn07Yy2ypwjG1RuX=6LWgHKhg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <zbeeble@gmail.com> 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: <Marvell 88SE9230 AHCI SATA controller> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?13de3cde-185b-a986-cbce-6ad984792952>