Intel rapid storage chipset controller issue - no longer fully redundant

Thanks, Yes, I looked at the log, and I think it is referring to the old drive, so how do I acknowledge it, so it can clear it?
I have selected clear cache under the unknown drive that was removed, but it doesn't do anything, it comes up with the below errors.

Pull the replacement drive and see where the console goes.

Is there a known good backup?

You mean, pull out the new SSD installed yesterday?  The server is in a datacenter, hours away, so it costs money every time I send someone out there to look at the server.This is  my backup server, so no, I don't have any backups of this server. It's just the OS drives that are having this issue, my data volumes are fine, they are on a different hardware raid controller.

I have restarted the server to see if that does anything.   I'll get back to you in a few min.

I suspect that there is an Intel RMM/iDRAC Enterprise/HPE iLO Advanced set up in the server? If so, then log on to the software RAID console (CTRL+I or CTRL+E IIRC) and see if the replacement drive can be flipped into the array.

I don't think there is an ILO, if there is, it's not configured :( so I'm assuming I can't do anything at this point?
The bad drive was physically removed from the server, so I don't want the drive into the array, right?
not sure what to do next...

The restart did the trick, the error is gone!!!!!!!!!!!!!!!!!!!!!!!!!!

thanks guys for your help

As an FYI: We deploy all nodes with Intel RMM/HPE iLO Advanced/Dell iDRAC Enterprise/ETC as out-of-band management is mandatory especially in a data centre that may not be close to anyone that could look into things.

If it saves one visit by the DC folks then it's virtually paid for itself.

yes good point.

Since I'm on the subject. ;)

Disaster Preparedness: KVM/IP + USB Flash = Recovery. Here’s a Guide

very good points, makes sense, with an ILO or simular, and having a flash drive with the OS already installed, will allow me to not even have to user the data center services, only for physically replacing a drive.

Yup. We've rebuilt Hyper-V hosts and nodes remotely using this method. It works really well.

Corsair Voyager Vega 32GB USB3 set up using Rufus to allow for uEFI and Secure Boot setup. Once Rufus is done we have a folder set that we put on that drive:
 _Drivers
 _BIOS
 _Firmware
 _ISOs

We keep the content in those folders relatively up to date based on the update status of the host/node.

that's great, I will try to remember that when I ship out any more servers.  Thanks for tips, so when formatting the USB drive,  
does this look like the right options?

Perfect. I do suggest 32GB or at least 16GB. We use this method to keep our Windows Desktop and Server operating system .ISO files up to date with the FULL version actually hosting an up to date .ISO file of itself in the image.

That one is close to 24GB in size. Thus, we use 32GB flash drives with the VEGA having a decent write speed to get them made.