From nobody Fri Jul 08 19:15:52 2022 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 9C85417FFC6E for ; Fri, 8 Jul 2022 19:17:24 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Lfjhg6Ynjz3Pnl for ; Fri, 8 Jul 2022 19:17:23 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.16.1/8.16.1) with ESMTPS id 268JFqsm049529 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 8 Jul 2022 12:15:52 -0700 (PDT) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.16.1/8.16.1/Submit) id 268JFq1g049528; Fri, 8 Jul 2022 12:15:52 -0700 (PDT) (envelope-from warlock) Date: Fri, 8 Jul 2022 12:15:52 -0700 From: John Kennedy To: "Wall, Stephen" Cc: "freebsd-arm@freebsd.org" Subject: Re: Installing 13.1 ARM on SSD Message-ID: References: List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4Lfjhg6Ynjz3Pnl X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of warlock@phouka1.phouka.net has no SPF policy when checking 107.170.196.116) smtp.mailfrom=warlock@phouka1.phouka.net X-Spamd-Result: default: False [-1.80 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; FORGED_SENDER(0.30)[warlock@phouka.net,warlock@phouka1.phouka.net]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-arm]; RCPT_COUNT_TWO(0.00)[2]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_NA(0.00)[]; R_SPF_NA(0.00)[no SPF record]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; ASN(0.00)[asn:14061, ipnet:107.170.192.0/18, country:US]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_SOME(0.00)[]; DMARC_NA(0.00)[phouka.net]; RCVD_TLS_LAST(0.00)[]; FROM_NEQ_ENVFROM(0.00)[warlock@phouka.net,warlock@phouka1.phouka.net] X-ThisMailContainsUnwantedMimeParts: N On Fri, Jul 08, 2022 at 06:26:59PM +0000, Wall, Stephen wrote: > I tried something like this - I used rsync to replicate the SD card's (mounted) msdos partition onto the SSD's (also mounted) efi partition. That got past the firmware message, but then it stopped in the boot loader asking for a partition to boot from. 'zfs:zroot/ROOT/default' resulted in an unknown partition. > > At the moment, I'm running with the SSD imaged from the FreeBSD RPI .img file, and that is working, but it's UFS, not ZFS. I'll give your steps a try, and if I get nowhere, I might wind up creating a UFS partition for root and boot, and make the rest of the disk zfs with my desired filesystems. So, bsdinstall should have set that up (zroot/ROOT/default). From the UFS disk, I think (off the top of my head) you can just do a "zfs import zroot" and then you should be able to see it (and everything else) with a: "zfs list -tall -r zroot" If you picked something other than zroot for the pool name, you might need to do some more tweaking. In my case, my USB disk is only ~256G. I don't know if uboot has any BIOS limitations like old x86 did. I've never had to be too wary, but then I've never had BIOS-breaking SSDs laying around to attach to RPI. I think uboot has some commands that might let you do some zfs exploration, but hate to point you at web resources because there seems to be a huge variations in what we end up with on FreeBSD/RPI. My RPI is a few hours into a firefox rebuild so I can't give you some real guidance from what I'm using at the moment.