Bug 11337 - network "e100 device eth0 does not seem to be present, delaying initialization" in journal - 4alpha3 dualcd
Summary: network "e100 device eth0 does not seem to be present, delaying initializatio...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard: 4alpha3
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-01 12:18 CEST by claire robinson
Modified: 2016-10-16 15:13 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
journal2.txt (109.91 KB, text/plain)
2013-10-01 12:44 CEST, claire robinson
Details

Description claire robinson 2013-10-01 12:18:23 CEST
4alpha3 DualCD 2nd build (DATE.txt Sept 30th)

network Bringing up interface eth0: ERROR: : [/etc/sysconfig/network-scripts/ifup-eth] e100 device eth0 does not seem to be present, delaying initialization.

network [FAILED]

Noticed this odd message in the journal. See bug 11333 and bug 11334 for other issues with this installation. X had failed to start.

Earlier in the journal it shows eth0 being renamed to enp5s8

Journal.txt is attachment 4397 [details] on bug 11334


Reproducible: 

Steps to Reproduce:
claire robinson 2013-10-01 12:18:51 CEST

CC: (none) => ennael1, mageia

claire robinson 2013-10-01 12:19:03 CEST

Whiteboard: (none) => 4alpha3

Comment 1 Colin Guthrie 2013-10-01 12:30:57 CEST
Hmmm, I guess a /etc/sysconfig/network-scripts/ifcfg-eth0 file is present on your installed machine? Is there also a /etc/sysconfig/network-scripts/ifcfg-enp5s8?

When on the live boot (i.e. before install), what is the name of the network device?

I'm wondering if we actually need to order our current /usr/lib/udev/rules.d/76-net.rules to 81 (i.e. after the renaming) as otherwise the eth0 file is likely created on boot before the device is renamed...
Comment 2 Colin Guthrie 2013-10-01 12:32:36 CEST
If you've still got this machine, could you rm the /etc/sysconfig/network-scripts/ifcfg-eth0 file (and maybe the enp5s8 one too) and reboot and see if it is recreated. If so, can you rename the udev rule mentioned above to be numbered 81 and rm the files again and reboot? If that works, this confirms the fix :)
Comment 3 claire robinson 2013-10-01 12:36:54 CEST
Thanks for the quick response, I was holding on to it in case you were around.

ifcfg-eth0 is there and executable, ifcfg-enp5s8 is also there but not executable.

report.bug.xz is attachment 4396 [details] on bug 11333

I'll remove those and reboot it now
Comment 4 claire robinson 2013-10-01 12:41:19 CEST
After removing both ifcfg-eth0 and ifcfg-enp5s8 and rebooting, only ifcfg-enp5s8 is recreated.

Should I still rename the udev rule?
Comment 5 claire robinson 2013-10-01 12:44:40 CEST
Created attachment 4398 [details]
journal2.txt

journal2.txt taken after reboot

journalctl -a -b --no-pager > journal2.txt
Comment 6 Colin Guthrie 2013-10-01 12:52:12 CEST
Not much point in renaming it I guess if it's not recreated on reboot. I'd be interested to know if the file exists in the live environment itself (and further, if it's physically on the filesystem of the live cd or if it's created when it's booted)

I still think renaming the udev rule makes sense so will probably commit that anyway. It could be that there is still a race but the CD-based boot make it more likely... I'm not 100% sure here... but the fact it's executable makes me think it may exist already on the cd...
Comment 7 claire robinson 2013-10-01 12:56:12 CEST
This is with dualcd rather than livecd
Comment 8 claire robinson 2013-10-01 13:54:31 CEST
Booted with kde livecd in live mode, it shows as connected as enp5s8.

I can get the journal from that if it helps too.

Do you need me to hold on to the dualcd installation still Colin or can I install over it?
Comment 9 Colin Guthrie 2013-10-01 14:07:34 CEST
Does the ifcfg-eth0 file exist on the live boot?

The live CD just copies everything from the CD filesystem to the HD and then does a few things after.

It would be good to know when the ifcfg-eth0 file gets created - i.e. if it's on the live CD filesystem and just copied across, or if it's generated on the CD when booting it, or if it's done as a post-copy task or if it's created on first boot of the new system. The fact it's executable suggests to me it's not created via the udev rules and it's created by something else... narrowing down where it's created is a step towards fixing the problem (that's my theory at least :D)
Comment 10 claire robinson 2013-10-01 14:10:42 CEST
In live mode on the livecd ifcfg-enp5s8 is there but no ifcfg-eth0
Comment 11 Colin Guthrie 2013-10-01 14:12:19 CEST
Thanks Claire :)

So I guess it's either created as a post-install task or on first boot. I should probably reproduce this myself and stop asking you to poke about so much :)
Comment 12 claire robinson 2013-10-01 14:16:57 CEST
It's ok :) If you have all the needed info though i'll install over the dualcd installation?
Comment 13 Colin Guthrie 2013-10-01 14:56:21 CEST
I think I'll have to do the same install in a VM with snapshots and roll back and forward to test any fix anyway, so I should be OK going forward. Thanks!
Comment 14 Colin Guthrie 2014-02-23 18:49:26 CET
Never did look into this one properly. Do you happen to know if it got magically fixed with all the other fixes at any point or if it's still a problem?
Comment 15 Samuel Verschelde 2016-10-16 15:13:32 CEST
(In reply to Colin Guthrie from comment #14)
> Never did look into this one properly. Do you happen to know if it got
> magically fixed with all the other fixes at any point or if it's still a
> problem?

Closing as "magically fixed", especially now that we don't have Dual Arch ISOs anymore. Please reopen if needed.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.