Re: mfii0 kudos to bouyer@ Was Re: dmesg | grep -c "not configured" = 240...

[Stephen Borrill <netbsd%precedence.co.uk@localhost>]

On Tue, 4 Dec 2018, Martin Husemann wrote:
> On Tue, Dec 04, 2018 at 07:17:59PM +0000, Mike Pumford wrote:
> > One thing that surprised me was that I was testing with the USB install
> > image but instead of landing in sysinst I ended up at a a login prompt which
> > was unexpected. Could this be because the USB disk that was my root device
> > ended up as sd23 and there is a hard coded sd0 somewhere in the install
> > code?
>
> No hardcoded sd0, but maybe the boot device matching did not properly work
> for this case (depends on geometry and stuff that the bootloader gets
> from bios USB emulation or something).

Interesting, I noticed exactly the same when booting a -current image to
test the original mfii changes. In my case, sd0 and sd1 are the HW RAID 
arrays and sd2 is the USB stick:

[     8.177453] sd2 at scsibus1 target 0 lun 0: <InnoDisk, USB Drive, 0225> disk removable
[     8.177453] sd2: 3958 MB, 522 cyl, 255 head, 63 sec, 512 bytes/sect x 8105984 sectors
[     8.287566] boot device: sd2
[     8.287566] root on sd2a dumps on sd2b

--
Stephen