Time to SPEED-UP upload rate

[Draftmancorp]

:scratch
I'm lost with your messages.

So can you post :
- from fvdw-sl assistant do you see your nas ?
- did you install patch03 ?
- currently can you login to the fw web-interface ?

Forbidden:
You don't have permission to access / on this server.
And putty too says access denied after root giveit2me...

This may happen if you have changed some user permissions. But a reboot should restore them

So if you have a shell access, can you post,

Code: Select all

ls -al /tmp/
ls -al /etc/patch_log
plugout check
echo $?

thanks for reply to me jocko :hail
sorry for messages, i was in panic. ok the situation now:

- Yes i see my 2 nas with fvdw-sl assistant-
- Yes i can login in the web interface after the last reboot.
- I don't know about patch 03, the 2 nas are correctly connected over internet but sems there are no update for them in the firmware update page. The patch update page require a file to upload, have you that, can i download it here?

here my code:

Code: Select all

root@Norman_Nas2:/ # ls -al /tmp/
total 24
drwxrwxrwx  6 root   root   4096 2018-01-01 12:00 .
drwxrwxr-x  9 root   sys    4096 2018-01-01 12:00 ..
drwxr-xr-x  2 nobody nobody 4096 2018-01-01 12:00 etc
drwxr-xr-x  2 root   root   4096 2018-01-01 12:00 mnt
drwxr-xr-x  4 root   root   4096 2018-01-01 12:00 usr
drwxr-xr-x  8 root   root   4096 2018-01-01 12:00 var

root@Norman_Nas2:/ # ls -al /etc/patch_log
ls: /etc/patch_log: No such file or directory

root@Norman_Nas2:/ # plugout check
root@Norman_Nas2:/ # echo $?
2
root@Norman_Nas2:/ #

[Jocko]

Hi

Indeed there are at least two issues

root@Norman_Nas2:/ # plugout check
root@Norman_Nas2:/ # echo $?
2

That would mean either you do not have set your user account or badly set either the nas does not have internet access. So seehttps://plugout.net/viewtopic.php?f=7&t=3224

but seems there are no update for them in the firmware update page

It is why patch03 is required with a fresh version 18.2, see https://plugout.net/viewtopic.php?f=3&t=3532

[Draftmancorp]

Hi

Indeed there are at least two issues

root@Norman_Nas2:/ # plugout check
root@Norman_Nas2:/ # echo $?
2

That would mean either you do not have set your user account or badly set either the nas does not have internet access. So seehttps://plugout.net/viewtopic.php?f=7&t=3224

TOOOOP, :doh you right. Now them are set it up correctly with my account information.

but seems there are no update for them in the firmware update page

It is why patch03 is required with a fresh version 18.2, see https://plugout.net/viewtopic.php?f=3&t=3532

All is done, patch 03 uploaded in the nases and upload result successful. :applause Thanks.
Whats next? can i try to set samba 4? or... may explode them all?

[Draftmancorp]

COOOOL, them works!
samba 4 is set up now!
Writing speed is up to an avarage 20mb/s, from before (it was 11/12mb/s).
Is something gooooood!

thanks @jocko

[Draftmancorp]

Hi @jocko ... however, the second nas is quiet strange, after some hours, it become invisible, it dishappear from the network and fvdw assistance can't reach it. No ping from windows, no more web interface. I have mandatory to reboot it switching the back switch off and on. that i don't like it so much.

how could it be? can i send here a log or something? how can i ask the right log to the nas? thanks.

[Draftmancorp]

nothing, after reboot now it continue to be invisible in the local network. sems like its ip configuration is not set correctly at boot... (this sems to me, i don't know if may is this the cause)

[Draftmancorp]

the nas is the same as last adventure: http://plugout.net/viewtopic.php?p=29643#p29643 may you could remember something.
But it never had a problem since now.
Are these few days that it jocking with ip configuration at boot and dishappear from the lan...

EDIT: anyway, i can't reach it any more, this is the 3rd manual reboot... sems it wont' boot properly the lan property... no fvdw-sl asisstant, no ping, no way to reach it...
damn... why? what can i do now? it is in raid6 mode and 7tb/10tb full. there is omething i can do?


EDIT: no way to ping it, 4th reboot... :sob yesterday I transfered a few fils to and from it :sob why today it's doing this?

[Draftmancorp]

Hi
Indeed there are at least two issues...

No way, today too, the nas lights up but remail unpingable, not reachable... I think that the patch 03 may have write something there? and then this happen... becouse this happen just after patch 03 and samba 4 set.
have you a solution for communicate a valid ip config to the nas?

[Draftmancorp]

UPDATE!!!!! :woohoo
moved by disperation, i tried to find anoter similar issue in the forum, i try someting similar but no proper the same, however i tried to follow the step by other users. so

- i performed a standalone kernel load and start, with kirkwood firmware, and the console succesfully upload the file with fvdw standard ip config (192.168.1.252).
- Then i performed ifconfig eth0 but nothing sems wrong...

Code: Select all

root@fvdw-sta-kirkwood:/ # ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:D0:4B:8D:9A:81 
          inet addr:192.168.1.252  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::2d0:4bff:fe8d:9a81/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:253 errors:0 dropped:0 overruns:0 frame:0
          TX packets:368 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:20879 (20.3 KiB)  TX bytes:37147 (36.2 KiB)
          Interrupt:11

- Then i performed ifconfig eth0 192.168.1.188 (where 192.168.1.188 is the correct ip of the nas, the ip that always it have set)
- Then i opened a new windows and connect to remote system 192.168.1.188
- Then i re-performed ifconfig eth0 and see that ip was correct as i set before (192.168.1.188)
- so, i performed a reboot -f

Now, i see the nas and i can enter in the web interface... but i have very very fear that tomorrow it'll do the same thing as yesterday and this morning...

browsing the nas web interface i notice that the samba4 option is again empty:

$matches[2]

If i try to set it to native samba, it response Fail: can not retrieve the package (-99)
I think that something with the firmware or patch 03 is not going well...
Again, in the firmware setting i cannot set my plugout account, that was empty: Fail: Bad plugout account (could not login)
Again, i try to edit time/date with automatic internet ntp address but impossibile aggiornare il campo Server NTP 1: (1)
Sems i can't edit many config...
Initially i think about a lan problem, but the Lan setting sems ok:

Screenshot_2.png

any ideas?

[fvdw]

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