No Shares management from Dashboard

[carloph]

dear Jocko,

I apologize for a so long exchange of emails (sometimes not well understood&answered from myself): I didn't imagine that the NAS mngt was so complicated :scratch I hope that in future something will be solve d

I just made a small donation for all your support up to now, thanks

Good Easther

[Jocko]

Hi carloph,

I am sorry but last days I could not browse our site (health issues).

You did not follow my last post and you destroyed the symlink. Tomorrow, I go to post commands for restoring it

[carloph]

Dear Jocko,

thanks for the reply.

I checked from Lacie fw and from fvdw and these are the output:

From fvdw

Code: Select all

root@fvdw-sta-kirkwood:/ # ls -la /md1/etc/uni*
lrwxrwxrwx    1 root     root            29 Jul 31  2013 /md1/etc/unicorn.conf -> /usr/lib/unicorn/unicorn.conf
-rw-rw-r--    1 root     root         16838 Mar 28 12:35 /md1/etc/unicorn.conf.org
-rw-rw-r--    1 root     root          1732 Dec 12  2011 /md1/etc/unicorn.prod
root@fvdw-sta-kirkwood:/ #

root@fvdw-sta-kirkwood:/ # ls -la /md1/usr/lib/unicorn/uni*
-rw-rw-r--    1 root     root           796 Mar 19  2009 unicorn-desktop.conf
-rw-rw-r--    1 root     root          1603 Aug 25  2010 unicorn-test-dbus.conf
-rw-rw-r--    1 root     root         16837 Mar 28 12:23 unicorn.conf
-rw-rw-r--    1 root     root         16840 Nov 23  2011 unicorn.conf.org
root@fvdw-sta-kirkwood:/ #


from Lacie

Code: Select all

ls -la /etc/unicorn.conf*
-rw-rw-r--    1 root     root         16840 Mar 02  2012 07:50 unicorn.conf
-rw-rw-r--    1 root     root         16838 Mar 28  2018 12:35 unicorn.conf.org
-rw-rw-r--    1 root     root          1732 May 29  2015 22:48 unicorn.prod


As you can see

1) the symlink in fvdw is still there, but not in Lacie
2) the other files have different timestamps

Thanks

[Jocko]

Hi carloph,

What do you mean by "From Lacie" :scratch
I did not notice previously you mentioned it on some posts

[carloph]

It means that loading the Lacie fw i can download, from the Dashboard, the log files including the etc and var directories

[Jocko]

Hi carloph,

Here additional information a bout symlink :
- last modification time is the created time of a symlink and not time of the last change of the target. So time on /md1/etc/unicorn.conf won't change as long as you do not delete it and recreate it
- I am pretty sure Lacie interface returns a fake real list on fs folder (so eg. on /etc) and does not return information about the symlink. So you can not use this way to valid the change.

then I tfpd the file /md1/usr/lib/unicorn/unicorn.conf
I changed the ssh content
and then tfpd it back to /md1/etc

You did not follow my last commands and when you did "then tfpd it back to /md1/etc" tftp uploaded the edited file toward the folder /usr/lib which is the file system loaded on the memory. So you lost it when you reboot the nas. You need to work in the folder /md1/usr/lib !

So do my commands from this post:https://plugout.net/viewtopic.php?f=26&t=2842&start=40#p27017

[carloph]

Dear Jocko,

thanks for your reply, I did as you suggest me:

Code: Select all

cd /md1/usr/lib
cp unicorn.conf unicorn.conf.org (this time you really made a backup on the raid)
tftp -l unicorn.conf -r unicorn.conf -g ip-pc

but SSH still not working (port 2222 not opened)

Here is the listing

Code: Select all

root@fvdw-sta-kirkwood: # ls -la /md1/usr/lib/unicorn/unicorn.conf*
-rw-rw-r--    1 root     root         16922 Apr 17 14:48 unicorn.conf
-rw-rw-r--    1 root     root         16840 Nov 23  2011 unicorn.conf.org

cat /md1/usr/lib/unicorn/unicorn.conf
......
        ssh:
            _config:
                enabled: true
                port: 2222
.....

[Jocko]

Ok carloph, the issue seems to be beyond my understanding...

I go to send a pm to Mijzlef to confirm some points. :scratch

[Mijzelf]

Lacie uses a layered filesystem. On a single disk box sda7 contains a temporary rootfs, which contains the tool to assemble a layered filesystem of sda8 and sda9/snaps/*.
sda8 is read-only, and contains the original firmware, sda9/snaps contains the changes to the original files, for instance by later firmware updates. Together they contain the running rootfs.
All directories in sda9/snap are added to the layer, and only the last can be changed by the OS, when running.

That means that if the layered rootfs consists of sda8+sda9/snaps/00+sda9/snaps/01+sda9/snaps/02, and both sda8 and sda9/snaps/01 contain a copy of a certain file, you'll see the one in sda9/snaps/01. And if you edit the file from the Lacie OS, the changes are written to sda9/snaps/02.

So in your case, all edits have to be done to the last copy of a file in snaps, else it won't work. The strange timestamps might be due to bugs in the layered filesystem. If you read a file, it has to parse all layers until it finds the most upper copy. For directories containing the timestamps, it has to merge all directories on all layers, as the actual files can be in different layers. It's easy to have a bug there.

[carloph]

Thanks for the explanation.

Do you have some suggestion or it remains only to fully reset/restore ?