• 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. In the process of trying out Jun's 1.03b bootloader on a new VM on my ESXI Server, I accidentally reused the serial number from another VM that was using the 1.02b bootloader. From other threads, I figured out how to edit the grub.cfg in the vmdk version of the bootloader to provide a new serial number and the VM booted but the Control Panel -> Info Center -> General page has no information on it Any suggestions for how to fix this will be greatly appreciated. (It is possible that this tab was blank when the original VM was created since I did not bother to look). P.S.: Synology Assistant does show the correct new serial number
  2. I'm guessing this is for me, so I will take this to General Questions ...
  3. I came upon this thread when I accidentally reused the same serial number when I created a test VM on my ESXi server to migrate from 1.02b to 1.03b bootloader. Unlike sbv3000's experience, one or the other XPE VM's crash after a while when both are running and I need to do a controlled experiment to see if the serial number is the root cause. In any case, is there a quick way for me to change one of the serial numbers without going back to the original bootloader image file, finding and editing the grub.cfg and making the vmdk file? Thanks.
  4. I did a successful install on the AsRock!
  5. Disabling the onboard NIC fixed the power off problem! Thanks, guys.
  6. @bearcat I might repurpose a seldom used AsRock Q1900DC-ITX with v1.04b and DS918+ based on your experience. I've been wanting to play with BTRFS and this will give me a platform to try it out on before I switch my "production" NASes over.
  7. @jarugut I have a different BIOS ("The Bay") that does not allow me to choose the ACPI version but will check that the onboard NIC is disabled as per your suggestion and from @bearcat earlier. Thanks
  8. @bearcatThat was an old signature! And I will look at the NIC setting tonight.
  9. I recently upgraded from 1.02b to 1.03b loader and 6.1.7 to 6.2.1 DS3615xs and everything works except for shutdown. I have C1E disabled in BIOS and my N54L uses an Intel NIC. Nothing extra. Any suggestions? Thanks.
  10. 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
  11. For now, I have gone back to 6.1.7
  12. 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.
  13. 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
  14. 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)
  15. 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.