Date: Sat, 12 Aug 2017 22:23:19 -0400 From: Paul Kraus <paul@kraus-haus.org> To: Chris Ross <cross+freebsd@distal.com>, FreeBSD FS <freebsd-fs@freebsd.org> Subject: Re: Oh no, what have I done... Message-ID: <035BFBCB-BA43-4568-89E9-8E8DCDFAA8CA@kraus-haus.org> In-Reply-To: <5B508AED-4DAC-42E4-8C56-4619C0D1A1C6@distal.com> References: <3408A832-BF2E-4525-9EAC-40979BA3555B@distal.com> <20170813000323.GC95431@server.rulingia.com> <5B508AED-4DAC-42E4-8C56-4619C0D1A1C6@distal.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Aug 12, 2017, at 9:22 PM, Chris Ross <cross+freebsd@distal.com> = wrote: >=20 >=20 >> On Aug 12, 2017, at 20:03 , Peter Jeremy <peter@rulingia.com> wrote: >>=20 >> On 2017-Aug-12 19:36:31 -0400, Chris Ross <cross+freebsd@distal.com> = wrote: >>> But, I fear I may=E2=80=99ve shot myself. Is there any way to = recover my raid1z vdev from this situation, and get a working zfs pool = back? >>=20 >> There's no way to detach the vdev /dev/da2p1 - you need to backup and >> re-create the pool. You need to re-attach /dev/da2p1 so the pool can >> be imported, then do a backup, destroy the pool and re-create it. >=20 > Can I attach a different similar drive as da2p1? Nope. > Or, does it have to have the same bits that were put on it when it = was in the pool previously? If the latter, I don=E2=80=99t have those = bits any more. The same disk. ZFS is looking for the labels it writes (4x for = redundancy; 2 at the beginning of the disk and 2 at the end; it only = _needs_ to find one of them) to identify the drive to include it in the = zpool. If that disk no longer contains the ZFS labels then you are = probably out of luck. You _may_, and this is a very, very long shot, be able to force an = import to a TXG (transaction group) _before_ you added the lone drive = vdev. > I=E2=80=99ll try putting a disk with the same layout in, and see how = that goes. That was a thought I=E2=80=99d had. Won=E2=80=99t work, without the ZFS labels it will not be seen as the = missing drive.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?035BFBCB-BA43-4568-89E9-8E8DCDFAA8CA>