Date: Tue, 29 May 2018 23:44:23 -0400 From: Evan Rowley <rowley.evan@gmail.com> To: "Peter G." <freebsd@disroot.org> Cc: freebsd-drivers@freebsd.org Subject: Re: Matching mps driver in 11.1-STABLE to LSI 2008 firmware Message-ID: <CAMhuX2CsxsjNd0tEL=wNStNvg7ET54%2B9UWcVqf-zghnVy4aJTA@mail.gmail.com> In-Reply-To: <a006beb3-deb3-ec3a-28e6-39ef0ce98958@disroot.org> References: <CAMhuX2DqDsem9uDFe2zGpc64-iATMSoRKJ3uXYOGt1LqaLoOdQ@mail.gmail.com> <94579286-7fcc-86ff-41d3-ceb6508f9b11@disroot.org> <CAMhuX2A_rRkvEY65_h7gfTKWFm0LU=BSW3EJ_u0wecg3cV70YQ@mail.gmail.com> <a006beb3-deb3-ec3a-28e6-39ef0ce98958@disroot.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi All, I realized that for some time I had been messaging Peter directly (Sorry about that!), and not the FreeBSD drivers mailing list. I have come to the conclusion that this is not a firmware/driver mismatch issue, rather it appears to be quirkiness with how FreeBSD 11.1 handles these particular drives. This conclusion was reached after updating the LSI SAS 2008 firmware on several machines to the latest version & still seeing drive errors. Interestingly, I can get these drives working fine under both Ubuntu 16.04 and SmartOS. Fromatting, creating a zpool, and doing ZFS scrubs all work OK. The errors shown in the following Gist are what I see on every FreeBSD machine I connect these to, even on machines which don't have an LSI SAS 2008 controller: https://gist.github.com/equalunique/ b34cd7d88b98d750074b82540c576d37 Many of these errors show up for each SAS drive: (da0:mps0:0:15:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code) (da0:mps0:0:15:0): Error 22, Unretryable error (da0:mps0:0:15:0): READ(10). CDB: 28 00 74 70 6d af 00 00 01 00 (da0:mps0:0:15:0): CAM status: SCSI Status Error (da0:mps0:0:15:0): SCSI status: Check Condition (da0:mps0:0:15:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code) (da0:mps0:0:15:0): Error 22, Unretryable error The drives are IBM branded Seagate ST1000NM0001 drives, matching FRU numbers 49Y1903, 49Y1930, and 49Y1939. Possibly related, here is another user reporting similar errors with FreeBSD 9 and the same model of Seagate disk: https://groups.google.com/ forum/#!topic/mailing.freebsd.questions/HplQgV3oy88 On Fri, Apr 27, 2018 at 5:47 PM, Peter G. <freebsd@disroot.org> wrote: > On 27/04/2018 21:56, Evan Rowley wrote: > > Thank you for your email! Sorry, I was confused before and specified > > 11.1-STABLE when I actually meant 11.1-RELEASE. > > > > Most likley I will need to flash these to the firmware version you are > > using: 20.00.07.00 > > > > Here are pictures of what I see using v19 firmware, which did work stable > > on older versions of FreeBSD's mps driver: http://imgur.com/gallery/ > Ka5naWd > > > > I wish there was a way to determine before testing which version firmware > > newer versions of FreeBSD mps driver require. > > Please just post your whole dmesg, so e.g. we could see what controller > that is and how the system recognizes it. > > -- > PG > -- - EJR
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMhuX2CsxsjNd0tEL=wNStNvg7ET54%2B9UWcVqf-zghnVy4aJTA>