Polanskiman

Ceci est la deuxième fois que je dois intervenir en mois de 24 heures. Merci de respecter les consignes du forum (elles sont en anglais. Si vous ne lisez pas l'anglais vous pouvez utiliser Google Translate): Par ailleurs la personne qui vous a répondu est un modérateur donc je vous suggère de faire un effort dorénavant.

@armazohairge Nous sommes dans la section française par conséquent je vous prierais de faire un gros effort sur: 1. votre façon d'écrire, car franchement on lutte, ajouté à cela les fautes de grammaires/d'orthographes à presque tous les mots ça devient très difficile. Nous n'attendons pas que vous écriviez un français littéraire mais entre ça et vous il y a une grosse marge de progression possible. 2. sur votre façon de vous diriger aux autres membres du forum. Votre compte à peine 4 mois, vous n'avez fait que 10 posts et vous avez déjà 1 warning. Je vous prierais par conséquent un tant soit peu d'humilité vis à vis des gens qui sont ici depuis bien des années et qui contribuent au quotidien. La critique est bienvenue sous condition qu'elle soit fondée et explicitée.

Sorry but not sure what you want to say with what is between brackets. Care to clarify?

WARNING This is an INTERMEDIATE update of DSM. BE CAUTIOUS WHEN UPDATING TO DSM 6.2.3 with Jun's loader. Several issues have been reported already. Try installing it first on a VM test machine. Warning regarding the NVMe patch It is STRONGLY RECOMMENDED to anyone using the NVMe patch to remove the cache prior to applying this update, else you risk losing your volume. Must Read this Warning regarding extra.lzma from @IG-88 This update breaks all custom modules (network and storage) and you will revert to native modules. Must Read this Warning regarding ESXi installs Because the update brakes Jun's loader Synoboot script, you should read this before applying the update.

This update has been recalled by Synology. Therefore it's no longer available. I am locking this thread. A new update has been made available. Please report your update in the following thread:

@Bjoern @mbaz @htanh034 @Chunga_Changa All of you seem to be new here. I suggest you read the READ ME topics pinned at the top of this page before posting. You are being asked the DSM version prior update: and not the update you just applied. If you did a clean/first install then please say it explicitly. Your post is put on hold until you provide the correct information. Please contact me via PM and I will edit and release your post. @valix Next time please post once you have done the actual update instead of saying "pending". This gives me unnecessary work to have to edit members posts. Thank you

@madhits45 You might want to read the message/READ ME topic at the very top of this thread. I will edit your post this time. Next time I wont bother and simply delete.

WARNING This is an INTERMEDIATE update of DSM. BE CAUTIOUS WHEN UPDATING TO DSM 6.2.3 with Jun's loader. Several issues have been reported already. Try installing it first on a VM test machine. Warning regarding the NVMe patch It is STRONGLY RECOMMENDED to anyone using the NVMe patch to remove the cache prior to applying this update, else you risk losing your volume. Must Read this Warning regarding extra.lzma from @IG-88 This update breaks all custom modules (network and storage) and you will revert to native modules. Must Read this Warning regarding ESXi installs Because the update brakes Jun's loader Synoboot script, you should read this before applying the update.

Moved to the appropriate forum section. Thank you @IG-88

The question(s) in this topic have been answered and/or the topic author has resolved their issue. This topic is now closed. If you have other questions, please open a new topic.

@supermounter I think that clears it up. Question closed.

The question(s) in this topic have been answered and/or the topic author has resolved their issue. This topic is now closed. If you have other questions, please open a new topic.

Nice. Seems Corona might have something to do with that perhaps?

Critical Update 6 has been put back online today, March 24, after being recalled by Synology on March 18, one day after it was released. Considering the MD5 hash and modification dates are exactly the same as the original update, this indicates the update was not modified by Synology. I would advise some caution. Carefully consider why Synology initially recalled the update and see if this could have any impact on your box. I am opening the thread again.

The question(s) in this topic have been answered and/or the topic author has resolved their issue. This topic is now closed. If you have other questions, please open a new topic.