From owner-freebsd-questions Wed Oct 16 11: 6: 9 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D15B37B419 for ; Wed, 16 Oct 2002 11:05:50 -0700 (PDT) Received: from hobbiton.shire.net (frogmorton.shire.net [204.228.145.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF89043E9C for ; Wed, 16 Oct 2002 11:05:49 -0700 (PDT) (envelope-from chad@shire.net) Received: from slc1298.modem.xmission.com ([166.70.13.28] helo=shire.net) by hobbiton.shire.net with asmtp (Exim 3.36 #9) id 181sYF-000G8U-00 for freebsd-questions@FreeBSD.ORG; Wed, 16 Oct 2002 14:05:49 -0400 Date: Wed, 16 Oct 2002 12:05:24 -0600 Subject: Re: "asr0: Blink LED 0x3 resetting adapter" adaptec 2100S Content-Type: text/plain; charset=WINDOWS-1252; format=flowed Mime-Version: 1.0 (Apple Message framework v546) From: Chad Leigh -- Shire.Net LLC To: freebsd-questions@FreeBSD.ORG Content-Transfer-Encoding: quoted-printable In-Reply-To: <0C6E2E86-DFCD-11D6-8FEC-0003931BED80@shire.net> Message-Id: X-Mailer: Apple Mail (2.546) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Monday, Oct 14, 2002, at 17:31 US/Mountain, Chad Leigh -- Shire.Net=20= LLC wrote: > > On Monday, October 14, 2002, at 01:59 , Chad Leigh -- Shire.Net LLC=20 > wrote: > >> Hi >> >> I run an adadptec 2100S. Today it displayed the following message,=20= >> and while the system was still "running" and pingable, you couldn't=20= >> do anything include login. >> >> "asr0: Blink LED 0x3 resetting adapter" > > It happened again, this time 0x68 in the message. The machine is=20 > running but the adapter resets itself and seems to go offline. =20 > Rebooting gets it going again for a few hours. Adaptec tech support=20= > thought maybe a bad cache memory module or something. They didn't=20 > find a 0x68 for blink codes listed in their manuals. > > I will be trying some other memory... It happened once more with 0x3 . Though the codes don't seem to be in=20= the code lists that adaptec tech support has, it appears that when a=20 fault happens, the internal LEDs will blink, making a specific HEX code=20= to help figure out what the problem is. This messages seems to be a=20 report on what the LEDs are doing when there is a fault. I replaced the cache memory module and the system has not had a problem=20= since, after 3 or more problems in one day on Monday. best regards Chad > > Chad > > >> >> Resetting the machine and going into the onboard ROM SMOR adaptec=20 >> manager on the card, nothing seemed out of the ordinary. All of the=20= >> disks and volumes were "optimal" and no errors were reported on card. >> >> I looked through both the mailist archives, in the adaptec manuals, =20= >> and the adaptec site to see if there was any sort of similar message=20= >> listed, but I found no info. Anyone know what this means? I looked=20= >> at the list of LEDs, wondering if 0x3 meant LED #3, but that does not=20= >> make sense, as that is >> >> "3 Indicates the controller=92s internal operating system is in its = idle >> loop." >> >> Thanks for any help. I have had some random freezeups on the=20 >> machine, off an on, most recently an hour or two before this adapter=20= >> reset happened, and I was wondering if they are related. >> >> BY random freezeups, I mean hard freeze on the machine. I had one=20 >> this morning, two weeks ago, and 99 days before that. >> >> But this message about the reset adapter did not hard freeze the=20 >> machine. I just think they might be related, like maybe the RAM=20= >> module on the adapter is flaky or something. >> >> Thanks >> Chad >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-questions" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message