Super169

- Outcome of the update: SUCCESSFUL - DSM version prior update: Fresh Install - Loader version and model: RedPill DS3615xs v7.0.1-42218 Update 2 - Using custom extra.lzma: NO - Installation type: ESXI 7.0U2a Build image from source: https://github.com/tossp/redpill-tool-chain/archive/refs/heads/master.zip Then convert img to vmdk for VM. May due to old CPU (E5-2600V2), fail to load with apollolake, can only use bromolow.

Fixed: This may due to my old cpu (E2660V2), which cannot simulate DS918+. Just down the source from https://github.com/tossp/redpill-tool-chain and build for bromolow (i.e. ds3615xs), it works fine.

I have the same problem installing in ESXi 7.0.U2A, the VM cannot be detected. Already set the MAC address in VM's network setting, but it cannot detected by Synology Assistant and web app, even the MAC has not shown in router. It's seems that the network has not started.

- Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922-2 - Loader version and model: JUN'S LOADER v1.03b - DS3617xs - Using custom extra.lzma: NO - Installation type: VM - Intel W2600CR2, E5-2660x2 - vSphere 6.7.0.2000, ESXi 6.7.0 Build 10302608 - Additional comments: Use 2 x SATA Controller (0 for img, 1 for others); NIC: E1000E

- Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922-2 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: VM - Intel W2600CR2, E5-2660x2 - vSphere 6.7.0.2000, ESXi 6.7.0 Build 10302608 - Additional comments: Use 2 x SATA Controller (0 for img, 1 for others); NIC: E1000E

- Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: VM - Intel W2600CR2, E5-2660x2 - vSphere 6.7.0.2000, ESXi 6.7.0 Build 10302608 - Additional comments: Use 2 x SATA Controller (0 for img, 1 for others); NIC: E1000E

- Outcome of the installation/update: SUCCESSFUL - DSM version prior update: -- clean installation using 6.2 image -- - Loader version and model: JUN'S LOADER v1.03b - DS3617 - Using custom extra.lzma: NO - Installation type: VM - Intel W2500CR2, E5-2660x2 - vSphere 6.7.0.2000, ESXi 6.7.0 Build 10302608 - Additional comments: Use 2 x SATA Controller (0 for img, 1 for others); NIC: E1000E

I don;t know what I can said.... Just can't believe..... I try to install again and capture all screen for reference, and it works right after installation. Here is the setting I used for installation. And I try to install again with "Ubuntu Linux (64 bit)", it works fine also. Just can't remember what's the difference, but it failed all the time last week. Thanks for your support, and I can work with 6.2.2 now.

I will try to follow your setting and install again tomorrow. Seems the only difference is the OS version, but I guess there should have no difference. Thanks a lot

The registration page I have tested years ago is not longer available, so I just use the default in img without change, do I need to modify it to met the MAC, or register in somewhere? The S/N in grub.cfg: set sn=A8ODN02468 Thanks a lot.

I have some DS3617xs VM running with DSM 6.2 build 23739, and I know that it may not be possible to upgrade to DS3617xs as it need to change the disk from SCSI to SATA. It may need to build a new VM and transfer the data and all setting to it. I found that some people reported that they can successful use DSM 6.2.2 with DS3617xs on ESXi in here ( but I have tested few days, no matter how I build the VM, upgrade from 6.2 or new installation, it cannot be detected after upgrade. I have followed the instruction here to build the VM. But it doesn't work for DSM 6.2.2 So far, I can only build the DSM6.2 VM with DS3615xs, a clean installation, with 2 SATA controller, one for the boot image, and one for other disk, and it need to change the NIC to E1000E after installation. However, it doesn't work for DS3617xs and DS918+ iamges, for DS3617xs, I can install / upgrade the DSM 6.2.2, but it cannot be detected after reboot, no matter which NIC is used, it cannot be detected in the router. For DS918+, it's even worse, I cannot boot the image, it cannot be detected by find.synology.com, and also not found in the router. I guess they may still have come setting I have missed, but I cannot found it out yet. Is there anyone know the VM configuration for running DSM 6.2.2 with DS3617xs or DS918+ image on ESXi? Thanks a lot!

- Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2-23739 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: VM - Intel W2500CR2, E5-2660x2 - vSphere 6.7.0.2000, ESXi 6.7.0 Build 10302608, - Additional comments: Use 2 x SATA Controller (0 for img, 1 for others); NIC: VMXNET 3

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2-23739 UPDATE 1 - Loader version and model: JUN'S LOADER v1.03a2 - DS3617xs - Using custom extra.lzma: NO - Installation type: VM - ESXi 6.5.0 - 2 x E5-2660V2 on Intel W2600CR - Additional comments: Has to add SATA Controller, and change loader's virtual devic node as SATA(0:0)

Oh, I have missed your post before. It seems that I have used wrong disk type, it should be SATA not IDE. After comment the options in grub.cfg, and changing the disk setting to SATA as in your post, it seems OK now, and it allow me to migrate the existing disk. Thanks a lot.

I tried to install a new VM, or upgrade the existing VM by replacing the 6.2 loader, both of them will stuck in the following screen. I have tried different options from this post, 1) set Boot Options to BIOS (actually there has no other choice in my VM setting) 2) modify the grub.cfg in bootloader, and change DiskIdxMap=0C to DiskIdxMap=0C00 3) Set the loader disk as IDE instead of SCSI All failed. I'm now running vSphere 6.5.0 on the server with 2 x E5-2660V2 on Intel W2600CR MB, will this be the problem of dual CPU? It works fine in v6.1.7, just cannot boot in v6.2. Any suggestion? Thanks in advance.

Thanks for the information. I have used the old vmdk with 1.03b image, and it will boot to the screen as your first post, and it cannot be detected. But I have already set the Boot Options to BIOS. Maybe I will try to copy one the vmdk of my DSM 6.1 machine for testing again. I'd like to confirm the step for upgrade, should it be upgraded to 6.2 then replace the img file, or replace the img file at 6.1 then upgrade to 6.2? Thanks a lot.

I'd like create a new VM to test 6.2 with 1.03b, but I can found any vmdk for 6.1. If I use the vmdk from 1.01, it will stop at boot, and cannot be detected in find.synology.com. I have already set the boot option to BIOS, but still cannot boot. Does it mean that the synoboot.img only work for 6.2? So, I have to install 6.1, and then upgrade to 6.2, and replace the synoboot.img after upgrade?

Do you mean that I should have problem? I was using the DS3617xs image already,

I've been using DSM 6.1.3-15152 Update 4 for few days, no problem encountered so far.

After searching in internet, it seems to be a issue in DSM, the user account is corrupted. However, I have disabled the admin account, and now my account cannot do anything. It cause "Operation Failed" in many functions. But I cannot follow the step from Synology to reset the account as there does not have reset button in XPEnology. Is there any other way to reset the account, I can still ssh to the server as root, but I don;t know how to reset my account.

More information: just tested, the task created is still working, and it can sync the file to other server. But I cannot create any new task, or update the existing task.

Just try to upgrade the DSM also, but still cannot fix the problem. But there has some strange in the DSM Update screen, it cannot show the model and current DSM version:

I have installed multiple XPEnology DS3617 on ESXi server, and setup file sync using DSM's "Shared Folder Sync". Recently, there has problem in "Shared Folder Sync", an error of "Operation failed" is prompted when I press the [Create] or [Edit] button in the task list. This feature should works before, I'm not sure if any recent update in package center cause this issue. Recently, I have updated the "File Station" in package center, and a new version DSM 6.1.3-15152 Update 3 is ready to update, but I have not update yet. Anyone here encounter such problem in "Shared Folder Sync"? Is there any thing I can do to solve this issue? Thanks in advance.