unmesh
-
Content count
76 -
Joined
-
Last visited
-
- 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
-
Don't know why but I haven't had this problem. Yet!
-
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!
-
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"
-
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.
-
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?
-
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!
-
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.
-
It worked fine on my ESXi install. ESXi 6.0u2? Which of the loaders did you use? And did you import the OVF or set things up manually? Thanks.
-
I built a VM with this OVF, installed DSM, installed Update 3 and was even able to reboot from the DSM UI. Once I powered down the VM, though, it cannot see the hard drives at power on and tries to PXE boot off the network and gives up saying it cannot find an OS. Any suggestions?
-
I'm trying to take the new DSM for a test drive in ESXi 6 with the new Jun 1.01 loader but importing the OVF file always gives me the error Failed to deploy VM: postNFCData failed Anyone else seeing this? I've tried the webui with both Chrome and Firefox in case there was a browser anomaly. I've also tried the Windows fat client but it too fails during upload.
-
I've upgraded 6 PCs to Win10 and haven't run into this. Is File Sharing enabled in the Windows Firewall settings? (As a quick check, you could turn off the Firewall temporarily and see if that restores network file access.)
-
This may not apply to OP's situation but I saw more predictable behavior with rsync between two instances of Xpenology when I turned off compression and encryption.
-
I use the "complex" method myself. How do you edit the serial number in the vmdk file?
-
You can't get SMART data on your hard drives if you use ESXi.