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."

Hi, Just to inform you guys, I upgraded my hardware to: Mobo: MSI B250 PRO VDH CPU: i3-7100 RAM: 16 DDR4 2333 Cooler: Hydro H60 High Liquid CPU Cooler (Old one I still had) DS918+ runs perfectly, no issues at all. Already running Virtual machines as Win10 and Ubuntu. Thx for your help!

OK, Downloaded: http://s000.tinyupload.com/?file_id=04147311964729253115 Added to [DS3615xs_DSM6.2-23739_MBR.img] But nothing to do... can't be found in the LAN. Really appreciate the effort to help me out but I failed... 😔 I will see if I can upgrade the hardware. I'm already running a DS918+ perfectly on another node...

Hi @IG-88, Thank you very much but where can I find the new 6.2.3 compatible [extra.lzma] ? Sorry for that question but I don't seem to find it.

Hi @IG-88, But I give up but just to info you. I tried loader 1.03b on DSM 6.2.3. DS3615xs Step 1: Downloaded: https://mega.nz/#!OV4gVKyZ!dCgfXx1bgAOyvbFwFiov3s7RSNoFuqnAcNmSllLoUiw Step 2: a) Mounted with OSFMount b) Edited [grub.cfg] Changed VID, PID of the USB drive SN generated for DS3615 MAC of the node c) Added files to 2nd partition of [synoboot.img] Downloaded [extra.lzma] for DS3615xs Extracted [rd.gz] and [zlmage] for [DSM_DS3615xs_25426.pat] Step 3: Used [Win32DiskImage] to write [synoboot.img] Step 4: Booted from USB - No - UEFI mode Result could't boot... Thx anyway...

Hi @Apfelbomber, Thank you for replying, I'll give a shoot to the ds3615xs tonight at home. On this board I don't have Inter NIC, it's like there's something to do with the NIC. Before each installation I format the USB as the SSD. USB using DISKPART to delete the EFI partition and the SSD using Disk Management to be sure no other partition still there. USBFLASHINFO Volume: F: Controller: SSS BC Possible Memory Chip(s): Toshiba TC58TFG7DDLTA00 Toshiba TC58TFG7DDLTA0D Memory Type: MLC Flash ID: 983A9493 7651 Flash CE: 1 VID: 0930 PID: 6544 Manufacturer: Kingston Product: DataTraveler 2.0 Query Vendor ID: Kingston Query Product ID: DataTraveler 2.0 Query Product Revision: 1.00 Physical Disk Capacity: 15518924800 Bytes Windows Disk Capacity: 15500050432 Bytes Internal Tags: 396H-QAH4 File System: FAT32 USB Version: 2.00 Declared Power: 200 mA ContMeas ID: 402F-03-00 Microsoft Windows 10 x64 Build 18363 GRUB.CFG set extra_initrd="extra.lzma" set info="info.txt" set vid=0x0930 set pid=0x6544 set sn=1430ODN026850 (generated for ds3617xs) set mac1=B4352F53161E set rootdev=/dev/md0 set netif_num=1 #set extra_args_3617='earlycon=uart8250,io,0x3f8,115200n8 earlyprintk loglevel=15' set extra_args_3617='' set common_args_3617='syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3617xs vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet syno_port_thaw=1' set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=1 SasIdxMap=0' set default='0' set timeout='4' set fallback='1' if [ -s $prefix/grubenv ]; then load_env if [ -n "$saved_entry" ]; then set default="${saved_entry}" fi fi VERSION="with Jun's Mod v1.03b" search --file -s /bzImage function savedefault { if [ -s $prefix/grubenv ]; then saved_entry="${chosen}" save_env saved_entry fi }

Hi everyone, Fulatins from Belgium, great job with XPEnology this is my dream coming true! Running DS918+ as shown in the picture [i5 Gen4] and trying to get it working on another system [i5 Gen3] but without success at this point.

Hi, I have an old system HP Pro 3500 which I would like to install XPEnology but it seems like I can't, the DiskStation is not found by Synology Assistant nor at https://find.synology.com. Already tried a couple of option but every one failed on different status: System: HP Pro 3500 Mobo: 701413-001 H61 Intel i5-3470 CPU @ 3.20GHz 4GB DDR3 BIOS: v8.14 01/23/2013 (last available) NIC: Realtek PXE B03 D00 NIC PCI: Realtek PXE B04 D00 Case 1: Loader: 1.04b [6.2/6.3] DSM: DS918+ Failed @: No DiskStation found on LAN Case 2: Loader: 1.02b [6.0.3 to 6.1.7] DSM: DS3617xs Failed @: Installation go through but when the DiskStation reboots get to "Migrate" or "Re-install" installation Case3: Loader: 1.02b MBR_Genesys DSM: DS3617xs Installation done : DiskStation found, installation process fully done, created Server and User, after reboot DiskStation was found and got access, Update to last available DSM version Failed @: Reboot DSM, couldn't be found anymore.