> Is the nfsroot also a wheezy one? I was assuming, creating one in wheezy creates a wheezy nfsroot? Your question now tells me that's not the case? I'm also not sure which setting influences this. In the nfsroot.conf I configured FAI_DEBOOTSTRAP as xenial one. I created the nfsroot with fai-setup -vl and configured everything to point to xenial, so I think I created a xenial nfsroot.
> Which FAI version are you using > inside the nfsroot? I added "deb http://fai-project.org/download wheezy koeln" to my sources.list so I'm using 4.3.2+wheezy1 > The 4.4 kernel does not support aufs, which is needed by dracut. Have > a look at http://wiki.fai-project.org/wiki/Grml_Kernel, which > describes how to use a 4.4 kernel to which I've added aufs support. I'm not using dracut (at least I think I'm not using it). At least I didn't include it in my NFSROOT-config: PACKAGES aptitude nfs-common fai-nfsroot module-init-tools ssh rdate lshw rpcbind rsync lftp less dump reiserfsprogs e2fsprogs usbutils hwinfo psmisc pciutils hdparm smartmontools parted mdadm lvm2 dnsutils ntpdate dosfstools xfsprogs xfsdump btrfs-tools procinfo numactl dialog console-common kbd iproute moreutils udev subversion xz-utils cupt pxelinux syslinux-common PACKAGES aptitude AMD64 grub-pc linux-image-generic live-boot > boot=live is not yet used/supported in recent FAI versions any more. > So this may be your first problem. I removed it and the kernel panic disappeared! But other errors appeared now: 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: opening conole: No such file or directory Target filesystem doesn't have requested /sbin/init run-init: opening console: No such file or directory ... No init found. Try passing init= bootarg. I think something is wrong with the folderstructure. He looks for /root/dev and stuff like this but the correct path is /root/live/filesystem.dir/
