DFBSD on 2nd drive fails to boot, FreeBSD succeeds same partition

[Chris Pressey]

On Wed, 28 Jul 2004 08:15:45 -0400
Pete Renshaw <colpete at xxxxxxxxxx> wrote:

> Matthew Dillon wrote:
> 
> >     The boot CD ought to be able to 'see' the second disk.   What
> >     is it not seeing?  The whole second drive is missing or is 
> >     it something like fdisk (from the cd) not being able to read
> >     the dos slice table on the second hd?
> > 
> > 					-Matt
> > 					Matthew Dillon 
> > 					<dillon at xxxxxxxxxxxxx>
> I tried installing again and noticed that it saw the fat32 as 
> "???unknown???".  After rebooting and not being able to boot I used
> the CD to try to see things.
> 
> Execution of the command
> mount /dev/ad1s2a /mnt
> FAILED with a return code of 1
> 
> (view log)
> 
> Error log  (this is the second hard drive portion of it)
> ,->>>Executing '[internal] discover_slices()'
> | Found slice #1, sysid 28, start 110446938, size 209712447
> | Found slice #2, sysid 165, start 63, size 52436097
> `->>> Exit status: 0
> 
> ,-<<< Executing 'rm -f /tmp/temp.fdisk'
> `->>> Exit status: 0
> 
> ,-<<< Executing '[internal] maybe_makedev()'
> | Seeing if ad1s2 needs to be created...
> | No, ad1s2 already exists
> `->>> Exit status: 0
> 
> ,-<<< Executing 'mount /dev/ad1s2a /mnt'
> | mount: /dev/ad1s2a : No such file or directory
> `->> Exit status: 1

Does it help if you manually "cd /dev && ./MAKEDEV ad1s2a" before using
the installer?  From this it looks like it somehow skipped making that
device node... I thought we caught all these cases, all but maybe not.

> If you need the whole error log including the first drive let me know.
> 
> Pete

If you could send me a copy directly, that'd be great.

-Chris