Re: Filesystem errors on armv7 -current

On Wed, Oct 21, 2026 at 10:43:23PM -0600, Warner Losh wrote:
> On Wed, Oct 21, 2026 at 9:18 PM Mark Millard <marklmi@yahoo.com> wrote:
> 
> > On 10/21/26 19:00, bob prohaska wrote:
> > > On Wed, Oct 21, 2026 at 01:21:02PM -0700, Rodney W. Grimes wrote:
> > >>> On Mon, Oct 19, 2026 at 06:43:59PM -0700, bob prohaska wrote:
> > >>> +error
> > >>> find: /usr/src/sys/contrib/device-tree/Bindings/reset: Input/output
> > error
> > >>> find:
> > >>>
> > +/usr/src/sys/contrib/libsodium/src/libsodium/crypto_stream/salsa20/xmm6int:
> > >>> +Input/output error
> > >>
> > >> There should be some clues in /var/log/messages about what these I/O
> > errors are.
> > >
> > > I've tried looking for substrings seen above in /var/log/messages and
> > found no
> > > obviously-related matches. Are there some other keywords related to disk
> > > problems that might turn up?
> > >
> > > Thanks for writing,
> > >
> > > bob prohaska
> > >
> > >
> > >
> >
> > There are a variety of specific types of messages, so do not take the
> > following  examples as what to expect in detail for USB. They are just
> > examples I have around:
> >
> > (da1:umass-sim1:1:0:0): WRITE(10). CDB: 2a 00 65 cf fa 80 00 00 40 00
> > (da1:umass-sim1:1:0:0): CAM status: CCB request completed with an error
> > (da1:umass-sim1:1:0:0): Retrying command, 3 more tries remain
> >
> > (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 7f 95 f4 80 00 02 00 00
> > (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
> > (da0:umass-sim0:0:0:0): Retrying command, 3 more tries remain
> >
> > (probe0:umass-sim2:2:0:0): INQUIRY. CDB: 12 00 00 00 24 00
> > (probe0:umass-sim2:2:0:0): CAM status: CCB request completed with an error
> > (probe0:umass-sim2:2:0:0): Retrying command, 3 more tries remain
> >
> > (probe0:umass-sim2:2:0:0): INQUIRY. CDB: 12 00 00 00 24 00
> > (probe0:umass-sim2:2:0:0): CAM status: CCB request completed with an error
> > (probe0:umass-sim2:2:0:0): Error 5, Retries exhausted
> >
> 
> So this means that umass can't communicate with the enclosure. Maybe it's
> a power issue and it's browning out.
> 
> Some types of command failures might not get retries. Note how
> > ":umass-sim" is common to the examples but not a typical string for most
> > other contexts.
> >
> > There may be other types of messages not analogous to any part of the
> > above messages.
> >
> 
> Are there any errors with ASC/ASCQ values?  Those are from the disk itself.

Seemingly not:
# grep ASC /var/log/messages
# grep ASQ /var/log/messages
# 

If this isn't the correct test string please indicate.

Thanks for writing,

bob prohaska