You're very close to the mark!
Addressing #1: That's very interesting! Is there a command I can run to confirm which config.txt I'm actually loading? To give you some context, I boot off an SD card (/boot/) but have root (/) on an SSD attached via a USB dongle. Here's some quick output to illustrate:
...
And it is at this exact moment that I believe you've shed enough light on this issue to illuminate my mistake.
Briefly, the above output is not what I was expecting to see! I was expecting to see /boot/ mounted from mmcblk0p1, not /dev/sda1. Checking blkid and /etc/fstab confirms it: I'm now virtually certain I'm booting off the SD card, but when root gets mounted, I'm somehow also mounting the /boot/ partition on /dev/sda1 over mmcblk0p1? I'll need to investigate further.
What's odd is that this whole "boot from the SD card, but then use an SSD-over-USB as root" configuration is one I've used for the better part of 7-8 years and this is the first time I've seen it not work! I have a series of 4 or 5 large one-liner commands that I execute as part of my standard post-install config steps, so I'll go back and review those. Perhaps I made a mistake there.
Thank you for the pointer in the right direction. I'll look into this today and post an update with the outcome. Hopefully we'll be able to close this thread and mark it as [SOLVED] for future folks who might land here from Google.
Addressing #1: That's very interesting! Is there a command I can run to confirm which config.txt I'm actually loading? To give you some context, I boot off an SD card (/boot/) but have root (/) on an SSD attached via a USB dongle. Here's some quick output to illustrate:
Code:
[root@test-rpi3bplus ~]$ lsblkNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTSsda 8:0 0 223.6G 0 disk ├─sda1 8:1 0 512M 0 part /boot/firmware└─sda2 8:2 0 223.1G 0 part /mmcblk0 179:0 0 29.8G 0 disk ├─mmcblk0p1 179:1 0 512M 0 part └─mmcblk0p2 179:2 0 29.3G 0 part And it is at this exact moment that I believe you've shed enough light on this issue to illuminate my mistake.
Briefly, the above output is not what I was expecting to see! I was expecting to see /boot/ mounted from mmcblk0p1, not /dev/sda1. Checking blkid and /etc/fstab confirms it: I'm now virtually certain I'm booting off the SD card, but when root gets mounted, I'm somehow also mounting the /boot/ partition on /dev/sda1 over mmcblk0p1? I'll need to investigate further.
Code:
[root@test-rpi3bplus ~]$ cat /etc/fstab proc /proc proc defaults 0 0PARTUUID=8a438930-01 /boot/firmware vfat defaults 0 2PARTUUID=8a438930-02 / ext4 defaults,noatime 0 1# a swapfile is not a swap partition, no line here# use dphys-swapfile swap[on|off] for that[root@test-rpi3bplus ~]$ blkid/dev/mmcblk0p1: LABEL_FATBOOT="bootfs" LABEL="bootfs" UUID="4EF5-6F55" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="aed7d8b6-01"/dev/mmcblk0p2: LABEL="rootfs" UUID="ce208fd3-38a8-424a-87a2-cd44114eb820" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="aed7d8b6-02"/dev/sda2: LABEL="rootfs" UUID="ce208fd3-38a8-424a-87a2-cd44114eb820" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="8a438930-02"/dev/sda1: LABEL_FATBOOT="bootfs" LABEL="bootfs" UUID="4EF5-6F55" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="8a438930-01"Thank you for the pointer in the right direction. I'll look into this today and post an update with the outcome. Hopefully we'll be able to close this thread and mark it as [SOLVED] for future folks who might land here from Google.
Statistics: Posted by davidtmyers — Wed Jan 15, 2025 5:39 pm