Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XEhNf-0008Vm-C6 for pgsql-admin@arkaria.postgresql.org; Tue, 05 Aug 2014 16:14:31 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XEhNe-0004qr-Rf for pgsql-admin@arkaria.postgresql.org; Tue, 05 Aug 2014 16:14:30 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XEhNe-0004qk-18 for pgsql-admin@postgresql.org; Tue, 05 Aug 2014 16:14:30 +0000 Received: from mail.journyx.com ([209.163.206.41] helo=mail.int.journyx.com) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XEhNa-0005Ly-Rg for pgsql-admin@postgresql.org; Tue, 05 Aug 2014 16:14:28 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.int.journyx.com (Postfix) with ESMTP id F3C0F300071; Tue, 5 Aug 2014 11:14:24 -0500 (CDT) Received: from mail.int.journyx.com ([127.0.0.1]) by localhost (mail.int.journyx.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id LONcc1cs-9PL; Tue, 5 Aug 2014 11:14:21 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by mail.int.journyx.com (Postfix) with ESMTP id 047D030A4D8; Tue, 5 Aug 2014 11:14:21 -0500 (CDT) X-Virus-Scanned: amavisd-new at mail.int.journyx.com Received: from mail.int.journyx.com ([127.0.0.1]) by localhost (mail.int.journyx.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id R8Ob0L_NE_kE; Tue, 5 Aug 2014 11:14:20 -0500 (CDT) Received: from mail.int.journyx.com (zimbra.int.journyx.com [192.168.100.5]) by mail.int.journyx.com (Postfix) with ESMTP id BF604300071; Tue, 5 Aug 2014 11:14:20 -0500 (CDT) Date: Tue, 5 Aug 2014 11:14:20 -0500 (CDT) From: Scott Whitney Reply-To: Scott Whitney To: jayknowsunix@gmail.com Cc: Craig James , pgsql-admin@postgresql.org Message-ID: <1611759767.760183.1407255260652.JavaMail.zimbra@mail.int.journyx.com> In-Reply-To: <9E9EF3AD-A2EC-4EEE-836C-860FECBD5F42@gmail.com> References: <9E9EF3AD-A2EC-4EEE-836C-860FECBD5F42@gmail.com> Subject: Re: Stuck LSI 9650SE-12 RAID Controller MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_760182_208238390.1407255260651" X-Originating-IP: [192.168.100.188] X-Mailer: Zimbra 8.0.7_GA_6021 (ZimbraWebClient - GC36 (Win)/8.0.7_GA_6021) Thread-Topic: Stuck LSI 9650SE-12 RAID Controller Thread-Index: qAbud70fQ56WwDI1lZGslXGv6uipkg== X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org ------=_Part_760182_208238390.1407255260651 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Unfortunately, yes, I have seen similar situations. On Adaptec, IBM ServeRAID and Perc cards. I would replace that card, personally, with a new one. Likely the card itself is going flaky. Usually when I have seen this, swapping the card for a like card and importing the RAID config from the drives resolves it, unless the card went REAL bad and actually damaged the RAID itself (which I have also seen). ----- Original Message ----- > Certainly doesn't sound like a PostgreSQL issue. Is there any sort of > advanced diagnostics for the raid controller? I certainly would want to > thrash it top to bottom before I trusted it enough to put it back in > service. > -- > Jay > Sent from my iPad > > On Aug 5, 2014, at 12:00 PM, Craig James wrote: > > > > Has anyone seen anything like this? > > > > Our LSI 9650SE-12 RAID Controller dropped the main Postgres disk offline > > ... it just disappeared as though the disk wasn't there. It was an 8-disk > > RAID10 unit. The other unit (RAID1 for Linux & pg_xlog) was still > > functional. > > > > Using tw_cli, it showed the array as "DEGRADED" and claimed to be verifying > > it. One disk in the array was "DEGRADED". There was no /dev entry for the > > device; Linux couldn't see it at all. > > > > There were two hot spares, but it didn't use them. Worse, there was nothing > > I could do to make it do anything. Every command reported "Failed" and no > > further explanation. Booting into the RAID BIOS gave the same problem: if > > I selected "rebuild" or "verify", it said "You must select an array..." > > even though I had selected the array. It was as though the array didn't > > exist, yet it was shown. > > > > I shut off the computer, unplugged the BBU from the RAID card and plugged > > it back in, unplugged and reinserted all the SATA cables, and then > > restarted. Exact same symptoms. > > > > I finally gave up trying to recover the database (we had a backup server). > > The RAID controller let me delete and recreate the degraded array, and now > > everything seems fine. I can rebuild the Postgres database on the new > > unit. But I've lost a HUGE amount of trust in the LSI 9650-SE RAID > > controller card. > > > > Thanks, > > Craig > > > -- > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin ------=_Part_760182_208238390.1407255260651 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Unfortunately, yes, I have seen = similar situations. On Adaptec, IBM ServeRAID and Perc cards.
I would replace that card, personally, with a new one. Likely t= he card itself is going flaky.

Usually when I have= seen this, swapping the card for a like card and importing the RAID config= from the drives resolves it, unless the card went REAL bad and actually da= maged the RAID itself (which I have also seen).


Certainly doesn't sound like a PostgreSQL issue. Is there any sort= of advanced diagnostics for the raid controller? I certainly would want to= thrash it top to bottom before I trusted it enough to put it back in servi= ce.
--
Jay

Sent from my iPad

>= On Aug 5, 2014, at 12:00 PM, Craig James <cjames@emolecules.com> wro= te:
>
> Has anyone seen anything like this?
>
> O= ur LSI 9650SE-12 RAID Controller dropped the main Postgres disk offline ...= it just disappeared as though the disk wasn't there.  It was an 8-dis= k RAID10 unit. The other unit (RAID1 for Linux & pg_xlog) was still fun= ctional.
>
> Using tw_cli, it showed the array as "DEGRADED" a= nd claimed to be verifying it. One disk in the array was "DEGRADED". There = was no /dev entry for the device; Linux couldn't see it at all.
> > There were two hot spares, but it didn't use them. Worse, there was n= othing I could do to make it do anything. Every command reported "Failed" a= nd no further explanation. Booting into the RAID BIOS gave the same problem= : if I selected "rebuild" or "verify", it said "You must select an array...= " even though I had selected the array. It was as though the array didn't e= xist, yet it was shown.
>
> I shut off the computer, unplugged= the BBU from the RAID card and plugged it back in, unplugged and reinserte= d all the SATA cables, and then restarted. Exact same symptoms.
> > I finally gave up trying to recover the database (we had a backup ser= ver). The RAID controller let me delete and recreate the degraded array, an= d now everything seems fine. I can rebuild the Postgres database on the new= unit. But I've lost a HUGE amount of trust in the LSI 9650-SE RAID control= ler card.
>
> Thanks,
> Craig
>


--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)<= br>To make changes to your subscription:
http://www.postgresql.org/mailp= ref/pgsql-admin

------=_Part_760182_208238390.1407255260651--