Date: Thu, 30 Jan 2025 12:05:54 +0000 From: Bob Bishop <rb@gid.co.uk> To: A FreeBSD User <freebsd@walstatt-de.de> Cc: "freebsd-current@freebsd.org" <freebsd-current@FreeBSD.org> Subject: Re: ZFS: Rescue FAULTED Pool Message-ID: <075A3339-6327-4C96-91D9-2F225AA74B38@gid.co.uk> In-Reply-To: <20250130123354.2d767c7c@thor.sb211.local> References: <20250129112701.0c4a3236@freyja> <Z5oU1dLX4eQaN8Yq@albert.catwhisker.org> <20250130123354.2d767c7c@thor.sb211.local>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, > [trimmed] >=20 > 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 useless in the realm of = professionals): I used a bunch of > cheap spotmarket SATA SSDs, a brand called "Intenso" common also here = in Good old Germany. > Some of those SSDs do have working LED when used with a Fujitsu SAS = HBA controller - but those > died very quickly from suffering some bus errors. Another bunch of = those SSDs do not have > working LED (not blinking on access), but lasted a bit longer. The = problem with those SSDs is: > I can not find the failing device easily by accessing the failed drive = by writing massive data > via dd, if possible.=20 > I also ordered alternative SSDs from a more expensive brand - but bad = Karma ... Yeah well there=E2=80=99s quite enough things that might go wrong even = without throwing dodgy SSDs into the mix. > Oliver >=20 >=20 > --=20 >=20 > A FreeBSD user -- Bob Bishop rb@gid.co.uk
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?075A3339-6327-4C96-91D9-2F225AA74B38>