Date: Mon, 22 Jan 2024 14:48:00 +0000 From: void <void@f-m.fm> To: freebsd-current <freebsd-current@freebsd.org> Subject: Re: vmm_load crashes to debugger early Message-ID: <a792963b-6a51-4ef6-8467-93e9f4979671@app.fastmail.com> In-Reply-To: <992106378.5645.1705927690900@localhost> References: <264b801d-8fb6-46c1-a8f2-c9f2070e4ca0@app.fastmail.com> <992106378.5645.1705927690900@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
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 --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a792963b-6a51-4ef6-8467-93e9f4979671>