Kernel #14 update - 5bigN2 unavailable

[Jocko]

So with this clean state, do:

- store the tar file in the share fvdw
- install the new file

tar -xzvf /direct-usb/fvdw/laniffunc_set_bonding.tar -C /etc/finc

- redo this sequence

Then in a Terminal window do
0/ 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

Then post here the content of messages


Note: when you enable/disable bonding feature, the web interface is hanged after submitting as the route used to submit is lost => you need to reload the web-interface

[macdalor]

So with this clean state, do:

- store the tar file in the share fvdw
- install the new file

tar -xzvf /direct-usb/fvdw/laniffunc_set_bonding.tar -C /etc/finc

Sorry but unless I misunderstood I do not have the "laniffunc_set_bonding.tar". The file you sent me is a .zip file that contains a "patch.tar" and a "md5" file...

Have I missed something?

[Jocko]

I attached later the file so it is available in my previous post

[fvdw]

I checked this function on my 5big2

the bonding is working normally and bonding module is loaded.

Code: Select all

root@fvdwsl-5big2:/ # lsmod
Module                  Size  Used by
8712u                 352203  0
bonding                95195  0
iscsi_tcp               7948  0
libiscsi_tcp           11247  1 iscsi_tcp
libiscsi               32040  2 libiscsi_tcp,iscsi_tcp
scsi_transport_iscsi    61216  2 iscsi_tcp,libiscsi
iscsi_trgt             99022  0
usblp                   9949  0
usb_storage            36889  0
ehci_orion              2686  0
ehci_hcd               39419  1 ehci_orion
root@fvdwsl-5big2:/ #

the laniffunc_xx_bonding.finc files are all from 6 sept 15

the web interface responds normally

Code: Select all

root@fvdwsl-5big2:/ # uname -a
Linux fvdwsl-5big2.local 3.14.2 #14 PREEMPT Sun Jan 17 20:40:19 CET 2016 armv5tel unknown unknown GNU/Linux
root@fvdwsl-5big2:/ #

[fvdw]

@jocko

output from dmesg when switching from status equally ditributed to use lan 2 if lan1 fails

at boot with distribute load mode

Code: Select all

[   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.210492] mv643xx_eth_port mv643xx_eth_port.0 eth0: link down
[   64.216497] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   64.223130] bonding: bond0: enslaving eth0 as an active interface with a down                            link.
[   65.021866] bonding: bond0: Adding slave eth1.
[   66.102690] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[   66.109311] bonding: bond0: enslaving eth1 as an active interface with a down                            link.
[   66.763099] IPv6: ADDRCONF(NETDEV_UP): bond0: link is not ready
[   67.165052] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, ful                           l duplex, flow control disabled
[   67.260871] bonding: bond0: link status definitely up for interface eth0, 100                           0 Mbps full duplex.
[   67.269635] bonding: bond0: first active interface up!
[   67.280871] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready


then switching mode to use lan2 if lan1 fails

Code: Select all

[  557.551991] bonding: bond0: Removing slave eth0.
[  557.556701] bonding: bond0: releasing active interface eth0
[  557.562304] bonding: bond0: Warning: the permanent HWaddr of eth0 - 00:d0:4b:                           93:07:72 - is still in use by bond0. Set the HWaddr of eth0 to a different addre                           ss to avoid conflicts.
[  557.622081] bonding: bond0: Removing slave eth1.
[  557.626788] bonding: bond0: releasing active interface eth1
[  557.672106] bonding: bond0 is being deleted...
[  557.677112] bonding: bond0: released all slaves
[  557.761776] bonding: bond0 is being created...
[  557.846741] bonding: bond0: Setting MII monitoring interval to 100.
[  557.873335] bonding: bond0: Recording eth0 as primary, but it has not been en                           slaved to bond0 yet.
[  558.180271] bonding: bond0: Adding slave eth0.
[  559.265010] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  559.271663] bonding: bond0: enslaving eth0 as a backup interface with a down                            link.
[  560.090332] bonding: bond0: Adding slave eth1.
[  561.172317] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[  561.178928] bonding: bond0: enslaving eth1 as a backup interface with a down                            link.
[  561.729183] IPv6: ADDRCONF(NETDEV_UP): bond0: link is not ready
[  565.904002] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, ful                           l duplex, flow control disabled
[  565.920957] bonding: bond0: link status definitely up for interface eth0, 100                           0 Mbps full duplex.
[  565.929703] bonding: bond0: making interface eth0 the new active one.
[  565.936252] bonding: bond0: first active interface up!
[  565.941525] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
root@fvdwsl-5big2:/ #


looks normal to me

[Jocko]

Yes fvdw, these 2 outputs are ok.
When you change the bond mode, several steps (reset iface and bring up/down) must be done on the slaves to avoid to have some orphan routes

[macdalor]

@Jocko, sorry but I had to reboot the NAS once I modified the bonding status as the NAS got stuck after I tried to reload it (as you mentioned in your post)...
I'll try again now...
It seems my NAS has got loads of issues since everything's working fine with fvdw...maybe something deeper than OS/Firmware/Kernel related...?

[macdalor]

Screen Shot 2016-01-20 at 20.24.13.png

hanging there :(

Code: Select all

root@lacie5big:/ # cat /var/log/messages

Jan 20 20:16:08 kirkwood syslog.info syslogd exiting
Jan 20 20:16:08 lacie5big syslog.info syslogd started: BusyBox v1.21.0
Jan 20 20:16:18 lacie5big local0.warn API[2016/01/20 20:16:18] nasapi.inc(36)[2249]: nasapi: lock time = 0
Jan 20 20:16:19 lacie5big local0.warn API[2016/01/20 20:16:19] nasapi.inc(46)[2249]: calling mrvlGetPlatForm
Jan 20 20:16:19 lacie5big local0.warn API[2016/01/20 20:16:19] nasapi.inc(670)[2249]: mrvlGetPlatForm Return Code: 5big2
Jan 20 20:16:19 lacie5big local0.warn API[2016/01/20 20:16:19] nasapi.inc(36)[2249]: nasapi: lock time = 0
Jan 20 20:16:19 lacie5big local0.warn API[2016/01/20 20:16:19] nasapi.inc(46)[2249]: calling mrvlSetBondingMode 1
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
Jan 20 20:16:19 lacie5big local2.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/sbin/modprobe bonding
Jan 20 20:16:19 lacie5big local0.warn API[2016/01/20 20:16:19] laniffunc_set_bonding.finc(21)[2249]: laniffunc_set_bonding: /sbin/modprobe bonding FAILED!
Jan 20 20:20:45 lacie5big syslog.info syslogd exiting

[Jocko]

Well, I think the best think to do is to reinstall firmware version 16.1:

- unplug your hfs
- reboot the nas
- load the web interface
- in "firmware upgrade menu" install again version 16.1
- install all patches for 16.1 and also this one sent by pm (no need to install again this patch viewtopic.php?f=7&t=2314)
- install again the last kernel version (fvdw's post)
- reboot the nas

- try to enable bonding

Note: lan setup menu is hanged only when you use static Ip and change it so as written by fvdw, the menu must not be hanged enabling/disabling bonding

[macdalor]

ok...I let you know once it's done