foxbat

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 Update 6 - Loader version and model: JUN'S LOADER v1.03b - DS3617xs - Using custom extra.lzma: NO - Installation type: ESX 6.5, ESX7.0 - Additional comments: FixSynoboot.sh applied.

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922- update 4 - Loader version and model: JUN'S LOADER v1.03b - DS3617xs - Using custom extra.lzma: NO - Installation type: VM - ESX 6.5, ESX 6.7u3 - Additional comment: reboot required! | NIC: E1000e

I m not agree! It's suitable only for very small VM's .Not for the production environment . (data transfer to/from esx data store using copy/paste it's very slow ). And there it's not deduplication as well.

Sorry, I did not know because I don't have free version. I'll try and report.

Veeam backup.

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.7-15284 - Loader version and model: JUN'S LOADER v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL + ESX + VMWS - Additional comments: REBOOT REQUIRED

@millenium - please tell me - new_ip does appear on Syn Assistant or only in router lease? I was unable to get any ip if I try to boot with 1.02b and hdd with 6.2.

Found one solution! After 2 days (Testing all JUNE bootloader and follow all info from here) finally I am happy! I’m sure that can be some sort of shortcuts but “better safe then sorry”. My setup - 4x4TB WD, RAID 5, June 1.02b, 6.1.7 (DSM_DS3615xs_15284.pat), bare metal - Update to 6.2 – brick. Step 0 - new 1.03a BL ( on esx/vmware workastion, bare metal) - no joy. ( tested on i5, i7, , network card intel, 3com, broadcom, e1000, e1000e, vmxnet3). 1 day of work+ 1 night Step1 - Follow the procedure from synology – download Ubuntu, live CD, assembly raid, backup data( on usb external storage) Step 2 - New usb stick with 1.02b – try to boot with it and with only one hdd from raid connected – After boot, not network and stick unusable (tested 2 times) – it looks like DSM6.2 from hdd write something on USB stick ! VERY IMPORTANT- USE FRESH STICK ( with right pid.vid ser/mac) - Boot from live CD with paragon software (based on WinPE) with all 4 hdd connected and WIPE ( not delete) first partition on every hdd ( ONLY FIRST ONE from all 4) Step 3 - Boot from USB with NO HDD and after connections on SYNology Assistant ( and ip from DHCP) –first HDD connected. After few seconds I was able to install (using Assistant) 6.1.7 (DSM_DS3615xs_15284.pat). Not working with DSM_DS3615xs_15152.pat !!!!! ( error mesaje – “need 15284 or newer”).\ Step 4 - Same as 3 but installation on hdd no 2 ( only) . Please pay attention – boot from USB WITH NO HDD connected!! Only after boot and visible on Assistant the hdd will be connected (I remove only power connector from each hdd) Step 5, 6 – same , with hdd 3, 4.one at the time. Same name on each installation(4) with same name as original storage and admin password. Step 7 – shutdown. Step 8 - Power on with only one hdd connected, login and check if error message ( danger, volum error, blabla,) pop up. Wait few seconds and connect all remaing drives(3).Another error message ( system partition failure on the new added drive but don’t worry, it’s ok). Reboot !! Login and - Press “repair” on volume/raid windows (Storage Manager) and ..voila! All my data are recovered!! All folder structure, all data, not single byte missing J. DSM 6.1.7 Of course, RAID SCRUBBING will take all night but my NAS it’s up and running! Settings are not preserved( I’ll do the LDAP settings tomorrow). Thank you all of great people here ! Sorry for the brief tutorial but I need to sleep after 2 nights. PS I have ex4 but I'm pretty sure that will work on btrfs as well

all options are not working for me wit 1.03 ( vmware or bare metal). my config - i5 3260, 4 x 4Tb RED WD, 8 - 16 GB RAM. tried with Intel network cards , not luck. ( all those configurations run great previously on xpen 5.2 - 6.1.7 ), bare metal or ESX now I m try with ubuntu to recover my data(12 TB, raid 5, ext4)

hello I'm testing june alfa 1.03a2 BL ( unfortunatelly by mistake I just brick my 12 TB syn on ESX ( update to DSM 6.2 on old boot loader). I don't receive any IP so I need vip/pid /mac/serno ( only to recover data and i'll go back 1.02b). Any clue please? Or, better, if there are any advice about how can I recover my data(raid 5, 4 x hdd). I want to mention that I dont ask for serial and stuff for accesing orignal services from Synology! Thank you very much for all help!

-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 - DS3618xs - Installation type: VM - ESX 6.5 - Additional comments: No reboot needed

- 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 (HP G8) + 3 x ESX (5.5, 6.0, 6.5u1) - Additional comments: Requires reboot

- 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, VM (ESX 5 + ESX 6.5) - Additional comments: Requires reboot

yes with 10 TB data on it

UPDATE OK on bare metal ( hp) and esx6.5. ( from 6.1.3 u8)