10.04 beta1 iSCSI-on-root fails on boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
initramfs-tools (Ubuntu) |
Fix Released
|
High
|
Colin Watson |
Bug Description
Binary package hint: open-iscsi
This is a follow-up of bug 546944; which focuses on issues with the installer. This bug focuses on boot problems after having used the installer cd to install to the iSCSI volume. After that, the vmlinuz and initrd.img on the iSCSI install are copied to the server and pxelinux works to boot the kernel and initrd image.
However, during boot it came across a problem with detecting my network interface eth0:
(..)
Begin: Loading essential drivers...
Done.
Begin: Running /scripts/
Done.
Begin: Mounting root file system...
Begin: Running /scripts/local-top ...
ipconfig: eth0: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
/scripts/
[ 1.63xxxxx] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 1.63xxxxx] r8169 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 1.63xxxxx] eth0: RTL8168d/8111d a ..., <mac>, XID .. IRQ 27
(..)
Begin: Retrying network config
ipconfig: /sys/class/
ipconfig: no devices to configure
/scripts/
(..)
The sequence between the last two (..) is repeated in a loop, until it drops to Busybox. Please note the "/tmp/net-/" directory in the last error message.
When checking the /sys/class/
Since i'm doing this iSCSI install on a new system, i'm not sure if this is a regression since 9.10. But the ethernet worked fine when installing over the network and fetching repositories from the internet during installation.
It appears to me that the modules for my network interfaces are dynamically loaded, but perhaps not in time? Because, shortly after the first error messages encountered, it detects my eth0 interface. At least in the logs, since ifconfig doesn't detect it.
So it appears the iscsi scripts have some issue that prevents them from connecting to my iSCSI server, as i can see no trace of that; perhaps a simple usleep() here and there would do wonders? ;-)
I just tested again with a server nightly, but the same problem is still present as of April 5th, 2010 lucid nightly.
This time i tested within Virtualbox, which uses pcnet ethernet driver; i hope the screenshot may provide a clue of what's going wrong here.