Holger Levsen writes: > > you can remount the /dev directory to /tmp/target/dev > > mount --bind /dev /tmp/target/dev
Hi, thanks for the hint, this was very helpful. Using this in form of a hook (see below) and resolving some package issues which were resulting of some Debian/Ubuntu differences and using the correct installserver architecture (AMD64) to create the nfsroot environment (I used a Intel Xeon server before but the client PC to be installed are AMD64 machines, that's why I had problems with the kernel/grub stuff) lead to a successfull Ubuntu installation process. Here the hook to dynamically create the /dev directory in the nfsroot environment: [EMAIL PROTECTED]:/opt/fai/hooks$ cat /opt/fai/hooks/instsoft.FAIBASE #!/bin/sh # make /dev available in the chroot-environment mount --bind /dev $FAI_ROOT/dev && echo Remounted /dev to $FAI_ROOT/dev #HG: work around buggy kernel postinst if [ ! -s $target/etc/kernel-img.conf ] ; then cat > $target/etc/kernel-img.conf <<-EOF do_boot_enable = no do_initrd = Yes EOF fi Nevertheless, when booting the installed PC with a precompiled AMD64 Ubuntu kernel (linux-image-amd64-k8) leads to the following screen (little bit mixed up with the grub menu entries): Booting 'Ubuntu, kernel 2.6.10-5-amd64-k8 ' kernel direct mapping tables upto 1010000000 @ 8000-c000 root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /boot/vmlinuz-2.6.10-4-amd64-k8 root=/dev/sda1 ro quiet splash [Linux-bzImage, setup=0x1600, size=0x13e7d2] initrd /boot/initrd.img-2.6.10-5-amd64-k8 [Linux-initrd @ 0x3fbd2000, 0x40e000 bytes] savedefault boot . Decompressing Linux...done. Booting the kernel. audit(1123516210.213:0): initialized Starting Ubuntu... /sbin/init: 428: cannot create /dev/null: Read-only file system /sbin/init: 429: cannot open dev/console: No such file Kernel panic - not syncing: Attempting to kill init! At the moment I don't hav any idea where to start looking as the fai.log logfile doesn't look too bad: http://www.thp.Uni-Koeln.DE/~sinder/fai/09082005/fai.log The warnings during setting up the kernel package don't seem to be important as /initrd.img and /vmlinuz seem to be created. The error.log logfile contains the following lines (btw, what should be used instead of /proc/ide/hd?)? dmesg.log:Warning: /proc/ide/hd?/settings interface is obsolete, and will be rem oved soon! dmesg.log:ide2: Wait for ready failed before probe ! dmesg.log:ide3: Wait for ready failed before probe ! dmesg.log:ide4: Wait for ready failed before probe ! dmesg.log:ide5: Wait for ready failed before probe ! fai.log:Couldn't find any package whose name or description matched "jove" fai.log:dpkg: warning, architecture `amd64' not in remapping table fai.log:dpkg: warning, architecture `amd64' not in remapping table software.log:Couldn't find any package whose name or description matched "jove" software.log:dpkg: warning, architecture `amd64' not in remapping table software.log:dpkg: warning, architecture `amd64' not in remapping table The 'jove' error messages is due to a missing amd64 jove package but doesn't lead to any problems (I have removed that package from the package list). Has anybody solved this kernel panic problem before? Google is not too helpful in this special case... Thanks again Andreas