[Bug 546964] [NEW] 10.04 beta1 iSCSI-on-root fails on boot

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

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/init-premount...
Done.
Begin: Mounting root file system...
Begin: Running /scripts/local-top ...
ipconfig: eth0: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
/scripts/local-top/iscsi: .: line 421: can't open /tmp/net-eth0.conf
[ 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/net/eth0: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
/scripts/local-top/iscsi: .: line 421: Can't open /tmp/net-/sys/class/net/eth0.conf
(..)

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/net/eth0/ directory within Busybox, i can
see that it got a symlink "device" pointing to "../../../0000:01:00.0";
the same numeric code as in my log pasted above. Modprobe also appears
to have the realtek modules. But ifconfig doesn't yield any output.

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? ;-)

** Affects: initramfs-tools (Ubuntu)
     Importance: High
     Assignee: Colin Watson (cjwatson)
         Status: In Progress

-- 
10.04 beta1 iSCSI-on-root fails on boot
https://bugs.edge.launchpad.net/bugs/546964
You received this bug notification because you are a member of Kernel Bugs, which is subscribed to initramfs-tools in ubuntu.