Re: setting currdev correctly after repartitioning

On Sat, Jun 22, 2024 at 10:13:14AM -0600, Warner Losh wrote:
>
>Because something is confusing things. You posted an error message with p2
>GPT partition name. You then posted a show part with MBR label. That's the
>confusing info we need to get to the bottom of. Is this a big in
>loader.efi? 

> Are there other storage devices confusing things? 

No other storage device is connected on the rpi4. There are 5 usually on the desktop
the ssd when it's plugged in makes it the 6th hence da5

> Is there some
>way it isnt da5, but some other disk? 

No it's da5 on my desktop and da0 on the rpi4

from desktop:

usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage device Micron CT1000X9SSD9 (0x0634:0x5605)
usb_msc_auto_quirk: UQ_MSC_NO_PREVENT_ALLOW set for USB mass storage device Micron CT1000X9SSD9 (0x0634:0x5605)
ugen0.10: <Micron CT1000X9SSD9> at usbus0
umass2 on uhub2
umass2: <Micron CT1000X9SSD9, class 0/0, rev 3.20/1.10, addr 12> on usbus0
umass2:  SCSI over Bulk-Only; quirks = 0x8100
umass2:7:2: Attached to scbus7
da5 at umass-sim2 bus 2 scbus7 target 0 lun 0
da5: <Micron CT1000X9SSD9 PMAP> Fixed Direct Access SPC-4 SCSI device
da5: Serial Number 2334E8D02C6E
da5: 400.000MB/s transfers
da5: 953869MB (1953525168 512 byte sectors)
da5: quirks=0x2<NO_6_BYTE>

>We need to get to the bottom of
>this...

Some more context:

The installation was initially created by dd-ing a -current rpi4
snapshot to this ssd. the partitioning is as set on the image, in other
words, MBR.

I have no clue why a p2 partition name is being referenced, and have made no
modifications to the loader.

>What does lsdev say at the OK prompt after it can't find loader.conf?

Type '?' for a list of commands, 'help' for more detailed help.
OK lsdev
unknown command
OK 

I can post the entire console output from u-boot onwards if you wish.

--