Date: Fri, 8 Sep 2017 11:06:05 -0400 From: john hood <cgull@glup.org> To: sthaug@nethelp.no Cc: freebsd-scsi@freebsd.org, jhb@freebsd.org, jkim@freebsd.org Subject: Re: GEOM probes fail on aac with EARLY_AP_STARTUP Message-ID: <0c73b27e-d4ac-4003-81df-b2d9a0a63a81@glup.org> In-Reply-To: <20170908.151504.74703639.sthaug@nethelp.no> References: <f2dceefe-8c2c-1bad-95ab-9dd138c8fcbe@glup.org> <20170908.151504.74703639.sthaug@nethelp.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/8/17 9:15 AM, sthaug@nethelp.no wrote:
> Is there any reason to believe this is limited to aac? I'm asking
> because your description is quite similar to boot problema I'm seeing
> with 11.1-STABLE on a server with mps (Avago) SCSI/SATA controller
> and SATA disks. I'm getting the dreaded "mounting from ... failed
> with error 19". 11.1-RELEASE seems to work okay but 11.1-STABLE does
> not.
Your issue isn't obviously directly related to mine. mps is a CAM driver
and aac is not (at least not for normal block volumes), which makes disk
probe/attach quite different. I also don't see an obvious driver flag
like the one in aac.
Do you see GEOM error messages like "Opened disk aacd0 -> 6"? When you
get a failed boot, if you type '?' at the mountroot prompt, do you see
the base device (ie "da0"), but not partitions/slices ("da0s1",
"da0p1")? If both of those are true, then your problem might be similar
to mine.
regards,
--jh
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0c73b27e-d4ac-4003-81df-b2d9a0a63a81>