AMI MegaRAID + Reboot issues
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. The exact dmesg shows: amr0: AMI MegaRAID mem 0x-0x irq 11 at device 11.0 on pci0 amr0: Series 475 40 Logical Drive Firmware Firmware E161, BIOS 3.13, 32MB RAM This is the same controller in both boxes that is giving us this particular problem. Has anybody experienced and managed to solve this problem. Not being able to remotely reboot our servers is not a good thing. Are there any other recommended AMI controllers? What I find odd is this controller is specifically mentioned in both the Hardware Notes and amr(4). -byron To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: AMI MegaRAID + Reboot issues
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= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: AMI MegaRAID + Reboot issues
On Tue, 2 Jul 2002, 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. My apologies to the list for this double post. Is seems the list manager is too smart for me. I'll post separately to -questions. -byron ( ... sneaks away in shame ... ) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: AMI MegaRAID + Reboot issues
--- Garance A Drosihn [EMAIL PROTECTED] wrote: 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. Did you check the BIOS settings on that machines, and if the Raid controller has its own BIOS, did you check that as well? Just an FYI. -- Hiten __ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message