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

[Chris Pressey]

On Wed, 28 Jul 2004 21:05:47 -0400
Pete Renshaw <colpete at xxxxxxxxxx> wrote:

> Chris Pressey wrote:
> 
> > On Wed, 28 Jul 2004 14:21:18 -0700 (PDT)
> > Matthew Dillon <dillon at xxxxxxxxxxxxxxxxxxxx> wrote:
> > 
> >> :> | 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.
> >> 
> >>     It looks like the installer is testing ad1s2 and assuming that
> >>     ad1s2a exists if ad1s2 does, but in fact this is not
> >necessarily>     the case.  MAKEDEV by default will create ad1s2 but
> >not>     ad1s2{partition}.
> > 
> > It looks that way, but the part of the log shown is actually
> > generated from two independent parts of the installer.  The 'mount'
> > bit has no direct relation to the 'maybe_makedev' bit.
> > 
> > Pete, I need to know exactly what you were trying to do when you got
> > the message
> > 
> > Execution of the command
> > mount /dev/ad1s2a /mnt
> > FAILED with a return code of 1
> > 
> > in order to figure this out (was it "Configure an Installed System"
> > by any chance?)
> > 
> > -Chris
> 
> "Configure an Installed System" is what I used then "view logs"  I'll
> have the full error report tomorrow morning.  The inspection of the
> first hard drive seemed OK.
>   
>  Pete

OK, I see it now.  Yup, it does indeed forget to make sure the device
for the / partition of the chosen slice exists before trying to mount
it.  The workaround for your situation is as I mentioned in the previous
email, before starting the installer: cd /dev && ./MAKEDEV ad1s2a

Either that or configure the installed system by hand.  Going back to
your greater problem, there's nothing in "Configure an Installed System"
that will help resolve boot issues.

It can't bee a boot0 problem if you're using Partition Commander as your
boot manager... possibly you're running into a problem we've had
occasional reports of: for some reason, the slice is just never marked
bootable (or gets unmarked somehow).  You can try to remedy this by
running "disklabel -B ad1s2" from the LiveCD.

Thanks for the report,
-Chris