Super169

Members
  • Content Count

    20
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Super169

  • Rank
    Junior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. - 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
  2. - 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
  3. - 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
  4. - 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
  5. 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.
  6. 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
  7. 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.
  8. 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
  9. - 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
  10. - 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)
  11. Super169

    DSM 6.2 Loader

    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.
  12. Super169

    DSM 6.2 Loader

    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
  13. Super169

    DSM 6.2 Loader

    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.
  14. Super169

    DSM 6.2 Loader

    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?
  15. Do you mean that I should have problem? I was using the DS3617xs image already,