From owner-freebsd-hackers@freebsd.org Thu Jan 30 15:09:32 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7872023C05D for ; Thu, 30 Jan 2020 15:09:32 +0000 (UTC) (envelope-from peter.rapcan@savba.sk) Received: from smtp.savba.sk (smtp.savba.sk [147.213.1.2]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 487kKR3KqCz4DJX for ; Thu, 30 Jan 2020 15:09:31 +0000 (UTC) (envelope-from peter.rapcan@savba.sk) Received: from [192.168.1.80] (fire.quniverse.sk [147.213.112.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: fyziprap) by smtp.savba.sk (Postfix) with ESMTPSA id D3AB255890; Thu, 30 Jan 2020 16:09:29 +0100 (CET) From: =?utf-8?Q?Peter_Rap=C4=8Dan?= Message-Id: Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: How do I tell gptzfsboot NOT to analyze other disks (or specify which disks to analyze)? Date: Thu, 30 Jan 2020 16:09:29 +0100 In-Reply-To: Cc: "freebsd-hackers@freebsd.org" To: Warner Losh References: X-Mailer: Apple Mail (2.3445.104.11) X-Rspamd-Queue-Id: 487kKR3KqCz4DJX X-Spamd-Bar: +++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of peter.rapcan@savba.sk designates 147.213.1.2 as permitted sender) smtp.mailfrom=peter.rapcan@savba.sk X-Spamd-Result: default: False [5.88 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:147.213.1.0/27:c]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; SUBJECT_ENDS_QUESTION(1.00)[]; DMARC_NA(0.00)[savba.sk]; NEURAL_SPAM_MEDIUM(1.00)[0.998,0]; URI_COUNT_ODD(1.00)[7]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(1.00)[1.000,0]; IP_SCORE(1.68)[ipnet: 147.213.0.0/16(4.38), asn: 2607(3.93), country: SK(0.09)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:2607, ipnet:147.213.0.0/16, country:SK]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2020 15:09:32 -0000 Thanks for your reply! I believe it is some kind of bug (maybe related to to = https://forums.freebsd.org/threads/gptzfsboot-error-128-after-adding-new-d= isks.65677/ but the solution provided there makes no difference in my = case). The funny thing is that the same system with the same type of disks = worked before (with 3 data HDDS and freeNAS [11.2-Ux]) there were no = gptzfsboot errors and the boot time was fast. After I added a 4th data = drive and upgraded the system (freeNAS) to new version, only then I = started getting the "gptzfsboot: error 128 lba some_block_number=E2=80=9D = errors. However I was not able revert to the state without the errors, = altough I tried the original version of freeNAS, with 3, 2, or 1 data = HDD(s), I tried wiping the HDDS, removing the partition table, creating = a new one, etc=E2=80=A6. I even tried installing freeBSD instead of = freeNAS :-). I am new to freeBSD=E2=80=A6 could you perhaps give me some advice how = to troubleshoot this error? Best, Peter > On 30 Jan 2020, at 15:49, Warner Losh wrote: >=20 >=20 >=20 > On Thu, Jan 30, 2020 at 7:42 AM Peter Rap=C4=8Dan = > wrote: > Hi, >=20 > Is there a way to tell gptzfsboot NOT to analyze other disks (or = specify which disks to analyze)? (My system is on PATA disk(s) while the = data disks are SATA, hence there is no use to probe the SATA disks to = search for a bootable system). >=20 > I am asking this to get around the following problem (bug?) I = encountered (tried both freeBSD 12.1 and freeNAS [11.2-U4 though = 11.3-RC2]):=20 > When booting, I get "gptzfsboot: error 128 lba some_block_number" = errors in the phase when gptzfsboot is probing my data HDDs (on which = there is no bootloader, nor system, the drives can be even empty, with = or without a partition table).=20 > The system boots eventually but the boot takes cca N x 7 minutes, = where N is the number of data disks gptzfsboot is trying to analyze = (there are several gptzfsboot: error 128 lba some_block_number lines per = disk and each takes some time to appear). >=20 > Short of hacking the code, there's really no way to do this. It's a = feature that it finds all the disks in the pool so we can boot off = zraid. > =20 > Note: installer CD boots the installer system just fine. Also, once = the system is installed, and the system has booted from HDD (this takes = ~30 minutes with multiple gptzfsboot: error 128 lba some_block_number = for each disk) the system works just fine, including the very same data = disks that "produce" the errors.=20 >=20 > Anyway, should this be reported as a bug? >=20 > You should report this as a feature request. It's not a bug, per se, = because we need to look for multiple drives in many cases. If you want = it to only look at the one disk that the boot loader was loaded from, = that would be your ask. >=20 > The other ask is to be more tolerant of this situation. A 7 minute lag = to probe a single drive is 7 minutes too long... That's clearly some = kind of bug, but without poking at your system in more detail, it's hard = to know for sure. >=20 > Warner > =20 > Any help is greatly appreciated. >=20 >=20 > Cheers, --Peter >=20 >=20 > P.S.: When putting the drives in another PC, the behavior is the same, = only gptzfsboot: error 128 lba some_block_number becomes gptzfsboot: = error 32 [if I remember the number correctly] lba some_block_number. > _______________________________________________ > freebsd-hackers@freebsd.org = mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers = > To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org = "