Package: 
linux-image<https://packages.debian.org/stretch/linux-image-4.4.0-1-amd64>
Version: 4.4.0-1<https://packages.debian.org/stretch/linux-image-4.4.0-1-amd64>
Severity: critical
Tags: d-i, stretch

I have used today's version of 
http://d-i.debian.org/daily-images/amd64/daily/netboot/netboot.tar.gz to 
perform a pxeboot with seeded configuration of stretch amd64.  Same thing 
happens if I perform a simple manual ext4 install On reboot, I get 'EXT4-fs 
(sda2): Cannot load crc32c driver.' and I end up at a busybox prompt.

If I rebuild by substituting ext4 with ext3, I get a successful boot.

Here is an example of the seed file entry for the filesystem configuration.  
Which worked in linux-image-4.3.0 earlky in March:

# for internal use; can be preseeded
d-i     partman-auto/expert_recipe      string  \
  custom1 ::                                          \
    75 1000 100 ext4                                    \
      $primary{ } $bootable{ }                          \
      method{ format } format{ }                        \
      use_filesystem{ } filesystem{ ext4 }              \
      mountpoint{ /boot }                               \
      .                                                 \
    1000 4000 5000 ext4                                 \
      $primary{ }                                       \
      method{ format } format{ }                        \
      use_filesystem{ } filesystem{ ext4 }              \
      mountpoint{ / }                                   \
      .                                                 \
    5000 10000 1000000000 btrfs                         \
      $primary{ }                                       \
      method{ format } format{ }                        \
      use_filesystem{ } filesystem{ btrfs }             \
      mountpoint{ /var }                                \
      .                                                 \
    4000 8000 10000 ext4                                \
      method{ format } format{ }                        \
      use_filesystem{ } filesystem{ ext4 }              \
      mountpoint{ /home }                               \
      .                                                 \
    1000 1000 4000 ext4                                 \
      method{ format } format{ }                        \
      use_filesystem{ } filesystem{ ext4 }              \
      mountpoint{ /tmp }                                \
      .


Here is the final output of the boot sequence to console:
=================
Loading Linux 4.4.0-1-amd64 ...
Loading initial ramdisk ...
modprobe: module btrfs not found in modules.dep
/dev/sda2: clean, 24088/137088 files, 160700/547840 blocks
[    1.486902] EXT4-fs (sda2): Cannot load crc32c driver.
mount: mounting /dev/sda2 on /root failed: No such file or directory
mount: mounting /dev on /root/dev failed: No such file or directory
mount: mounting /run on /root/run failed: No such file or directory
run-init: current directory on the same filesystem as the root: error 0
Target filesystem doesn't have requested /sbin/init.
run-init: current directory on the same filesystem as the root: error 0
run-init: current directory on the same filesystem as the root: error 0
run-init: current directory on the same filesystem as the root: error 0
run-init: current directory on the same filesystem as the root: error 0
run-init: current directory on the same filesystem as the root: error 0
No init found. Try passing init= bootarg.


BusyBox v1.22.1 (Debian 1:1.22.0-18) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)
====================




Reply via email to