--- title: "#incident articles | Hashnode" description: "Explore 11 articles tagged #incident on Hashnode. Tutorials, guides, and how-tos from the community." url: "https://hashnode.com/tag/incident" --- Tag # #incident 11 posts · 0 followers [Human Business Works](https://hashnode.com/@humanbusinessworks) · [Aug 28](https://hashnode.com/posts/blameless-postmortem-government-contract-outage/6a91a279266bc596963c42d6) ### [Running a Blameless Postmortem When a Government Contract Is on the Line](https://humanbusinessworks.hashnode.dev/blameless-postmortem-government-contract-outage?utm_source=hashnode&utm_medium=feed) When an outage triggers a contractual incident report, blameless postmortems get harder. Here's how to satisfy a government client without turning the internal review into a blame exercise. 7 min read · [humanbusinessworks.hashnode.dev](https://humanbusinessworks.hashnode.dev/blameless-postmortem-government-contract-outage?utm_source=hashnode&utm_medium=feed) [JJozzieTech](https://hashnode.com/@jjozzietech) · [Aug 13](https://hashnode.com/posts/zfs-missing-vdev-recovery/6a7e27de21c0f66fbbcb83f8) ### [Recovering a ZFS pool with a missing RAIDZ1 vdev — without wiping a single disk](https://jjozzietech.hashnode.dev/zfs-missing-vdev-recovery?utm_source=hashnode&utm_medium=feed) Same outage, same box, a harder failure. A whole RAIDZ1 vdev showed unavailable. The GUI said wipe or reassign. Reading the ZFS labels said otherwise. 12 min read · [jjozzietech.hashnode.dev](https://jjozzietech.hashnode.dev/zfs-missing-vdev-recovery?utm_source=hashnode&utm_medium=feed) [Srekaravarshan N K](https://hashnode.com/@srekaravarshan) · [Aug 13](https://hashnode.com/posts/transaction-leak-connection-pool-outage/6a7da14d41767cf0e58b2e58) ### [How a Transaction We Forgot to Close Took Down a Service](https://srekaravarshan.hashnode.dev/transaction-leak-connection-pool-outage?utm_source=hashnode&utm_medium=feed) A survey API went down at 155 requests a minute while the database sat idle. The cause was a transaction we opened and never closed. 4 min read · [srekaravarshan.hashnode.dev](https://srekaravarshan.hashnode.dev/transaction-leak-connection-pool-outage?utm_source=hashnode&utm_medium=feed) [JJozzieTech](https://hashnode.com/@jjozzietech) · [Aug 6](https://hashnode.com/posts/truenas-smb-sid-acl-recovery/6a74e60e24ac8097ad95e444) ### [After a TrueNAS ISO reinstall — the two things that broke that no one warned me about](https://jjozzietech.hashnode.dev/truenas-smb-sid-acl-recovery?utm_source=hashnode&utm_medium=feed) A fresh ISO fixed the service layer. Then Windows stopped authenticating. The SID mismatch, the missing ACL entries, and the fix that got SMB back. 9 min read · [jjozzietech.hashnode.dev](https://jjozzietech.hashnode.dev/truenas-smb-sid-acl-recovery?utm_source=hashnode&utm_medium=feed) [JJozzieTech](https://hashnode.com/@jjozzietech) · [Jul 16](https://hashnode.com/posts/opnsense-bare-metal-18-months/6a593eeecc2782d0ac07f54b) ### [OPNsense on bare metal — 18 months as the only perimeter](https://jjozzietech.hashnode.dev/opnsense-bare-metal-18-months?utm_source=hashnode&utm_medium=feed) OPNsense on bare metal, 18 months as sole perimeter. Four things it taught me — plus four gaps I still haven't closed. 12 min read · [jjozzietech.hashnode.dev](https://jjozzietech.hashnode.dev/opnsense-bare-metal-18-months?utm_source=hashnode&utm_medium=feed) [JJozzieTech](https://hashnode.com/@jjozzietech) · [Jul 9](https://hashnode.com/posts/how-i-got-a-suspended-truenas-pool-back-online-without-replacing-a-single-disk/6a4f06503e999a588a84af93) ### [How I got a suspended TrueNAS pool back online without replacing a single disk](https://jjozzietech.hashnode.dev/how-i-got-a-suspended-truenas-pool-back-online-without-replacing-a-single-disk?utm_source=hashnode&utm_medium=feed) An 11-disk RAIDZ1 vdev showed multiple faulted drives and one member removed after a rack outage. Two commands got the pool back — no disk swaps. 9 min read · [jjozzietech.hashnode.dev](https://jjozzietech.hashnode.dev/how-i-got-a-suspended-truenas-pool-back-online-without-replacing-a-single-disk?utm_source=hashnode&utm_medium=feed) [Jordan Bourbonnais](https://hashnode.com/@clawpulse) · [Apr 23](https://hashnode.com/posts/a-practical-guide-to-building-ai-agent-incident-response-systems/69e9766dc7aafe334297ef03) ### [A Practical Guide to Building AI Agent Incident Response Systems](https://clawpulse.hashnode.dev/a-practical-guide-to-building-ai-agent-incident-response-systems?utm_source=hashnode&utm_medium=feed) What you'll learn How to architect incident response workflows that detect and react to AI agent failures in real-time Best practices for designing escalation policies tailored to different agent behaviors Techniques for implementing automatic remed... 4 min read · [clawpulse.hashnode.dev](https://clawpulse.hashnode.dev/a-practical-guide-to-building-ai-agent-incident-response-systems?utm_source=hashnode&utm_medium=feed) [Rahul Sehrawat](https://hashnode.com/@rahulseh1998) · [Apr 13](https://hashnode.com/posts/leadership-ai-incident-response/69dc7a320826097b1f4b7d46) ### [Leadership AI Incident Response: The First Six Hours](https://ai-zero-to-hero.hashnode.dev/leadership-ai-incident-response?utm_source=hashnode&utm_medium=feed) Your AI feature is on the front page of tech media. It is 9 am on a Tuesday. Your phone is ringing. Here is the six hour playbook for the leader whose job starts when engineering incident response ends. 18 min read · [ai-zero-to-hero.hashnode.dev](https://ai-zero-to-hero.hashnode.dev/leadership-ai-incident-response?utm_source=hashnode&utm_medium=feed) [Hasibul Hasan](https://hashnode.com/@hsblhsn) · [Aug 4, 2023](https://hashnode.com/posts/how-paypal-almost-lost-their-database/64ccc89ee8c10188752e2562) ### [How PayPal Almost Lost Their Database.](https://hsblhsn.me/how-paypal-almost-lost-their-database?utm_source=hashnode&utm_medium=feed) Due to an outdated difference between Linux and Solaris. 2 min read · [hsblhsn.me](https://hsblhsn.me/how-paypal-almost-lost-their-database?utm_source=hashnode&utm_medium=feed)