Re: updating from r231158 to 234465: mounting from ufs:/dev/ad4s1a failed with error 19

On Saturday, April 28, 2012 1:20:22 pm Anton Shterenlikht wrote:
> On Fri, Apr 27, 2012 at 07:51:11AM -0400, John Baldwin wrote:
> > On Thursday, April 26, 2012 6:42:15 pm Anton Shterenlikht wrote:
> > > I was updating from r231158 to 234465
> > > (amd64 laptop Compaq 6715s),
> > > and I think I must've messed someting
> > > up in the kernel config. Now I get
> > > build error, panic of a loader error,
> > > depending on which kernel I build.
> > > 
> > > *********************************************************
> > > 
> > > If I build GENERIC, I get:
> > > 
> > > (transcribed by hand)
> > > 
> > > mountroot: waiting for device /dev/ad4s1a
> > > Mounting from ufs:/dev/ad4s1a failed with error 19.
> > > 
> > > mountroot> ?
> > > 
> > >  List of GEOM managed disk devices:
> > > 
> > >   cd0
> > > 
> > > mountroot>
> > 
> > Hmm, so GENERIC is not finding ad4.  Can you look in the dmesg
> > (using scroll-lock) to see if GENERIC finds your ATA controller
> > ok?
> 
> I see only one line:
> 
> ata0: <ATA channel> at channel 0 on atapci0
> 
> ata does not appear anywhere else.
> 
> > 
> > > The device is certainly correct in r231158:
> > > 
> > > BUZI> df
> > > Filesystem  512-blocks     Used    Avail Capacity  Mounted on
> > > /dev/ad4s1a  101554068 46474368 46955376    50%    /
> > > devfs                2        2        0   100%    /dev
> > > BUZI> 
> > > 
> > > *********************************************************
> > > 
> > > If I add
> > > 
> > >  device atadisk
> > > 
> > > to GENERIC, then I get this linking error:
> > 
> > Yes, you aren't supposed to use 'atadisk' with ATA_CAM.  See the UPDATING 
> > entry 20110424 for more details on that.
> > 
> > However, can you obtain a verbose dmesg from your old kernel?
> 
> Amazingly (for me) I can't!
> 
> Twice I got a panic. The third time,
> and thereafter, I get the same error as with GENERIC:
> 
>  Mounting from ufs:/dev/ad4s1a failed with error 19.
> 
> I also see:
> 
> ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0exb
> ata0: stat1=0x00 err=0x00 lsb=0x00 msb=0x00
> ata0: reset tp2 stat0=00 stat1=00 devices=0x10000

Hmmm, I don't know how to grok these lines, but does your disk work at all now 
with any kernel?  It may be that your disk has died (or a cable, etc.) and it
just happened to coincide with your upgrade?

-- 
John Baldwin