Quelle: https://academy.pointtosource.com/synology/synology-ds920-nvme-m2-ssd-volume/

With the new x23 models being delivered, a lot of chat has started up again surrounding the NVMe slots on Synology Diskstations. Until now, the only official way to use these slots was as a read or read/write cache, not always something that was a) desired b) needed or c) actually that useful, given the way an associated volume would crash if the r/w cache failed. A better option (most agreed) would be to use those NVMe SSDs as a separate volume.

 

The DS923+ has been given that ability right out of the box, and can be set up from DSM. Officially, Synology has not provided support for any older models, but there is a way... and that way is detailed below.

https://feed.jaytuned.com/_FileUpload/Boost%20your%20system%20speed%20by%20creating%20an%20SSD%20vol...

#synology #ssd #nvme

Fundus im Internet: https://www.computerbase.de/forum/threads/dauer-des-softwaresupports.2057104/#post-26362967

Modelle aus dem Jahr 2013 haben im September 2021 noch das neue DSM7 Update bekommen.
Modelle aus dem Jahr 2011 haben im September 2021 das letzte DSM6.2.4 Update bekommen
Also auch nach 7-10 Jahren haben die Geräte noch DSM Updates bekommen.

Pakete wie Mail Plus oder Active Backup die um 2017/2018 rauskamen sind auch für 2011er Modelle erschienen

Grob gesagt:
Mit 5 Jahren kann man fix rechnen, obwohl es eher 7-9 Jahre sind (Stand heute).
Super Kritische Sicherheitslücken wurden bis dato alle geschlossen.

Hier gibt es aber eine Übersicht wie welche Modelle noch voll oder eingeschränkt mit Updates versorgt werden:
https://www.synology.com/de-de/products/status?tab=hardware&model=DS213+

Mit einem "Plus" Modell ist man in der Regel auf der "sicheren" Seite, da für diese Modelle auch die meisten Pakete erscheinen. Wie z.B Active Backup, Virtual Machine Manager, Docker, Snapshot Replication. Diese Pakete gib es nicht für J oder Value Geräte.

 

#synology #support

Problem:

https://support.apple.com/en-us/HT205926

The Apple Support Article says:

In macOS 10.13.4 and later, packet signing is off by default. Packet signing for SMB 2 or SMB 3 connections turns on automatically when needed if the server offers it. The instructions in this article apply to macOS 10.13.3 and earlier.

Turn off packet signing for SMB 2 and SMB 3 connections

You can turn off packet signing if the client and server are on a secure network.

When you use an SMB 2 or SMB 3 connection, packet signing is turned on by default. You might want to turn off packet signing if:

• Performance decreases when you connect to a third-party server.

• You can’t connect to a server that doesn’t support packet signing.

• You can’t connect a third-party device to your macOS SMB server.

If you turn off packet signing, you lower the security of the SMB connection. Turn off packet signing only if both the client and server are on a secure network.

Turn off packet signing

Turn off packet signing on a macOS client

Check to see if your macOS computer has an /etc/nsmb.conf file.

If your macOS computer has a /etc/nsmb.conf file

• Open the /etc/nsmb.conf file.

• Set the signing_required value to “no,” like this:

[default]
signing_required=no

• Save the /etc/nsmb.conf file.

• Disconnect and then reconnect any mounted SMB shares to make the changes take effect.

If your macOS computer doesn’t have an /etc/nsmb.conf file

• Open Terminal.

• Use these commands to create an /etc/nsmb.conf file that has a signing_required value that’s set to “no”:

sudo -s
echo “[default]” >> /etc/nsmb.conf
echo “signing_required=no” >> /etc/nsmb.conf
exit

• Disconnect and then reconnect any mounted SMB shares to make the changes take effect.

Turn off packet signing on a macOS computer that hosts SMB shares

Simple way to create a MD5 hash value of a file with windows command line tool:

https://support.microsoft.com/de-ch/help/889768/how-to-compute-the-md5-or-sha-1-cryptographic-hash-v...

Its necessary to download the following tool:

https://support.microsoft.com/en-us/help/841290

After extracting the exe file you can add the extraction path to environment variable "PATH" in the system settings to access the tool from any location in cmd:

Take a look at: https://support.plesk.com/hc/en-us/articles/115003766853-How-to-specify-PHP-version-for-command-line...

I had to add PATH to .bash_profile file

1. Connect via SSH with the system user to the server

2. Add the PHP path toe .bash_profile file

echo "PATH=/opt/plesk/php/7.3/bin:$PATH" >> ~/.bash_profile

3. Reconnect SSH Connection

How to add and remove programs to a chrooted shell environment template

Look at: https://support.plesk.com/hc/en-us/articles/213909545

The above adds the OS version of PHP to the chroot environment, not the PHP executables that are used for the websites.

I therefore replaced

./update_chroot.sh --add php

with

./update_chroot.sh --add /opt/plesk/php/7.1/bin/php

You may want to repeat that with other available php versions.

For convenience I also linked that php binary to usr/bin:

ln -s /opt/plesk/php/7.1/bin/php /var/www/vhosts/chroot/usr/bin/php

Afterwards, of course, do a ./update_chroot.sh --apply <domain>|all