From owner-freebsd-questions@freebsd.org Thu Nov 8 12:42:28 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0E10F1128CF4 for ; Thu, 8 Nov 2018 12:42:28 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.fagskolen.gjovik.no", Issuer "Fagskolen i Gj??vik" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 81F967C597 for ; Thu, 8 Nov 2018 12:42:21 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.15.2/8.15.2) with ESMTPS id wA8CgFrL058822 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Thu, 8 Nov 2018 13:42:15 +0100 (CET) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.15.2/8.15.2/Submit) with ESMTP id wA8CgEKq058819 for ; Thu, 8 Nov 2018 13:42:15 +0100 (CET) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Thu, 8 Nov 2018 13:42:14 +0100 (CET) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: FreeBSD questions Subject: 13.0-CURRENT: Cannot probe medium sector size Message-ID: User-Agent: Alpine 2.21.9999 (BSF 287 2018-06-16) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.fig.ol.no X-Rspamd-Queue-Id: 81F967C597 X-Spamd-Result: default: False [-2.18 / 200.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.98)[-0.977,0]; NEURAL_HAM_LONG(-0.81)[-0.805,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; HAS_ORG_HEADER(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[fagskolen.gjovik.no]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[smtp.fagskolen.gjovik.no]; NEURAL_HAM_SHORT(-0.38)[-0.383,0]; IP_SCORE(-0.01)[ipnet: 2001:700::/32(-0.02), asn: 224(-0.01), country: NO(-0.01)]; FORGED_SENDER(0.30)[Trond.Endrestol@fagskolen.gjovik.no,trond@fagskolen.gjovik.no]; R_DKIM_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:224, ipnet:2001:700::/32, country:NO]; FROM_NEQ_ENVFROM(0.00)[Trond.Endrestol@fagskolen.gjovik.no, trond@fagskolen.gjovik.no] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2018 12:42:28 -0000 I have a non-vital VM on XenServer 7.6, running: FreeBSD freebsd-head-zfs.FQDN 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r340244: Thu Nov 8 12:47:24 CET 2018 root@freebsd-head-zfs.FQDN:/usr/obj/usr/src/amd64.amd64/sys/XENGUEST amd64 1300003 1300003 The boot disks are partitioned as shown below: $ gpart show -p ada0 ada1 ada2 => 40 33554352 ada0 GPT (16G) 40 1024 ada0p1 freebsd-boot (512K) 1064 33553320 ada0p2 freebsd-zfs (16G) 33554384 8 - free - (4.0K) => 40 33554352 ada1 GPT (16G) 40 1024 ada1p1 freebsd-boot (512K) 1064 33553320 ada1p2 freebsd-zfs (16G) 33554384 8 - free - (4.0K) => 40 33554352 ada2 GPT (16G) 40 1024 ada2p1 freebsd-boot (512K) 1064 33553320 ada2p2 freebsd-zfs (16G) 33554384 8 - free - (4.0K) Before and while presenting the boot loader's menu, the screen is filled with: Cannot probe medium sector size See https://ximalas.info/~trond/13.0-CURRENT-r340244-Cannot-probe-medium-sector-size/13.0-CURRENT-r340244-Cannot-probe-medium-sector-size.png The system is bootable. It's been like this for a long time, but I figured it's time to do something, if possible. Are there any chance of silencing these messages? Are the partitions misaligned? Does XenServer convey the necessary information? The same issue holds true for non-UEFI systems running under recent versions of VirtualBox. (XenServer supports only BIOS/legacy boot firmware.) -- Trond.