From nobody Sun Jan 7 17:56:58 2024 X-Original-To: freebsd-stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T7Pz32LZ9z55YG6; Sun, 7 Jan 2024 17:57:03 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T7Pz31Swrz4V98; Sun, 7 Jan 2024 17:57:03 +0000 (UTC) (envelope-from lev@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1704650223; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=HGStHKmNPazPmWtR7oEhpy4qTf/4ZQS3U6FARk4litA=; b=YPo4TFZL6YB3hlmj+HJufyanbFOpa6ue5NfRu2VuCK3MzBUGqPUpNr7XRJha9jeKL/ssDp kxga4vuYplfSf+Xx11iTiNODpvKLbUemBAcTQzFWSeBGCpKsAXjCMNu+IVjzRoQC2Jxu18 XExiDiKjvoh2NwKdY6RRpv2F1XNZ5DRl9sx2GdjPnnzHDjTH/CkIkiH0HsLILWcju/Ye+x MJEwZWhU2HH3WNK71IWcb8qORdwKdZpRGjzr9F5CPxmqZzPXULmooqC8p8Fml2YCc8vJUK KA7ZKCv01g9BGJZbfj2dKQkQonkKJQviKtCTgzEBjaep9FA+iaNyn+AmkiWBxQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1704650223; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=HGStHKmNPazPmWtR7oEhpy4qTf/4ZQS3U6FARk4litA=; b=T8jezpsaLvh9H8GkUrTk0mUdicBztmqMszrxBAezk3deotfczbWjqtC3kbT+0zGJSKlMrw A40oj1K3Gav37YuxNydhq3f+Ps1mD0am/5Fj6mt2oRcN2mPkfuUXuVRjG9fimuVeEVLDDz pZveXAm480cxptM50rSk3fKpwzB+u1cyUXvzIVXQBQfvg4pu7cUq4kEkA+RCOjoJTRob6k D0JbMUFsZvslNsHn2fbCbAvRrdSMSnSGlI3Btb61ER1iM4Ze6jjwB5kWRjnCSWKtsmVm7X 4h/xMhK+quFtwDU5Z+nR3lWQZWZjg9hbh723Lxt0tMGSsNgI25nY0mEYBQuvww== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1704650223; a=rsa-sha256; cv=none; b=dU/oNAnFZZW9ojUI59q4iwTL6BDrMNJvp6i8ivyVaih4OmHOpJA58CSn0YOyp4403lOUEi qhus5eJ7UzbfRmuQjKfyi76m2VPSu4nvSijINWi23E9uwpJMIKjJvw9RMQZkR314XQg1Wx uYNBEoTHdz9Ha8x4t8gSXjUXnfts4hpXeUVImTzRn7tLmxXTTkFqwQ3Ghfv3S6WLhXfkG9 ZzJGguDMG3MaJ9aTF9jhNgGL3FDtkIqfVL13GbrSLEokHeOvX7Fycipjyf4D9qaeVMApbq ZOTyoqsGxKxQf+lXuaGZi+SzW51N3nQ0Is5eNyiP2Z6gAa7A3S8vvuJGNyzpiQ== Received: from onlyone.not-for.work (onlyone.not-for.work [IPv6:2a01:4f8:201:6350::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: lev/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4T7Pz26tRszVLM; Sun, 7 Jan 2024 17:57:02 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [192.168.136.24] (83-84-181-95.cable.dynamic.v4.ziggo.nl [83.84.181.95]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.not-for.work (Postfix) with ESMTPSA id 1EDA532D; Sun, 7 Jan 2024 20:56:58 +0300 (MSK) Message-ID: <065f4f5c-f38b-45f4-b7e7-5248f871f7e6@FreeBSD.org> Date: Sun, 7 Jan 2024 18:56:58 +0100 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Reply-To: lev@FreeBSD.org Subject: Re: FreeBSD 13.2-STABLE can not boot from damaged mirror AND pool stuck in "resilver" state even without new devices. To: Miroslav Lachman <000.fbsd@quip.cz>, freebsd-fs , freebsd-stable References: Content-Language: en-US From: Lev Serebryakov Organization: FreeBSD In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 07.01.2024 16:38, Miroslav Lachman wrote: >>> ZFS: i/o error - all block copies unavailable >>> ZFS: can't read MOS of pool zroot >>> >>>     after that. >>   I've re-created pool from scratch >> >>   zpool create znewroot ada0p3 && zfs send zroot | zfs receive znewroot && zpool destroy zroot && zpool attach znewroot ada0p3 ada1p3 >> >>   but gptzfsboot still can not boot from it with same diagnostics :-( > > How large are your disks in a question? 2TB ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: ACS-2 ATA SATA 3.x device ada0: Serial Number K5HPZZLD ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 1907729MB (3907029168 512 byte sectors) ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 ada1: ATA8-ACS SATA 3.x device ada1: Serial Number WD-WMC1P0504169 ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 1907729MB (3907029168 512 byte sectors) > As far as I search the internet it is caused by the boot code (later stage which is in a file in /boot directory) was moved too far from the beginning of the disk and some old BIOS cannot allow the system to continue booting. Oh, it is good hypothesis. It is Haswell-time MSI board (old Hetzner EX40 instance)... > It can also be avoided if your machine supports EFI boot, but my HP Microserver Gen 8 does not support it. I'll try to switch to EFI, but it needs some luck to get to BIOS with provided KVM, it is very unstable :-) -- // Lev Serebryakov