ie download the file from the website then browse to download folder etc, versus clicking on the update button which says there is an update and clicking on install or similar whereby the a file is downloaded, installed and the NAS reboots.
Ive done several rounds of the latter, and the installed version is DSM 4.3-3827 update 5. My NAS sole internet exposure would have only been when I was bit torrenting raspberry Pi OS, (which I havent for several months.).
Opinions ??
A.
Currently I am backing up to an external 1.27 Tb is going to take a while even with USB3.
Hi, I administer over 30 of these that are deployed in small schools as a file server. All bar one were up to date so did not get hit, and yes most face the internet as remote access via HTTP/S or WebDav is a key feature schools like.
The one that was hit belonged to a school that had declined any form of ongoing maintenance, but I wont go on about that, regardless immediately the NZ distributor notified me of the issue I logged into this one as I knew all the others were running lattest or near firmware, and immediately I went to update it, wham, I immedatily phoned the school and they pulled the power, this was a lucky move.
Anyway, fortunately the encryption process is very slow, and the system as configured by me kept local USB disc timeline backups, so recovery has fortunately not been too painful.
To answer afe66's question:
It most definitely make life easy if you have both a config backup and a current data backup of some form, If the machine is still running and seems to not be running Synosync then do a config backup and attempt to offline the files.
Download the lattest firmware to your PC. Power up the NAS with discs removed. Once its running, which may take 1-2min and eventually it beeps, physically connect the drives while the system is still running. Run DS-Assist, it should either automatically take you to a web page to install DSM or select that via DSM assist and reinstall the system. Once up and running if you need to reload the config then do so.
If you are still paranoid backup the data, then rebuild the volumes and put the data back, a config rebuild post volume rebuild is probably also best.
In my case, and I recommend this, if you have the option to remove the discs before all the above and pull all the files off via a nix machine then do so, this is easy if its just running jobd or raid1, but if a higher level of raid this might be a little harder to sort.
Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly
to your computer or smartphone by using a feed reader.