Bohemian

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.7-15284 Update 3 - Loader version and model: TCRP UEFI.v0.9.4.9 - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock Z170 Extreme6 - Additional comments: Set static to "true" in user_config.json, initial boot with TCRP friend

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.7-15284 Update 3 - Loader version and model: Jun's Mod V1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock Z170 Extreme6 - Additional comments: New bootloader, so Reboot & Migration Required

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.7-15284 Update 2 - Loader version and model: Jun's Mod V1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock Z170 Extreme6 - Additional comments: REBOOT REQUIRED - Had to power cycle hardware after update

- Outcome of the update: SUCCESSFUL - DSM version prior update: 6.1.7-15284 - Loader version and model: Jun's Mod V1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock Z170 Extreme6 - Additional comments: REBOOT REQUIRED

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.6 15266 Update 1 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Using custom extra.lzma: No - Installation type: BAREMETAL - ASRock Z170 Extreme6 - Additional comments: REBOOT REQUIRED

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.5-15266 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock Z170 Extreme6 - Additional comments: NO REBOOT REQUIRED

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.5-15254 Update 1 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Using custom extra.lzma: No - Installation type: BAREMETAL - ASRock Z170 Extreme6 - Additional comments: REBOOT REQUIRED

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.5-15254 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: Baremetal (ASRock Z170 Extreme6) - Additional comments: No Reboot Required

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4 15217 Update 5 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: Baremetal (ASRock Z170 Extreme6) - Additional comments: Reboot Required - Re-edited synoinfo.conf to re-enable SHR

Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4-15217 Update 2 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: Baremetal - Additional comments: Requires reboot, reloaded custom synoinfo.conf

Excuse my ignorance, but can I add the ramdisk to my USB stick after already installing DSM? (And presumably rebooting). I'd like to use an Intel NIC I have installed on my already working ds3615 system. Would adding the ramdisk foobar my system?

All fine here too. No NAS restart required, only SMB service. ASRock Z170 Extreme6, DS3615xs bare metal, Jun's Mod V1.02b

DS3615xs Jun's Mod V1.02b Custom ASRock H/W (see sig) From 6.1.3-15152 Update 8 No issues.

Loader: Jun's v1.02b (3615xs) DSM: 6.1.4 U1 Hardware: ASRock Z170 Extreme6 + 16Gb RAM + 5x 4TB 3.5" HDD Updated from 6.1.3 U8 without any issues.

Thanks - good to know.

I'm still running on my testing server but looking to take the plunge. I did the edits above to enable SHR on DSM 6.1.3. But when I upgrade to DSM 6.1.4, my modified synoinfo.conf gets overwritten and I lose the changes for SHR support. So two questions: 1) Is there any way to make these changes stick or will I likely face the same issue every time I update? 2) If my SHR system boots after an upgrade with a non-modified synoinfo.conf, is my storage / system at risk? Any insights / speculation would be welcome. Thanks!