SOLVED - Re: Moved a FC10 drive between two systems - eth0 not recognized

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Just wanted to update the list on a success.

Tom Horsley wrote:
On Wed, 14 Oct 2009 14:11:29 -0400
Robert Moskowitz wrote:

So what is the magic as there is no longer kudzu?

Try removing /etc/udev/rules.d/70-persistent-net.rules
(created by udev it recognizes things like mac addr
which is probably different).

You might want to remove 70-persistent-cd.rules
as well, since it will be looking for a specific
cd/dvd drive which probably isn't the same either.
All fixed now. I had to wait to schedule another time slot to take my mail server down.

Interestingly these files had two entries, the old and new system's vaules. For NET I had:

# cat old-70-persistent-net.rules

# This file was automatically generated by the /lib/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.

# Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 (rule written by anaconda) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:50:8b:71:9d:da", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x8086:0x2449 (e100)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:02:a5:d2:ca:35", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"


After moving the file, putting the drive in the newer system and powering up I had:


# cat 70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.

# PCI device 0x8086:0x2449 (e100)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:02:a5:d2:ca:35", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

So it seemed that the process was adding the new card in as eth1, when there WAS no eth1. But the interface was not working, eventhough 'ifconfig -a' showed it there. Niether 'ifup eth0' or 'service network restart' got it working. Took another reboot, and then it worked.

And yes, there was also a change in the CD drive discription...

THANKS!


--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux