From owner-freebsd-questions@freebsd.org Fri Dec 13 21:38:55 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 C09221D79AF for ; Fri, 13 Dec 2019 21:38:55 +0000 (UTC) (envelope-from freebsd-database@pp.dyndns.biz) Received: from keymaster.local (ns1.xn--wesstrm-f1a.se [IPv6:2a00:d880:5:1b9::8526]) (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 47ZPDt3Fx6z4Xtm for ; Fri, 13 Dec 2019 21:38:53 +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 xBDLcjBW001548 for ; Fri, 13 Dec 2019 22:38:46 +0100 (CET) (envelope-from freebsd-database@pp.dyndns.biz) Subject: Re: Root volume renumbered unexpectedly, no longer boots To: freebsd-questions@freebsd.org References: From: =?UTF-8?Q?Morgan_Wesstr=c3=b6m?= Message-ID: <28a92269-832b-61d0-3d25-68be2439dd9c@pp.dyndns.biz> Date: Fri, 13 Dec 2019 22:38:44 +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: 47ZPDt3Fx6z4Xtm 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 2a00:d880:5:1b9::8526) smtp.mailfrom=freebsd-database@pp.dyndns.biz X-Spamd-Result: default: False [2.96 / 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]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_SPAM_MEDIUM(0.13)[0.129,0]; RCVD_TLS_LAST(0.00)[]; NEURAL_SPAM_LONG(0.66)[0.661,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:2a00:d880::/32, 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: Fri, 13 Dec 2019 21:38:55 -0000 On 2019-12-13 21:57, Matthew Pounsett wrote: > After powering the system back up, it looks > like the boot volume has been renumbered from da0 to da4. > > There is a new wrinkle... since booting from a USB stick so that I could > get into the box and double-check some things, and confirm the location of > the root volume, the BIOS no longer seems to see da4 as a potential boot > volume. First thing I would check is the SATA controller mode in BIOS and make sure it didn't switch from AHCI to IDE/Legacy/RAID (or whatever you used to run it as). This assuming the SSD is connected to the mainboard controller of course. I'm not saying this is what happened but at least we could get that possibility out of the way. Regards Morgan