From nobody Mon Jan 22 14:48:00 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4TJY4T5sn1z583JC for ; Mon, 22 Jan 2024 14:48:25 +0000 (UTC) (envelope-from void@f-m.fm) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4TJY4S5tmRz4GRZ for ; Mon, 22 Jan 2024 14:48:24 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm3 header.b=wWY9vRlq; dkim=pass header.d=messagingengine.com header.s=fm3 header.b="I2/6ap3r"; dmarc=pass (policy=none) header.from=f-m.fm; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 64.147.123.21 as permitted sender) smtp.mailfrom=void@f-m.fm Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id CA91D3200A8F for ; Mon, 22 Jan 2024 09:48:22 -0500 (EST) Received: from imap46 ([10.202.2.96]) by compute6.internal (MEProxy); Mon, 22 Jan 2024 09:48:22 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm3; t=1705934902; x=1706021302; bh=vpIefVfijy lKfZd7byrQkTCE/VvkKQmIYtjyHcQzE9o=; b=wWY9vRlqTHtuHd1VnyFpjEv1YF qdvQxzP2RDEHErGOAFqSe7Hr4neV6E7otkFFfVRfJX9DO9vs3vBk0OiN8KMRIrgH +Mz1n+IBKM3OTaOqNQD+LqozlBeNwlM1p+1i4MbMXySc+EN8oUyxdFxhhdInbBYR zHksz5ZkbCcszMwoEpq5cvIbtMfbbbdWF8pV+SjsHbfmv4p4PgwKYpEznKGZxeTn Cn3Lu4illDe9AlhgCfQW/gj8oxPx8AVcXk7GWR9kxHPa03u5b5dBAfnu82FeHmsb GoGgVBuUSiQoKBjrzn1xxNJ8atCoWsBB7Dbf43Bd+PQ75uac55aH/NRjryhQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; t=1705934902; x=1706021302; bh=vpIefVfijylKfZd7byrQkTCE/Vvk KQmIYtjyHcQzE9o=; b=I2/6ap3rg2prMkuiJeineBirzzd7pfUih5UhU3LBD8kE T5EOxqY+oCo9g6+sYvbZqgVauaFv8300eHZvVRpOgjTZeR/NNlYPb/A+22faTVBR pGvg7t+4/r/RBulfQX0SNyk+QtbeAz1T3PMZ7900+dMhFFpApOzCzqarSpTNYFXC 6MOFy418Ix00nrrj+EQ5sRguxsZpQcEnVN6cYQcjZvPuJPPAdhR/z57s3UNR9K3g RpJsXMZqP4kK2pOrvIa8u0FhHGVrLA9bOcMv9yFEImpLBUIdcBgksg/GMeKKAozi Kg5899RyFxqx1nI96wqxuumstXUSxHXaqp7yjN/SIw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdekiedgieejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpehvohhiugcuoehvohhiugesfhdqmhdrfhhmqeenucggtffr rghtthgvrhhnpeehhfeutdegkefhjefhhfdvgeektddujeegvdeludeljeehudelvddvvd egieegieenucffohhmrghinhepuhhsvghrrdhfmhenucevlhhushhtvghrufhiiigvpedt necurfgrrhgrmhepmhgrihhlfhhrohhmpehvohhiugesfhdqmhdrfhhm X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 052892A20090; Mon, 22 Jan 2024 09:48:22 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.11.0-alpha0-119-ga8b98d1bd8-fm-20240108.001-ga8b98d1b List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Message-Id: In-Reply-To: <992106378.5645.1705927690900@localhost> References: <264b801d-8fb6-46c1-a8f2-c9f2070e4ca0@app.fastmail.com> <992106378.5645.1705927690900@localhost> Date: Mon, 22 Jan 2024 14:48:00 +0000 From: void To: freebsd-current Subject: Re: vmm_load crashes to debugger early Content-Type: text/plain X-Spamd-Bar: ----- X-Spamd-Result: default: False [-5.09 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.21]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm3,messagingengine.com:s=fm3]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.21:from]; XM_UA_NO_VERSION(0.01)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US]; FREEMAIL_FROM(0.00)[f-m.fm]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; TO_DN_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+] X-Rspamd-Queue-Id: 4TJY4S5tmRz4GRZ Hi, On Mon, 22 Jan 2024, at 12:48, Ronald Klop wrote: > Hi, > > Can you mount /boot on another system? not sure how as the system cannot find the pool called 'zroot'. There are two zpools on the server - zroot for HD and 'ssd' for the ssds. I can boot to -current usb stick and zpool import -f ssd. The problem arose when I found I couldn't start grub2-bhyve-booting VMs. This is after a powercut during a storm. The storm caused the UPS to fail. I think there may have been a surge because mains power went off and on rapidly. It tripped a 30A ring main which very rarely happens. So trying to boot the server - it came back up, but I found that grub2-bhyve caused a drop to db. rebooted and tried to kldload vmm with same result. Rebooted, built new world & kernel, another reboot, same vmm result. I thought "maybe the issue is with kldload" and other stuff in /boot/loader was working so put vmm_load="YES" in the loader and now it won't boot at all :( My own idiot fault... > Can you press a key to interrupt booting the kernel? I'm not sure what > the name of this stage of the booting is called and if it depends on > which bootloader you are using. It can get to the beastie menu. >> OK > set vmm_load=NO >> OK > unload vmm >> OK > boot This still causes the drop to debugger. The machine is a gen8 hp proliant. I can get to a virtual serial console via ssh into iLo (so get a scrollable term) but that returns "monitor in graphics mode or unsupported text mode" when it drops to db>. I got a screengrab on the html5 remote virtual console but there is no way to scroll up and if the console is expanded or maximised the font size scales with it. Screengrab is here: http://void.f-m.fm.user.fm/Screenshot_20240122_135539.png Plenty more of probably very useful information has scrolled off the top :( > You can use the command "lsmod" and "show" to see what modules are > already loaded and what variables are used while booting. "lsmod" showed empty results, "show" displayed the following useful information: http://void.f-m.fm.user.fm/Screenshot_20240122_142642.png I think I now have a plan, of sorts... 1. boot to memstick and zfs import the ssd zpool 2. zfs snapshot the volumes there to another machine 3. format the machine from scratch and restore the ssd zpool Thank you for your help --