DSfuchs

In order for DSM 7.2 to be available to you, you need model modding on one of the following models: DS1517+ DS1817+ RS818(RP)+ RS1219+ RS2416(RP)+ Take a look at this in the related topic: https://xpenology.com/forum/topic/70401-synology-plus-series-internal-flashdom-repair-and-model-modding

Ja, das geht. Auch kannst Du direkt ein modding auf ein 18/19er-Modell mit machen. Dafür habe ich dieses Thema hier aufgemacht:

Ist das Problem behoben? Wenn nein, dann schreibe mal bitte welche CPU verbaut ist, und welcher Lader genutzt wird.

Hallo, eine CPU mit einer TDP von 65w ist als NAS wegen des Stromverbrauchs und der Abwärme ungeeignet. Außerdem gibt es mit INTEL CPUs keine Probleme, um ein neueres DSM zu nutzen. Alles mit TDP <10w ist sinnvoll. Das geht z.B. los ab Intel N3150 https://ark.intel.com/content/www/de/de/ark/products/87258/intel-celeron-processor-n3150-2m-cache-up-to-2-08-ghz.html Bei neueren CPU-Familien sollte man nur die "Apollo Lake" wegen der begrenzten Lebensdauer außen vor lassen.

I would like to once again urgently point out the need to back up every DOM of Synology + models. It's done in a few seconds. Simply run via SSH with root: dd if=/dev/synoboot of=/volume1/myShare/DS412+synoboot-6.2.4u5.img where "myShare" is your share for general purpose. Of course, it only makes sense if the file is then downloaded from the Synology to another location.

I can also confirm full USB functionality and advanced speed via TCRP. My systems are not only used for testing purposes. As of a year ago, ARPL didn't work. It's also super easy and quick to migrate from internal RAID0 using a single Linux mdadm-command. If you have an external single drive, you should ideally place the parity disk of a RAID4 there. If you have a dual(or more)-case, it makes sense to place the mirror drives of the RAID10 (RAID0+1 with 2 near-copies) there. In general, the slow hard drive performance when writing in RAID 5/6 scenarios, with only 3-5 drives, is out of the question for me anyway. I can also imagine the long recovery times with the associated collapse in performance. We're not talking about a data center-sized installation where the penalty is almost negligible. Always remember that the higher the number of hard drives, the more likely (I love RAID4 there) it is that a hard drive will fail.

I expand real devices and Xpenologies via external USB3 enclosures. These are also available as internal drives via Settings.

This only worked for me with a DS710+ as a 3615xs. The Synology devices are proprietary boxes and not normal PCs. This is due, among other things, to the BIOS and the KBC-like parts of Synology.

Directly to the left of my answer you can use the up arrow to rate it and also mark an answer for the solution.

You're welcome, but I would be happy about a voting then, above 0. The voting is on the left side of the post.

There's an internet archive for this sort of thing https://web.archive.org/web/20210305152847/https://archive.synology.com/download/Os/DSM

Probably only @IG-88 can help.

The voting is on the left side of the post.

https://web.archive.org/web/20210412133958/https://global.download.synology.com/download/DSM/release/6.1.7/15284/DSM_VirtualDSM_15284.pat

Have you already tried the version 6 assistant? https://archive.synology.com/download/Utility/Assistant/6.2-24922

You'll probably have to remake the friend from scratch. Or ask @Peter Suh for help with a repair. On a real Synology the files would now be shot on the internal flash.

Ja, Du musst nur eine existierende ("echte") Seriennummer mit den zugehören MAC's dieses Synology Modells benutzen. Alle drei Werte (Modell, Seriennummer, MACs) bilden eine Einheit, die valide sein muss. Dabei findet kein Abgleich des Gerätes in anderen Synology-Konten statt 🙄🤐

You're welcome, but I would be happy about a voting then, above 0.

There's an internet archive for this sort of thing https://web.archive.org/web/20210305152847/https://archive.synology.com/download/Os/DSM

A standard Btrfs volume, i.e. not the proprietary SHR, can easily be read and written using Windows drivers. These two drivers has to be installed. Linux filesystem Btrfs: https://github.com/maharmstone/btrfs Linux MD software RAID devices: https://github.com/maharmstone/winmd Linux "ddrescue" can be used for backup and restore of the DSM system partition. It becomes available with the "SynoCli Disk Tools" package on DSM: https://synocommunity.com/package/synocli-disk For example, the associated command with root in the SSH terminal or as a scheduled task would be: ddrescue /dev/md0 /volume1/GeneralPurposeShareName/Systempartition.img A “ddrescue” installed on the Tiny Core Linux (TCL), may be tinycore redpill (TCRP), can then be used to restore the image.

Due to many further questions/problems here in the thread, I would like to expand the topic to all models of the Synology "+" series and all questions about internal flash memory regarding hardware replacement, image repair, elsewhere with a new topic. Synology model upgrades are also possible here: As already mentioned, the thread owner also has the opportunity to close this topic here. From my side, thank you @wool very much for the information about the pin-out and the ideas that came from it.

Due to many questions/problems in the "DS412+ USB flash module pinout" thread, I would like to expand the topic to include all models in the Synology "+" series, and all questions about the internal flash memory regarding hardware replacement, image repair. Synology Model upgrades are also possible here.

Since the image is OK and starts with my RS812+, I assume that the internal flash memory is no longer able to provide the necessary USB2.0 protocol to start the device due to aging.