piter
-
Posts
10 -
Joined
-
Last visited
Everything posted by piter
-
I know that we have to run these commands after installing update 2 (in this example for DS3622xs+): ./rploader.sh update sudo ./rploader.sh postupdate broadwellnk-7.1.0-42661 In my case sudo was very important - without sudo I had a lot of errors (including "Compressed data is corrupt"). My question is: don't we have to run this command at the end: ./rploader.sh backup
-
- Outcome of the update: UNSUCCESSFUL - DSM version prior update: new install - Loader version and model: TCRP 0.8.0.0 DS918+ - Using custom extra.lzma: NO - Installation type: ESXi 6.7.0 Update 3 (Build 16713306) VM on Xeon(R) CPU E5-2650 v3 - Additional comments: Recovery loop - Outcome of the update: SUCCESSFUL - DSM version prior update: new install - Loader version and model: TCRP 0.8.0.0 DS3622xs+ - Using custom extra.lzma: NO - Installation type: ESXi 6.7.0 Update 3 (Build 16713306) VM on Xeon(R) CPU E5-2650 v3 - Additional comments: Control panel -> Update & Restore -> DSM Update -> "Status" shows "Connection failed. Please check your Internet connection." and "Release notes" link points to example.com webpage (it's a little strange)
-
- Outcome of the update: UNSUCCESSFUL - DSM version prior update: 7.1-42661-1 - Loader version and model: TCRP 0.8.0.0 DS3622xs+ - Using custom extra.lzma: NO - Installation type: ESXi 6.7.0 Update 3 (Build 16713306) VM on Xeon(R) CPU E5-2650 v3 - Additional comments: Recovery loop
-
There are couple problems with these dirs, especially with custom apps like Universal Media Server. Besides I really don't see a reason to have these folders...
-
Hi. Does anybody know how to stop DSM 6.0 from creating @eaDir directories everywhere? I've tried several solutions, but none of these work in DSM 6.0...
-
I've connected 3 disks - 2 SCSI disks with DSM 5.2 data and 1 SATA disk with image created by you. It works perfectly on VMware ESXI. I was worried about my virtual SCSI controller (VMware Paravirtual) and virtual network adapter (VMXNET 3), but they both are working fine. Very good job jun! Thanks!
-
This was on existing xpenology VM, but I've created this VM manually a month ago. I think that it is possible to create a new VM (with serial port), upload and attach your disk image (vmdk + img files). My guest OS type is: Other 3.x or later Linux (64-bit).
-
OK, got it working in ESXI 6.0. I've simply uploaded synoboot.vmdk and synoboot.img files to ESXI datastore and attached synoboot.vmdk as SATA hard disk. I had to add serial port to virtual machine.
-
I can't import OVF to ESXI 6.0 because I'm getting this error: Opening OVF source: d:\server\xpenology\ovf\ds3615.ovf Enter login information for target vi://10.11.11.1/ Username: root Password: ******** Error: Host name (root) resolve failed Warning: - No manifest file found. - Wrong file size specified in OVF descriptor for 'synoboot.vmdk' (specified: 0, actual 432). Completed with errors I'm using ovftool - what am I doing wrong?
-
Is anybody able to create bootable ISO image?