It's not as simple as that. Busybox's fsck applet is only the frontend that calls filesystem-specific fsck implementations, and those implementations are not included in Busybox (rightly so, IMO - I wouldn't want to have to deal with data-loss bugs caused by skew between the standard tools and reimplementations in Busybox).
If we want to include repair facilities in the initramfs (which might well be a good idea), we'll need to arrange for initramfs-tools to copy the appropriate fsck implementation into the initramfs, as well as enabling this applet.
It's not as simple as that. Busybox's fsck applet is only the frontend that calls filesystem-specific fsck implementations, and those implementations are not included in Busybox (rightly so, IMO - I wouldn't want to have to deal with data-loss bugs caused by skew between the standard tools and reimplementations in Busybox).
If we want to include repair facilities in the initramfs (which might well be a good idea), we'll need to arrange for initramfs-tools to copy the appropriate fsck implementation into the initramfs, as well as enabling this applet.