Guest: FreeBSD-CURRENT. Originally a 20 GB virtual hard disk, the UFS file system became full so I grew the disk (to 40 GB), the partition and the file system. Now the guest will no longer start.
Immediately after the VirtualBox prompt to select a boot device (I refrain from keying F12):
https://pastebin.com/tUMy7Kur
Any suggestions?
Host details:
Code: Select all
$ about
===================
General information
===================
boot environment now (N) … 12.0-CURRENT-up-20170330_080908 NR 2017-03-30
after restart (R) … 12.0-CURRENT-up-20170330_080908 NR 2017-03-30
boot loader …………………………………… BSD
type ……………………… EFI
CPU ………………………………………………………… Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz
number of cores ……………… 4
host ……………………………………………………… momh167-gjp4-hpelitebook850g2-trueos.university.brighton.ac.uk
memory ………………………………………………… 16384 MB available, 3102 MB free
OS git branch ……………………………………………………………………………………… drm-next
OS git revision ………………………………………………………………………………… a009033ff
OS kernel build time ………………………………………………………… Wed 2017 Mar 29 20:13:33 UTC
OS kernel identity …………………………………………… (uname -i) GENERIC
OS platform (architecture) ……………………… (uname -m) amd64
OS release level ………………………………………………… (uname -r) 12.0-CURRENT
OS version and patch level …… (freebsd-version) 12.0-CURRENT
TrueOS package set ………………… STABLE
TrueOS version …………………………… TrueOS-Desktop-201703201429
uptime ………………………………………………… 5:54
user …………………………………………………… grahamperrin
More (TrueOS Desktop):
desktop environment …… KDE
sound card driver ………… pcm1: <Realtek (0x0280) (Analog 2.0+HP/2.0)> on hdaa1 (1p:1v/1r:2v) default
wireless driver ……………… iwm0
X11 drivers ………………………… intel_drv.so
$
The case above should not be confused with recent FreeBSD bug 218698, which affects multiple guests.
In the case above, as far as I can tell, only a FreeBSD-CURRENT guest is affected. (My GhostBSD and Windows 7 guests run without difficulty, and so on.)