From owner-freebsd-questions@freebsd.org Sat Dec 14 10:05:06 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 DE07D1C865F for ; Sat, 14 Dec 2019 10:05:06 +0000 (UTC) (envelope-from freebsd-database@pp.dyndns.biz) Received: from keymaster.local (ns1.xn--wesstrm-f1a.se [81.4.102.176]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "keymaster.pp.dyndns.biz", Issuer "keymaster.pp.dyndns.biz" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 47Zjns22ybz4CxV for ; Sat, 14 Dec 2019 10:05:04 +0000 (UTC) (envelope-from freebsd-database@pp.dyndns.biz) Received: from [192.168.69.69] ([192.168.69.69]) by keymaster.local (8.15.2/8.15.2) with ESMTP id xBEA3jxc004426 for ; Sat, 14 Dec 2019 11:03:45 +0100 (CET) (envelope-from freebsd-database@pp.dyndns.biz) Subject: Re: Root volume renumbered unexpectedly, no longer boots To: freebsd-questions@freebsd.org References: <28a92269-832b-61d0-3d25-68be2439dd9c@pp.dyndns.biz> From: =?UTF-8?Q?Morgan_Wesstr=c3=b6m?= Message-ID: <7a20b370-6dac-3caf-3f45-fe485c56b372@pp.dyndns.biz> Date: Sat, 14 Dec 2019 11:03:45 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47Zjns22ybz4CxV X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd-database@pp.dyndns.biz has no SPF policy when checking 81.4.102.176) smtp.mailfrom=freebsd-database@pp.dyndns.biz X-Spamd-Result: default: False [3.06 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; IP_SCORE(-0.03)[asn: 198203(-0.17), country: NL(0.02)]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; TO_DN_NONE(0.00)[]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_SPAM_MEDIUM(0.18)[0.179,0]; RCVD_TLS_LAST(0.00)[]; NEURAL_SPAM_LONG(0.71)[0.712,0]; HFILTER_HELO_IP_A(1.00)[keymaster.local]; R_SPF_NA(0.00)[]; HFILTER_HELO_NORES_A_OR_MX(0.30)[keymaster.local]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:198203, ipnet:81.4.100.0/22, country:NL]; MID_RHS_MATCH_FROM(0.00)[]; DMARC_NA(0.00)[pp.dyndns.biz]; RCVD_COUNT_TWO(0.00)[2] 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: Sat, 14 Dec 2019 10:05:06 -0000 > 48 disks, actually. :) Half of those are on an external JBOD connected > via an LSI FC controller. This server is significantly older than my > association with it, so I'm uncertain about how the internal 24 drives are > connected. If it helps, dmesg only reports ses0 and ses1 drivers. The > boot disk and the first 24 ZFS drives are all on ses0. I think that > implies only two controllers in use, not three. > Yeah, I see now that your mainboard has a SAS controller in addition to the Intel ICH10 controller. That BIOS setting I suggested would only affect disks attached to the Intel controller. The SAS controller should have it's own option BIOS settings, available through some key combo during boot. I have no experience with these controllers though so I couldn't tell if something in their settings suddenly made them report disks in a different order. Hopefully someone who knows how they work will read this and help you. /Morgan