installing FreeBSD on Virtual Box error: "Cannot dump. No dump device defined"
*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'd like to understand what this problem is, and what exactly causes it, as others have experienced it while installing on their main computer, not in a virtual box.
Any ideas on what caused it or what I should try to get it working?
The error is not "Cannot dump. No dump device defined." The error is a kernel panic before that. You're seeing that message because there is no disk location to store the memory from the panicked kernel. There isn't anything to fix with the dump device.
This is happening while trying to start init (which appears to not be found) but the panic does not seem to be related to not finding init. That would produce a "no init" message. I only mention this at all because it's rare to see it cycling through init locations like that. And that is probably a symptom of the real problem. There is something going on which causes a page fault. Exactly what it is, I couldn't tell you from what I know.
What version of FreeBSD is this?
Have you tried booting another version and seen if you still get the error?
I tried version 6.2 . I'll try downloading 5.5 and see if I get the same thing, but it might take a while with my slow connection. I'll post back after I try that.
i had the same problem on a katmai 450Mhz cpu with 128 sd ram. the problem was one of the DIMMs. i switched the memory module to the other one and all went well.
Thanks for the suggestion, but I don't think I can do that in a virtual machine... But it's good to know if something goes wrong when I install it in my main box...
I also tried NetBSD (3.1 I think...). It worked on my main box a few months ago... With a normal boot it freezes after displaying "warning: no /dev/console". I tried boot -v and after a few dozen segmentation faults, saying something about no free space (on the cd-rom?) it launched an install menu! Now I didn't finish with the install, as I already tried it, and wanted something new, but it's behaviour in a virtual machine seems quite weird...
Don't know if this info might help in any way to find a solution, but... If you have any other ideas or suggestions, I would be greatfull.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.