• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About unmesh

  • Rank
    Regular Member

Recent Profile Visitors

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

  1. unmesh

    6.1.7 to 6.2 migration partially successful

    Be aware that it was not completely successful for me! I downloaded the V1.03 bootloader and edited grub.cfg to put in my serial number and MAC address. I shutdown the DSM 6.1.7 VM and pointed the virtual HD to the new bootloader. I also changed the virtual NIC to e1000e. I then booted the VM and picked the ESXi entry from the bootloader menu. I opened a web browser to the DSM's IP address and did a manual update to the DS3615 6.2-23739 pat file, let it reboot and then logged in to the DSM GUI. That is when I noticed that several of the Control Panel screens were messed up and went back to 6.1.7
  2. unmesh

    6.1.7 to 6.2 migration partially successful

    For now, I have gone back to 6.1.7
  3. I'm running ESXi 6.7 and did a migration from DS3615 6.1.7 and bootloader v1.02 to DS3615 6.2-23739 and bootloader v1.03. The migration seemed to be successful but, when I logged in, the network setting page in the GUI did not have a gateway configured (amongst other problems) and won't let me manually correct it. Has anyone else seen this? Is there a fix other than trying to go back to 6.1.7? I have a backup but it is on a slower server and I'd prefer to get his one fixed! Thanks.
  4. unmesh

    Tutorial: Install DSM 6.2 on ESXi 6.7

    I used Ragz's MAC address in both the VM and the grub.cfg file but the e1000e VNIC is still not showing up on the network. The potential differences that I can see from some of the others is that I am using BIOS to boot instead of EFI and need to put the synoboot.vmdk on IDE 0 (Master) instead of SATA 0. Also the VM is type 14 and the S/N is not in any way correlated to the MAC address Hopefully someone can suggest other things to try. Thanks. P.S.: FWIW, I have DSM 6.1.7 running as a VM with V1.02 bootloader on the same ESXi 6.7 server with a e1000 VNIC. CPU is Haswell i3-4130
  5. unmesh

    DSM 6.2 Loader

    The tutorial reference link says I should be using e1000e and not e1000! Is it safe to shut down the VM and change network adapters or do I need to do something else? Assuming this works, is it then OK to install 6.2.1 from the DSM 6.1.7 GUI? (I will switch from EFI to BIOS too)
  6. unmesh

    DSM 6.2 Loader

    I have a DS3615 6.1.7 running with the V1.02b loader on ESXi 6.7 with an E1000 VNIC configured and EFI boot and tried to first upgrade only the loader to V1.03b. I can select the ESXi entry in Grub, see the "screen will stop updating shortly" message but Synology Assistant does not see a server on the LAN. Should it work or does V1.03b have to be paired with DSM 6.2.x? Thanks.
  7. I haven't had problems with this before but after a power outage earlier today, I get a "connection refused" message when I try to access the web admin page with a browser on a Windows PC. I can mount SMB shares and see all my files and SSH into the box I've tried both http:// and https:// Synology Assistant cannot see the server either I'm running Jun's 1.02b loader and one of the recent 6.1 builds Any ideas to fix this will be greatly appreciated
  8. unmesh

    DSM 6.1.6-15266

    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.5-15254 Update 1 - Loader version and model: JUN'S LOADER v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: VM - ESXi 6.5.0 Update 1 Build 7967591 - Additional comments: REBOOT REQUIRED
  9. unmesh

    DSM 6.1.x Loader

    Don't know why but I haven't had this problem. Yet!
  10. unmesh

    DSM 6.1.x Loader

    Thanks, worked for my migration except that I also had to change the VM settings to do a EFI boot instead of it's previous BIOS boot. Now to figure out if I can change the hard drive format from ext4 to btrfs which was my motivation to upgrade in the first place!
  11. unmesh

    Recommended Hardware?

    I've had good experiences with my Gen7 HP and may buy the Gen8. The Syno in the link uses 2." drives, not 3.5"
  12. Earlier today, I tried installing the VPN Server package and it won't install because "package is not from a trusted publisher"! I then tried other Synology packages and get the same message. Anyone run into this? P.S.: If I change the settings to allow packages from "Any Publisher", the install is successful.
  13. My NAS is serving a bunch of PCs that do file sharing using a drive letter CIFS/SMB mount as guest. If I have to do something manually, I usually SSH into the NAS as root and do a "su guest". After updating to the latest DSM 5.2, this no longer works. "whoami" shows I am still root. Anyone else noticed this? Any suggestions?
  14. unmesh

    DSM 6.1.x Loader

    v1.0 fails too using OVF import. The problem seems to be that synoboot.img is not loading successfully. I then converted synoboot.img to synoboot.vmdk using the Starwind converter and set up a VM manually and it works!
  15. unmesh

    DSM 6.1.x Loader

    Yeah 6.0u2 and loader v1.0. Using the OVF but make sure it is an SATA disk. I could only set this up in the webui (https://your esxi ip/ui). v1.1 did not work for me per my earlier posting; will try v1.0 and report back.