Recommended Posts

Hi all.

I just bought a Synology DS418 NAS with Realtek RTD1296 CPU. According to this page : Installing Sync on NAS, my NAS architecture is supported; confirmed by the success story of one DS118 user which uses the same architecture in this thread : Synology DS118 (Realtek RTD1296).

However, I've got this problem twice now where my NAS would crash immediately after installing, forcing me to force shutdown the NAS, reboot, and be presented with the Install DSM page afterwards, losing all my settings in the progress. Fortunately my data is intact after rebuild, but the downtime is definitely a problem.

I'm willing to try again to get Sync working or for the sake of troubleshooting, but I won't do the same steps described in the Installing Sync on NAS page above only to get the same result. Any suggestions? Thank you.

Package used : Sync 2.5 packages for DSM 6.0-6.1 for rtd1296 Version 2.5.12-1

DSM version : DSM 6.1.5-15254 dated 2018/01/26

Custom package installed : Download Station and USB Copy.

Share this post


Link to post
Share on other sites

On your NAS check folder /usr/local/resiliosync/ - what you have there? Send its content to tech support. 

After that delete everything from  /usr/local/resiliosync/
attached are the binary and config file from the spk package.

put binary to /usr/local/resiliosync/bin , config - to /usr/local/resiliosync/var and run manually:
./rslsync --config  /usr/local/resiliosync/var/sync.conf

See what error you'll get. You'll need ssh to your NAS.

rslsync

sync.conf

Share this post


Link to post
Share on other sites
23 hours ago, Helen said:

On your NAS check folder /usr/local/resiliosync/ - what you have there? Send its content to tech support.

There is no resiliosync folder as the installation crashed my system.

23 hours ago, Helen said:

After that delete everything from  /usr/local/resiliosync/

Considering this done as the folder didn't exist.

23 hours ago, Helen said:

attached are the binary and config file from the spk package.

put binary to /usr/local/resiliosync/bin , config - to /usr/local/resiliosync/var and run manually:
./rslsync --config  /usr/local/resiliosync/var/sync.conf

I think there is a mistake, I can't access the attached files. Is it because my forum account has less than the required minimum posts/age?

Quote

Sorry, there is a problem

The page you are trying to access is not available for your account.

Error code: 2C171/1

 

23 hours ago, Helen said:

See what error you'll get. You'll need ssh to your NAS.

Not crucial, but can I use the Synology DSM Log Center package instead? Or will it only display the current user's log?

Share this post


Link to post
Share on other sites

I got the files. This is all the output I get :

By using this application, you agree to our Privacy Policy, Terms of Use and End User License Agreement.
https://www.resilio.com/legal/privacy
https://www.resilio.com/legal/terms-of-use
https://www.resilio.com/legal/eula

Resilio Sync forked to background. pid = 8658

No crashes, confirmed by logging out and back in from the Web GUI. But still no Sync app.

 

This is the contents of the /usr/local/resiliosync/var/sync.log

platform: Linux 4.4.15+ #15254 SMP Fri Jan 26 06:41:27 CST 2018 aarch64
version: 2.5.12.1191
[23:56:33.932] VerifyFileWithHash failed on file /usr/local/resiliosync/var/settings.dat with status 2.
[23:56:33.932] VerifyFileWithHash failed on file /usr/local/resiliosync/var/settings.dat with status 2.
[23:56:33.932] VerifyFileWithHash failed on file /usr/local/resiliosync/var/settings.dat with status 2.
[20180219 23:56:33.933] ZIP: Can't locate [version] in zip, error -100.
[20180219 23:56:33.933] I! Configuration from file "/usr/local/resiliosync/var/sync.conf" has been applied
[20180219 23:56:33.937] Directory root is ""
[20180219 23:56:33.937] test sha1: AE2BD7EFDA5522C4E9982D06081A783392A9A442
[20180219 23:56:33.937] test sha2: 630ECD7966D4137655124448CBA21B4DF422B49D332BB2C8CBC1B2581BD910DD
[20180219 23:56:33.937] test aes: 0A949BB2416EF035F1C32458C654EA5A27FEEFB4E1D5136E930EEE818E919292
[20180219 23:56:33.937] diskio_controller created
[20180219 23:56:33.937] VerifyFileWithHash failed on file /usr/local/resiliosync/var/settings.dat with status 2.
[20180219 23:56:33.937] VerifyFileWithHash failed on file /usr/local/resiliosync/var/settings.dat with status 2.
[20180219 23:56:33.937] VerifyFileWithHash failed on file /usr/local/resiliosync/var/settings.dat with status 2.
[20180219 23:56:33.989] register diskio completion queue with id 1
[20180219 23:56:33.989] PLC[0x00000055b8da6580] binding on 0.0.0.0:60446
[20180219 23:56:33.989] D! 20PeerListenConnection::listen[0x00000055b8da6580][8] bound listening socket 8 to IP 0.0.0.0:60446
[20180219 23:56:33.989] PLC[0x00000055b8da9ef0] binding on [::]:60446
[20180219 23:56:33.990] D! 20PeerListenConnection::listen[0x00000055b8da9ef0][9] bound listening socket 9 to IP [::]:60446
[20180219 23:56:33.990] UDP: bound listening socket 10 to IP 0.0.0.0:60446
[20180219 23:56:33.990] UDP: bound listening socket 11 to IP [::]:60446
[20180219 23:56:33.990] D! 20HttpListenConnection::listen[0x00000055b8daa060][14] bound listening socket 14 to IP 0.0.0.0:28888
[20180219 23:56:34.039] register diskio completion queue with id 2
[20180219 23:56:34.041] Create diskio thread for drive with id 5685773939, path: 
[20180219 23:56:34.041] Create diskio thread for drive with id 1913439235, path: 
[20180219 23:56:34.042] diskio thread start, drive_id = 5685773939, priority = normal
[20180219 23:56:34.042] Create diskio thread for drive with id 4798354109, path: 
[20180219 23:56:34.042] diskio thread start, drive_id = 1913439235, priority = normal
[20180219 23:56:34.042] Create diskio thread for drive with id 6625789009, path: 
[20180219 23:56:34.042] diskio thread start, drive_id = 4798354109, priority = normal
[20180219 23:56:34.042] diskio thread start, drive_id = 6625789009, priority = normal
[20180219 23:56:34.042] IPv6 is installed
[20180219 23:56:34.042] VerifyFileWithHash failed on file /usr/local/resiliosync/var/sync.dat with status 2.
[20180219 23:56:34.042] VerifyFileWithHash failed on file /usr/local/resiliosync/var/sync.dat with status 2.
[20180219 23:56:34.042] VerifyFileWithHash failed on file /usr/local/resiliosync/var/sync.dat with status 2.
[20180219 23:56:34.042] Unsupported or empty sync.dat file
[20180219 23:56:34.042] My PeerID: 10DE21F5B05F19008A3225AE6C57BDA531A63B65
[20180219 23:56:34.043] LC: LoadLicenses: there is no pro license
[20180219 23:56:34.043] VerifyFileWithHash failed on file /usr/local/resiliosync/var/history.dat with status 2.
[20180219 23:56:34.043] VerifyFileWithHash failed on file /usr/local/resiliosync/var/history.dat with status 2.
[20180219 23:56:34.043] VerifyFileWithHash failed on file /usr/local/resiliosync/var/history.dat with status 2.
[20180219 23:56:34.043] Joining to the multicast group 239.192.0.0:3838 on interface 192.168.1.4 (bond0)
[20180219 23:56:34.043] Joining to the multicast group 239.192.0.0:3838 on interface 127.0.0.1 (lo)
[20180219 23:56:34.044] Create diskio thread for drive with id 56482912404380324902, path: 
[20180219 23:56:34.044] diskio thread start, drive_id = 56482912404380324902, priority = normal
[20180219 23:56:34.048] Scheduler: Apply global rule, download limit: -1, upload limit: -1
[20180219 23:56:34.048] CoreState: Total memory: 1729716224, used by Sync: 7880704, percentage used: 0.46
[20180219 23:56:34.048] message thread start
[20180219 23:56:35.930] D! 15UpnpFetchSocket::set_error[0x0000007fa0000f50][-1] 111 (Connection refused)
[20180219 23:56:36.049] Debug log mask has been set to FFFFFFFF
[20180219 23:56:36.049] Features mask has been set to 0
[20180219 23:56:42.264] D! 15UpnpFetchSocket::set_error[0x0000007fa0001660][-1] 111 (Connection refused)
[20180219 23:56:46.421] NAT-PMP: Unable to map port with NAT-PMP.
[20180219 23:56:49.410] D! 15UpnpFetchSocket::set_error[0x0000007fa0000f50][-1] 111 (Connection refused)
[20180219 23:56:55.151] D! 15UpnpFetchSocket::set_error[0x0000007fa0003270][-1] 1 (hostname not found)
[20180219 23:56:55.197] D! 15UpnpFetchSocket::set_error[0x0000007fa0003c00][-1] 1 (hostname not found)
[20180219 23:56:55.197] D! 15UpnpFetchSocket::set_error[0x0000007fa00038d0][-1] 1 (hostname not found)
[20180219 23:56:55.197] D! 15UpnpFetchSocket::set_error[0x0000007fa00035a0][-1] 1 (hostname not found)
[20180219 23:56:56.741] D! 15UpnpFetchSocket::set_error[0x0000007fa00033f0][-1] 111 (Connection refused)
[20180219 23:57:05.967] OpenSSL: Loaded X509 trusted CA from "/etc/ssl/certs/ca-certificates.crt"
[23:57:58.560] Debug log mask has been set to FFFFFFFF
[23:57:58.560] Features mask has been set to 0
[20180219 23:57:58.562] ZIP: Can't locate [version] in zip, error -100.
[20180219 23:57:58.562] I! Configuration from file "/usr/local/resiliosync/var/sync.conf" has been applied
[20180220 00:00:01.152] Scheduler: Apply global rule, download limit: -1, upload limit: -1
[20180220 00:01:36.203] CoreState: Total memory: 1729716224, used by Sync: 10088448, percentage used: 0.58

 

The process does show though (Attached).

 

What do I do next?

Process.PNG

Edited by Palthron
Added sync.log

Share this post


Link to post
Share on other sites

Welp, in all my infinite wisdom I decided to try rebooting the NAS. Upon reboot, my volume status is now Crash, and all my data gone.

 

  1. All system settings intact
  2. The NAS log says : Service [Windows file service] failed to start. Please contact Synology support for assistance.

 

I am currently restarting once more for good measure.

Edit : Nope, second restart- same state. Settings intact but my volume crashed.

Share this post


Link to post
Share on other sites
16 hours ago, Palthron said:

The NAS log says : Service [Windows file service] failed to start. Please contact Synology support for assistance.

you know it's not Sync service, right? Just to confirm - when you completely remove Sync from NAS and reboot it, no problem appears, correct? 

Share this post


Link to post
Share on other sites

you know it's not Sync service, right?

I know, I'm just quoting what the log says, in which there is only one entry- the side effect of installing Sync.

 

1 minute ago, Helen said:

Just to confirm - when you completely remove Sync from NAS and reboot it, no problem appears, correct? 

My volume stays crashed.

Share this post


Link to post
Share on other sites
2 hours ago, Palthron said:

My volume stays crashed.

ok. and if you reinstall dsm - it reboots all right until you install Sync. Then the problem reappears. right?
I\m just trying to sort this out. 

Share this post


Link to post
Share on other sites
3 hours ago, Helen said:

ok. and if you reinstall dsm - it reboots all right until you install Sync. Then the problem reappears. right?
I\m just trying to sort this out. 

Yes, exactly

Share this post


Link to post
Share on other sites

interesting, sync is not that privileged in the system so as to be able to crash DSM, especially on a new powerful NAS. 

After the recent test:  /usr/local/resiliosync/ - what you have there? Send its content to tech support. 

Share this post


Link to post
Share on other sites

Sorry for the delay, other stuffs came up.

 

These are the files. Where do I send them?

FileDelayConfig
http.port
storage.db
storage.db-wal
sync.lng
sync.log
syncapp.pid

 

Share this post


Link to post
Share on other sites

Here's the log for my disks

 

[ 4152.881784] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 115133 failed (29793!=0)

[ 4152.890690] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 115134 failed (18577!=0)

[ 4152.899603] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 115135 failed (40128!=0)

Share this post


Link to post
Share on other sites

obviously it's beyond Sync. There's definitely something wrong with volume/raid configuration. 
There's also nothing critical in the logs you've sent. You might want to debug this with Synology or remount your filesystem. 

Share this post


Link to post
Share on other sites

5 months later and I took the plunge of reinstalling the Resilio Sync package on a whole new set of disks. The NAS itself has been running smoothly.

 

Package used : Sync 2.6.0 Build 1 packages for rtd1296

DSM version : DSM 6.2-23739-2 dated 2018/07/12

 

But now instead of crashing, it immediately presents me with a dialog box stating :

Sorry, this user account has not been assigned proper privileges to perform this action.

Now my previously working admin account (The very one that I uses for installing Resilio Sync) has loses all its admin permission, including access to Control Panel. My datas are still accessible from the network though, both for read and write operation.

 

Any pointers?

 

 

Edit : Upon further investigation, all my Synology admin account has lost their permissions, locking me out of the box Control Panel. Pointers before I contact the Synology team to restore my roles?

Share this post


Link to post
Share on other sites

I got access back to my admin account by resetting my admin password through hardware means. Still, the problem remains. Why would installing Resilio Sync package broke my NAS, twice? Even with a whole different set of disks?

 

Edit : I can see the package has been installed. I lack the guts to run it without further info.

Edit 2 : I can see that there is no user for Resilio Sync created. Could it be that the crash occurred when the package was trying to create a user for itself (rslsync)?

Edit 2b : Scratch that, the user exists but unlistable, I can't create it manually on account that it already exists.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now