92
edits
Hardware Incident Response: Memory Slot Failure on banshee: Difference between revisions
Jump to navigation
Jump to search
Hardware Incident Response: Memory Slot Failure on banshee (view source)
Revision as of 01:00, 12 June 2025
, 12 Juneno edit summary
(Created page with "This document outlines how we handled a memory stick failure on the server banshee. It details the actual steps we took, the tools and commands we used, and the reasoning behind our decisions. ⚠️ Important: This is not a universal or comprehensive guide. Hardware failures — including memory issues — can vary widely in symptoms and impact. There may be multiple valid ways to respond depending on the urgency or available resources. This write-up should be seen as...") |
No edit summary |
||
| Line 1: | Line 1: | ||
This document outlines how we handled a memory stick failure on the server banshee. It details the actual steps we took, the tools and commands we used, and the reasoning behind our decisions. | This document outlines how we handled a memory stick failure on the server banshee. It details the actual steps we took, the tools and commands we used, and the reasoning behind our decisions. | ||
For full context and team discussions, see the [https://chat.dsinternal.net/#narrow/stream/24-SRE-.23-Critical/topic/.E2.9C.94.20banshee.2Ews.2Emaxmaton.2Enl Zulip conversation related to this incident]. | |||
⚠️ Important: This is not a universal or comprehensive guide. Hardware failures — including memory issues — can vary widely in symptoms and impact. There may be multiple valid ways to respond depending on the urgency or available resources. | ⚠️ Important: This is not a universal or comprehensive guide. Hardware failures — including memory issues — can vary widely in symptoms and impact. There may be multiple valid ways to respond depending on the urgency or available resources. | ||
This write-up should be seen as one practical example that may help guide similar interventions in the future or serve as a starting point when assessing next steps in a hardware-related incident. | This write-up should be seen as one practical example that may help guide similar interventions in the future or serve as a starting point when assessing next steps in a hardware-related incident. | ||