What happened to my interfaces?

D

Deleted member 143446

Guest
Today while I am online, suddenly internet connection down. I applied all I had in my first ait kit but did not work !

I checked that my usb dongle device is working- at leats seem connected in lsubs. But I could not ifup/ifdown my ethernet interface eth0.

I am using static IP since I have only one PC connected to modem. My usb modem have a gateway over 192.168.9.1 address.
I checked /etc/network/interfaces file and they are all there and adjusted like that(since I am using usb-dongle I used hotplug) :

allow-hotplug lo
iface lo inet loopback

allow-hotplug eth0
iface eth0 inet static
address 192.168.9.101
broadcast 192.168.9.255
netmask 255.255.255.0
gateway 192.168.9.1

I run sudu ifconfig and I can only see there is a loopback adapter, not eth0 anymore.

Code: 
$ sudo ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 70 bytes 8038 (7.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 70 bytes 8038 (7.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


I could not start it by using ifup/ifdown gives these errors :

Code: 
$ sudo ifdown eth0
ifdown: interface eth0 not configured

Code: 
$ sudo ifup eth0
Cannot find device "eth0"

When I did this :

Code: 
$ sudo ifup -av --force --ignore-errors
it gives :

/bin/run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/ethtool
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant

ifup: configuring interface lo=lo (inet)
/bin/run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/ethtool
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
/sbin/ip link set dev lo up
/bin/run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/000resolvconf
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/clamav-freshclam-ifupdown
run-parts: executing /etc/network/if-up.d/ethtool
run-parts: executing /etc/network/if-up.d/wpasupplicant
/bin/run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/000resolvconf
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/clamav-freshclam-ifupdown
run-parts: executing /etc/network/if-up.d/ethtool
run-parts: executing /etc/network/if-up.d/wpasupplicant

I reset my usb device by using sudo usbreset and usb_modeswitch programs. They said reset successful, so they saw my usb device.

I restart networking services by using :

Code: 
$ sudo systemctl restart networking
$ sudo systemctl restart systemd-resolved
$ sudo resolvconf -u

In dmesg I saw these lines :

Code: 
[  830.344000] sr 10:0:0:0: [sr3] scsi-1 drive
[  830.374242] sr 10:0:0:0: Attached scsi CD-ROM sr3
[  830.374338] sr 10:0:0:0: Attached scsi generic sg5 type 5
[  830.563001] sr 10:0:0:0: ioctl_internal_command return code = 8070000
[  830.563008] sr 10:0:0:0: Sense Key : Hardware Error [current]
[  830.563010] sr 10:0:0:0: Add. Sense: No additional sense information
[  830.955002] sr 10:0:0:0: ioctl_internal_command return code = 8070000
[  830.955009] sr 10:0:0:0: Sense Key : Hardware Error [current]
[  830.955011] sr 10:0:0:0: Add. Sense: No additional sense information
[  849.922841] sr 10:0:0:0: ioctl_internal_command return code = 8070000
[  849.922849] sr 10:0:0:0: Sense Key : Hardware Error [current]
[  849.922851] sr 10:0:0:0: Add. Sense: No additional sense information
[ 3275.787615] cdc_ether: probe of 3-2.3:1.0 failed with error -84
[ 3329.902633] usb 3-2.3: reset full-speed USB device number 12 using uhci_hcd
[ 3467.022619] usb 3-2.3: reset full-speed USB device number 12 using uhci_hcd
[ 3467.246619] usb 3-2.3: reset full-speed USB device number 12 using uhci_hcd
[ 3490.310615] usb 3-2.3: reset full-speed USB device number 12 using uhci_hcd
[ 3577.838610] usb 3-2.3: reset full-speed USB device number 12 using uhci_hcd
[ 3621.070606] usb 3-2.3: reset full-speed USB device number 12 using uhci_hcd
[ 3804.526593] usb 3-2.3: reset full-speed USB device number 12 using uhci_hcd
[ 3824.910596] usb 3-2.3: reset full-speed USB device number 12 using uhci_hcd
[ 4888.974510] usb 3-2.3: reset full-speed USB device number 12 using uhci_hcd
[ 5533.198486] usb 3-2.3: reset full-speed USB device number 12 using uhci_hcd
[ 5885.082440] usb 3-2.3: reset full-speed USB device number 12 using uhci_hcd
[ 5929.302429] usb 3-2.3: reset full-speed USB device number 12 using uhci_hcd
[ 6215.214407] usb 3-2.3: reset full-speed USB device number 12 using uhci_hcd
[ 6352.526404] usb 3-2.3: reset full-speed USB device number 12 using uhci_hcd
[ 6387.022393] usb 3-2.3: reset full-speed USB device number 12 using uhci_hcd
[ 6570.702379] usb 3-2.3: reset full-speed USB device number 12 using uhci_hcd
[ 6703.982369] usb 3-2.3: reset full-speed USB device number 12 using uhci_hcd
[ 6833.230365] usb 3-2.3: reset full-speed USB device number 12 using uhci_hcd
[ 6849.582357] usb 3-2.3: reset full-speed USB device number 12 using uhci_hcd
[ 6880.046355] usb 3-2.3: reset full-speed USB device number 12 using uhci_hcd
[ 6996.750350] usb 3-2.3: reset full-speed USB device number 12 using uhci_hcd
[ 7089.193476] usb 3-2.3: USB disconnect, device number 12
[ 7097.994339] usb 3-2.3: new full-speed USB device number 13 using uhci_hcd
[ 7098.109474] usb 3-2.3: not running at top speed; connect to a high speed hub
[ 7098.135474] usb 3-2.3: unable to read config index 2 descriptor/start: -32
[ 7098.135477] usb 3-2.3: chopping to 2 config(s)
[ 7098.135479] usb 3-2.3: can't read configurations, error -32
[ 7098.218334] usb 3-2.3: new full-speed USB device number 14 using uhci_hcd
[ 7098.333473] usb 3-2.3: not running at top speed; connect to a high speed hub
[ 7098.359474] usb 3-2.3: unable to read config index 2 descriptor/start: -32
[ 7098.359477] usb 3-2.3: chopping to 2 config(s)
[ 7098.359479] usb 3-2.3: can't read configurations, error -32
[ 7098.361475] usb 3-2-port3: attempt power cycle
[ 7098.966347] usb 3-2.3: new full-speed USB device number 15 using uhci_hcd
[ 7099.001473] usb 3-2.3: not running at top speed; connect to a high speed hub
[ 7099.027475] usb 3-2.3: unable to read config index 2 descriptor/start: -32
[ 7099.027478] usb 3-2.3: chopping to 2 config(s)
[ 7099.027480] usb 3-2.3: can't read configurations, error -32
[ 7099.110334] usb 3-2.3: new full-speed USB device number 16 using uhci_hcd
[ 7099.145474] usb 3-2.3: device descriptor read/8, error -71
[ 7099.281473] usb 3-2.3: device descriptor read/8, error -71
[ 7099.387477] usb 3-2-port3: unable to enumerate USB device
[ 7099.614333] usb 3-2.3: new full-speed USB device number 17 using uhci_hcd
[ 7099.733475] usb 3-2.3: not running at top speed; connect to a high speed hub
[ 7100.809502] sr 10:0:0:0: [sr3] scsi-1 drive
[ 7100.844429] sr 10:0:0:0: Attached scsi CD-ROM sr3
[ 7100.844760] sr 10:0:0:0: Attached scsi generic sg5 type 5
[ 7101.046492] sr 10:0:0:0: ioctl_internal_command return code = 8070000
[ 7101.046500] sr 10:0:0:0: Sense Key : Hardware Error [current]
[ 7101.046502] sr 10:0:0:0: Add. Sense: No additional sense information
[ 7101.535488] sr 10:0:0:0: ioctl_internal_command return code = 8070000
[ 7101.535495] sr 10:0:0:0: Sense Key : Hardware Error [current]
[ 7101.535497] sr 10:0:0:0: Add. Sense: No additional sense information
[ 7102.492502] sr 10:0:0:0: ioctl_internal_command return code = 8070000
[ 7102.492510] sr 10:0:0:0: Sense Key : Hardware Error [current]
[ 7102.492512] sr 10:0:0:0: Add. Sense: No additional sense information

In above "Attached scsi CD-ROM sr3" lines show my usb modem.
Finally I did the last chance to bring my interface to life : UNPLUGGING ! :eek: Plug- replug bring it back to life.

My questions are :
1.What is "Sense Key : Hardware Error [current]" means in above journal ?
2. What happened to my modem suddenly?
3. What tools can I add to my first aid kit about it in such situations?

I want to ask to Linux experts since my well-working first ait kit did not work today. Any help is appreciated. Thanks.
 


eaglehopes said:
Sense Key : Hardware Error
Click to expand...
When the USB device gets connected, it is identified as a block storage device. The command set for those devices is basically SCSI (transported over USB). So the kernel issues a few SCSI commands to that device, for example to find out the capacity. Your USB-to-NVM bridge chip answers with "unit not ready", for whatever reason (for example, because the firmware is still initializing itself).
Usually this is the stages of hardware failure
 
Thanks @Lord Boltar , I am just connected to ask "do any body knows any network profiler/analyser tools etc." like sysprof or system profiler which collects information about system-hardware failures on network.
Lord Boltar said:
Usually this is the stages of hardware failure
Click to expand...
:eek: Horrible !
By the way do you know any such tool? I am looking dozens of forums and two times more than pages to find a solution but, everyone of them suggest looking journals, logs etc. Is there any tool to combine all(at last most/even some or I am consent to a few of them) together to easily see where is the problem? Is it in software or hadware?
You alread said that it is a sign of hardware failure. But what is :
cdc_ether: probe of 3-2.3:1.0 failed with error -84
Click to expand...
or
usb 3-2.3: can't read configurations, error -32
usb 3-2.3: device descriptor read/8, error -71
Click to expand...
etc. Where can I find that which code means what? I could not find a catalog of them. Maybe these kind of error catalogs helps Linux users more ! (I am just a humble user, but if I was one of the Linux developers/team member, I will put some links to error catalogs).
 
If my internet goes down...the first thing I do is turn off the Modem...wait 2 mins and re-start...if this doesn't work I reset the Modem (put paper clip in small hole at the back).
confused0071.gif


If that fails I ring my ISP after all that's what I'm paying for.
happy0043.gif


Here in Australia we have the NBN...(No Bloody Network) it's suppose to be the best thing since sliced bread...it's better than what we use to have but I still get dropouts every now and then...which is a real pain.
mad0016.gif
 
osprey said:
Just a note on this config:

It's usually by default:
Code: 
auto lo
Click to expand...
Since my modem is USB, only hotplug make it work again after re-plug. Once upon a time it was auto but not worked, so I found from Debian Network settings page and changed it. [Edited] Actually this page : https://wiki.debian.org/NetworkConfiguration , you can see that both auto and allow-hotplug used at the same time.
 
Last edited by a moderator:
My reaction to KSystemLog tool and error codes is simply this ʘ‿ʘ
I noticed lots of warnings and errors about my system there... and I started to look deeper to solve them !
 
eaglehopes said:
I read the link, but I have still have one question : I can not access to system and service logs by using KSystemLog GUI, how can I run it as super user?
Click to expand...
I found :
$ sudo ksystemlog
 
eaglehopes said:
Since my modem is USB, only hotplug make it work again after re-plug. Once upon a time it was auto but not worked, so I found from Debian Network settings page and changed it. [Edited] Actually this page : https://wiki.debian.org/Netwyou can see that both auto and allow-hotplug used at the same time.orkConfiguration , you can see that both auto and allow-hotplug used at the same time.
Click to expand...
Hello eaglehopes.

There seems to be a lack of clarity here in your post #8.

The loopback device is "lo", and as mentioned in post #6, it is usually configured as mentioned there like this:
Code: 
auto lo
The loopback device is not hotplugged like a usb, or like an ethernet can be, so there is no point in configuring it as:
Code: 
allow-hotplug lo
Rather the loopback device is a network device that allows the computer to run networking within itself even if not networked with any external devices. Hence it appears as a network device when you run a command to identify the network devices such as "ifconfig" or "ip a". Its network address is 127.0.0.1. It's built into the system and so is a pseudo-device rather than a card or adapter or a usb or other pluggable device. When it is configured with the "auto" option, the system knows what to do with it automatically. If it is treated like a usb or ethernet device with the option "allow-hotplug", you may simply be interfering with its normal operation unnecessarily. It makes little sense to configure the loopback device in that way. It is clear from reading the debian NetworkConfiguration page that you linked to, that the loopback device is only configured as "auto lo", and it is only the other devices that are configured with "allow-hotplug".

eaglehopes wrote:
you can see that both auto and allow-hotplug used at the same time.
Click to expand...
If this statement is saying that the options "auto" and "allow-hotplug" can appear in the one configuration file, as shown in the debian NetworkConfiguration link, it makes sense. But a close reading of that link shows that the loopback device lo is only ever configured with "auto", with "allow-hotplug" being applied exclusively to other devices which may appear in the same configuration file.

None of this may resolve your original issue, but for the sake of clarity I thought it worth mentioning.
 
I
osprey said:
Hello eaglehopes.

There seems to be a lack of clarity here in your post #8.

The loopback device is "lo", and as mentioned in post #6, it is usually configured as mentioned there like this:
Code: 
auto lo
The loopback device is not hotplugged like a usb, or like an ethernet can be, so there is no point in configuring it as:
Code: 
allow-hotplug lo
Rather the loopback device is a network device that allows the computer to run networking within itself even if not networked with any external devices. Hence it appears as a network device when you run a command to identify the network devices such as "ifconfig" or "ip a". Its network address is 127.0.0.1. It's built into the system and so is a pseudo-device rather than a card or adapter or a usb or other pluggable device. When it is configured with the "auto" option, the system knows what to do with it automatically. If it is treated like a usb or ethernet device with the option "allow-hotplug", you may simply be interfering with its normal operation unnecessarily. It makes little sense to configure the loopback device in that way. It is clear from reading the debian NetworkConfiguration page that you linked to, that the loopback device is only configured as "auto lo", and it is only the other devices that are configured with "allow-hotplug".

eaglehopes wrote:

If this statement is saying that the options "auto" and "allow-hotplug" can appear in the one configuration file, as shown in the debian NetworkConfiguration link, it makes sense. But a close reading of that link shows that the loopback device lo is only ever configured with "auto", with "allow-hotplug" being applied exclusively to other devices which may appear in the same configuration file.

None of this may resolve your original issue, but for the sake of clarity I thought it worth mentioning.
Click to expand...
:) It is my mistake ! You are right, I am changing that configuration to auto! Thanks for saying that!
 
You must log in or register to reply here.

Members online

Total: 828 (members: 7, guests: 821)

Latest posts

Top