OS not detecting network drive.

Issues related to configuring your network
Post Reply
llwb
Posts: 20
Joined: 2017/03/22 02:48:12

OS not detecting network drive.

Post by llwb » 2017/07/24 08:09:27

Hi i followed the following guide and everything went accordingly however when I do ifconfig I still cant see eth0... please help
the guide i use:
https://exxactcorp.com/blog/how-to-inst ... -centos-6/

out put I try:
[lwb@localhost Desktop]$ ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:64 errors:0 dropped:0 overruns:0 frame:0
TX packets:64 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4416 (4.3 KiB) TX bytes:4416 (4.3 KiB)

virbr0 Link encap:Ethernet HWaddr 52:54:00:8B:76:B5
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

[lwb@localhost Desktop]$ dmesg | grep -i e100
e1000e: Intel(R) PRO/1000 Network Driver - 3.3.5.3-NAPI
e1000e: Copyright(c) 1999 - 2016 Intel Corporation.
e1000e 0000:00:1f.6: PCI INT A -> GSI 16 (level, low) -> IRQ 16
e1000e 0000:00:1f.6: setting latency timer to 64
e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
e1000e 0000:00:1f.6: irq 136 for MSI/MSI-X
e1000e 0000:00:1f.6: (unregistered net_device): registered PHC clock
e1000e 0000:00:1f.6: eth0: (PCI Express:2.5GT/s:Width x1) 70:4d:7b:71:19:b6
e1000e 0000:00:1f.6: eth0: Intel(R) PRO/1000 Network Connection
e1000e 0000:00:1f.6: eth0: MAC: 12, PHY: 12, PBA No: FFFFFF-0FF
[lwb@localhost Desktop]$ dmesg | grep -i e1000e
e1000e: Intel(R) PRO/1000 Network Driver - 3.3.5.3-NAPI
e1000e: Copyright(c) 1999 - 2016 Intel Corporation.
e1000e 0000:00:1f.6: PCI INT A -> GSI 16 (level, low) -> IRQ 16
e1000e 0000:00:1f.6: setting latency timer to 64
e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
e1000e 0000:00:1f.6: irq 136 for MSI/MSI-X
e1000e 0000:00:1f.6: (unregistered net_device): registered PHC clock
e1000e 0000:00:1f.6: eth0: (PCI Express:2.5GT/s:Width x1) 70:4d:7b:71:19:b6
e1000e 0000:00:1f.6: eth0: Intel(R) PRO/1000 Network Connection
e1000e 0000:00:1f.6: eth0: MAC: 12, PHY: 12, PBA No: FFFFFF-0FF
[lwb@localhost Desktop]$ ifup
Usage: ifup <device name>
[lwb@localhost Desktop]$ ifup eth0
/sbin/ifup: configuration for eth0 not found.
Usage: ifup <device name>
[lwb@localhost Desktop]$ lspic -nn | grep -i net
bash: lspic: command not found
[lwb@localhost Desktop]$ lspci -nn | grep -i net
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I219-V [8086:15b8] (rev 31)
04:00.0 Network controller [0280]: Qualcomm Atheros Device [168c:003e] (rev 32)

User avatar
TrevorH
Site Admin
Posts: 33202
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: OS not detecting network drive.

Post by TrevorH » 2017/07/24 08:51:56

Support for that adapter is already included in the CentOS kernel so there is no need to follow that guide at all. I recommend undoing whatever steps you followed from that and revert the changes - it is not required.

Post the output from ifconfig -a
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

llwb
Posts: 20
Joined: 2017/03/22 02:48:12

Re: OS not detecting network drive.

Post by llwb » 2017/07/24 08:55:17

Thanks for replying, here is the output:
[root@localhost Desktop]# ifconfig -a
eth0 Link encap:Ethernet HWaddr 70:4D:7B:71:19:B6
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:16 Memory:f7300000-f7320000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:276 errors:0 dropped:0 overruns:0 frame:0
TX packets:276 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:20976 (20.4 KiB) TX bytes:20976 (20.4 KiB)

pan0 Link encap:Ethernet HWaddr 1E:7E:46:76:B9:F0
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

virbr0 Link encap:Ethernet HWaddr 52:54:00:8B:76:B5
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

virbr0-nic Link encap:Ethernet HWaddr 52:54:00:8B:76:B5
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500

User avatar
TrevorH
Site Admin
Posts: 33202
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: OS not detecting network drive.

Post by TrevorH » 2017/07/24 09:48:31

So the adapter is being seen and is called eth0. From the error you got from ifup I would guess that you have no /etc/sysconfig/network-scripts/ifcfg-eth0 file and you probably need to create one.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

llwb
Posts: 20
Joined: 2017/03/22 02:48:12

Re: OS not detecting network drive.

Post by llwb » 2017/07/24 23:48:31

Thanks for the reply ! is there a way to auto generate one ? I mean i am pretty new to this, as i would like the IP address to be dynamic ...
I try adding in the following lines to the folder(/etc/sysconfig/network-scripts/ifcfg-eth0):
DEVICE=eth0
TYPE=Ethernet
ONBOOT=yes
BOOTPROTO=dhcp
IPV4_FAILURE_FATAL=yes
NAME="System eth0"
HWADDR=70:4D:7B:71:19:B6
but my ifconfig still doesn't show eth0 :(

User avatar
TrevorH
Site Admin
Posts: 33202
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: OS not detecting network drive.

Post by TrevorH » 2017/07/25 08:48:21

What error do you get now with that file in place when you run ifup eth0 ?
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

llwb
Posts: 20
Joined: 2017/03/22 02:48:12

Re: OS not detecting network drive.

Post by llwb » 2017/07/26 06:37:55

Thanks ! I got it fix as I forget to run #service network restart in root ...

Post Reply