Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it

On Sat, Oct 01, 2022 at 11:08:05AM -0700, Mark Millard wrote:
> On 2022-Oct-1, at 09:33, bob prohaska <[email protected]> wrote:
> 
> 
> 
> I'll note that the:
> 
> da0: <SABRENT  0214> Fixed Direct Access SPC-4 SCSI device
> da0: Serial Number DD564198838F9
> 
> does not match other log files:
> 
> da0: <SABRENT  1214> Fixed Direct Access SPC-4 SCSI device
> da0: Serial Number 000000000000A
> 
> but it may well be an example of garbage-in/garbage-out.
>
 
If you're comparing past yesterday, probably not. I tried
a different enclosure (same make/model) on the chance the
first one was somehow damaged. There wasn't much difference
in behavior, if anything it was a bit less likely to boot.
For present purposes that seemed helpful so I kept it in place.

Apologies for not mentioning it, I didn't think anybody 
would notice..... and then forgot.

As an aside, the new u-boot.bin does seem much better
at provoking loops, all with error 22 or 110 prominent.
So far nothing obviously new. 

Thanks for your patience!

bob prohaska
 



> The same goes for the usual:
> 
> umass0:  SCSI over Bulk-Only; quirks = 0x8100
> 
> vs. the 3 odd examples:
> 
> umass0:  SCSI over Bulk-Only; quirks = 0xc105
> umass0:  SCSI over Bulk-Only; quirks = 0xc105
> umass0:  SCSI over Bulk-Only; quirks = 0x8101
> 
> 
> 
> You also got another "0 Storage Device(s) found". It again has
> the sequence for portstatus:
> 
> 311, 311, (sequence of 5 instanced of:) 301
> 
> for:
> 
> Manufacturer 
> Product      U-Boot Root Hub
> SerialNumber 
> bind node usb1@1
> 
> So, just like the others.
> 
> ===
> Mark Millard
> marklmi at yahoo.com
> 
> 
>