L. V. Lammert wrote:
At 08:28 PM 5/5/2009 -0400, you wrote:
...
Usual error is to forget that "boot" specified on the installboot command
line is not the one in the installboot directory or your current root
partition, but rather the /boot that exists on the root partition of the
target drive (i.e., the "boot" you WILL use, not the one that you already
used).
Confirmed. Here is what worked: First problem, I missed the '/mnt' for
boot:
/usr/mdec/installboot -v /mnt/boot /usr/mdec/biosboot wd0
I used both sd0 and wd0 to make sure it would work, .. both indicated
'cross-device install'? Am I correct that the boot *device* specified
should be wd0, when the drive will be physically used as bootable?
no, all installboot does is install a tiny little program (biosboot)
in the PBR, and point it to the inode used by the file /boot. So, it
needs to know about which file "boot" will end up being "/boot"
It needs to know where to put it, it really doesn't care what driver
will hook to the device after boot. As the name implies, biosboot uses
the bios, not the kernel driver. Biosboot is finished with its job long
before the kernel is even loaded (is five seconds "long"? :).
See faq14 for more info on how this all works.
You want something like:
/usr/mdec/installboot -v /mnt/boot /usr/mdec/biosboot sd0
assuming sd0a is mounted on /mnt and is your new disk.
(alternately: just boot install media, point it at sd0, and it will do
the rest for you...)
Nick.
