Re: Network fails on headless system. I'm stuck!
Since Andrei didn't seem to have CC-ed you,
https://lists.debian.org/debian-user/2014/10/msg00873.html
He said,
> See if your kernel includes all the needed options for systemd
> /usr/share/doc/systemd/README.gz
Also, I'm sure the arm list will be of more use, am adding them to the CC list.
OP, with attachments, at
https://lists.debian.org/debian-user/2014/10/msg00870.html>
On Sun, Oct 12, 2014 at 9:42 PM, JPT <j-p-t@gmx.net> wrote:
> Hi,
>
> I have an ARM hardware (ReadyNAS rn104) running debian jessie (testing).
> kernel is selfbuilt 3.16.3
>
> Since a few days the system fails to boot. Serial console breaks at a
> point where it is fiddling with disks and network.
> Networking is not yet up. So I don't have any way to access the headless
> system.
>
> I suspect an update in the networking scripts or systemd.
> Could you please add a warning if a basic system library gets replaced
> by a version that requires additional kernel features? The last time I
> ran into a problem is only a few months ago.
>
> Where can I find a list of the recently updated packages in the jessie repo?
>
> The problems started with network having problems.
> After a little bit of trying, I got a kernel panic (see chrash.log)
> This was on oct, 10th around 8 pm.
> after that, the network did never ever come up again.
> To make things worse, the serial console stops working during boot-up as
> well.
>
> an excerpt from the syslog during unsuccessful start-up. I marked a few
> things I found interesting.
>
> Oct 11 11:59:37 NAS kernel: [ 3.086492] libphy: Fixed MDIO Bus: probed
> Oct 11 11:59:37 NAS kernel: [ 3.090847] tun: Universal TUN/TAP device
> driver, 1.6
> Oct 11 11:59:37 NAS kernel: [ 3.095908] tun: (C) 1999-2004 Max
> Krasnyansky <maxk@qualcomm.com>
> Oct 11 11:59:37 NAS kernel: [ 3.102894] libphy: orion_mdio_bus: probed
> Oct 11 11:59:37 NAS kernel: [ 3.151215] mvneta d0070000.ethernet
> *eth0:* Using random mac address 4e:8f:db:a2:ed:cb
> Oct 11 11:59:37 NAS kernel: [ 3.159900] mvneta d0074000.ethernet
> *eth1:* Using random mac address 5e:fe:87:9a:fb:0f
> Oct 11 11:59:37 NAS kernel: [ 3.168573] pegasus: v0.9.3 (2013/04/25),
> Pegasus/Pegasus II USB Ethernet driver
> ...
> Oct 11 11:59:37 NAS kernel: [ 97.390160] IPv6: ADDRCONF(NETDEV_UP):
> eth0: link is not ready
> Oct 11 11:59:37 NAS kernel: [ 102.820073] mvneta d0070000.ethernet
> eth0: link up
> Oct 11 11:59:37 NAS kernel: [ 102.824896] IPv6:
> ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> ...
> Oct 11 11:59:43 NAS nmbd[2973]: [2014/10/11 11:59:43.387204, 0]
> ../source3/lib/interface.c:543(load_interfaces)
> Oct 11 11:59:43 NAS nmbd[2973]: *WARNING: no network interfaces found*
> Oct 11 11:59:43 NAS nmbd[2973]: [2014/10/11 11:59:43.389441, 0]
> ../source3/nmbd/nmbd_subnetdb.c:250(create_subnets)
> Oct 11 11:59:43 NAS nmbd[2973]: create_subnets: No local IPv4
> non-loopback interfaces !
> Oct 11 11:59:43 NAS nmbd[2973]: [2014/10/11 11:59:43.389697, 0]
> ../source3/nmbd/nmbd_subnetdb.c:251(create_subnets)
> Oct 11 11:59:43 NAS nmbd[2973]: create_subnets: Waiting for an
> interface to appear ...
> ...
> Oct 11 12:01:05 NAS systemd[1]: Job
> dev-disk-by\x2dlabel-NAS\x2dBOOT.device/start timed out.
> Oct 11 12:01:05 NAS systemd[1]: Timed out waiting for device
> dev-disk-by\x2dlabel-NAS\x2dBOOT.device.
> Oct 11 12:01:05 NAS systemd[1]: Dependency failed for File System Check
> on /dev/disk/by-label/NAS-BOOT.
> Oct 11 12:01:05 NAS systemd[1]: Job
> dev-disk-by\x2dlabel-S3T\x2dDATEN.device/start timed out.
> Oct 11 12:01:05 NAS systemd[1]: Timed out waiting for device
> dev-disk-by\x2dlabel-S3T\x2dDATEN.device.
> Oct 11 12:01:05 NAS systemd[1]: Dependency failed for File System Check
> on /dev/disk/by-label/S3T-DATEN.
> Oct 11 12:01:05 NAS systemd[1]: Job
> dev-disk-by\x2dlabel-S3T\x2dMEDIEN.device/start timed out.
> Oct 11 12:01:05 NAS systemd[1]: Timed out waiting for device
> dev-disk-by\x2dlabel-S3T\x2dMEDIEN.device.
> Oct 11 12:01:05 NAS systemd[1]: Dependency failed for /media/MEDIEN.
> Oct 11 12:01:05 NAS systemd[1]: Dependency failed for File System Check
> on /dev/disk/by-label/S3T-MEDIEN.
> Oct 11 12:01:05 NAS systemd[1]: Job
> dev-disk-by\x2dlabel-NAS\x2dSWAP.device/start timed out.
> Oct 11 12:01:05 NAS systemd[1]: Timed out waiting for device
> dev-disk-by\x2dlabel-NAS\x2dSWAP.device.
> Oct 11 12:01:05 NAS systemd[1]: Timed out waiting for device
> dev-disk-by\x2dlabel-S3T\x2dSWAP.device.
> Oct 11 12:01:05 NAS systemd[1]: Job dev-ttyS0.device/start timed out.
> Oct 11 12:01:05 NAS systemd[1]: Timed out waiting for device
> dev-ttyS0.device.
> Oct 11 12:01:05 NAS systemd[1]: Dependency failed for *Serial Getty on
> ttyS0.*
>
>
> the last message I got on the serial terminal was:
> ng device sys-subsystem-net-devices-eth0.device...
> [ ***] (5 of 7) A start job is running for dev-disk-by\x2dl...14s / 1
> which wasn't readable because of a lot of CR without LF. the syslog
> above tells more about it.
> After this the serial console stops working.
>
>
> attached
> crash.log - the kernel panic that occured while I had network problems
> history.log - /var/log/apt/history.log - I cannot find anything network
> related in there.
>
>
> any idea what the problem is, and how to solve?
>
> thanks for any help,
>
> Jan
>
>
> ps. I did not subscribe the list. Please CC me.
--
Joel Rees
Be careful when you see conspiracy.
Look first in your own heart,
and ask yourself if you are not your own worst enemy.
Arm yourself with knowledge of yourself.
Reply to: