After power Black out

[araldo60]

Jocko wrote this.

So it seems after removing sda1boot, you succeeded to reboot and upgrade again the fw from its web-interface !
Can you confirm that point please

Please answer the question otherwise we can not help you any further, thank you

And I have one more for you, does the fvdw-sl webinterface works, it must otherwise how do you use the web-console, it must ne used from within the webinterface

yes after jocko write i repeat and post all. All command execution goes well .......
if i understand well what are you writing about fwdw-sl works
and i using web console inside fwdw-sl to do the command suggested.

you can found the command execution in the post before

root@Lacie-2-Big.local /$ ls /sda7/lacie-boot
sda1boot
root@Lacie-2-Big.local /$ cat /sda1/boot.log
start boot log
is a physical machine
detect and set platform
2big2
kirkwood
UIMAGE-414133-KIRKWOOD-1
Current kernel: 4.14.133 #1 PREEMPT Wed Jul 17 14:46:56 CEST 2019
2big2
kirkwood
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...
run udevstart to update dev nodes when necessary
inserting kernel modules:
modprobe: module 'iscsi_trgt' not found
start buttons control daemon
device = 2big2
source = buttons-nwsp2
buttons-nwsp2 daemon started

[fvdw]

It seems to be difficult for you to answer the questions. So again.

Jocko wrote this.

So it seems after removing sda1boot, you succeeded to reboot and upgrade again the firmware from its web-interface !
Can you confirm that point please

So
1. Did you remove the file sda1boot ?
2. Did you get after removing sda1boot and performinga reboot an older version of fvdw-sl firmware?
3. If that was the case did you upgrade again to the latest version?
4. Does the webinterface of fvdw-sl firmware works?
Please answer these questions :tapfoot

[araldo60]

It seems to be difficult for you to answer the questions. So again.

Jocko wrote this.

So it seems after removing sda1boot, you succeeded to reboot and upgrade again the firmware from its web-interface !
Can you confirm that point please

So
1. Did you remove the file sda1boot ?
2. Did you get after removing sda1boot and performinga reboot an older version of fvdw-sl firmware?
3. If that was the case did you upgrade again to the latest version?
4. Does the webinterface of fvdw-sl firmware works?
Please answer these questions :tapfoot

yes removed
yes rebooted try to access with older version without result
yes upgrade again same result no access
yes the frimware works in any case older and last version

[fvdw]

try to access with older version

What did you try to access?

[araldo60]

try to access with older version

What did you try to access?

try to access with mac at folder

[fvdw]

So summarizing,
Nas boots normally an web interface is working

In the web interface what do you see as size of available disk space and free disk space?

[araldo60]

So summarizing,
Nas boots normally an web interface is working

In the web interface what do you see as size of available disk space and free disk space?

Total memory : 3720.13 GB
Memory avaible:: 3548.89 GB

the nas setting is with static ip address
trasmission protocol is normally operating
plex media server is working but web interface not found server
under mac i see server on line but when i try connect after few seconds say connection failed
user connection is admin for folder i try to create user any difference

[fvdw]

With "memory" I assume you mean disk space, correct?

Do you have started the afp server ?
If you cannot connect with your mac. It means either you use wrong credentials or afp access is not enable for the folder. You can check that in web interface in shared folder menu an user menu

[Jocko]

Hi,

Enable afp server is useful only for old Mac version. But you should at least enable zeroconf service.

[araldo60]

With "memory" I assume you mean disk space, correct?

Do you have started the afp server ?
If you cannot connect with your mac. It means either you use wrong credentials or afp access is not enable for the folder. You can check that in web interface in shared folder menu an user menu

yes is disk space

is the first thing that i ask how to restart service or check

but i have a question if the afp service is open before why after blackout is not open ???