I ran into the same problem.
The root cause of the problem is that the logic for selecting the fsck
programs to include in the initramfs is not the same as the logic
for deciding which fsck program to run during boot.
During build /usr/share/initramfs-tools/hooks/fsck parses /etc/fstab to
det
I ran into the inverse situation: my /etc/fstab said ext3, but at
runtime the initramfs looked for /sbin/fsck.ext4, and couldn't find it.
Perhaps instead of special-casing ext3/ext4, it might be better to make
it use 'fsck -N' (or equivalent) to discover which fsck backend will be
used at runt
Package: initramfs-tools
Version: 0.118
Severity: normal
--- Please enter the report below this line. ---
I have a ext3 formatted / which in /etc/fstab is mounted with ext4. This
does not cope well with the logic in hooks/fsck which assumes that
fsck.$fs will work with a filesystem entry $fs i
3 matches
Mail list logo
