From owner-freebsd-questions@freebsd.org Wed Nov 27 15:53:07 2019 Return-Path: Delivered-To: freebsd-questions@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 A3D771AFCCC for ; Wed, 27 Nov 2019 15:53:07 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (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 47NQKD2Vxdz4DJd for ; Wed, 27 Nov 2019 15:53:02 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 3800A960 for ; Wed, 27 Nov 2019 10:52:57 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Wed, 27 Nov 2019 10:52:57 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= date:from:to:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm1; bh=RKg28Zhl0WIHcAbuu22iwVWPc1r dGjKnXIq0RL0zdFM=; b=n1seOrUiqaC5DAlrgWArkOjkga6g7HgvGRHyD34AWs4 6Rs8CkIfmYIv3qMqfVkftExhqDRnS++EPQRCUegBHNUNy38klQDiYTmZFfu5eWX7 /ujBcIRV4I4K/zrrubLxtjPqzEoifXlHx36JcH6Ekk7o6tlv3F5Z7P6iV/SuMAxT 1IO24j0YpC3sRj7A+Exm3plis4wmGmCrJkDtTdlD2z8pTc6IVR1ZHMImgDpu9Dh8 0pnb1svPU2TYW0WY1xcYvp6X0NfAd0tUrR6WTk7wGCWQX5oRy11HHEZhPbWredgV qu7OJkbTPv1i+kt2qCBnVVPKhixycGkAwtSs5tJGSwQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=RKg28Z hl0WIHcAbuu22iwVWPc1rdGjKnXIq0RL0zdFM=; b=GSCAYkroZrXHK4oq8ituja M8S9xjoGLQhG6zTYJ/GV2fkInQgjLIqFsopMxZqbaHF45hrjHXViK8HfmegL83PR liE2dlCiH4seYEIIdNeFhjzOBgxHQOywTLZKqZtzg2Q/P5cJxT57lJUj4lfQx3WC Qnp5c6Yd0rLxs5nts+7OE1+eXGLykETlFZuWUvKElnxeJa4dlj7+4b/I8zcZFCO+ /dg8Ua7ePWXxYFE5RiHMpBzo8DLIkBd9sxu0Zo61afamPCfGYIC42yxCUzSG/JE/ vuoe4mrsMWA5u1nHYW+Svfq4kCcb3rSIH08lJhBMRT/90tINIiJ3VX7ORJ5xq7fw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudeihedgkedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujggfsehgtd erredtredvnecuhfhrohhmpehtvggthhdqlhhishhtshcuoehtvggthhdqlhhishhtshes iiihgihsthdrnhgvtheqnecukfhppeekvddrjedtrdeluddrleelnecurfgrrhgrmhepmh grihhlfhhrohhmpehtvggthhdqlhhishhtshesiiihgihsthdrnhgvthenucevlhhushht vghrufhiiigvpedt X-ME-Proxy: Received: from bastion.zyxst.net (bastion.zyxst.net [82.70.91.99]) by mail.messagingengine.com (Postfix) with ESMTPA id 39BB9306005E for ; Wed, 27 Nov 2019 10:52:54 -0500 (EST) Date: Wed, 27 Nov 2019 15:52:24 +0000 From: tech-lists To: freebsd-questions@freebsd.org Subject: Re: 12.1-STABLE r354923 snapshot install doesn't like manual ufs setup Message-ID: <20191127155224.GC75104@bastion.zyxst.net> Mail-Followup-To: freebsd-questions@freebsd.org References: <20191127033739.GB75104@bastion.zyxst.net> <20191127131609.e69ab03c.freebsd@edvax.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="p2kqVDKq5asng8Dg" Content-Disposition: inline In-Reply-To: <20191127131609.e69ab03c.freebsd@edvax.de> User-Agent: Mutt/1.12.2 (2019-09-21) X-Rspamd-Queue-Id: 47NQKD2Vxdz4DJd X-Spamd-Bar: -------- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=zyxst.net header.s=fm1 header.b=n1seOrUi; dkim=pass header.d=messagingengine.com header.s=fm1 header.b=GSCAYkro; dmarc=none; spf=pass (mx1.freebsd.org: domain of tech-lists@zyxst.net designates 64.147.123.19 as permitted sender) smtp.mailfrom=tech-lists@zyxst.net X-Spamd-Result: default: False [-8.21 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[zyxst.net:s=fm1,messagingengine.com:s=fm1]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.19]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; DMARC_NA(0.00)[zyxst.net]; DKIM_TRACE(0.00)[zyxst.net:+,messagingengine.com:+]; SIGNED_PGP(-2.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[19.123.147.64.list.dnswl.org : 127.0.5.1]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:11403, ipnet:64.147.123.0/24, country:US]; RCVD_TLS_LAST(0.00)[]; IP_SCORE(-3.51)[ip: (-9.89), ipnet: 64.147.123.0/24(-4.91), asn: 11403(-2.68), country: US(-0.05)] 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: Wed, 27 Nov 2019 15:53:07 -0000 --p2kqVDKq5asng8Dg Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Wed, Nov 27, 2019 at 01:15:42PM +0100, Polytropon wrote: >On Wed, 27 Nov 2019 03:37:39 +0000, tech-lists wrote: >> Hi, >> >> Got a new ssd so tried latest snapshot install to it. I wanted seperate = /usr >> /var and / partitions, also to enable trim, also two 16GB swap partition= s, >> so selected manual UFS, completed the install, reboot, cannot find kerne= l. > >Did you do this using the bsdinstall program, or manually >via shell? I don't know specifically if it was the bsdinstall program. I guess it was.= It was whatever is invoked after booting the install disk/image and then selecting "Install". >> Repeated the install the same way again with same result. Rebooted, ran >> the installer for a third time, selected auto ufs and everything worked >> as expected on reboot, but of course without the modifications I wanted. >> >> Is this a known issue? > >Even though bsdinstall isn't that bad, I personally prefer >to prepare the disk via shell commands manually before I >return to bsdinstall, add the created partitions, and have >the installer do it's work, in case I needed something that >is "non-standard" (as you've described). This is because of >my impression (I wouldn't call it an issue though) that the >bsdinstall program doesn't understand when you leave its >predefined path... ;-) I'd say if it's not working as suggested or implied then it's broken, or why have the manual option at all? I don't expect the consequence of selecting this option to be "doesn't install a kernel" or "everything is installed, i= t's just not bootable" without notification. I've not encountered the issue before because my installation context is mostly bhyve-based so I just accept the defaults. Because this is bare meta= l, I was hoping to optimise the SSD somewhat. >> Also, MBR is selected by default. SHould I be using GPT instead, nowaday= s? >Probably yes. Use GPT. Use MBR only if you have a good reason >to do so (inter-OS things might be such a case). There should be a reason why this is selected as default. "Most x86 systems" isn't enough. I'd fix this if I knew how. What is the GPT advantage? thanks for the clarification --=20 J. --p2kqVDKq5asng8Dg Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAl3em8sACgkQs8o7QhFz NAX3Yg/+MHqY4sEQi03v+5NMS+D/Dt4gQr25i88ge/17k/p5uqUCNjTO2tIcwGM4 pc1/7VN03T8cU4RMO7cL92kIwWxkNwZY/SyFUmQlgQGuoiUJCoveUW5dnwuupzAv R/G/R3erAsGHjTPI+B3dFrIfFuBh+nKeyzeq/aU9jtEw/t+Wd7M03Jm1UmPQXcli 6zCf72WIqZ4l282nTbjXJIoCfVHZb9iQQSQ0plr8UlWKnAi7e7iIiZXteYwknNX3 XGPlmZHmfcnp08rlILSUlHtFGY3+yMhpcqfGxSm9GCZXyDZlCX5DUPJJ4Hu/RHsx UpYJWBx0myzcQMgieQetd9a4Qu0idt3gXPUY0uAxKcC6MhAJqCDSgHLtJNb4Q7QR StvfUuVp2AQxJ0yFJBE4PH1dqkeeAG2vTP6HSZTGhHml9IAt5AcTiV0sN8zhKgUg wBaCK1XRUUW6Oj6RiCMQFWixC9zaJEYuTdiOghobwqgnlhnLwbjIMwtXtwyP6VPv z6gn9okgk3SF37g4kqizs/ebva8l/t3NFhqu6ktAAOuQ+q295GKlc/GhACNm0+cT W1nBrTFzUIZSUwKZV9kOrVZU/LsviXBbsq0vR09FUyHdoq6+jWXsNByx0LIOyC4S DsattooMyIoT1+vIM8hex8lVTmL0XrYV+MgVVMv3nv1YzmKKQv0= =wngM -----END PGP SIGNATURE----- --p2kqVDKq5asng8Dg--