Date: Sat, 13 Dec 2025 20:25:12 -0500 From: Daniel Anderson <development@kd2ycu.com> To: Doug Hardie <bc979@lafn.org> Cc: questions@freebsd.org Subject: Re: Disk Structures Message-ID: <7488FA7A-531E-4128-8E4F-67ECBDD03AC3@kd2ycu.com> In-Reply-To: <6313E2A5-DF59-442A-84E0-102652AA5C80@sermon-archive.info> References: <7FA6EBCD-71E8-41D8-8C31-6DCB289CBEC1@sermon-archive.info> <93A62DBA-EACB-4C9D-81D7-1BC2C30CA7C5@kd2ycu.com> <6313E2A5-DF59-442A-84E0-102652AA5C80@sermon-archive.info>
next in thread | previous in thread | raw e-mail | index | archive | help
Right but how are you getting it to the micro SD card? > On Dec 13, 2025, at 5:24 PM, Doug Hardie <bc979@lafn.org> wrote: > > 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 <development@kd2ycu.com> wrote: >> >> Are you using the official Raspberry Pi images or imager? I believe there’s a few specific requirements for the partitions... >> >>> On Dec 13, 2025, at 4:54 PM, Doug Hardie <bc979@lafn.org> wrote: >>> >>> 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. >>> >>> If I list the dev entries for mmcsd, I get the following. >>> >>> 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 >>> >>> This looks like the drive was partitioned using GPT. However, gpart list shows MBR. I removed the non-relevant entries: >>> >>> 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 >>> >>> There are the two partitions I expected. A boot partition, and a data partition. Looking at the df output: >>> >>> 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# >>> >>> 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? >>> >>> 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. >>> >>> 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 >>> >>> I would like to verify that the new SD card is good. >>> >>> >>> -- Doug >>> >>> >> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7488FA7A-531E-4128-8E4F-67ECBDD03AC3>