Hibbian
/
Raspi-image-spec
1
0
Fork 0
Code Issues 3 Pull Requests Packages Projects Releases Wiki Activity
Raspi-image-spec/rootfs/etc/initramfs-tools/hooks/rpi-resizerootfs

53 lines
1.1 KiB
Plaintext
Raw Normal View History

rpi-resizerootfs: switch the root filesystem resizing away from a systemd oneshot service Switch away from using a systemd service for the initial root resize. Instead, we resize the root partition and filesystem in the initrd. To simplify things, the initrd script will check whether it should resize the partition on every boot. It does this by checking if the entire disk (ignoring an empty 4MB) is in use. However, the scripts themselves are deleted from the system after the initrd is generated. After the image is installed, the resize script should exist only in the initrd. When the kernel gets upgraded (eg, for a security update) or a new initrd is generated due to a package install, the new initrd will not contain the resize script. At that point, nothing will remain from the image's initial resize bootstrapping process. This process (but not the scripts) is similar to what cloud-initramfs-growroot does. However, that particular package has an indirect dependency on Python, and we don't necessarily want that overhead in our images just for resizing.
2021-04-30 18:23:21 +01:00
#!/bin/sh
set -e
#
# List the soft prerequisites here. This is a space separated list of
# names, of scripts that are in the same directory as this one, that
# must be run before this one can be.
#
PREREQS=""
case $1 in
prereqs) echo "$PREREQS"; exit 0;;
esac
. /usr/share/initramfs-tools/hook-functions
Document and complete rpi-resizerootfs hook The main trigger was a missing program in the initramfs, which probably everyone assumed was there ... but wasn't. (See next commit ...) So instead list every program that we need/call, so that we *know* that that program is included in the initramfs. Also document this new 'policy'. Also group the programs by the package which has them and sort the list alphabetically by the package names.
2022-11-06 19:17:27 +00:00
# List ALL the programs we need, because we explicitly call them
# Don't *assume* it will be included!
# The update-initramfs script will figure out any dependencies
# that also need to be included, so lets not do that
#
# Find the path as used by the package itself; usrmerge may not be used
# from coreutils
copy_exec /usr/bin/realpath
copy_exec /usr/bin/tail
copy_exec /usr/bin/test
Explicitly copy 'fsck*' into the initramfs While fsck.ext4 and fsck.vfat are part of the initramfs, it turns out that fsck itself isn't! While it normally gets included in the initramfs, for some reason that doesn't happen with our image creation, so it isn't available on first boot, so explicitly copy 'fsck' so that it will be included. For that to work, 'logsave' is needed too, so include that as well. During boot up, initramfs wants to check the filesystems and it does so via `fsck`, which then (presumably) checks the filesystem being used and calls the appropriate fsck.* to do the actual checking. But when `fsck` itself isn't available you get the following warning: "Warning: fsck not present, so skipping root file system" When it is available, you'll get a message like this: "Begin: Will now check root file system ... fsck from util-linux 2.38.1" Let's also follow our own advise and not *assume* the needed fsck programs are present in initramfs, but add them explicitly. Now we can start the resize operations while knowing the current filesystem is in a proper/clean state.
2022-11-06 22:06:05 +00:00
# from dosfstools
copy_exec /sbin/fsck.vfat
Document and complete rpi-resizerootfs hook The main trigger was a missing program in the initramfs, which probably everyone assumed was there ... but wasn't. (See next commit ...) So instead list every program that we need/call, so that we *know* that that program is included in the initramfs. Also document this new 'policy'. Also group the programs by the package which has them and sort the list alphabetically by the package names.
2022-11-06 19:17:27 +00:00
# from e2fsprogs
copy_exec /sbin/resize2fs
Explicitly copy 'fsck*' into the initramfs While fsck.ext4 and fsck.vfat are part of the initramfs, it turns out that fsck itself isn't! While it normally gets included in the initramfs, for some reason that doesn't happen with our image creation, so it isn't available on first boot, so explicitly copy 'fsck' so that it will be included. For that to work, 'logsave' is needed too, so include that as well. During boot up, initramfs wants to check the filesystems and it does so via `fsck`, which then (presumably) checks the filesystem being used and calls the appropriate fsck.* to do the actual checking. But when `fsck` itself isn't available you get the following warning: "Warning: fsck not present, so skipping root file system" When it is available, you'll get a message like this: "Begin: Will now check root file system ... fsck from util-linux 2.38.1" Let's also follow our own advise and not *assume* the needed fsck programs are present in initramfs, but add them explicitly. Now we can start the resize operations while knowing the current filesystem is in a proper/clean state.
2022-11-06 22:06:05 +00:00
copy_exec /sbin/fsck.ext4
Document and complete rpi-resizerootfs hook The main trigger was a missing program in the initramfs, which probably everyone assumed was there ... but wasn't. (See next commit ...) So instead list every program that we need/call, so that we *know* that that program is included in the initramfs. Also document this new 'policy'. Also group the programs by the package which has them and sort the list alphabetically by the package names.
2022-11-06 19:17:27 +00:00
# from grep
copy_exec /bin/grep
Explicitly copy 'fsck*' into the initramfs While fsck.ext4 and fsck.vfat are part of the initramfs, it turns out that fsck itself isn't! While it normally gets included in the initramfs, for some reason that doesn't happen with our image creation, so it isn't available on first boot, so explicitly copy 'fsck' so that it will be included. For that to work, 'logsave' is needed too, so include that as well. During boot up, initramfs wants to check the filesystems and it does so via `fsck`, which then (presumably) checks the filesystem being used and calls the appropriate fsck.* to do the actual checking. But when `fsck` itself isn't available you get the following warning: "Warning: fsck not present, so skipping root file system" When it is available, you'll get a message like this: "Begin: Will now check root file system ... fsck from util-linux 2.38.1" Let's also follow our own advise and not *assume* the needed fsck programs are present in initramfs, but add them explicitly. Now we can start the resize operations while knowing the current filesystem is in a proper/clean state.
2022-11-06 22:06:05 +00:00
# from logsave
copy_exec /sbin/logsave
Document and complete rpi-resizerootfs hook The main trigger was a missing program in the initramfs, which probably everyone assumed was there ... but wasn't. (See next commit ...) So instead list every program that we need/call, so that we *know* that that program is included in the initramfs. Also document this new 'policy'. Also group the programs by the package which has them and sort the list alphabetically by the package names.
2022-11-06 19:17:27 +00:00
# from mount
copy_exec /bin/mount
copy_exec /bin/umount
# from parted
resizerootfs: switch from using sfdisk to parted for resizing partitions sfdisk is a bit crusty - it doesn't understand gpt partition tables very well, for example. By switching to parted, we can handle gpt issues (which may be useful in the future, and is definitely useful for other boards), and we no longer have to hardcode that 4M alignment workaround. Parted will tell us the free space at the end of the disk. Because we're already using partprobe, there's no additional dependencies needed.
2021-07-02 02:54:29 +01:00
copy_exec /sbin/parted
rpi-resizerootfs: switch the root filesystem resizing away from a systemd oneshot service Switch away from using a systemd service for the initial root resize. Instead, we resize the root partition and filesystem in the initrd. To simplify things, the initrd script will check whether it should resize the partition on every boot. It does this by checking if the entire disk (ignoring an empty 4MB) is in use. However, the scripts themselves are deleted from the system after the initrd is generated. After the image is installed, the resize script should exist only in the initrd. When the kernel gets upgraded (eg, for a security update) or a new initrd is generated due to a package install, the new initrd will not contain the resize script. At that point, nothing will remain from the image's initial resize bootstrapping process. This process (but not the scripts) is similar to what cloud-initramfs-growroot does. However, that particular package has an indirect dependency on Python, and we don't necessarily want that overhead in our images just for resizing.
2021-04-30 18:23:21 +01:00
copy_exec /sbin/partprobe
Document and complete rpi-resizerootfs hook The main trigger was a missing program in the initramfs, which probably everyone assumed was there ... but wasn't. (See next commit ...) So instead list every program that we need/call, so that we *know* that that program is included in the initramfs. Also document this new 'policy'. Also group the programs by the package which has them and sort the list alphabetically by the package names.
2022-11-06 19:17:27 +00:00
# from util-linux
copy_exec /bin/lsblk
copy_exec /sbin/blkid
Explicitly copy 'fsck*' into the initramfs While fsck.ext4 and fsck.vfat are part of the initramfs, it turns out that fsck itself isn't! While it normally gets included in the initramfs, for some reason that doesn't happen with our image creation, so it isn't available on first boot, so explicitly copy 'fsck' so that it will be included. For that to work, 'logsave' is needed too, so include that as well. During boot up, initramfs wants to check the filesystems and it does so via `fsck`, which then (presumably) checks the filesystem being used and calls the appropriate fsck.* to do the actual checking. But when `fsck` itself isn't available you get the following warning: "Warning: fsck not present, so skipping root file system" When it is available, you'll get a message like this: "Begin: Will now check root file system ... fsck from util-linux 2.38.1" Let's also follow our own advise and not *assume* the needed fsck programs are present in initramfs, but add them explicitly. Now we can start the resize operations while knowing the current filesystem is in a proper/clean state.
2022-11-06 22:06:05 +00:00
copy_exec /sbin/fsck