Re: ZFS: Rescue FAULTED Pool

2025-02-07 Thread Bob Bishop
Hi, > On 7 Feb 2025, at 08:48, A FreeBSD User wrote: > > Am Tue, 4 Feb 2025 12:18:06 +0200 > Andriy Gapon schrieb: > >> On 01/02/2025 10:57, A FreeBSD User wrote: >>> Hello, this exactly happens when trying to import the pool. Prior to the >>> loss, device da1p1 >>> has been faulted with numb

Re: ZFS: Rescue FAULTED Pool

2025-02-07 Thread A FreeBSD User
Am Tue, 4 Feb 2025 12:18:06 +0200 Andriy Gapon schrieb: > On 01/02/2025 10:57, A FreeBSD User wrote: > > Hello, this exactly happens when trying to import the pool. Prior to the > > loss, device da1p1 > > has been faulted with numbers in the colum/columns "corrupted data"/further > > not seen n

Re: ZFS: Rescue FAULTED Pool

2025-02-04 Thread Andriy Gapon
On 01/02/2025 10:57, A FreeBSD User wrote: Hello, this exactly happens when trying to import the pool. Prior to the loss, device da1p1 has been faulted with numbers in the colum/columns "corrupted data"/further not seen now. ~# zpool import pool: BUNKER00 id:

Re: ZFS: Rescue FAULTED Pool

2025-02-03 Thread A FreeBSD User
Am Sat, 1 Feb 2025 09:10:25 -0500 Dennis Clarke schrieb: > >> > >> The most useful thing to share right now would be the output of `zpool > >> import` (with no pool name) on the rebooted system. > >> > >> That will show where the issues are, and suggest how they might be solved. > >> > > > > H

Re: ZFS: Rescue FAULTED Pool

2025-02-01 Thread Dennis Clarke
The most useful thing to share right now would be the output of `zpool import` (with no pool name) on the rebooted system. That will show where the issues are, and suggest how they might be solved. Hello, this exactly happens when trying to import the pool. Prior to the loss, device da1p1

Re: ZFS: Rescue FAULTED Pool

2025-02-01 Thread A FreeBSD User
Am Thu, 30 Jan 2025 16:13:56 -0500 Allan Jude schrieb: > On 1/30/2025 6:35 AM, A FreeBSD User wrote: > > Am Wed, 29 Jan 2025 03:45:25 -0800 > > David Wolfskill schrieb: > > > > Hello, thanks for responding. > > > >> On Wed, Jan 29, 2025 at 11:27:01AM +0100, FreeBSD User wrote: > >>> Hello,

Re: ZFS: Rescue FAULTED Pool

2025-01-30 Thread Allan Jude
On 1/30/2025 6:35 AM, A FreeBSD User wrote: Am Wed, 29 Jan 2025 03:45:25 -0800 David Wolfskill schrieb: Hello, thanks for responding. On Wed, Jan 29, 2025 at 11:27:01AM +0100, FreeBSD User wrote: Hello, a ZFS pool (RAINDZ(1)) has been faulted. The pool is not importable anymore. neither wit

Re: ZFS: Rescue FAULTED Pool

2025-01-30 Thread Patrick M. Hausen
Hi all, > Am 30.01.2025 um 12:35 schrieb A FreeBSD User : > Well, in this case I do not use dedicated ZIL drives. I also made several > experiences with > "single" ZIL drive setups, but a dedicated ZIL is mostly useful in cases were > you have > graveyard full of inertia-suffering, mass-spinning

Re: ZFS: Rescue FAULTED Pool

2025-01-30 Thread Bob Bishop
Hi, > [trimmed] > > Well, this is a hard and painful lecture to learn, if there is no chance to > get back the pool. Have you tried import -FX ? -FXn might tell you non-destructively whether that will work but I have never been down this particular hole. > A warning (but this seems to be use

Re: ZFS: Rescue FAULTED Pool

2025-01-30 Thread A FreeBSD User
Am Wed, 29 Jan 2025 03:45:25 -0800 David Wolfskill schrieb: Hello, thanks for responding. > On Wed, Jan 29, 2025 at 11:27:01AM +0100, FreeBSD User wrote: > > Hello, > > > > a ZFS pool (RAINDZ(1)) has been faulted. The pool is not importable > > anymore. neither with import -F/-f. > > Although t

Re: ZFS: Rescue FAULTED Pool

2025-01-29 Thread Alan Somers
On Wed, Jan 29, 2025 at 3:27 AM FreeBSD User wrote: > > Hello, > > a ZFS pool (RAINDZ(1)) has been faulted. The pool is not importable > anymore. neither with import -F/-f. > Although this pool is on an experimental system (no backup available) > it contains some data to reconstruct them would tak