Initramfs init: Difference between revisions
Prabuanand (talk | contribs) (added sample mkinitfs.conf) |
(Add command when running outside system) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 2: | Line 2: | ||
== Usage == | == Usage == | ||
Under a running alpine machine, the following command can be used if for some reason the initramfs has not been created properly for a new kernel. | Under a running alpine machine, the following command can be used if for some reason the initramfs has not been created properly for a new kernel. | ||
{{cmd|mkinitfs -c /etc/mkinitfs/mkinitfs.conf -b / <kernelvers>}} | {{cmd|# mkinitfs -c /etc/mkinitfs/mkinitfs.conf -b / <kernelvers>}} | ||
The script is located in {{path|/sbin/}} and is created with ash. It expects {{path|/lib/modules}} to be populated with the <code><kernelvers></code> listed. | The script is located in {{path|/sbin/}} and is created with ash. It expects {{path|/lib/modules}} to be populated with the <code><kernelvers></code> listed.<br> | ||
Therefore normally just running <code>mkinitfs</code> should be enough if you need to rebuild it. | |||
== | Sometimes, e.g. to fix a non booting installation or when installing, you may have to rebuild the initramfs from another system, you do not need to chroot.<br> | ||
Mount <code>/</code>, <code>/boot</code> etc. and then run: | |||
{{cmd|# mkinitfs -c /mnt/etc/mkinitfs/mkinitfs.conf -b /mnt/ $(ls /mnt/lib/modules/)}} | |||
== Initramfs init cmdline options == | |||
In addition to the [https://www.kernel.org/doc/html/v4.14/admin-guide/kernel-parameters.html kernel boot parameters] are a number of parameters that the init script understands. These are documented in the <code>mkinitfs-bootparam(7)</code> man page. | In addition to the [https://www.kernel.org/doc/html/v4.14/admin-guide/kernel-parameters.html kernel boot parameters] are a number of parameters that the init script understands. These are documented in the <code>mkinitfs-bootparam(7)</code> man page. | ||
| Line 14: | Line 19: | ||
Although you may specify your own init script when building an initramfs, these parameters allow for extensive control over the initial startup of an Alpine Linux system. | Although you may specify your own init script when building an initramfs, these parameters allow for extensive control over the initial startup of an Alpine Linux system. | ||
== Troubleshooting == | |||
To troubleshoot booting issues, when using [[Bootloaders#GRUB|grub]], replace <code>quiet</code> with <code>debug_init single</code> in the boot command line. | |||
== See Also == | == See Also == | ||
* [https://wiki.postmarketos.org/wiki/The_initramfs PostmarketOS Wiki] | * [https://wiki.postmarketos.org/wiki/The_initramfs PostmarketOS Wiki] | ||
* [https://wiki.archlinux.org/title/Arch_boot_process#initramfs ArchWiki boot process] | * [https://wiki.archlinux.org/title/Arch_boot_process#initramfs ArchWiki boot process] | ||
[[category:Kernel]] | [[category:Kernel]] | ||
[[Category:Booting]] | [[Category:Booting]] | ||
Latest revision as of 07:33, 28 September 2025
mkinitfs is a tool to create initramfs images. Initramfs images are small images which contain a small filesystem with everything required to boot Alpine. For example, when booting a setup with full disk encryption, the initramfs contains the binaries required to prompt for a password and mount the encrypted disk.
Usage
Under a running alpine machine, the following command can be used if for some reason the initramfs has not been created properly for a new kernel.
# mkinitfs -c /etc/mkinitfs/mkinitfs.conf -b / <kernelvers>
The script is located in /sbin/ and is created with ash. It expects /lib/modules to be populated with the <kernelvers> listed.
Therefore normally just running mkinitfs should be enough if you need to rebuild it.
Sometimes, e.g. to fix a non booting installation or when installing, you may have to rebuild the initramfs from another system, you do not need to chroot.
Mount /, /boot etc. and then run:
# mkinitfs -c /mnt/etc/mkinitfs/mkinitfs.conf -b /mnt/ $(ls /mnt/lib/modules/)
Initramfs init cmdline options
In addition to the kernel boot parameters are a number of parameters that the init script understands. These are documented in the mkinitfs-bootparam(7) man page.
Depending on your HDD type and filesystem used, the file appears as follows:
Contents of /etc/mkinitfs/mkinitfs.conf
Although you may specify your own init script when building an initramfs, these parameters allow for extensive control over the initial startup of an Alpine Linux system.
Troubleshooting
To troubleshoot booting issues, when using grub, replace quiet with debug_init single in the boot command line.