I managed to install syncthing v1.12.1 on my ReadyNAS 422 running ReadyNAS 6.10.10. Changed the config.xml to listen on 0.0.0.0:8384. I started syncthing from the CLI. Used the GUI to set up. As soon as I started syncing files the CLI showed errors and syncthing stopped. df showed /dev/md0 was 100% used. It was ~13% used before syncing started. I assume it’s an index file or something in the wrong place that’s the culprit?
This is the second time I got it installed. Same thing happened the first time. I had to reset the NAS to factory default and wait 3 days for the volume to resync before I tried again. (!)
So now md0 is full, the nas GUI doesn’t work. I restarted from the command line. It has not fully booted after an hour, the GUI doesn’t work though the CLI does.
Can I fix this without reinstalling ReadyNAS from scratch? If not, how can I make sure the installation goes better next time?
What size is /dev/md0 and how many files are being synced?
Since it ran out of space so quickly, I’m guessing that it’s separate from the primary storage array. It might be a pair of small flash modules.
Syncthing keeps track of the state of files being synced across all peers in a database whose size is affected by the number of files being synced.
Maybe. It sounds like ReadyNAS (based on Debian Wheezy Linux) is just out of space to boot the GUI. According to the spec sheet, the 422 model has 2GB of RAM – plenty enough for Linux to run in memory without fully depending on free disk space. Since the NAS is accessible via CLI, shutting down Syncthing, deleting Syncthing’s database, and rebooting should be enough for the NAS to recover.
See Syncthing’s FAQ the command-line options for specifying a different location for its database.
Since the ReadNAS’ /dev/md0 is most likely flash media, it might not be the best place for Syncthing’s database (there could be a lot of write cycles).
However, putting it on the main storage volume also might not be ideal depending on the number and typical file sizes being synced – e.g. indexing 1 million tiny files when they sit alongside Syncthing’s database could be a drag on performance.
But without enough details about your current setup, it’s all just educated guesses.
