Re: Raspberry Pi 4 and M.2 SATA SSD recognized but not booting or available for install - unsupported interface

On Apr 11, 2024, at 10:13, Johan Helsingius <julf@Julf.com> wrote:

> Thank you for the helpful information, Mark!
> 
> On 11/04/2024 18:23, Mark Millard wrote:
> 
>> As far as I know, bsdinstall does nothing for U-Boot materials for
>> any system that requires such. That is always additional activity.
> 
> Good to know - thanks!
> 
>> I'll note that it seems likely that most folks do not use bsdinstall
>> at all, instead starting with a snapshot or release image. (I'm not
>> claiming that you should do so: I do not know your context.)
> 
> I started out with an image, but could not get it to boot.

Which image(s)?

Only the likes of, say,

FreeBSD-14.0-STABLE-arm64-aarch64-RPI-20240404-72c3d91294c4-267114.img.xz
and:
FreeBSD-15.0-CURRENT-arm64-aarch64-RPI-20240404-112783ebbc31-269103.img.xz
and:
FreeBSD-14.0-RELEASE-arm64-aarch64-RPI.img.xz

are set up with the extra materials that I referenced for the RPi*'s. Note:
Those are UFS based, not ZFS based.

Note:

*-arm64-aarch64-*memstick.img*
*-arm64-aarch64-*disc1.iso*
*-arm64-aarch64-*boot*.iso*

are set up as bsdinstall sets things up: no RPi* or U-Boot materials present.

>> Output from the likes of:
>> # gpart show
>> # gpart show -pl
> 
> mmcsd0 is the SD card, da0 USB stick (that I am currently running from)
> and da1 is the SSD I would like to run from.
> 
> # gpart show
> =>       63  124735425  mmcsd0  MBR  (59G)
>         63       8129          - free -  (4.0M)
>       8192    1048576       1  fat32lba  (512M)
>    1056768  123678720       2  linux-data  (59G)
> 
> =>      63  31301568  da0  MBR  (15G)
>        63      1985       - free -  (993K)
>      2048    102400    1  fat32lba  [active]  (50M)
>    104448  10381312    2  freebsd  (5.0G)
>  10485760  20815871       - free -  (9.9G)
> 
> =>       0  10381312  da0s2  BSD  (5.0G)
>         0       128         - free -  (64K)
>       128  10381184      1  freebsd-ufs  (4.9G)
> 
> =>       40  937703008  da1  GPT  (447G)
>         40     532480    1  efi  (260M)
>     532520       2008       - free -  (1.0M)
>     534528    4194304    2  freebsd-swap  (2.0G)
>    4728832  932972544    3  freebsd-zfs  (445G)
>  937701376       1672       - free -  (836K)
> 
> #  gpart show -pl
> =>       63  124735425    mmcsd0  MBR  (59G)
>         63       8129            - free -  (4.0M)
>       8192    1048576  mmcsd0s1  (null)  (512M)
>    1056768  123678720  mmcsd0s2  (null)  (59G)
> 
> =>      63  31301568    da0  MBR  (15G)
>        63      1985         - free -  (993K)
>      2048    102400  da0s1  (null)  [active]  (50M)
>    104448  10381312  da0s2  (null)  (5.0G)
>  10485760  20815871         - free -  (9.9G)
> 
> =>       0  10381312   da0s2  BSD  (5.0G)
>         0       128          - free -  (64K)
>       128  10381184  da0s2a  (null)  (4.9G)
> 
> =>       40  937703008    da1  GPT  (447G)
>         40     532480  da1p1  efiboot0  (260M)
>     532520       2008         - free -  (1.0M)
>     534528    4194304  da1p2  swap0  (2.0G)
>    4728832  932972544  da1p3  zfs0  (445G)
>  937701376       1672         - free -  (836K)

There is no pre-supplied ZFS based image available from
FreeBSD.

What did you put in da1p1 (efiboot0) ? That area you have
to deal with for bsdinstall usage. Some folks extract and
copy over what is in the msdosfs in a:

*-arm64-aarch64-RPI-*.img.xz

as a means of getting an officially-built set of such
materials when they want to customize other aspects.

===
Mark Millard
marklmi at yahoo.com