Time to SPEED-UP upload rate

[Draftmancorp]

Why do you want to use a manual set ip address?
Seems your firmware might be corrupt. What version are you running? Also it seems your nas doesn't have access to the internet.
Do you have ssh access? If yes post output of

Code: Select all

cat boot.log

hi jocko, i want my nases in static ip becouse of i use many times the web interface and some shared folder in windows that ise \\IPADDRESS. Then i like to have all devices with a fixed ip in the office, so, in order. (and, if you remember, my nas have a problem with dhcp ip configuration at boot)
Yes ... sems that after loaded the standalone kernel and set ip via telnet many hours ago, now it working well... but i don't trust in it :-D

here the log:

Code: Select all

login as: root
root@192.168.1.188's password:
root@Norman_Nas2:/ # cat boot.log
start boot log
is a physical machine
detect and set platform
5big2
kirkwood
UIMAGE-414133-KIRKWOOD-1
Current kernel: 4.14.133 #1 PREEMPT Wed Jul 17 14:46:56 CEST 2019
device 5big2
family kirkwood
 mount dev/pts
update dev nodes
booting using sda1 root file system...
enable IP forwarding...
run udevstart to update dev nodes when necessary
inserting kernel modules:
modprobe: module 'iscsi_trgt' not found
start buttons control daemon
device = 5big2
source = buttons-nwsp2
buttons-nwsp2 daemon started
Keep old Min free memory=2856
initializing date
Mon Jan  1 12:00:00 CET 2018
configuration partition is rightly mounted
create temporary passwd file
create temporary group file
set samba environment for version 4.x
configure loopback network interface
setting reboot and standby
5big2
rebootd-nwsp2
5big2
standbyd-nwsp2
start fan
starting php based setup routines step 1
 * Initialize the volatile db file...    [ OK ]
 * Starting udevd...                                     [ OK ]
 * Starting RAID monitor:                                [ OK ]
 * Starting restore RAID devices...
   - Assembling device /dev/md0:  [ OK ]
 * Finishing restore RAID devices...     [ OK ]
 * Found database configuration file...  [ OK ]
 * Updating Disks database...                    [ OK ]
 * Starting mount of volumes...
   - Mounting volume 5BIG2:  [ 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 DDNS Service...                      [ 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 mount of remote shares...
 * Finishing mount shares...                     [ OK ]
 * Starting FTP Service...                               [ OK ]
 * Starting Minidlna Server...                   [ FAIL ]
starting php based setup routines step banner


*** fvdw-sl NAS firmware
    This is fvdw-sl version: fvdw-sl 18.2 patched
    built on: October 18 2019

    LAN IP address: 192.168.1.188 (static)

    Port configuration:

    LAN   -> eth0
php based setup routines finished
web permission on resolv.conf
set device tuning for dms performance
move smbd en nmbd db files away from ram disk to prevent hanging samba server
LED settings
else loop1 finished
rcS finished
root@Norman_Nas2:/ #


do you see something wrong?

[Jocko]

Hi

You lost me again...

Yes ... sems that after loaded the standalone kernel and set ip via telnet many hours ago, now it working well... but i don't trust in it

use fvdw-sl console and a static ip on a regular booting is not related :scratch

on fvdw-sl console, the standalone kernel set itself an ip (in your case 192.168.1.252) and when you reboot it it is the firmware which set manually your static ip (so 192.168.1.188).

if now you can get an access is not related to your previous fvdw-sl console use. In my opinion there is an hardware issue with the nas iface

[Draftmancorp]

Hi

You lost me again...

Yes ... sems that after loaded the standalone kernel and set ip via telnet many hours ago, now it working well... but i don't trust in it

use fvdw-sl console and a static ip on a regular booting is not related :scratch
on fvdw-sl console, the standalone kernel set itself an ip (in your case 192.168.1.252) and when you reboot it it is the firmware which set manually your static ip (so 192.168.1.188).
if now you can get an access is not related to your previous fvdw-sl console use. In my opinion there is an hardware issue with the nas iface

Yes i know about 192.168.1.252, i mean that thankfully that procedure i was able to connect to it and perform a "ifconfig eth0 192.168.1.188", now i can use again my nas reaching it to 192.168.1.188.
I really didn't find another way to connect to it, no ping, no web interface, no ssh.
After that, it become again pingable and reachable.

Do you thinking that this could be a HW problem ... really?

[Jocko]

i mean that thankfully that procedure i was able to connect to it and perform a "ifconfig eth0 192.168.1.188", now i can use again my nas reaching it to 192.168.1.188

It is where you lost me. If you did that from fvdw-sl console, then when you reboot the nas you lost your change. then according with your output

Code: Select all

login as: root
root@192.168.1.188's password:
root@Norman_Nas2:/ #

that means later the firmware succeeded to set itself this Ip

[Draftmancorp]

i mean that thankfully that procedure i was able to connect to it and perform a "ifconfig eth0 192.168.1.188", now i can use again my nas reaching it to 192.168.1.188

It is where you lost me. If you did that from fvdw-sl console, then when you reboot the nas you lost your change. then according with your output

Code: Select all

login as: root
root@192.168.1.188's password:
root@Norman_Nas2:/ #

that means later the firmware succeeded to set itself this Ip

:shocked damn... well, I thought I did something super smart, instead, is like that i did nothing becouse after reboot the command that i performed were ignored?
oh man...

ok, so i think i need to see how it work next days, becouse i do a schedule power off at 01:00 and power on at 07:00.
Tomorrow see if it boot up with ip or not...
in case, have you idea how to check if something not working properly?