INTL 3:770/1 3:770/3
REPLYADDR tnp@invalid.invalid
REPLYTO 3:770/3.0 UUCP
MSGID: 9ffc0f52
REPLY: afb2709d
PID: SoupGate-Win32 v1.05
On 24/01/2025 09:37, Theo wrote:
> The Natural Philosopher wrote:
>> On 23/01/2025 22:12, Chris Green wrote:
>>> Is it simply a matter of leaving /boot on the SD card and changing /
>>> to being a USB drive or does one need to edit something in /boot
>>> somewhere?
>>
>> AFAICR what you do is simply edit a file and tell it that / is not where
>> it thinks it is
>>
>> But it depends on exactly what you want to happen
>>
>> The boot process is as follows (I think: Others will correct If I've got
>> it wrong)
>>
>> The Pi firmware looks on the SD card for a Vfat partition, and in there
>> is a file called cmdline.txt
>>
>> e.g.
>> console=serial0,115200 console=tty1 root=PARTUUID=778a9e44-02
>> rootfstype=ext4 fs
>> ck.repair=yes rootwait noswap=1
>>
>> That file tells the boot loader wher the root directory is to be found
>> that it is to grab the kernel off
>
> Not quite. If you do it this way, the kernel comes from the SD card and the
> cmdline is the *kernel* command line, ie it tells that kernel where to find
> its root FS once it has started. That means you need to ensure that the
> kernel on the SD card remains updated, because any kernel on USB storage
> will be ignored.
>
Oh yes, you are right there. If you only adjust that line, you will
still have the fstab on the USB drive mounting the SD boot partition in
/boot/firmware. So the kernel will get updated OK automagically.
It is however needlessly messy which is why I went all USB/SSD and
ditched the SDcard.
> If you did that way, you could set it up with just a FAT /boot partition on
> the SD and then your ext4 rootfs on USB, and adjust the cmdline and
> /etc/fstab to match. That way any updates would deploy the SD card /boot.
>
Yes. Exactly.
> However if you ever want to re-image your rootfs you have to remember that
> you also need to re-image your SD and set up this arrangement again.
> Otherwise you'd be booting old kernels from SD with your new USB rootfs.
>
> By using bootcode.bin only on SD (something I've not tried), you can use
> standard OS images on your USB without any changes.
> Or you could boot direct from USB on those Pis that support it with no SD.
>
Ultimately, that is IMHO the better approach. As long as the Pi can
recognise and boot from USB, leave the SD card out altogether.,
IIRC the most successful approach was in the end, for me, to simply
install raspios on the USB drive and forget the SD card altogether.
Later Pis are perfectly happy to try the SD card like an old PC trying a
floppy drive, to boot, but on failure simply look at the USB drives.
And the fact that the boot process uses PARTUUID rather then physical
devices means its agnostic between SDCARD and USBdrive.
The only change I made somewhere was to stop the Pi endlessly trying to
access the SDcard that was no longer there.
in /boot/firmware/config.txt
#since we are booting from SSD
# disable constant SD scan
# We wouldn't be here on an SD card boot
dtparam=sd_poll_once
I really do advise people not to try and split between SDcard and USB.
Just install the OS on the USB to start with.
It works with later pis automatically
--
"Anyone who believes that the laws of physics are mere social
conventions is invited to try transgressing those conventions from the
windows of my apartment. (I live on the twenty-first floor.) "
Alan Sokal
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
SEEN-BY: 4/0 19/10 88/0 90/0 105/81 106/201 128/187 129/305 153/757
SEEN-BY: 153/7715 154/110 218/700 840 220/70 221/1 6 360 226/17 30
SEEN-BY: 226/100 227/114 229/110 111 114 200 206 275 300 317 400 426
SEEN-BY: 229/428 470 550 616 664 700 705 266/512 267/800 291/111 292/854
SEEN-BY: 301/1 310/31 320/219 322/757 335/364 341/66 342/200 396/45
SEEN-BY: 460/58 633/280 712/848 770/1 3 100 330 340 772/210 220 230
SEEN-BY: 880/1 900/0 102 106 902/0 19 26 905/0 930/1 2320/105 5020/400
SEEN-BY: 5075/35
PATH: 770/3 1 218/840 221/6 341/66 902/26 229/426
|