Alan Dozier

I don't know, but if someone can figure out how my fiddling got the upgrade to work, it might work for you. That is why it would be good if some experts have a look at it.

Hi guys, I have some knowledge of computers and decided to do an Xpenology setup last April. I installed the 1.02a alpha loader on a ESXI 6.5 VM. I used an old server for the job. Every thing was fine until a couple of days ago when I clicked the update button for DSM. I lost connection to my Xpenology VM. I read everything in this forum over and over and began trying things. I could not get the serial connection to work. I could putty or winscp to my Host but that was it. No matter what I did to get to my Xpenology VM it was connection refused using the serial connection. I fiddled with the firewall, you name it. SO I went to another method, create another VM and migrate the data drive. Well the problem was I had used all my space, since I dedicated this server to just being an Xpenology box. So in the VM setup I used existing hard drive and not knowing what I was doing I put the synoboot.img in a temp directory and then put it on the virtual DVD drive. When I started this test VM up I got "No Operating System Found". I have never used ESXI before last April and know very little about it, so I do a lot of dumb stuff. After I fiddled around with this VM for hours, I went back and started my original VM and boom, I noticed on my virtual switch the connections were lit up! I did the find.synology on my browser and it found my original VM and asked if I wanted to recover the data because it had been moved from another machine. I said yes and a miracle ocured and I was back in business. Apparently what had happened was I had uploaded by accident the 1.02b synoboot.img to my old VM while fiddling with my test VM and did not know it. I got clued into this because the date on it was June 25 on the original VM. At least this is my best reconstruction of past events. Some knowledgeable people on this forum might be able to figure out what happened and post an easy fix for those who decided to test fate and do the latest update and loose their connection to their box. At least for those like me who were running on ESXI 6.5 VM.