• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Super169

  • Rank

Recent Profile Visitors

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

  1. - 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)
  2. 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.
  3. 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.1.7, just cannot boot in v6.2. Any suggestion? Thanks in advance.
  4. 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.
  5. 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 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?
  6. Do you mean that I should have problem? I was using the DS3617xs image already,
  7. I've been using DSM 6.1.3-15152 Update 4 for few days, no problem encountered so far.
  8. 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.
  9. 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.
  10. 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:
  11. 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.