---
title: "Discussion on \"Recovering a ZFS pool with a missing RAIDZ1 vdev — without wiping a single disk\" | Hashnode"
description: "Discussion on \"Recovering a ZFS pool with a missing RAIDZ1 vdev — without wiping a single disk\". 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."
url: "https://hashnode.com/posts/zfs-missing-vdev-recovery/6a7e27de21c0f66fbbcb83f8"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [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.

Aug 13 · 12 min read · jjozzietech.hashnode.dev  
Read the article

-   [#homelab](https://hashnode.com/tag/homelab)
-   [#truenas](https://hashnode.com/tag/truenas)
-   [#zfs](https://hashnode.com/tag/zfs)
-   [#storage](https://hashnode.com/tag/storage)
-   [#incident](https://hashnode.com/tag/incident)
-   [#recovery](https://hashnode.com/tag/recovery)

## Written by

[JJozzieTech](https://hashnode.com/@jjozzietech)

@jjozzietech · Sydney, Australia

  
[View profile](https://hashnode.com/@jjozzietech)

Enterprise lab. Sydney rack. I write about what actually breaks.

Sydney-based infrastructure operator. Enterpriselab, DePIN workloads, and the incident logs behind them. I write about what actually breaks.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.