Re: Filesystem errors on armv7 -current

On Oct 21, 2026, at 9:43 PM, Warner Losh <imp@bsdimp.com> 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:
> 
> 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.

One can buy a cheap inline USB power meter or tester to see
what sort of voltage/current is in use. Fancier ones such as
FNIRSI FNB48P that will let you see a realtime graph of
voltage/current at various sampling rates + you can upload
this data (+ there is vibe coded s/w to run on linux/mac for
this as well). Very useful for debugging this sort of
problems.