Fulatins

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.2.1 69057-Update 3 - DSM version AFTER update: DSM 7.2.1 69057-Update 4 - Loader version and model: TinyCore RedPill Loader - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL: i5-9500 - ASRock Z390M Pro4 - 32GB DDR4 - 4 HDD - 2 NICs - Additional Comments: Manual Update, reboot and everything seems to be OK but Virtual Machine auto start failed, "No Network Interface available". Solved by: VM Manager > Network > Action > Edit > Checked available interfaces, manually started VM.

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.2-64570 update-3 - Loader version and model: TinyCore RedPill Loader - Using custom extra.lzma: NO - Installation type: BAREMETAL: i5-9500 - ASRock Z390M Pro4 - 32GB DDR4 - 4 HDD - 2 NICs - Additional comments: Manual Update, reboot and everything seems to be OK

- Outcome of the update: SUCCESSFUL - DSM version prior update: 7.2-64570 Update 1 - Loader version and model: TCRP v0.9.4.9 + Friend 0.0.5j DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL: i5-9500 - ASRock Z390M Pro4 - 32GB DDR4 - 4 HDD - 2 NICs - Additional comments: Manual Update

- Outcome of the update: SUCCESSFUL - DSM version prior update: 7.1.1-42962 Update 5 - Loader version and model: TCRP v0.9.4.9 + Friend 0.0.5j DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL – i5-9500; ASRock Z390M Pro4 - 32GB DDR4, 4 HDD, 2 NICs - Additional comments: Created a new USB boot drive, starting from TCRP v0.9.4.9 image: ./rploader.sh update now ./rploader.sh fullupgrade now ./rploader.sh serialgen DS918+ ./rploader.sh identifyusb now ./rploader.sh satamap now ./rploader.sh build ds918p-7.2.0-64570 withfriend exitcheck.sh reboot

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.1-42692 Update 4 - Loader version and model : Automated RedPill Loader ARPL 1.1-beta2a - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Z390M Pro4 - i5-9500 - Additional comments: Updated via DSM GUI

Salut, Peut-être une bête question mais aurait-il des avantages à migrer de Xpenology DS918+ build vers Xpenology DS3622xs+? Je suppose que sur ce dernier on aurait la possibilité d'installer plus de disque, non!? Donc cela dépendrait de l'utilisation de chacun... Dans mon cas, je voudrais avoir au moins 8 disques, j'ai reçu le matos. Merci d'avance,

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.0-42661 - Loader version & Model: Automated RedPill Loader 0.5 alpha-1 DS918+ - Installation type: BAREMETAL - Z390M Pro4 / i7-9500 - Additional comments: Got to use another USB stick.

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426-2 - Loader version and model: RedPill TinyCore V.04.6 DS3615xs DSM-7.1.0-42661 - Using custom extra.lzma: NO - Installation type: Bare-metal on ASRock Z390M Pro4 - i5-9500 - 32 GB Corsair Vengeance LPX - S. 860 EVO 250GB - RAID Mirror Seagate IronWolf 3TB - Additional comments: Use official Synology .pat file from https://archive.synology.com/download/Os/DSM

Salut, Désolé pour les question, je n'arrive pas a les effacer! J'ai compris que en faite c'est normal que cela reste sur "Starting Kernel with USB boot", c'est diffèrent au loader JUN, j'avais un souci mais c'est que mon i5 est de 3th GEN et pour le DS918+ c'est minimum 4th GEN. J'ai utilisé un i7 9th GEN et maintenant cela fonctionne parfaitement.

Salut, J'ai relancé utilisant le USB LEGACY BOOT, maintenant j'arrive a passer ce stade mais je reste bloqué sur: Decompressing Linux... Parsing ELF... done. Booting the kernel. Merci d'avance,

Salut, J'essaie d'installer apollolake-7.1.0-42661 sur DS918+, clean install, mais j'ai un souci avec le loader, je pense avoir suivi toute les étapes correctement, le build se fait, d'après moi, correctement mais lorsque je relance la machine reste sur: "Starting Kernel with USB boot" Je ne vois pas vraiment où j'ai commis de faute, aurait quelqu'un une idée de ce problème? Merci d'avance,

Hi all, I was wondering, now DSM 7 is out, would Synology ever force DSM NAS owners to upgrade to DSM 7 compatible devices and end DSM 6? They could do that updating DSM 6 packages until all packages will only be compatible with DSM 7, right? I'm quite confident and hoop this wouldn't happens in the next 2 years but what is the XPEnology Community thoughts about this? Thx,

Hi, I used FreeNas, Qnap, XigNas but DSM is the "real thing", from my experience, FreeNas is by far the best in deep configuration. Couple years ago I had a Synology box but when I run into XPE I was chocked by the speed of DSM on a old laptop that couldn't even run Windows on a "normal" way, I build a i5 32 GB M2 SSD NVMe box. And as @painkiller895 said, I hoop this is not the end of Xpenology, maybe a "Donation" button could help! Grtz,

Auto installation Outcome of the update: SUCCESS DSM version prior to update: DSM 6.2.3-25426 Update 1 Loader version and model: Jun v1.04b - DS918+ Using custom extra.lzma: NO Installation type: MSI B250M PRO-VDH / i3-7100 / 32 DDR4 2333 Additional comments: After FixSynoboot.sh script

Auto installation Outcome of the update: FAILED DSM version prior to update: DSM 6.2.3-25426 Update 1 Loader version and model: Jun v1.04b - DS918+ Using custom extra.lzma: NO Installation type: MSI B250M PRO-VDH / i3-7100 / 32 DDR4 2333 Additional comments: Node restarted but still "Fail to update the file. The file is probably corrupt." Manual installation Outcome of the update: FAILED DSM version prior to update: DSM 6.2.3-25426 Update 1 DSM downloaded from: https://archive.synology.com/download/DSM/criticalupdate/update_pack/25426-2/ Loader version and model: Jun v1.04b - DS918+ Using custom extra.lzma: NO Installation type: MSI B250M PRO-VDH / i3-7100 / 32 DDR4 2333 Additional comments: "Node restarted but still "Fail to update the file. The file is probably corrupt."