Date: Fri, 27 Feb 2015 11:13:00 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 198071] emulators/virtualbox-ose-kmod: vboxdrv confusing geom Message-ID: <bug-198071-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198071 Bug ID: 198071 Summary: emulators/virtualbox-ose-kmod: vboxdrv confusing geom Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: vbox@FreeBSD.org Reporter: oklaspec@gmail.com Assignee: vbox@FreeBSD.org Flags: maintainer-feedback?(vbox@FreeBSD.org) Created attachment 153577 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=153577&action=edit failed dmesg dump Problem concerning only for boot time with the vboxdrv enabled. Load vboxdrv on loaded system by kldload have success and work fine. Two discs and hardware ride of them become not very accessible. Few available - mean that it in /dev are present but partitions is not visible by bsdlabel and did not see anything. Fdisk - sees bsd mark. Because of this, the OS does not boot. There was another single disk with FreeBSD installed, but not connected to any ride is visible fine. Here dmesg bring both for comparison. The Kernel is copy of generic release 9.3 plus built in ipfw and two routing tables in it. Preview two distinct lines dmesg, in working: GEOM_RAID: NVIDIA-1: Array NVIDIA-1 created. in a failed: GEOM_RAID: Promise: Array Promise created. Full dmesg from working and filed attached --- Comment #1 from Bugzilla Automation <bugzilla@FreeBSD.org> --- Auto-assigned to maintainer vbox@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-198071-13>