skepticwr

Hello, I am certainly not an expert but if you run the ./rploader.sh postupdate command it will spit out usage and there you can see examples of what you can specify as arguments. I believe that the postudate command would be useful only in minor updates like Update1 or Update2 where the main version number will remain the same for example 7.1.0-42661. If it was a major version number change I think a loader rebuild would be necessary. In you case the broadwellnk-7.1.0-42661 the broadwellnk defines the platform and the 7.1.0-42661 the DSM version. When I did the postupdate for DS918+ I had to use ./rploader.sh postupdate apollolake-7.1.0-42661. On the DS3615xs+ I used ./rploader.sh postupdate bromolow-7.1.0-42661 The codenames apollolake, bromolow etc are the Intel platform. Try run the command ./rploader.sh postupdate only and you will see the output. I hope I am not making any mistakes and hopefully someone with more knowledge can chime in. I did two successful postupdates with DS3615xs and DS918+ and in both cases it was intel platform-dsmversion (bromolow-7.1.0-42661, apollolake-7.1.0-42661)

Anybody has a guide on how to use this yet please? Thank you.

I believe you need to type: ./rploader.sh postupdate broadwellnk-7.1.0-42661

Hello everyone. Could someone please comment on what is the correct procedure and command to do a postupdate on a DS918+? I tried this: ./rploader.sh update now ./rploader.sh fullupgrade now ./rploader.sh backup ./rploader.sh postupdate apollolake-7.1.0-42661 But I keep getting Check custom_config.json for platform settings. I copy paste the platform from the output of the postupdate function to make sure. On another note I was able to do yesterday ./rploader.sh postupdate bromolow-7.1.0-42661 for DS3615xs+. While troubleshooting today I tried this as well and still game me the Check custom_config.json error message. Thanks in advance. UPDATE: I think I realized my mistake. Updating in case someone else is in the same boat. I was trying to migrate from a previously setup of a DS3615xs+. Had to manually reinstall update2, make sure Synology Assistant found it as recoverable, perform the recovery, upon reboot go to TCRP and run the commands above and then the postupdate worked without spitting the check custom_config.json error.

Has anyone experienced an issue with VMM, where it displays Guest has not initialized the display (yet)? Using DS3615xs on 6.2.2 on a Dell PowerEdge T410 server with Intel® Xeon® Processor E5503. Same error under 6.2.1. Any advice would be much appreciated. Thanks.

Did you try Edit Virtual Machine -> General -> Gear Icon next to CPU(s) -> Advanced Options -> Enabled CPU compatibility mode? Wasn't able to run CentOS until this was checked.