From owner-freebsd-questions@FreeBSD.ORG Wed Sep 11 01:18:45 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 80CB0744; Wed, 11 Sep 2013 01:18:45 +0000 (UTC) (envelope-from freebsd@pki2.com) Received: from btw.pki2.com (btw.pki2.com [IPv6:2001:470:a:6fd::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4BDC42B18; Wed, 11 Sep 2013 01:18:45 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by btw.pki2.com (8.14.7/8.14.5) with ESMTP id r8B1Ia9n048851; Tue, 10 Sep 2013 18:18:36 -0700 (PDT) (envelope-from freebsd@pki2.com) Subject: Re: Problems with stable/9 and LSI controlers? From: Dennis Glatting To: "Kenneth D. Merry" In-Reply-To: <20130910202937.GA53967@nargothrond.kdm.org> References: <20130910185251.GA46692@nargothrond.kdm.org> <20130910192606.GA49545@nargothrond.kdm.org> <20130910202937.GA53967@nargothrond.kdm.org> Content-Type: text/plain; charset="ISO-8859-1" Date: Tue, 10 Sep 2013 18:18:35 -0700 Message-ID: <1378862315.88480.0.camel@btw.pki2.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-yoursite-MailScanner-Information: Dennis Glatting X-yoursite-MailScanner-ID: r8B1Ia9n048851 X-yoursite-MailScanner: Found to be clean X-MailScanner-From: freebsd@pki2.com Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Sep 2013 01:18:45 -0000 Both servers work with this patch applied. On Tue, 2013-09-10 at 14:29 -0600, Kenneth D. Merry wrote: > On Tue, Sep 10, 2013 at 12:35:02 -0700, Dennis Glatting wrote: > > On Tue, 10 Sep 2013, Kenneth D. Merry wrote: > > >On Tue, Sep 10, 2013 at 12:11:38 -0700, Dennis Glatting wrote: > > >>On Tue, 10 Sep 2013, Kenneth D. Merry wrote: > > >> > > >>>On Tue, Sep 10, 2013 at 11:21:02 -0700, Dennis Glatting wrote: > > >>>> > > >>>>Today I updated several systems against stable/9 that had not bee > > >>>>updated > > >>>>in ~five months. Two of the systems are serviced by LSI 2008 controllers > > >>>>with a RAID1 array housing the operating system. > > >>>> > > >>>>These systems no longer properly boot. > > >>>> > > >>>>Specifically, they begin the boot process but bomb when they try to > > >>>>mount > > >>>>root. Neither system sees the GPT partitions of the boot disk at the > > >>>>"mountroot>" prompt. On one system I replaced the hard disks, > > >>>>repartitioned, and reinstalled but the problem continued. > > >>>> > > >>>>I don't see any mention of geom or controller update in UPDATING but I > > >>>>know they have been updated because I saw their revisions fly actross my > > >>>>screen during the svn update. Also, I am running IR vers 16 on my > > >>>>controllers, which is the latest version of LSI firmware. > > >>>> > > >>>>Is there some new action I have to take to sucessfully boot LSI disks > > >>>>against the updated kernel? > > >>> > > >>>Can you try the mpslsi driver from LSI's web site and see if that works? > > >>> > > >>>If it does, then it is a problem we've introduced locally. > > >>> > > >> > > >>I'll give it a shot but just to be clear, I have been running the 16 > > >>firmware for months. > > > > > >The issue is very likely in the driver, not the firmware. I'm just > > >trying to figure out whether it broke in LSI's Phase 16 or in our > > >additional changes in FreeBSD. > > > > > >In any case, I've reproduced the problem, and hopefully I'll know soon > > >where the issue is. > > > > > >So don't worry about trying LSI's driver. Just go back to the previous > > >version of stable/9 that worked for you until we fix it. > > > > > >This only affects RAID volumes, not regular disks. > > > > > > > Thanks. > > > > I downloaded the mpslsi.ko driver from LSI under r255451 and the system > > now boots. > > Okay, try the attached patch with the new driver and see whether it fixes > the problem for you. > > The issue was that with the new rescanning code, we weren't rescanning RAID > volumes that got created. > > It fixes the problem for me with a RAID-1 volume. > > There is still the issue of all of the verbose probe errors that crop up > when an Integrated RAID volume is enabled, but it isn't obvious at the > moment whether we can easily fix that. > > Ken