Akide_Liu

New Members
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Akide_Liu

  • Rank
    Newbie

Recent Profile Visitors

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

  1. Source page of update introduction: https://translate.google.com/translate?sl=auto&tl=en&u=https%3A%2F%2Fen.llycloud.com%2Farchives%2F2313 The 6.2.0 system that I used to use before the group has recently found that there are some small bugs that do not affect the use but still a bit of a coping. So I decided to update to the latest version of the system. I tried the direct update before, but without success, the entire group system was blacked out. Later I checked some information and found the problem: the boot does not support Because Jun.sloader v1.02b DS3617xs was used before. This guide supports up to DSM 6.1 (.2/.3/.4/.5/.6/.7), and I can upgrade to 6.2. So in this article, I will introduce the synology VM replacement boot and update system based on the vSphere platform. Software preparation Black Group Guide: https://xpenology.com/forum/topic/7848-links-to-loaders/ Black Qunhui User Upgrade Report: https://xpenology.com/forum/topic/20031-dsm-622-24922-update-3/?do=findComment&comment=124017 StarWind V2V Image Converter: https://www.starwindsoftware.com/starwind-v2v-converter Upgrade feasibility survey First we need to check the version of the boot support, for example we want to upgrade to the latest version of DSM 6.2.2, so we need at least v1.03b boot I have tested my environment. vSphere 6.7U2 only supports DS3617xs for the time being , so we have to choose Jun's Loader v1.03b DS3617xs. Everyone's environment is different, and it may take a few more attempts to succeed. Boot download: file download Then let's take a look at the installation of other users to see if there are any precedents for successful installation: We can see a similar example: He upgraded to 6.2.1 and then used the 1.03 boot, and used the same ESXi 6.7 platform and E1000E NIC as I did. More valuable value Then he also described some areas that need attention, such as requiring 3 manual restarts, unable to log in to web conlsoe and other issues. Step 1: Convert the boot file First we need to convert the boot .img file to the VM disk form: Use the StarWind V2V Image Converter tool: Then we can see two files like this: These two files are the files we need to upload to the vSphere repository. Step 2: Upload the boot file First of all! ! ! Create a snapshot or backup The upgrade may fail because the environment may be different. If it fails. . . . . I don't know how to roll back. The only way I think of is to download the VM disk to the local and read the content. Note: The virtual opportunity to do storage is normal, so don't choose to generate virtual machine memory snapshots. My environment here: 380GB content seconds to generate snapshots Select upload file: Select the two files that were generated before: Shut down the virtual machine and select system settings Delete the previous boot disk, 50MB of a disk, but do not delete the storage disk Add new device – add existing hard drive Add a new boot disk that was previously uploaded, the same size is 50MB, then save the settings. prompt: The added hard disk has to choose the SATA controller . It has been tested before. If you use the SCSI controller, you may not find the hard disk. Determine the type of E1000E used by the NIC, otherwise it may not be recognized. Then boot the system, if you can not boot the heavy, start the virtual machine 摁F2 adjust the startup item I chose the default option baremetal boot, which is said to be better compatible with virtualization using the third VMware/ESXi boot. Of course, the benevolent sees the wise and sees wisdom. Because I used the baremetal boot before, I can't find the hard disk if I use VMware boot. Then the interface appears and you can find the NAS by opening http://find.synology.com/ in your browser. Then we log in to the NAS and make sure there is no problem with the replacement boot. Step 3: Update the DSM system DSM release note: https://www.synology.com/en-us/releaseNote/DS3617xs#ver_24922-3 Log in to the group system to update DSM, because I have already updated it and I will not do it again. It's all graphical. If you don't know how to update, the official documentation is as follows: https://www.synology.com/en-global/knowledgebase/DSM/help/DSM/AdminCenter/system_dsmupdate note: In the update process, as long as the ping command has been used to monitor whether the NAS network card can be connected, basically the system can be started as long as the network card is connected. If the web conlsoe can't log in, the system is loading and waiting for more. Or reboot. During the update process, you may need to manually restart multiple times. I have restarted this installation twice. The previous install report was restarted three times. Regardless of success or failure, I hope that everyone will share their try installation report to the community, so that more people will find less pitfalls: https://xpenology.com/forum/topic/20031-dsm-622-24922-update-3 / Finally add a few screenshots after the success: Written in the last words Qunhui's DSM system is really the first choice in the NAS. If you have the strength, you should support the genuine Huihui as much as possible. Then wait for DSM7.0 to be released, I hope this update will have a lot of highlights: Https://nascompares.com/2019/08/31/synology-2020-launch-in-taiwan-dsm-7-0-new-nas-active-insight-hybrid-share-and-more/
  2. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2-23739 - Loader version and model: Jun's Loader v1.03b DS3617xs - Using custom extra.lzma: NO - Installation type: VM - VMware ESXI 6.7 U2, E1000E NIC - Additional comment: Take a snapshot before system updating. Two manually reboots required, during the initial automatically reboot, system will update to 6.2.2-24922 and can not login web console. After that system try to install 6.2.2-24922 update 3 from 6.2.2-24922, wait 3 mins then manually reboot. Use ping to check network connection then manually reboot, system will update properly and welcome to 6.2.2-24922 U3
  3. Hi, XPEnology team, I used the 1.04 boot for esxi 6.5, i modified the vm's network card configuration to e1000e and i can successful to see the boot page' use find.synology.com to find your nas' but i can not find the ip address from my router which is running the DHCP service. And the same time, i saw some webpage there shows 1.04 boot is fit the Esxi 6.7 However if i swap to use 1.03 boot, installation process will be successful, i would like to try the new features in least version DSM, so you can any suggestion for this issue or tell me how to debug to look for where the specific issue is.