On Tue, Mar 10, 2009 at 5:40 PM, Alan DeWitt <[email protected]> wrote: > I'm not sure this is strictly speaking a newbies question, but here we > go. I've got an old OpenBSD server that I wish to virtualize. (It'd > probably be easier to just rebuild it from scratch in a VM, but what's > the fun in that?) > > I nfs-mounted some space to my source system and - after puzzling a > bit over which disk slice to dd - I copied as such: > > dd if=/dev/wd0c of=/mnt/heron/hedgehog bs=512x1008 count=16383 > > I then fired up qemu using the disk image file on the VM host and the > darn thing actually booted to OpenBSD. Woo-hoo! > > However, the VM does not mount the disks after / properly. Which I > guess is not much of a surprise, as the image file produced by dd is > considerably smaller than I would have expected, at 8455200768 bytes > when my source machine has about 15G used. The VM fails to mount other > slices with automatic fsck failing due to bad superblocks and magic > numbers. > > I'm presuming at this point that I have an incomplete disk copy. > > Was wd0c not the correct thing to copy with dd? Did I do something > incorrectly in my dd command? Is there perhaps an 8GB filesize limit > somewhere I'm not aware of? (nfs host is Ubuntu 8.04.) Any ideas or > tips to point me in a useful direction?
Why did you do "bs=512x1008 count=16383"? By my calculations, that is precisely 7.87 1024-based gigabytes. wd0c is the entire drive, including the bootloader, so that is the correct one to rip, but you want the *entire* drive, so leave off the count= param. _______________________________________________ Openbsd-newbies mailing list [email protected] http://mailman.theapt.org/listinfo/openbsd-newbies
