When using the memorystick install option the disk configuration step assigned the boot disk as /dev/da1p2. Now, when I attempt to boot from the newly created install the boot process halts with a prompt for the boot disk. I must enter /dev/da0p2 then the boot process continues as expected. I believe the MRR needs to be modified to fix this. Will gladly accept any friendly advice on how to do this. Fix: The disk configuration software did not anticipate that the target disk was also a USB disk as was the memorystick install boot. The memorystick image was assigned /dev/da0 and the target USB disk assigned /dev/da1. When I remove the memorystick and reboot the new target disk becomes /dev/da0. The memorystick install went very nicely and could be about the most direct and simplest install I have performed. But, the install software has not been modified to address this scenario. It could be that this is the way it going to be and the MBR will need to be modified after a USB target disk is created this way. However, the install software should be intelligent enough to know that when a memorydisk install is being used that this device will be taking the /dev/da0 slot. I have some suggestions for a few improvements in the new FreeBSD install. To whom can I address these to?
Responsible Changed From-To: freebsd-amd64->freebsd-sysinstall reclassify.
For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped