From owner-freebsd-stable@freebsd.org Tue Oct 6 10:16:52 2020 Return-Path: Delivered-To: freebsd-stable@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 D753A42ECF3 for ; Tue, 6 Oct 2020 10:16:52 +0000 (UTC) (envelope-from rpalov@e-card.bg) Received: from e-card.bg (mail.e-card.bg [193.47.74.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4C5D0M3HfNz4HPm for ; Tue, 6 Oct 2020 10:16:50 +0000 (UTC) (envelope-from rpalov@e-card.bg) Comment: DomainKeys? See http://domainkeys.sourceforge.net/ Received: (qmail 71471 invoked by uid 89); 6 Oct 2020 10:16:42 -0000 Received: from unknown (HELO webbie.e-card.bg) (10.20.10.13) by mail.e-card.bg with SMTP; 6 Oct 2020 10:16:42 -0000 Reply-To: rpalov@e-card.bg To: freebsd-stable@freebsd.org From: =?UTF-8?B?0KDRg9C80LXQvSDQn9Cw0LvQvtCy?= Subject: Issues with gptboot loader Organization: E-CARD LTD. Message-ID: Date: Tue, 6 Oct 2020 13:16:42 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4C5D0M3HfNz4HPm X-Spamd-Bar: ++++ X-Spamd-Result: default: False [4.74 / 15.00]; HAS_REPLYTO(0.00)[rpalov@e-card.bg]; ARC_NA(0.00)[]; R_DKIM_ALLOW(0.00)[e-card.bg:s=default]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(0.00)[+mx]; MIME_GOOD(-0.10)[text/plain]; REPLYTO_ADDR_EQ_FROM(0.00)[]; TO_DN_NONE(0.00)[]; NEURAL_SPAM_MEDIUM(1.04)[1.041]; RCPT_COUNT_ONE(0.00)[1]; HAS_ORG_HEADER(0.00)[]; RBL_VIRUSFREE_BOTNET(2.00)[193.47.74.3:from]; NEURAL_SPAM_SHORT(0.69)[0.694]; DKIM_TRACE(0.00)[e-card.bg:+]; DMARC_POLICY_ALLOW(0.00)[e-card.bg,quarantine]; NEURAL_SPAM_LONG(1.01)[1.005]; BAD_REP_POLICIES(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:35293, ipnet:193.47.74.0/24, country:BG]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-stable] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Oct 2020 10:16:52 -0000 Hello all, We have following situations with FreeBSD 12.1 Release. Updating to FreeBSD 12 Stable does not change the situation. We have Server with 8T UFS root partition created on top of AVAGO 9361-4i RAID 10 with lastest firmware. It works on FreeBSD 11.1 Stable, before upgrade and boot in normal fashion. After the ugprade the OS to FreeBSD 12.1 or 12.2 it was unable to boot. We backup the content of system disk and start playing with the RAID configuration, changing RAID cards and so on. Our results are as follow with FreeBSD12.1 Release IMG: When the RAID is 8T the booting process freezes on message "gptboot: invalid backup GPT header" When we recreate the RAID of 4T it boots to mountfrom> prompt and to continue, we need to enter the same disk device, which is described in the fstab manualy, etc: ufs:/dev/da0p2 When we recreate the RAID with (500G and 2500G) it boots normal and mount the root partiion. The issues described above are valid only for gptboot loader. With zfs installed there is this message: "Shortening read at 4294967200" from 16 to 15 Then we decide to exclude the RAID card from the setup and connect one 6T drive to the motherboard and here the major factor of succesful boot becomes the presence of usb drive with freebsd install image. When we install FeeBSD on partition with size up to 5T, the system boots normaly mount the root partition and the OS is ready for operations. Here does not matter if the flash drive is present or not. When we install FreeBSD on the full size of the HDD 6T( eg 5.5T usable ) and try to boot with usb drive plugged, the booting process fails with message "can't load kernel". If the flash drive is removed from the Server, the booting proccess goes successful. Here we do not repeat the steps with zfsloader. The motherboard is SUPERMICRO X11DPI-NT with lates BIOS firmware. Is any one having issues like this ? Is this behavior enougth for PR request ? -- Chhers Rumen Palov