jessiewonka wrote: ktb wrote:
Btw I also then ran "sudo raspi-config --expand-rootfs" to resize the partition, as my SD card is much larger than that image. Is this best practice?
That is usually a good idea.
It seems that raspi-config can resize the partition by ssh into the Pi, and then the final step takes places upon reboot?
Yes. You should reboot after using the raspi-config option to expand the root filesystem.
jessiewonka wrote:So is this approach getting around unmounting the drive by that last step reboot? Their warning, "Calling ioctl() to re-read partition table.
Re-reading the partition table failed.: Device or resource busy. The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8)." made me a little nervous.
I don't think I understand exactly what you are asking here. If you use raspi-config to expand the root filesystem, you should reboot regardless of whether you choose the "A1 Expand Filesystem" option from the interactive ncurses menu interface or call raspi-config directly from the command line with the "--expand-rootfs" option. I don't think you need to worry about that warning message.
Actually, I think recent versions of Raspbian come with init=/usr/lib/raspi-config/init_resize.sh
in the /boot/cmdline.txt file so that it's the first thing that happens when you install and boot up a fresh copy of Raspbian. It should then reboot automatically. The custom ARpiCADE images do not have that, so you need to do it manually.