How to get into Areca BIOS on a Mac Pro

[Spacedust]

I'm using normal BIOS for my Areca card. When I press TAB or F6 during bootup process nothing is happening. I need to get into BIOS to turn off fan failure reporting, because it's being sent to me via mail each time. I really need monitoring when something is wrong with my array.

 

[wonderspark]

I thought Macs could only use the browser-based management. I log in via Firefox to my localhost address, and all the controls for alarms and email notification is in there.

Did you install the McRAID ArcHTTP proxy server when you set up your system?

If you log in there, you can click System Controls>Alert By Mail Configuration, and choose the level of notification based on Urgent, Serious, Warning, Information or Disable.

 

[Spacedust]

I thought Macs could only use the browser-based management. I log in via Firefox to my localhost address, and all the controls for alarms and email notification is in there.

Did you install the McRAID ArcHTTP proxy server when you set up your system?

If you log in there, you can click System Controls>Alert By Mail Configuration, and choose the level of notification based on Urgent, Serious, Warning, Information or Disable.

Fan Failed is a urgent alert, so I have disable all e-mails :/

 

[nanofrog]

I'm using normal BIOS for my Areca card. When I press TAB or F6 during bootup process nothing is happening. I need to get into BIOS to turn off fan failure reporting, because it's being sent to me via mail each time. I really need monitoring when something is wrong with my array.

You will not be able to get direct access to the Areca's firmware in a MP (boot cycle or otherwise). But that doesn't mean you're stuck with your issue.

Try the McRAID (ARCHTTP), and see if you can gain access to that setting (I don't expect this to be the case, but it's worth a quick look anyway). If not, the next thing you can try is using the CLI.

Past that, you'll have to stuff it in a PC, and do it that way.

But I'd recommend putting in the time to figure out exactly what/when/where/why is going on, as it could be something you don't expect, such as low voltages (particularly on the +3.3V signal <under-volt condition> - dealt with this before, and it ended up being a bad +3.3V reg in the PSU due to damage caused by a UPS inverter before it was known that standard step inverters were damaging Active Power Factor Controlled PSU's, which the MP uses).