I've had the same new problem twice now, on initial boot post-install:
Loading Linux 4.4.0-2-amd64 ... Loading initial ramdisk ... Loading, please wait... mdadm: No devices listed in conf file were found. Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/disk/by-uuid/49cc7fa6-a12e-4aa9-a433-26b6aba9b06a does not exist. Dropping to a shell! modprobe: module ehci-orion not found in modules.dep BusyBox v1.22.1 (Debian 1:1.22.0-9+deb8u1) built-in shell (ash) Enter 'help' for a list of built-in commands. /bin/sh: can't access tty; job control turned off (initramfs) cat /etc/mdadm/mdadm.conf HOMEHOST <system> ARRAY /dev/md/0 metadata=1.2 UUID=09d24517:e5d90d78:98e26e42:6a3ecb7d name=cp1055:0 (initramfs) mdadm --assemble /dev/md/0 mdadm: /dev/md/0 has been started with 2 drives. (initramfs) exit /dev/md0: clean, 42804/610800 files, 375335/2439168 blocks [ 92.138317] kvm: disabled by bios [ 92.206867] kvm: disabled by bios [ 93.037036] bnx2x 0000:01:00.0 eth0: Warning: Unqualified SFP+ module detected, Port 0 from FINISAR CORP. part number FTLX1471D3BCL Debian GNU/Linux 8 cp1055 ttyS1 cp1055 login:
At a glance it looks similar to our md device assembly timeout issues, but it's not that. It's that the UUID for the root device is wrong, so it doesn't even try to assemble the correct device. Anyone have a clue about recent changes that could've precipitated this behavior?