Re: Filesystem errors on armv7 -current

On Wed, Oct 21, 2026 at 08:18:05PM -0700, Mark Millard 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
> 
> 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.

I see: 
# grep umass /var/log/messages
Oct 13 14:46:39 pelorus kernel: umass0 on uhub2
Oct 13 14:46:39 pelorus kernel: umass0: <JMicron External USB 3.0, class 0/0, rev 2.10/2.04, addr 6> on usbus0
Oct 13 14:46:39 pelorus kernel: umass0:  SCSI over Bulk-Only; quirks = 0x0
Oct 13 14:46:39 pelorus kernel: umass0:0:0: Attached to scbus0
Oct 13 14:46:39 pelorus kernel: da0 at umass-sim0 bus 0 scbus0 target 0 lun 0
Oct 17 00:08:48 pelorus kernel: umass0 on uhub2
Oct 17 00:08:48 pelorus kernel: umass0: <JMicron External USB 3.0, class 0/0, rev 2.10/2.04, addr 6> on usbus0
Oct 17 00:08:48 pelorus kernel: umass0:  SCSI over Bulk-Only; quirks = 0x0
Oct 17 00:08:48 pelorus kernel: umass0:0:0: Attached to scbus0
Oct 17 00:08:48 pelorus kernel: da0 at umass-sim0 bus 0 scbus0 target 0 lun 0

To my eye those seem to be boot messages, not errors encounterd while
running.

I have seen references to umass on other machines that do look like
running errors but they seem to clear on retry.

Pelorus is still doing a catch-up buildworld, once it finishes I'll
try to get smartmontools installed.


Thanks for writing!

bob prohaska