sebg35

Hello, Yes 7.0.1 on my side, 3622XS. (Xeon variant) Edit -> Baremetal

Hi, I successfully migrate my Gen10 Plus (Xeon E-2224) with redpill and Tinycore. I used loader for DS3622XS & DSM 7.0.1, and choose to migrate my data. (I came from DS3617XS and dsm 6.2.3) Everything was smooth and i didn't loose anything. I can confirm also that with DS3622XS,i can see my 4 CPU Core (insteed of 1 with 3615XS & 918+) Great job guys ! Many thanks ! Note : I blocked Internet during setup/Migration but maybe not needed anymore.

Yep that's what i did in my last test : All 4 disks were formated

I also get the installation loop -> DS3617XS - Installation loop - Not asking for migration -Previous DSM install from 6.2.3 with Internet connection disconnected DS3615XS - Installation OK - Only one CPU core Seen (As DSM 7 & 918+) - Not asking for migration -Previous DSM install from 6.2.3 with Internet connection disconnected DS3617XS - Installation loop - asking to format all 4 disks - 4 disks formated with Internet connection disconnected I rollback to Jun & DSM 6.2.3 with DS3617XS

Hello, I am trying to install DSM 7 on my Gen10 plus using Tinycore & DS3617XS loader. DSM 62.3 was previously installed using Jun and with Satamap as : DiskIdxMap=0C SataPortMap=1 Using Tinycore & satamap show : Installation is working but after the reboot, it asked again for DSM installation. (DSM installation loop) i tried with the following satamap config but it is always the same thing (SataPortMap=1 DiskIdxMap=0C, SataPortMap=4 DiskIdxMap=00,) I am using only the internal controler with 4 disks. Any idea ? EDIT : It seems like SataPortMap=4 DiskIdxMap=00 is working only using 3615xs image. But with 3615xs loader, DSM is only seeing 1 core instead of 4. (Like 918+) Any tips to make 3617xs working ?

Sure i will give a try :), thanks

Hi, how does it works exactly ? I mean for Baremetal, with redpill tools, we burn the loader into a USB stick, boot from the usb stick and then install DSM. With @pocopico 's loader, we boot the baremetal from usbstick, create the loader -> where is the loader created ? On usbstick ? on HDD present in Baremetal ?

Just a quick reminder for myself (and maybe it can help other) for the next try : When i start to upgrade my Gen10 plus (1 internal Sata with 4 disks 1,2,3,4) from 6.2.3 (Jun loader 3617xs) to 7.0.0 (Redpill) 3615xs : Only one disk was shown with id 13 ? In order to get all 4 disks working i was needed to modify grub : Jun Loader 6.2.3 Grub : Bold : present by default on Jun loader ? 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' Redpill Loader 7.0.0 Grub : Bold : Added linux /zImage mac3=xx mac2=xx DiskIdxMap=00 mac1=xxmac4=xx netif_num=4 earlycon=uart8250,io,0x3f8,115200n8 syno_hdd_powerup_seq=0 vid=xx syno_hdd_detect=0 pid=xx console=ttyS0,115200n8 elevator=elevator sn=xx root=/dev/md0 SataPortMap=1 SasIdxMap=0 sata_uid=1 sata_pcislot=5 earlyprintk loglevel=15 log_buf_len=32M syno_port_thaw=1 HddHotplug=0 withefi syno_hw_version=DS3615xs vender_format_version=2

Hi Witewulf, i already rollback. I Will try leater with empty disk to check logs before crash.

Hi, Same logs on my baremetal gen10 plus, using the 3615xs and 7.0.1. My cpu is xeon e-2224. FYI always crashing When i try to log in. I rollback to 6.2.3.

You have to add a new sata controller, and set HDD to use the new sata controller (1:0, 1:1, ...) Sata controller usage are defined under your disks settings, under VM confgiuration.

You might check : Loader is using sata0:0 HDD is using sata1:x Your grub has correct configuration (DiskIdxMap=1000 & SataPortMap=1 in my case) Sata boot is selected on 1st boot using your console access

tail -f /var/log/messages

Anyrhing else to do prior creating the script is needed ? /usr/local/etc/rc.d/S99Powersaving.sh: line 3: /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor: No such file or directory

Just tried with my Gen10 plus (with Xeon E-2224) and 918+ loader with 7.0.1 NIC : Only 2 detected (4 set in grub) I use a LAG (802.3ad of 2 nic : Working) Install : No issue at all : It asked for migrating my OLD disk (No production disk has been used) CPU : My Xeon E-2224 is only shown as one core (Same issue has in 6.2.3 with 918+ -> Need 3617xs loader to have all 4 cores used) Info Center : Working Applications : Synology Photo / Drive: Face detection not working Unable to play a video under File station (Video was uploaded with the backup feature using Synology photo for Android; Not working also on 6.2.3) The rest seems to work fine Surveillance Station : Working with one camera added Active Backup For business : Working well. (backup with esxi 7.0 is working) Plex : Working Docker : Not tested. Face detection Log : 2021-09-07T18:56:23+02:00 NAS synofoto-face-extraction[13956]: json_utils.cpp:147 Failed to parse json file [/tmp/VideoStation/enabled] 2021-09-07T18:56:24+02:00 NAS synofoto-face-extraction[13956]: /source/synophoto-plugin-face/src/face_plugin/lib/face_detection.cpp:214 Error: (face plugin) load network failed 2021-09-07T18:56:24+02:00 NAS synofoto-face-extraction[13956]: uncaught thread task exception /source/synofoto/src/daemon/plugin/plugin_worker.cpp:90 plugin init failed: /var/packages/SynologyPhotos/target/usr/lib/libsynophoto-plugin-face.so /proc/cpuinfo : cat /proc/cpuinfo | grep 'processor\|name\|cores' processor : 0 model name : Intel(R) Xeon(R) E-2224 CPU @ 3.40GHz cpu cores : 1 I revert to my 6.2.3 with 3617xs loader from June. waiting for 3617xs support.