Date: Tue, 6 Nov 2018 15:05:02 +0100 From: Philipp Vlassakakis <freebsd-en@lists.vlassakakis.de> To: Alejandro Imass <aimass@yabarana.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: ZFS re attaching failed device to pool Message-ID: <4C7379FD-8646-4246-9CD0-AC3B281B32C9@lists.vlassakakis.de> In-Reply-To: <CAHieY7R%2BCNNzPQwCGJW8ugy266EXXBZmF1EPs2gvacJ3=56eiA@mail.gmail.com> References: <CAHieY7RP9hjZ8TDqz8PFNoeo2gVY5%2BA2icA288mmvh__e1j5XA@mail.gmail.com> <CAHieY7R%2BCNNzPQwCGJW8ugy266EXXBZmF1EPs2gvacJ3=56eiA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Alex, Did you try =E2=80=9Ezpool online zroot NAME-OF-DEGRADED-DISK=E2=80=9C and =E2= =80=9Ezpool zroot clear=E2=80=9C ? Regards, Philipp > On 6. Nov 2018, at 14:53, Alejandro Imass <aimass@yabarana.com> wrote: >=20 >> On Tue, Nov 6, 2018 at 8:50 AM Alejandro Imass <aimass@yabarana.com> wrot= e: >>=20 >> Dear Beasties, >>=20 >> I have a simple 2 disk pool and one disk started failing and zfs put it i= n >> a UNAVAIL status. I shut down the server and took it apart, cleaned it an= d >> removed a third device that was on Sata Port C which I think may have bee= n >> the culprit of the bus fault. This third disk was unrelated to the pool a= nd >> was an older disk which just had some backup data and was running on an o= ld >> enclosure with the SATA wires hanging out, etc. you know, those 5 minute >> hacks that you forget about.. >>=20 >> After rebooting, the BIOS saw the failed device and the system booted >> fine. I ran a smartctl long test on the failed device which took like 7 >> hours and the report shows no errors and the device is like new. >>=20 >> So now I want to tell ZFS to re-attach the device but the documentation i= s >> not too clear about this. All the docs, and example I find is physically >> replacing with another device, not the same one. >>=20 >> My question is almost identical to this one which has not been answered >> either: >>=20 >>=20 >> https://forums.freebsd.org/threads/re-attaching-failed-device-to-pool.660= 27/ >>=20 >> So: can I re-attach by running the replace command on the SAME device? I >> haven't tried it, but from the question above it seems that it won't let >> me. Besides I don't want to screw up so if anyone has done this before pl= s. >> advise how to proceed in these cases. >>=20 >> TIA! >> -- >> Alex >>=20 >>=20 >>=20 > I forgot to mention I ran zpool clear zroot and it ran the scrub but did > not put the disk back ONLINE. Here is the result: >=20 > root@poseidon:~ # zpool status -v > pool: zroot > state: DEGRADED > status: One or more devices could not be used because the label is missing= > or > invalid. Sufficient replicas exist for the pool to continue > functioning in a degraded state. > action: Replace the device using 'zpool replace'. > see: http://illumos.org/msg/ZFS-8000-4J > scan: scrub repaired 0 in 0h8m with 0 errors on Tue Nov 6 05:27:20 2018 > config: >=20 > NAME STATE READ WRITE CKSUM > zroot DEGRADED 0 0 0 > mirror-0 DEGRADED 0 0 0 > 5540674508897617692 UNAVAIL 0 0 0 was > /dev/diskid/DISK-WD-WCC4N6XZY8C2 > diskid/DISK-WD-WCC4N2YTRX40p3 ONLINE 0 0 0 >=20 > errors: No known data errors >=20 > Again, TIA for any pointers on how to re-attach the failed disk. >=20 > --=20 > Alex > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.or= g"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C7379FD-8646-4246-9CD0-AC3B281B32C9>