Mailinglist Archive: opensuse-bugs (2746 mails)

< Previous Next >
[Bug 826700] New: mkinitrd with manual iSCSI drive connected puts unneeded iscsi and tg3 modules in initrd rendering system unbootable
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 25 Jun 2013 18:04:53 +0000
  • Message-id: <>

Summary: mkinitrd with manual iSCSI drive connected puts
unneeded iscsi and tg3 modules in initrd rendering
system unbootable
Classification: openSUSE
Product: openSUSE 12.3
Version: Final
Platform: x86-64
OS/Version: openSUSE 12.3
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Other
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: kl@xxxxxxxxxxx
QAContact: qa-bugs@xxxxxxx
Found By: ---
Blocker: ---

User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101
Firefox/20.0 SeaMonkey/2.17.1

I am using an iSCSI-connected data drive which is set to "manual" and
nevertheless automatically mounted after the system has booted.
(Options nofail,acl,user_xattr,_netdev in /etc/fstab)

In this environment mkinitrd complains:
WARNING: iSCSI device /dev/disk/by-path/[...]:storage.lun1-lun-1-part1 is using
'node.conn[0].startup = manual'!
WARNING: System not bootable with this setting, need to be set to 'onboot'
instead, using:

It then puts the following unneeded and unwanted modules into the initrd:

Kernel Modules: af_packet tg3 scsi_transport_iscsi libiscsi libiscsi_tcp
iscsi_tcp crc32c-intel
Firmware: tigon/tg3_tso5.bin tigon/tg3_tso5.bin tigon/tg3_tso.bin
tigon/tg3_tso.bin tigon/tg3.bin tigon/tg3.bin
Features: network iscsi

Unfortunately - due to another bug (Bug 598730) - the tg3 Network driver
(still) doesn't work when loaded from initrd and so the boot hangs with no way
to interrupt and access the system.
Fail-safe mode also doesn't help here.

If - before running mkinitrd - I stop the iSCSI service ( systemctl stop
iscsid.service ) then the initrd is created the way it should without the
unwanted kernel-modules / firmware /features.

During automatic updates this is not possible, so...

mkinitrd should not try to be smarter than the user here. ;-)

Reproducible: Always

Steps to Reproduce:
1. configure/start iSCSI to manually connect to a data drive.
2. run mkinitrd.
3. watch initrd beeing created with lots of uneeded modules/features.

Actual Results:
mkinitrd complains about wrong iSCSI settings and builds initrd containing
unneeded modules/features which - in combination with Broadcom Ethernet -
render system unbootable.

Expected Results:
mkinitrd should not complain about "manual" iSCSI and - if iSCSI is configured
for "manual" - should NOT include features network/iscsi andnot include
iSCSI-modules and network modules.

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
Follow Ups