Kernel #14 update - 5bigN2 unavailable

[fvdw]

seems the problem is caused by this

Code: Select all

Jan 20 20:16:19 lacie5big local0.warn API[2016/01/20 20:16:19] laniffunc_set_bonding.finc(15)[2249]: laniffunc_set_bonding: bonding_masters file not found

it means the initialization script dit not find this file

Code: Select all

/sys/class/net/bonding_masters

the question is now why is this file missing (it is created by the kernel) :scratch

[macdalor]

the good news about this is that the issue isn't related to my NAS :-D

currently installing the patches...

[fvdw]

if you have booted the new kernel
can you post the output of this command

Code: Select all

dmesg | grep bonding

on my 5big2 it gives this result

Code: Select all

root@fvdwsl-5big2:/ # dmesg | grep bonding
[   62.647687] bonding: Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
[   62.717461] bonding: bond0 is being deleted...
[   62.722148] bonding: bond0: released all slaves
[   62.779754] bonding: bond0 is being created...
[   62.844982] bonding: bond0: Setting MII monitoring interval to 100.
[   63.131815] bonding: bond0: Adding slave eth0.
[   64.223130] bonding: bond0: enslaving eth0 as an active interface with a down link.
[   65.021866] bonding: bond0: Adding slave eth1.
[   66.109311] bonding: bond0: enslaving eth1 as an active interface with a down link.
[   67.260871] bonding: bond0: link status definitely up for interface eth0, 1000 Mbps full duplex.
[   67.269635] bonding: bond0: first active interface up!


[Jocko]

@fvdw
Be careful, you misunderstand this warning, I added it in the debug version of laniffunc_set_bonding.finc. This goal is to trace the firmware did not find the file and then need to load the bonding module.
So in this verbose version is ok.

@macdalor
Sorry but you still need to reinstall version 16.1

[macdalor]

@macdalor
Sorry but you still need to reinstall version 16.1

yep...work in progress ;)

[macdalor]

Reinstalled 16.1 / all patches / kernel #14 -> ok
tried bonding -> error msg: "Fail : Can't set the asked bonding mode!"
the "dmesg | grep bonding" command doesn't return anything... :hammerhead

[Jocko]

At least it is a better web-interface behaviour !

So try again with this sequence

/ load the web-interface

1/

Code: Select all

echo > /var/log/messages
/etc/nas_status.sh --start-debug

2/ try to enable bonding feature (do nothing else in the web interface)

3/ stop debug mode, and read log file

Code: Select all

/etc/nas_status.sh --stop-debug
cat /var/log/messages

[fvdw]

did the bonding work with the old kernel ?

seems something in your hardware prevents the bonding driver from loading

[Jocko]

Yes fvdw, it worked, in an output on nas-central.org, you can note

Code: Select all

* Configuring Bonding interface...       [ OK ]
 * Configuring LAN interface...            [ OK ]

......

starting php based setup routines step banner

*** fvdw-sl NAS firmware

    This is fvdw-sl version: fvdw-sl 16.1 patched

    built on: Oct 01 2015

    LAN IP address: 192.168.1.41 (DHCP)

    Port configuration:

    LAN   -> bond0

So we can be sure there is no hardware issue

[macdalor]

it started misbehaving again once debug activated but here is the result while hanged ...

Code: Select all

root@lacie5big:/ # echo > /var/log/messages
root@lacie5big:/ # /etc/nas_status.sh --start-debug
root@lacie5big:/ # etc/nas_status.sh --stop-debug
root@lacie5big:/ # cat /var/log/messages

Jan 20 21:59:31 lacie5big syslog.info syslogd started: BusyBox v1.21.0
Jan 20 21:59:41 lacie5big local0.warn API[2016/01/20 21:59:41] nasapi.inc(36)[1500]: nasapi: lock time = 0
Jan 20 21:59:41 lacie5big local0.warn API[2016/01/20 21:59:41] nasapi.inc(46)[1500]: calling mrvlGetPlatForm
Jan 20 21:59:41 lacie5big local0.warn API[2016/01/20 21:59:41] nasapi.inc(670)[1500]: mrvlGetPlatForm Return Code: 5big2
Jan 20 21:59:41 lacie5big local0.warn API[2016/01/20 21:59:41] nasapi.inc(36)[1500]: nasapi: lock time = 0
Jan 20 21:59:41 lacie5big local0.warn API[2016/01/20 21:59:41] nasapi.inc(46)[1500]: calling mrvlGetNetworkSetting
Jan 20 21:59:41 lacie5big local0.warn API[2016/01/20 21:59:41] nasapi.inc(667)[1500]: mrvlGetNetworkSetting Return Code: Array():if => eth0...
Jan 20 21:59:41 lacie5big local0.warn API[2016/01/20 21:59:41] nasapi.inc(36)[1500]: nasapi: lock time = 0
Jan 20 21:59:41 lacie5big local0.warn API[2016/01/20 21:59:41] nasapi.inc(46)[1500]: calling mrvlGetSystemName
Jan 20 21:59:41 lacie5big local0.warn API[2016/01/20 21:59:41] nasapi.inc(670)[1500]: mrvlGetSystemName Return Code: lacie5big
Jan 20 21:59:41 lacie5big local0.warn API[2016/01/20 21:59:41] nasapi.inc(36)[1500]: nasapi: lock time = 0
Jan 20 21:59:41 lacie5big local0.warn API[2016/01/20 21:59:41] nasapi.inc(46)[1500]: calling mrvlGetDDNSStatus
Jan 20 21:59:41 lacie5big local0.warn API[2016/01/20 21:59:41] nasapi.inc(670)[1500]: mrvlGetDDNSStatus Return Code: 0
Jan 20 21:59:41 lacie5big local0.warn API[2016/01/20 21:59:41] nasapi.inc(36)[1500]: nasapi: lock time = 0
Jan 20 21:59:41 lacie5big local0.warn API[2016/01/20 21:59:41] nasapi.inc(46)[1500]: calling mrvlGetDDNSProviders
Jan 20 21:59:41 lacie5big local0.warn API[2016/01/20 21:59:41] nasapi.inc(667)[1500]: mrvlGetDDNSProviders Return Code: Array():dyndns => http://www.dyndns.com/...
Jan 20 21:59:41 lacie5big local0.warn API[2016/01/20 21:59:41] nasapi.inc(36)[1500]: nasapi: lock time = 0
Jan 20 21:59:41 lacie5big local0.warn API[2016/01/20 21:59:41] nasapi.inc(46)[1500]: calling mrvlGetDDNSConf
Jan 20 21:59:41 lacie5big local0.warn API[2016/01/20 21:59:41] nasapi.inc(667)[1500]: mrvlGetDDNSConf Return Code: Array():service => ...
Jan 20 21:59:41 lacie5big local0.warn API[2016/01/20 21:59:41] nasapi.inc(36)[1500]: nasapi: lock time = 0
Jan 20 21:59:41 lacie5big local0.warn API[2016/01/20 21:59:41] nasapi.inc(46)[1500]: calling mrvlSetDDNSSuccess
Jan 20 21:59:45 lacie5big local2.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/bin/ps -ef
Jan 20 21:59:45 lacie5big local0.warn API[2016/01/20 21:59:45] nasapi.inc(670)[1500]: mrvlSetDDNSSuccess Return Code: 11
Jan 20 21:59:45 lacie5big local0.warn API[2016/01/20 21:59:45] nasapi.inc(36)[1500]: nasapi: lock time = 0
Jan 20 21:59:45 lacie5big local0.warn API[2016/01/20 21:59:45] nasapi.inc(46)[1500]: calling mrvlGetDDNSStatus
Jan 20 21:59:45 lacie5big local0.warn API[2016/01/20 21:59:45] nasapi.inc(670)[1500]: mrvlGetDDNSStatus Return Code: 0
Jan 20 21:59:45 lacie5big local0.warn API[2016/01/20 21:59:45] nasapi.inc(36)[1500]: nasapi: lock time = 0
Jan 20 21:59:45 lacie5big local0.warn API[2016/01/20 21:59:45] nasapi.inc(46)[1500]: calling mrvlGetEthStatus
Jan 20 21:59:45 lacie5big local0.warn API[2016/01/20 21:59:45] nasapi.inc(667)[1500]: mrvlGetEthStatus Return Code: Array():eth0 => Array()...
Jan 20 21:59:45 lacie5big local2.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/bin/ps -ef
Jan 20 21:59:51 lacie5big local0.warn API[2016/01/20 21:59:51] nasapi.inc(36)[1627]: nasapi: lock time = 0
Jan 20 21:59:51 lacie5big local0.warn API[2016/01/20 21:59:51] nasapi.inc(46)[1627]: calling mrvlGetPlatForm
Jan 20 21:59:51 lacie5big local0.warn API[2016/01/20 21:59:51] nasapi.inc(670)[1627]: mrvlGetPlatForm Return Code: 5big2
Jan 20 21:59:51 lacie5big local0.warn API[2016/01/20 21:59:51] nasapi.inc(36)[1627]: nasapi: lock time = 0
Jan 20 21:59:51 lacie5big local0.warn API[2016/01/20 21:59:51] nasapi.inc(46)[1627]: calling mrvlSetBondingMode 1
Jan 20 21:59:51 lacie5big local2.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/sbin/modprobe bonding
Jan 20 21:59:51 lacie5big local0.warn API[2016/01/20 21:59:51] laniffunc_set_bonding.finc(20)[1627]: laniffunc_set_bonding: /sbin/modprobe bonding FAILED!
Jan 20 22:02:32 lacie5big syslog.info syslogd exiting