Date: Fri, 7 Feb 2025 09:48:21 +0100 From: A FreeBSD User <freebsd@walstatt-de.de> To: Andriy Gapon <avg@FreeBSD.org> Cc: freebsd-current@freebsd.org Subject: Re: ZFS: Rescue FAULTED Pool Message-ID: <20250207094848.3fcdd20a@thor.sb211.local> In-Reply-To: <e94ec688-099d-4368-b383-ea358dff85ef@FreeBSD.org> References: <20250129112701.0c4a3236@freyja> <Z5oU1dLX4eQaN8Yq@albert.catwhisker.org> <20250130123354.2d767c7c@thor.sb211.local> <980401eb-f8f6-44c7-8ee1-5ff0c9e1c35c@freebsd.org> <20250201095656.1bdfbe5f@thor.sb211.local> <e94ec688-099d-4368-b383-ea358dff85ef@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Am Tue, 4 Feb 2025 12:18:06 +0200 Andriy Gapon <avg@FreeBSD.org> 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 now. > > > > > > ~# zpool import > > pool: BUNKER00 > > id: XXXXXXXXXXXXXXXXXXXX > > state: FAULTED > > status: The pool metadata is corrupted. > > action: The pool cannot be imported due to damaged devices or data. > > The pool may be active on another system, but can be imported using > > the '-f' flag. > > see:https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-72 > > config: > > > > BUNKER00 FAULTED corrupted data > > raidz1-0 ONLINE > > da2p1 ONLINE > > da3p1 ONLINE > > da4p1 ONLINE > > da7p1 ONLINE > > da6p1 ONLINE > > da1p1 ONLINE > > da5p1 ONLINE > > > > > > ~# zpool import -f BUNKER00 > > cannot import 'BUNKER00': I/O error > > Destroy and re-create the pool from > > a backup source. > > > > > > ~# zpool import -F BUNKER00 > > cannot import 'BUNKER00': one or more devices is currently unavailable > > > Too late now, but another useful command for situations like this is > zdb -G BUNKER00 > It would print a log of various pool import actions. Not "too late", very much appreciated, such helpful worst-case-scenario would have a nice place in a small section "desaster recovery" in the handbook, wouldn't it? The handbook is quite superficial at that point ... Kind regards, Oliver > > E.g., on a good pool: > # zdb -G rpool > > ZFS_DBGMSG(zdb) START: > spa.c:5694:spa_open_common(): spa_open_common: opening rpool > spa_misc.c:419:spa_load_note(): spa_load(rpool, config trusted): LOADING > vdev.c:162:vdev_dbgmsg(): disk vdev '/dev/gpt/S6PEN.rpool': best uberblock found > for spa rpool. txg 61892397 > spa_misc.c:419:spa_load_note(): spa_load(rpool, config untrusted): using > uberblock with txg=61892397 > spa_misc.c:2311:spa_import_progress_set_notes_impl(): 'rpool' Loading checkpoint txg > spa_misc.c:2311:spa_import_progress_set_notes_impl(): 'rpool' Loading indirect > vdev metadata > spa_misc.c:2311:spa_import_progress_set_notes_impl(): 'rpool' Checking feature flags > spa_misc.c:2311:spa_import_progress_set_notes_impl(): 'rpool' Loading special > MOS directories > spa_misc.c:2311:spa_import_progress_set_notes_impl(): 'rpool' Loading properties > spa_misc.c:2311:spa_import_progress_set_notes_impl(): 'rpool' Loading AUX vdevs > spa_misc.c:2311:spa_import_progress_set_notes_impl(): 'rpool' Loading vdev metadata > spa_misc.c:2311:spa_import_progress_set_notes_impl(): 'rpool' Loading dedup tables > spa_misc.c:2311:spa_import_progress_set_notes_impl(): 'rpool' Loading BRT > spa_misc.c:2311:spa_import_progress_set_notes_impl(): 'rpool' Verifying Log Devices > spa_misc.c:2311:spa_import_progress_set_notes_impl(): 'rpool' Verifying pool data > spa_misc.c:419:spa_load_note(): spa_load(rpool, config trusted): spa_load_verify > found 0 metadata errors and 4 data errors > spa_misc.c:2311:spa_import_progress_set_notes_impl(): 'rpool' Calculating > deflated space > spa_misc.c:2311:spa_import_progress_set_notes_impl(): 'rpool' Starting import > spa.c:8925:spa_async_request(): spa=rpool async request task=2048 > spa_misc.c:419:spa_load_note(): spa_load(rpool, config trusted): LOADED > ZFS_DBGMSG(zdb) END > > On a bad pool, the log may have helped to identify the exact problem. > -- A FreeBSD user [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQRQheDybVktG5eW/1Kxzvs8OqokrwUCZ6XI8AAKCRCxzvs8Oqok r8iTAPwN+WFMbpZA7R+QwEuklMFyqfFKYpuQgp32U25ZoVuQDQEA8ExkypZzniU1 pnGgZMvoM4oAnP5rYNokhaMRux9zCgc= =vBUI -----END PGP SIGNATURE-----help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20250207094848.3fcdd20a>