

So why binutils, fontconfig and libsm are dependencies? I don't understand where did you get the dependencies.Nevertheless, I successfully got the newest Synology Drive version built and it's running without any problem so far. The newest Synology Drive client was released to be compatible with the new DSM 7, but older NAS with DSM 6 might still provide the version 2.0.3-11102 to download. Synology released a release candidate of it in June 2021, Version: 7.0-41882. This package might be incorrectly flagged out-of-date because the new DSM 7 is not released yet to the public. (Save as PKGBUILD in temporary folder and run makepkg -si to install.) Optdepends=('nautilus: For nautilus integration' )Ĭonflicts=('cloudstation-beta' 'cloudstation-3.0' 'cloudstation-drive' )

Here's the PKGBUILD I used to get to the as of this writing recent-most release, v3.0.1: # Maintainer: Felipe Martin ĭepends=('glibc' 'libsm' 'binutils' 'fontconfig' )

#Synology cloud station drive crashes upgrade#
+md5sums_x86_64=('6381889cd48f13a18ae60e7c2ca46df7')įor anyone who has already upgraded their NAS to 7.0 and is looking get a working Synology drive again, until the package is updated you might want to upgrade ahead of time. Pkgdesc="Drive for PC, the desktop utility of the DSM add-on package, Drive, allows you to sync and share files owned by you or shared by others between a centralized Synology NAS and multiple client computers."Īrch=('i686' -13,11 +13,11 conflicts=()
#Synology cloud station drive crashes Patch#
Follow the instruction to repair the storage pool.Here is a patch if it can help: diff -git a/PKGBUILD b/PKGBUILD.Once replaced, click on “Repair” from the “Action” menu.Remove and replaced accordingly with a same size or bigger capacity. Alternatively, head over to “Storage Pool” and check if the status has been changed to “Degraded” If yes, go to the HDD / SSD tab to check which drive has failed.Once in that page, Head over to “Overview” and click “Repair” That will begin works to repair the system partition. Click on the top left icon in the synology management interface page and select storage manager.Look for the button to “beep off” Once selected, the noise should immediately stop.Once login into the management page, open up “Control Panel” and head over to “Hardware & Power”.If you are not sure of the IP address of the Synology network attached storage, you may refer to this link “ Locate your synology in the network“

Fire up your web browser and type in the IP address of your DSM.System shuts down after pressing power button (normal operation)įrom my experience, synology unit will make continuous beeping noise when problem 2 occurs.Volume Degrades or crashes (high priority).There could be several reasons why the synology beeps. And to find out what went wrong, you will need to head into the DSM management page to find out what went wrong. Generally when a synology NAS starts to produce beeping sound out of the blue, it means that there is some issues with the device itself.
