From owner-freebsd-questions Tue Jul 2 14:11: 3 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 D262937B794; Tue, 2 Jul 2002 14:10:13 -0700 (PDT) Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id D429E448D1; Tue, 2 Jul 2002 12:09:39 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id g62J9MY3082410; Tue, 2 Jul 2002 15:09:37 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20020702155421.C3475-100000@pan.ehsbrann.com> References: <20020702155421.C3475-100000@pan.ehsbrann.com> Date: Tue, 2 Jul 2002 15:09:21 -0400 To: Byron Schlemmer , FreeBSD-Hackers From: Garance A Drosihn Subject: Re: AMI MegaRAID + Reboot issues Cc: FreeBSD-Questions Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) 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 At 4:49 PM +0100 7/2/02, Byron Schlemmer wrote: >Hi, > >I've posted on this before, and I've received no reply. I'm >cross-posting just in case it was missed before (I am desperate for >help) and to ask for further advice. > >Basically we have a number of FreeBSD servers, running 4.5-RELEASE >and 4.6-RELEASE, that use AMI MegaRaid 500 controllers. These boxes >refuse to reboot when sent a reboot or shutdown -r. They simply >close all processes and show : > >amr0: flushing cache...done >Rebooting... > >At this point the numlock key is locked, and Ctrl + Alt + Deleting >does nothing. This will not help much, but I can at least say that I have noticed your messages go by. Unfortunately I have no experience with any raid controllers under freebsd. If you made it successfully to the "Rebooting..." line, then I think it's at the point that freebsd has done everything it expected to do, and freebsd has told the hardware to reboot. I do not know why the hardware wouldn't reboot at that point. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message