Problem with fvdw-sl 16

[grishin]

@grishinThe output of dmesg on your box is different and looks normal with the exception that the ethernet settings seems to be modified is this be purpose? Did you change the setting?

Hm, maybe I had created the problem, but everything worked fine on lacie firmware :dontknow
ethernet setting
flow control rx&tx enabled (further +)
interrupt moderation +
ip checksum offload -
Jumbo Packet 9014 bytes
Large Send Offload v1 (ipv4) +
Large Send Offload v2 (ipv4) +
Large Send Offload v2 (ipv6) +
TCP checksum offload (ipv4) rx&tx +
TCP checksum offload (ipv6) rx&tx +
UDP checksum offload (ipv4) rx&tx +
UDP checksum offload (ipv6) rx&tx +
boot.log

Code: Select all

start boot log
detect and set platform
2big1
UIMAGE-3142-2BIG1-6
2big1
 mount dev/pts
update dev nodes
booting using sda1 root file system...
make dev node for buttons...
make dev node for tun device...
enable IP forwarding...
start buttons control daemon
device = 2big1
source = buttons-nwsp2
buttons-nwsp2 daemon started
Sat Nov  5 23:04:13 YEKT 2016
create temporary passwd file
run udevstart to update dev nodes when necessary
inserting kernel modules:
modprobe: module 'xor.ko' not found
create temporary group file
configure loopback network interface
setting reboot and standby
2big1
rebootd-isp1
2big1
standbyd-isp1
starting php based setup routines step 1

 * Found XML database configuration file...    [ OK ]
 * Starting udevd...                 [ OK ]
 * Finishing restore RAID devices...     [ OK ]
 * Updating Disks database...           [ OK ]
 * Starting mount of volumes...
   - Mounting volume Vol-A:  [ OK ]
   - Mounting volume Vol-B:  [ OK ]
 * Finishing mount of volumes...        [ OK ]
 * Generating Hosts File...           [ OK ]
 * Configuring System Hostname...        [ OK ] 
 * Configuring LAN interface...        [ OK ]
 * Initializing Timezone...           [ OK ]
 * Starting web server...              [ OK ]
 * Starting mount of internal USB ...
 * Finishing mount internal USB ...     [ OK ]
 * Configuring Disks...              [ OK ]
 * Configuring Samba...                [ OK ]
 * Configuring System Users...
   Root password: use default password
   Set users, linux and samba accounts    [ OK ]
 * Starting Fvdw-sl Discovery Daemon...    [ OK ]
start rpcbind service
starting php based setup routines step 2
 * Starting dropbear...              [ OK ]
 * Kill temporary dropbear...          [ OK ]
starting php based setup routines step 3
 * Starting NFS Server...              [ OK ]
 * Starting daemon update Hosts File...  [ OK ]
 * Starting Disk Temperature Guard...     [ OK ]
 * Starting mount of remote shares...
 * Finishing mount shares...           [ OK ]
 * Starting FTP Service...              [ FAIL ]
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.3 (static)

    Port configuration:

    LAN   -> eth0
php based setup routines finished
web permission on resolv.conf
set device tuning for dms performance
move some smbd en nmbd db files from to prevent samba issue when copying large amounts of files (more then 50 thousand)
LED settings
else loop1 finished
rcS finished


And what is exactly the problem you have?

i can't copy file from comp to lacie2big because constant error (on screenshot) with file larger 100 mb. Of course, i have free space on disk.

[fvdw]

Does the problem also occur when you do not change the ethernrt settings? My experience with jumbo frames is not positive and always gave problems like transmission errors or even system hanging.
I will post this evening the 2.6.39.4 kernel and modules then you can test if the 3.14 kernel has a problem on the 2big1

[grishin]

Does the problem also occur when you do not change the ethernrt settings? My experience with jumbo frames is not positive and always gave problems like transmission errors or even system hanging.

I restored ethernet setting by default and successful copied file 559 mb. But no, problem is not solved, file 2.11Gb still have problem "not enough space".

[fvdw]

attached a 2.6.39.4 kernel used in the past.
To test you have two option for both you need to install the kernel modules first, for that extract the modules archive in the system root directory, you should have now a folder /lib/modules/2.6.39.4 containing all the modules
Option 1: use the load and start external kernel of the fvdw-sl console (put the kernel first in the tftp folder of the fvdw-sl console)
Option 2: write the kernel to sda6 (dd if=UIMAGE-26394-2BIG1-21 of=/dev/sda6) of course first put the kernel in the system root,
after writing the kernel reboot

Option 1 is preferred for testing, if the kernel solves your problem then you need to do option 2 to let the firmware use the kernel at each boot automatically.

ps this kernel has no raid support, so if you use that then this kernel is a no go for you
ps1 you will get some error messages of modules that are not found, for testing the ethernet driver these can be ignored, we can solve that later by modifying the insert modules script

[andreid]

Hello,
I've restored the 3.14.2 kernel on my box.
No errors in logs (except the xor.ko module), but the transfer errors on big files still exist.

Code: Select all

start boot log
detect and set platform
2big1
UIMAGE-3142-2BIG1-6
Current kernel: 3.14.2 #6 Sat Nov 29 22:15:32 CET 2014
2big1
 mount dev/pts
update dev nodes
booting using  root file system...
make dev node for buttons...
make dev node for tun device...
enable IP forwarding...
start buttons control daemon
device = 2big1
source = buttons-nwsp2
buttons-nwsp2 daemon started
Sun Nov  6 20:26:19 UTC 2016
create temporary passwd file
run udevstart to update dev nodes when necessary
inserting kernel modules:
modprobe: module 'xor.ko' not found
create temporary group file
configure loopback network interface
setting reboot and standby
2big1
rebootd-isp1
2big1
standbyd-isp1
starting php based setup routines step 1

 * Starting udevd...                 [ OK ]
 * Found XML database configuration file...    [ OK ]
 * Finishing restore RAID devices...     [ OK ]
 * Updating Disks database...           [ OK ]
 * Starting mount of volumes...
   - Mounting volume Vol-A:  [ OK ]
 * Finishing mount of volumes...        [ OK ]
 * Generating Hosts File...           [ OK ]
 * Configuring System Hostname...        [ OK ] 
 * Configuring LAN interface...        [ OK ]
 * Initializing Timezone...           [ OK ]
 * Starting web server...              [ OK ]
 * Starting mount of internal USB ...
 * Finishing mount internal USB ...     [ OK ]
 * Configuring Disks...              [ OK ]
 * Configuring Samba...                [ OK ]
 * Configuring System Users...
   Root password: use default password
   Set users, linux and samba accounts    [ OK ]
 * Starting Fvdw-sl Discovery Daemon...    [ OK ]
start rpcbind service
starting php based setup routines step 2
 * Starting dropbear...              [ OK ]
 * Kill temporary dropbear...          [ OK ]
starting php based setup routines step 3
 * Starting daemon update Hosts File...  [ OK ]
 * Starting mount of remote shares...
 * Finishing mount shares...           [ 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.10.202 (DHCP)

    Port configuration:

    LAN   -> eth0
php based setup routines finished
web permission on resolv.conf
set device tuning for dms performance
LED settings
else loop1 finished
rcS finished


I'm using raid 1, so the 2.6.39.4 kernel it's not an option for me.
When I'm testing with a non-fvdw 2.6.38 kernel, everything works as it should.

[fvdw]

I could recompile 2.6.39.4 kernel with raid support I will look at that. Were did you found the 2.38 kernel?

[andreid]

Hi fvdw,
I found the 2.6.38 kernel on http://lacie-nas.org/, ftp downloads: ftp://lacie-nas.org/kernel/.
I'll be glad if you could compile the 2.6.39 fvdw kernel with raid support.
Thank you!

[fvdw]

thhx, I quickly looked at that kernel it supports raid but only raid 0 and 1.
I will try to compile the 2.6.39.4 kernel to add raid support but that will be not on short notice

It remains strange that the 3.14.2 kernel has a problem as we use it also on the kirkwood devices, it uses the same code for the ethernet driver...maybe I need to double check the configuration

[grishin]

attached a 2.6.39.4 kernel used in the past.Option 1 is preferred for testing, if the kernel solves your problem then you need to do option 2 to let the firmware use the kernel at each boot automatically.

I could not use fvdw-sl console 6 for load&start external kernel (process starting, but tftp not send file & not load), but fvdw-sl console 5.5 work fine. Result - with kernel 2.6.39.4 bigfile copy without problem except for slow speed ~9,4 MB/sec, on lacie firmware with jumbo packet 9014 average speed 16-17 MB/sec.
Waiting fix sometime, if you have freetime :snicker

[fvdw]

attached a new 2.6.39.4 kernel with raid support (after loading the right modules) and the corresponding modules
You can keep using the 3.14.2 insert-modules script although some modules will not load as they are in this kernel already included. it concerns the ehci usb driver and usb mass storage driver.
In this kernel xor module must be loaded, but that command is present in insert-modules script.
The modules archive can be extracted in system root folder

Please test