From nobody Sat Dec 13 22:24:39 2025 X-Original-To: questions@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 4dTLVC1gHDz6KBfm for ; Sat, 13 Dec 2025 22:24:51 +0000 (UTC) (envelope-from bc979@lafn.org) Received: from mail.sermon-archive.info (sermon-archive.info [47.181.130.121]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4dTLVC0tpNz49wH for ; Sat, 13 Dec 2025 22:24:51 +0000 (UTC) (envelope-from bc979@lafn.org) Authentication-Results: mx1.freebsd.org; none Received: from smtpclient.apple (mini [10.0.1.251]) by mail.sermon-archive.info (Postfix) with ESMTPSA id 4dTLV96X9rz1tDrD; Sat, 13 Dec 2025 14:24:49 -0800 (PST) Content-Type: text/plain; charset=utf-8 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.200.81.1.6\)) Subject: Re: Disk Structures From: Doug Hardie In-Reply-To: <93A62DBA-EACB-4C9D-81D7-1BC2C30CA7C5@kd2ycu.com> Date: Sat, 13 Dec 2025 14:24:39 -0800 Cc: Doug Hardie , questions@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <6313E2A5-DF59-442A-84E0-102652AA5C80@sermon-archive.info> References: <7FA6EBCD-71E8-41D8-8C31-6DCB289CBEC1@sermon-archive.info> <93A62DBA-EACB-4C9D-81D7-1BC2C30CA7C5@kd2ycu.com> To: Daniel Anderson X-Mailer: Apple Mail (2.3864.200.81.1.6) X-Virus-Scanned: clamav-milter 1.5.1 at mail X-Virus-Status: Clean X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:5650, ipnet:47.181.128.0/18, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4dTLVC0tpNz49wH The original installation was from = FreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img and I have been trying = FreeBSD-15.0-RELEASE-arm64-aarch64-RPI.img -- Doug > On Dec 13, 2025, at 14:09, Daniel Anderson = wrote: >=20 > Are you using the official Raspberry Pi images or imager? I believe = there=E2=80=99s a few specific requirements for the partitions... >=20 >> On Dec 13, 2025, at 4:54=E2=80=AFPM, Doug Hardie = wrote: >>=20 >> I have a couple of Raspberry Pi 5s. One of which is a production = server for mail. It works just fine. However, the disk structure is = quite confusing. I only noticed this because of trying to bring up = another similar server. =20 >>=20 >> If I list the dev entries for mmcsd, I get the following. >>=20 >> mail# ll /dev/mmcs* >> crw-r----- 1 root operator 0x49 Nov 26 15:47 /dev/mmcsd0 >> crw-r----- 1 root operator 0x4a Nov 26 15:47 /dev/mmcsd0s1 >> crw-r----- 1 root operator 0x4b Nov 26 15:47 /dev/mmcsd0s2 >> crw-r----- 1 root operator 0x4e Nov 26 15:47 /dev/mmcsd0s2a >> crw-r----- 1 root operator 0x4f Nov 26 15:47 /dev/mmcsd0s2b >>=20 >> This looks like the drive was partitioned using GPT. However, gpart = list shows MBR. I removed the non-relevant entries: >>=20 >> mail# gpart list mmcsd0 >> Geom name: mmcsd0 >> entries: 4 >> scheme: MBR >> Providers: >> 1. Name: mmcsd0s1 >> Mediasize: 52428800 (50M) >> type: fat32lba >> 2. Name: mmcsd0s2 >> Mediasize: 128124452864 (119G) >> type: freebsd >>=20 >> There are the two partitions I expected. A boot partition, and a = data partition. Looking at the df output: >>=20 >> mail# df -h >> Filesystem Size Used Avail Capacity Mounted on >> /dev/ufs/rootfs 108G 9.1G 90G 9% / >> devfs 1.0K 0B 1.0K 0% /dev >> /dev/msdosfs/EFI 50M 25M 25M 50% /boot/efi >> tmpfs 12G 85M 12G 1% /tmp >> /dev/da0s2 25G 1.3G 22G 6% /mailbkup >> mail#=20 >>=20 >> The entries for / and /boot/efi are not at all what I expected. The = /mailbkup seems normal. How do I make sense of all this? >>=20 >> I duplicated the microSD card but it doesn't boot the new machine. I = believe that is caused by a hardware failure in the Pi. It does some = strange rebooting before ever reading the SD card. Never the less, I = should be able to mount the copied SD card on a working machine, but = can't figure out how to do that. Messages shows the new disk is da1. >>=20 >> mail# mount /dev/da1s2 /mnt >> mount: /dev/da1s2: No such file or directory >> mail# mount /dev/mmcsd1s2b /mnt >> mount: /dev/mmcsd1s2b: No such file or directory >>=20 >> I would like to verify that the new SD card is good. >>=20 >>=20 >> -- Doug >>=20 >>=20 >=20