What "mucking about with partitions" is needed? You simply run raspi-config-usb (download/file.php?id=19959) and select "Expand Filesystem". No knowledge of partitions is needed.HawaiianPi wrote: ↑Wed Apr 04, 2018 5:06 pmHowever, there are problems associated with keeping /boot on the SD card as well. The script that automatically resizes the root partition will work on your USB boot device when booted directly, or using bootcode.bin only, but it will fail if /boot and / (root) are on different devices. And mucking about with partitions can be a daunting task for those not familiar with such things.
Your script is not standard. It requires downloading some script from some website over the Internet, and it requires trusting some entity that posts to a forum as "RonR".What "mucking about with partitions" is needed?
n67 wrote: ↑Wed Apr 04, 2018 8:25 pmYour script is not standard. It requires downloading some script from some website over the Internet, and it requires trusting some entity that posts to a forum as "RonR".
You can assume that when regulars talk about what can and can't be done, they mean using only standard, approved tools.
It's best that the /boot mount entry in /etc/fstab references /dev/mmcblk0p1. That's where booting is actually originating from and things like raspi-config need to make changes to /dev/mmcblk0p1. The boot partition of the USB device is not used. usb-boot is setting things up correctly.
RonR's assumption is that we all want to have more than one bootable USB drive attached to our systems, and starting the boot process from SD is required to ensure that the correct boot device is chosen, and you'll want the SD card mounted as /boot for kernel and firmware updates to be properly applied (in which case the boot partition on the USB drive is just wasted space and not needed).
No. The USB boot bit is set in the factory.
Simply edit /boot/cmdline.txt and change:
Code: Select all
# dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=PARTUUID=????????-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
I've been through countless kernel updates and have never experienced any problems.
The boot partition of the SD card is being updated whenever you update the flash drive because the boot partition of the SD card is mounted on /boot when the flash drive is running. The root partition of the SD card is not being used.