Hostilian

Members
  • Content count

    125
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Hostilian

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. I don't think it's guaranteed to have networks available just because it scans for an IP address during PXe boot.. Does it actually find an IP address via PXE? My testing for ESXi is out of date (I last tried it on 6.1 but all my machines are bare metal - I don't have a need to install Synology inside a VM). This test was for VMWare 'Workstation' though.. Need details. What sort of NIC do you have and have you entered a valid serial number and MAC Addresses in the grub.cfg file (within the image or on the disk)? You can use OSFMount (plenty of guides on here) to mount and edit the IMG File (before you convert it).. Which hardware (server type or whitebox), which Syno hardware (918, 3615, 3617) etc etc. #H
  2. For Vmware tools you need to use Open VM Tools.. I got mine here - http://spk.4sag.ru/ Download the Application package and install manually.. I think you might need to change the trust level to 'any publisher' and possibly allow beta versions (this is done from the Syno web console).. I think a fellow forum user (4sag) runs this site, so props to him/her..
  3. Hi all I just spent 20 minutes testing this in VMWare Workstation 14. Worked fine! Process probably isn't that different from ESXi - and you can always move the box into ESXi if you wanted to.. Step by step.. Sorry, didn't do any pictures, but if you know your way around Vmware, it won't be an issue.. Process! Download Jun's DS3617 .img file - 1.03b. Convert the img file to VMDK (vmware disk) using Starwind v2v image converter (free program). Create the new Synology VM.. note.. Move the vmdk file, created earlier, into the new VM's folder. - Create the new VM you want to use for Synology.. Hardware compatibility ESXi 6.5 (so you can move it around). - Guest OS = Linux. Version = Other linux 4.x or later - 64bit. - Add a new SATA hard disk and opt to use an existing virtual disk. Use the VMDK created above as it's source. - Create 2x SCSI disks (your main Syno disks) of whichever size you need. - Remove soundcard, USB drives and add serial port. You probably won't need a CDRom drive either. Edit the VM's settings! - Ensure that 'BIOS' is the boot method (not UEFI) - see Advanced section on Options tab. *UEFI might work - didn't test it.. Start the VM and open the BIOS settings - or else you'll find it will try to boot to the network.. - Edit the VM's BIOS - by hitting escape when starting it - and change the boot order to ensure the SATA drive is first in the boot order. Not SCSI.. Not network. Only the SATA drive first! That's it configured, now to install DSM.. You can follow the standard procedure for this.. - Boot the machine and scan the network for the allocated IP.. - Install the PAT file for DSM 6.2.. - Reboot, set a static IP address, update to U2 etc. Job done.. Hopefully this is of some use! #H
  4. Hostilian

    Supported PCI-e Sata cards?

    Syba SI-PEX40062 SATA III 4 Port PCI-e 2.0 x2 Card ....This one works in the DS3617 box I use for my VMWare LUNs..
  5. Hostilian

    DSM 6.2-23739 Update 2

    - Outcome of the update: SUCCESSFUL (with caveat) - DSM version prior update: DSM 6.1.7 u2 (DS3617xs) - Loader version and model: JUN'S LOADER v1.03b - DS3617xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock J3455-ITX, using Intel NIC, 16GB RAM and 3x SATA disks (SSD, SSD, 3.5). - Additional comments: Upgrade went fine to 6.2 (now Update 2) - but write transfer speeds about about 60-70% of what they were (I think). Read speeds look ok..
  6. Hostilian

    DSM 6.2-23739 Update 2

    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.7 (DS3615xs) - Loader version and model: JUN'S LOADER v1.03b - DS3617xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - (old Dell Optiplex 755) - Additional comments: Upgraded from DS3615xs (DSM 6.1) to DS3617xs (DSM 6.2) without a problem - with Intel NIC.. - Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.1.7 u2 (DS3617xs) - Loader version and model: JUN'S LOADER v1.03b - DS3617xs - Using custom extra.lzma: NO (is there one for 1.03b?) - Installation type: BAREMETAL - ASRock J3455, using realtek onboard NIC, 16GB RAM and 3x SATA disks (SSD, SSD, 3.5). - Additional comments: Failed to find on network following boot.. Will re-try with an Intel NIC..
  7. Hostilian

    Progress of 6.2 loader

    Tested the new loader (Thanks Jun) with my crappy old Dell desktop (as above). Same serial and MAC as used for above. Planning to install DS3617 image, so using that 1.03b loader.. Boots fine, gets IP Address OK.. It even finds my old DS3615 install on it.. This is gonna be interesting. Selected a fresh install of DS3617 DSM and installed the new PAT file (without update 2) DSM 6.2-23739 Booted fine.. Even had my customizations still in place (wallpaper, login banner and text). Installed update 2 from web and rebooted. Updated fine - even had all my old test data in place.. Tested Write/Read.. 112MB/s both ways on GBEthernet.. Superb work as always Jun.. 🤘 Will be doing some more testing before upgrading my main boxes but this is looking excellent!! #H
  8. Hostilian

    Progress of 6.2 loader

    No joy for me either on 1.03a It is an old test machine (old Dell desktop) so its CPU is waaaaay older than Haswell. Worked fine as a test machine in the past, but I guess I'll wait until this has broader CPU support before testing again! Won't be anywhere near my 'production' NAS boxes on DS3615 and 2x DS3617 for a while yet! 😕 Thanks for all your efforts, guys! #H
  9. Hostilian

    DSM 6.1.5-15254 Update 1

    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.5-15254 - Loader version and model: Jun's Loader v1.02b - DS3617xs - Installation type: ASRock J3445 ITX, 12GB (1600 MHz) RAM - Additional comments: No reboot required but services restarted. No problem after reboot too..
  10. I think you can use external USB as an rsync destination.. You're limited in what you can use (I wanted the files browsable anyway, so wasnt a problem) but it works.. At least I think it did when I tried it! Very interesting.. Will see if I can figure out how to set one of the drives (or more) as eSata, thanks!
  11. Thanks.. Aye, external is an option - though performance would obviously drop.. At least I'll be able to fully control utilisation and power though.. Don't think I have an external 3.5 caddy (only 2.5) so I'd need to order one.. I'm actually thinking of moving the drive to another NAS that I only switch on for test lab work.. That might be the best option! Thanks for the ideas!
  12. Scenario is that I use my always-on NAS as a surveillance station NAS (plus a music share, out of convenience). It was a DS216j but it wasnt powerful enough. New box has a disk dedicated to the surveillance station footage (lets say disk 1) Another for occasional remote Backups (disk 2). There are no Packages installed on this drive.. Another SolidState Disk for installed Apps and some VMs (disk 3). I dont use Disk2 that much (just for occasional backups) and I don't want it always on. I am not convinced HDD hibernation is working as it runs warm (not hot) just warm - even when nothing is accessing it (29DegC).. Can I do anything to get it to shut down properly - aside from removing the power cable until I need it? The previous backup disk failed (this is a RMA disk) and I don't want it to be 'on' if it's not required.. Would there be any effects of removing the power from the drive between DSM updates? Thanks! #H
  13. Hostilian

    Poor SSD Write speeds

    If you're copying a very large file, then I'm sure there are a few other topics (from a while back) on something similar. Is this using Windows to copy the files using Windows explorer - or allowing the two synology boxes to do the copy?
  14. Hostilian

    Migrate baremetal to ESXI

    Sounds like a lot more hassle than it's worth.. If you have spare disks, I would just set it up the same again in ESXi and just copy the data across.. Though in my testing, BareMetal was faster for me than ESXi.. I keep my couple of (always-on) VMs on an SSD in Synology VMM, and it's fine.. For anything more advanced (virtualisation-wise) then I felt I was better off with a separate ESXi server - using my bare metal Synology box as iSCSI Storage.. Depends if you want to mess around with vmotion etc..