updateHello everyone,
Following a comprehensive investigation and recovery assessment, our team was unable to retrieve any additional data from the affected drives.
With all services redeployed and the investigation concluded, we are now closing this case. We sincerely apologize once again for the disruption and inconvenience this incident caused, and we appreciate your patience throughout the process.
Oct 26 · 20:14 CT
updateHello team,
Regrettably, we were unable to restore the original node in its current state. To restore stability as quickly as possible, we have fully redeployed all affected services onto a new node.
Key Details:
Data Recovery: For services with active backups on file, data has been restored from the most recent snapshot.
Next Steps: Our team is actively investigating the original node to evaluate whether additional data can be recovered.
We sincerely apologize for this disruption and appreciate your patience as we work through the recovery process.
Oct 22 · 00:42 CT
updateWe've identified the issue with the node and our engineering team is actively working on a resolution. We will provide another update shortly.
Oct 21 · 18:23 CT
investigatingOur team has identified that a drive (/dev/sdc) in the system is in a failed state. To prevent further issues and restore the system to full health, we are establishing an emergency maintenance window, effective immediately. Please be advised that customers may experience temporary downtime while we replace the drive and synchronize the array. We will provide another status update as soon as the restoration is complete.
Oct 21 · 14:06 CT
