I installed FreeBSD 10 to VirtualBox 4.3.6 running on Windows Vista from FreeBSD-10.0-RELEASE-i386-bootonly.iso and it fails to boot from the disk after installation. I can't attach .webm video, so I just post two screens.
All nice and well but you're not giving us much to go by. Just a few error messages don't cut it. For example; are you actually using ZFS on this environment or not? And if so; how much memory have you reserved for this environment?techtonik said:I installed FreeBSD 10 to VirtualBox 4.3.6 running on Windows Vista from FreeBSD-10.0-RELEASE-i386-bootonly.iso and it fails to boot from the disk after installation. I can't attach .webm video, so I just post two screens.
ShelLuser said:For example; are you actually using ZFS on this environment or not? And if so; how much memory have you reserved for this environment?
ShelLuser said:Also important; when you boot using the cd (ISO) device again does it allow you to access your installed system?
ShelLuser said:Just today I've set up a FreeBSD 10 test environment myself using VirtualBox 4.2.16 running on Windows 7
SirDice said:More importantly, what kind of hardware did you configure Virtualbox with?
OS Type: FreeBSD
System Base Memory: 128 MB
Processor(s): 1
Execution Cap: 100%
Boot Order: Floppy, CD/DVD, Hard Disk
VT-x/AMD-V: Enabled
Nested Paging: Enabled
Display
Video Memory: 5 MB
3D Acceleration: Disabled
2D Video Acceleration: Disabled
Remote Desktop Server: Disabled
Storage Controller: IDE
IDE Primary Master:
FreeBSD-10.0.vdi (Normal, 2.00 GB)

Audio Host Driver: Windows DirectSound
Controller: ICH AC97
Network Adapter 1: Intel PRO/1000 MT Desktop (NAT)
Attach the ISO to the virtual machine again and use it to boot the system. Fire up the live cd mode. Then when you've booted check which harddisks the system detects. Try something like this:techtonik said:ShelLuser said:Also important; when you boot using the cd (ISO) device again does it allow you to access your installed system?
What should I do to test it?
# sysctl kern.disks
. Once you know the name of the disk, I suspect this to be named ada0 then you can check if it actually has any partitions on it using this command: # gpart show -l ada0
. If the name differs then you should obviously substitute the name I used with the correct one. # mount /dev/ada0p2 /mnt
. Then check if you can actually see something when using ls /mnt
. df -lh
, perhaps the cause of the problem is easier than we're thinking (2Gb should be enough but it's not exactly much to work with).Simple; I was too lazy to perform the upgrade. I was eager to spend time on FreeBSD so didn't want to bother with having to wait for some update to complete. I'll probably do that somewhere next week.techtonik said:ShelLuser said:Just today I've set up a FreeBSD 10 test environment myself using VirtualBox 4.2.16 running on Windows 7
Why didn't you use the latest 4.3.6?
# gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ada0
. This will tell the system to install the pmbr file to your hard disks master boot record. Next it installs the second part of the bootcode (gptboot) to the first partition; indicated by the -i parameter.ShelLuser said:Anyway, fortunately this is easily fixable. Start the system using the CD again; either start the live cd modus or simply boot into single user mode. Once the system has booted you should try using this command:# gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ada0
mergemaster -Ui
could recreate /etc, but without knowing what happened, it's questionable whether that would be a good step.