BUGS > 2012.1.1

PXE boot problem

(1/2) > >>

When PXE booting, /proc/mdstat doesn't exist, and the script in the initrd at /scripts/local-top/mdadm causes the boot to panic and fall to the initrd shell.

Removing /scripts/local-top/mdadm from the initrd (and it's reference in the ORDER file in the same directory), and re-making the initrd image allows successful PXE booting.

I don't know why /proc/mdstat doesn't exist when pxe booting, and I'm sure fixing that is the correct way to fix the problem, rather than my hacky "remove the mdadm" method above, and probably needs to be investigated by someone that understands the boot process more than I do.

Mmmh i do not modify the initram init script but pxe booting works very well. Which siduction image do you use?

I downloaded all of them, except no-x. I'm assuming they all use the same kernel / initrd, so I only have one of those on my tftp server, and have multiple menu entries that point at different nbd mounts for the different isos. I took the kernel image and initrd from the KDE ISO (I still have the ISO loopback mounted on my storage box!)

I just tried booting the original initrd (I also added firmware-linux-nonfree to mine) from the KDE iso on a virtual machine (VirtualBox) too, it also fails with the same message - cannot initialise MD subsystem (/proc/mdstat missing). Hunting around the initrd image, I see no 'md' in /conf/modules, and I also see MD_MODULES='' in /conf/conf.d/md, yet lots of md modules in /lib/modules/3.4.../kernel/drivers/md, so I'm pretty sure md is compiled as modules, not compiled into the kernel. lsmod at the busybox shell it drops too when it aborts the boot shows no md module loaded. And yeah, I dug through the init scripts quite a bit, and now have a modest understanding of what's calling what :)

Are you pxe booting the 32 bit ISOs by chance?? Maybe worth pointing out I'm using the 64 bit ISOs. I didn't download the 32 bit ones, but maybe that's why it works for you, but not for me?

Im using the 32 bit KDE iso image. Are you sure that your nbd-server works properly? I also have a boot message "canot init MD subsystem" but the next messages is

--- Code: ---
Probing devices (nbd0)
Detected live squashfs filesystem ...
copy filesystem from nbd0 to ram ...

--- End code ---



[0] Message Index

[#] Next page

Go to full version