From owner-freebsd-current@freebsd.org Thu Sep 19 16:57:12 2019 Return-Path: Delivered-To: freebsd-current@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 4EAF712895C for ; Thu, 19 Sep 2019 16:57:12 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm1-x341.google.com (mail-wm1-x341.google.com [IPv6:2a00:1450:4864:20::341]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Z3141RW2z40fN; Thu, 19 Sep 2019 16:57:11 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm1-x341.google.com with SMTP id b24so4770207wmj.5; Thu, 19 Sep 2019 09:57:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=HXTb6GmlOnOKZz1NXq/gjbIHOHFklQijxHl2IEHg2PY=; b=hXNDiO1kQtcke1nVp+vr++3R6m3CVmyxoWcAiMvyjBgumaeUzRQsQwsnSaE5qEW1jA pcmx9Jd0BflXAnKrkwTwpljSiPSuZeorLjPAR5XzNY8h480F0uGr4UOsx+lo1CKHUJmY g7qJw7Y/j4eJ0ZtC2Up8Z6TVQKhOUKCQzGhGfmzoUHlAQE9OmiZe5VsV6i/GPS5JAeLx 4DsxbJzGFnihQ4cCZrKI94HtCy6mJRcGjlAC4Rge3Sq8PwHLdiNlEL0CoZQFf0y0jtuN epWdxgN/m0ZmWiIbVpTIZjTBoDdDImDYYyEcQK6Q59eV8GXw88d1Aikjb/F1yIJagnmr FV2A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=HXTb6GmlOnOKZz1NXq/gjbIHOHFklQijxHl2IEHg2PY=; b=cKenIokoMfWS30GCcmyn3lesocrLAGSdyAypm9zzGhRIAOAN3rGKg9ZkC4YqZnQiKJ qkvuRTQkf2GtZl7P3455fQZ/AX6jkDmhyMH7Lpy4gVM0ubTiLgxaiOM9xit3pIQvkuqL YvMr7sJhIcnKFtL9RPrZm6U4S0Q2rhJ59qZqRSCsqlBwU+Y4f5DW5Uk1IzG+3IE+gOUE wVOGX72t5DHXuJ4BRNdOCgmbW69cvpkLj2zlWhZ3fcc174wRdV1pMr+EUyVpDUKnAjQE vXEIWhMn3FzblhMyVpS7LsM7XXqhOXMqZhL92uj2tke4dCUsYoICBqNKOEirfdn0rb8A Nq7g== X-Gm-Message-State: APjAAAVzbuoT0iQOuJJHJQgxPdYGuwSiPi//GTOhMqRo+eew7Kl0BlbA Gmhp5q0uSsBRUp+/ayiBJ0HUZtUo X-Google-Smtp-Source: APXvYqyL481r/N98RuZANBdqsoKor4IJ0yAQZMkP3Aa+haqvmnjthRruq87xop/s75THZglckAnyyA== X-Received: by 2002:a05:600c:2059:: with SMTP id p25mr3921915wmg.50.1568912230474; Thu, 19 Sep 2019 09:57:10 -0700 (PDT) Received: from ernst.home (p5B3BEE6F.dip0.t-ipconnect.de. [91.59.238.111]) by smtp.gmail.com with ESMTPSA id o9sm14971669wrh.46.2019.09.19.09.57.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 19 Sep 2019 09:57:09 -0700 (PDT) Date: Thu, 19 Sep 2019 18:57:06 +0200 From: Gary Jennejohn To: Michael Gmelin Cc: Kurt Jaeger , Toomas Soome , freebsd-current@freebsd.org Subject: Re: Lockdown adaX numbers to allow booting ? Message-ID: <20190919185706.41988cfc@ernst.home> In-Reply-To: <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org> References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> <20190919155713.GG2863@home.opsec.eu> <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 46Z3141RW2z40fN X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-6.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Sep 2019 16:57:12 -0000 On Thu, 19 Sep 2019 18:04:54 +0200 Michael Gmelin wrote: > > On 19. Sep 2019, at 17:57, Kurt Jaeger wrote: > > > > Hi! > > > >>> We have a system with 10 SATA disks. 2 disks are for the system, > >>> 8 disks drive a data pool 'bck', configured as raidz2, for backup purposes: > >>> > >>> bck 72.8T 38.7T 34.1T - - 1% 53% 1.00x ONLINE - > > > >>> The problem is that if all 10 disks are connected, the system > >>> looses track from where it should boot and fails to boot (serial boot log): > > > >> Why this order does change? One would expect disks 0 and 1 to be OS disks and the rest for data??? > > > > 0+1 are 2.5", and the initial setup was: > > - we installed system disks as zroot > > - shipped the box to the housing facility > > - booted and added the drives > > > > At that time we did not do additional tests about the disk/boot sequence > > etc. > > > >> Also the question is, what you mean with ???system looses track???? > > > > I interpret the hang during boot as 'it looses track'. So I guess > > it tries to read the kernel from the wrong drives. > > > >> disk4 becomes adaX? why it matters, are you using ufs on boot disks? > > > > No, zpool only. > > > > I've made a few more details available here: > > > > https://people.freebsd.org/~pi/host/dmesg.txt > > https://people.freebsd.org/~pi/host/devlist.txt > > https://people.freebsd.org/~pi/host/gpart.txt > > https://people.freebsd.org/~pi/host/pciconf.txt > > https://people.freebsd.org/~pi/host/zpool.txt > > What about gpart output of the pool drives? > > In general you would create zpools using gptids or gpt labels, > not the devices, so you___re independent of device numbering. > The boot loader should only be installed on drives that contain > the boot pool (maybe you have old boot loaders on data > drives?). > Maybe the cam(4) hint settings could help in your case. -- Gary Jennejohn