MonsterMegs - Notice history

The motherboard and memory have been replaced. The server is now back online. With all new hardware except for the hard drives. This should resolve the reboot issues. So we are gonna consider this closed.

There have been a few random reboots, but not quite as frequently as they were. Since this is still ongoing, the datacenter is going to replace the memory and motherboard, that we have replaced all components with new ones.

The server is going offline now and is expected to be down for about 30-60 minutes. We will update when the server is back online.

We are monitoring the server for random reboots to track down the cause. There may be short interruptions though out the day as we attempt to capture logs on the random reboots.

The server seems to be stable at this time. We will reopen this incident if there are any further issues.

Upon a kernel crash, the server did not come up properly. We initiated a manual reboot and now the server is back online. We will monitor closely and update if there are any further issues.

We are gonna close this incident for now. Meanwhile we will monitor the server closely and if any further issues arrive, we will once again reopen it with additional updates.

The cpu has been replaced and we will continue to monitor closely to watch for any further reboots.

Well the server was running fine for about 1 1/2 hours with no reboots and then the issued returned. We are gonna try to swap out the cpu and hopefully this resolves the problem. If that does not work, the last resort would be to change out the chassis completely.

The server will be going down in about 5 minutes to replace the cpu.

It appears the PSU replacement did the trick and the server is no longer rebooting every few minutes. We will continue to monitor closely over the next few hours and will reopen this incident if the issue arises again.

The Power supply has been replaced and the server is back online. We are going to monitor closely for any further repeated reboots over the next couple hours.

In talks with the datacenter, it appears that the power supply may have become faulty. They are going to take the server down and replace the power supply.

We are working out an issue with repeated reboots on the server. We will update when we have more information.

The firmware upgrades have been completed and everything is back online. We found there was an issue with earlier versions of the Samsung 990 Pro's that were allowing the disk to fail much earlier than its lifespan. We applied the latest firmware that addresses that issue as well as both of the drives in the server as of now, are the latest production version of the hard drives.

So with that said, we do not anticipate any further hard drive failures.

The server has been back online for about 30 minutes now. We are waiting for the raid to finish rebuilding and then we will proceed with the firmware updates.

The server has just went down for the hard drive replacement. Please anticipate several shorter downtimes over the next couple hours as we apply these firmware updates in rescue mode.

We have checked the server in recue mode and the drive did not show. We have gotten the server back online with the single drive. So the datacenter will be replacing this drive very shortly. Once the server is back online, we will performing firmware updated so all internal server components to hope this rectifies the hard drives failing or bricking themselves before their life span.

We are investigating why on reboot the Cloudlinux system did not load.

The server is back online and the grub entry issue has been fixed permanently we feel.

The server is having an issue coming up from a reboot. We are currently working on it and will update shortly.

We are closing this incident for now. We are still working with the datacenter for a fix. This seems to be related to Almalinux and the way it handles the grub and boot partitions when the disk drives are in a raid format. We are exploring options to bypass this can copy the EFI boot partitions across all drives.

We found that the server for some reason just dropped all hard drives from the server. Upon doing a full server reset, the drives then showed back up. We are having the datacenter looking for a resolution so this does not happen again. Hopefully it can be a firmware update of some sort and not actually the motherboard itself. Either way, we will update as we gather more information on a resolution to this.

The server is back online, but we still need to investigate the reason for the crash and boot into bios. We will update this when we have more info.

We have found that the server crashed and rebooted to the bios screen. The datacenter is currently looking into this to see if it is a hardware issue.

The server is now back online.

We are still investigating the issue and awaiting he datacenter to plug in a KVM console for further troubleshooting.

We have contacted the datacenter as the server is inaccessible. We update as more information comes available.