Tuatara

Members
  • Content Count

    60
  • Joined

  • Last visited

Everything posted by Tuatara

  1. Fantastic. There is always just one more detail to remember!
  2. OK, I thought you passedthrough M1015, I'm curious if this card being recognized by DSM or not. I wasted two evenings trying to install SIL3112 based PCIe-to-SATA card. I either got DOA card or my only PCI slot is broken .. going to ship it back. I tried passthrough of the M1015 ages back. Right now, I can't remember if I had it working ... I think so, but I probably compiled/added the driver myself. I did put in a number of different manufacturers cards - Sil3114 for certain, and also a JMicron JMB363 - in which I compiled and added the driver to the Synology, and also into ESXi (for fu
  3. Paravirtual. Exactly as I'd specified in the "Idiot's Guide" (found earlier in this thread). I boot off the [Datastore] Synology/esxi_synoboot_3202_v2.vmdk - Configured as IDE (0:0) Hard Disk 1 SCSI Controller 0 - Paravirtual - No SCSI Bus Sharing All physical disks are RDM (Mapped Raw LUN) - Compatibility Mode (Physical) - vmdk files are stored in the VM directory (for example: /dev/sda) - vml.020000000050014ee25daf1b94574443205744 / [Datastore] Synology/WDC_2.0TB_1.vmdk - Configured as SCSI (0:0) Hard Disk 2 (8 total drives RDM on a M1015, with additional 5 drives RDM off Intel M
  4. For interest, I'll give it a go ... shut down Synology ... clear the RDMFilter flag ... restart VM ... synology running ... SSH login ... and we're ready. Let's check my first RDM drive in the array ... [spoiler=smartctl -a /dev/sda]mediacat> smartctl -a /dev/sda smartctl 5.42 2011-10-20 r3458 [x86_64-linux-3.2.30] (local build) Copyright © 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD20EFRX-68AX9N0 Serial Number: WD-WCC1T0773149 LU WWN Device Id: 5 0014ee 25daf1b94 Firmware Version: 80.00A80
  5. yes, i did reboot it. Rebooting won't do it. You have to RESTART the Virtual Machine in order for it to pick up the changed settings for the RDM controller. Restarting the Synology is still going to use the same VM setup!
  6. Thanks for the hint =) I'm keen to try it, even though I'm running 5.5 currently, but can easily rebuild it with 5.1 as I'm not 'live' yet with my home lab. VMWare doesn't often remove base features in point updates. I'm positive that these options are also available in 5.5 ... it's just in 5.1 when they were first noted as being available. Regards, Tuatara
  7. SMARTd is running on vSynology? I thought if one does RDM (ie created via vmkfstools {-z,-r} ), then SMART stats are not being exposed to a guest VM, vSynology in this case. Absolutely correct. There are NO SMART STATISTICS when using a RDM drive. This is BY DESIGN. However, we all know about pushing design limits! If you are using ESXi 5.1, and are willing to push boundaries, you can follow the guide available here: ESXi 5.1 and SMART monitoring In a nutshell (first post in the thread): All you need to do is the following and then any disk (not USB) you plugin in therea
  8. After following the guide for wmware tools I could not get shutdown and reboot to work from the vSphere client. The problem was that the "shutdown" binary did not function on my Synology install. I decided to just create my own "shutdown" script and replace the binary that was in /sbin/ with it: You beauty! I remember doing a similar thing now! Umm ... yeah ... ... works great for me too. The script I had written was much simpler though ... mine only called poweroff, since that was all I cared about doing through vSphere at the time. I've updated my DSM 4.2 to your script -
  9. Nice Cookin' Doc! I've tried now on Trantor's 4.3 version. Works like a charm Sweet! That's great news! I blame my SFTP transfer program - I had exported the file from the running Synology and saved it to a Windows Machine to attach to my post. Fantastic News! Easy fix ... and I'll go update my post with a fixed version immediately. This means that I did not miss anything in my notes, and the Idiot's Guide to VMTools could have been written! However, I hope that for everyone, the above post is good enough. You're (all) very welcome! [EDIT: Link to post for
  10. can you tell which logs should contain VMware tools entries and is there any tools specific logging which can be enabled? I don't have the time to research/debug what it is I've done to get my version working (I do remember spending a reasonable amount of time on it though). I've probably forgotten something somewhere. It may be a few days (weekend?) before I can get back to you on this.
  11. Ok ... I've got my installation working, and the vmtools always start up automatically without issue. Did you set the script to be executable? [chmod +x S22open-vm-tools.sh] Upon startup you should see "Starting VMWare Tools:" in the logfile if the [s22open-vm-tools.sh] script is executed. When starting the VMTools manually do they start up, and are visible in ESXi vSphere? [/opt/bin/vmtoolsd --background /var/run/vmtoolsd.pid] Can you control the running VMTools through vSphere [manually or automatic?] Check the logs to see if there is anything failing, or if the vmtools daemon can
  12. How to install optware bootstrap and open-vm-tools into DSM 4.2 and 4.3 (to Update 3 - tested & confirmed) open-vm-tools can be installed, after installing the bootstrap for optware. After installing the syno open-vm-tools kernel files, the open-vm-tools themselves are installed as the standard ipkg. Add in a startup script, for DSM 4.2 only replace the shutdown binary with a script, and open-vm-tools are running in ESXi. Good Luck! Tuatara UPDATE: Fixed the ^M (linefeed) characters from the end of each line. I blame my SFTP transfer application on Windoze. UPDATE 2:
  13. I have not yet migrated to DSM 4.3 (still watching the threads), and am personally still using DSM 4.2, so I can't really answer for any differences in DSM 4.3. I have VMWare tools compiled and installed under DSM 4.2, and have startup/shutdown/IP monitoring/etc. all working well for me. I'm not experiencing any (undue) long delays during shutdown.
  14. Interesting ... I'm using 4.2, and with this version only SCSI controller 0 can be active (AFAIK). I didn't extensively try SCSI 1 - no need. In any case, why would you want to skip controller 0? (i.e. the first in the scanning order)
  15. Tuatara I have run out of options. My DSM does not see any Disks, Volues VM loads and DSM runs, But no storage devices of any kind in Storage Manager. Build 4.3 v1.1 Config: HP Proliant Gen 8 16gb DDR Intel G1610 CPU 4 x WD-RE4 RDM's Separate SCSI Channel Would you look at my VMX? Thanks Hi NetSpider, No worries ... a quick look indicates that you have created a new SCSI Controller as Controller 1 and attached all of the drives to this controller. AFAIK the only controller supported must be SCSI Controller 0. You also have two E1000 network cards assigned to the
  16. Hey Guys, Sorry that I haven't been active on the forum ... I promise I'll keep an eye on developments, but it's been a maniacally busy time for me. I would love to know what firmware his card is running and what settings he used (in esxi and in his card bios) and what build he is using. Mine is running in IT mode FW: 11.00.00.00 / BIOS: 7.21.00.00 / 22-AUG-11 (LSI P11), but I'll flash it to whatever mode I need to if it'll work via passthrough. I got bored and setup 2x3tb last night via RDM, but I'd love to do it via VT-d. I have my XPEnology running using a M1015, flashed t
  17. wow,you are better than me I tested on two machine and got 5MB/s =_=" So very, very strange. I'm getting 50MB/s+ on 4 disk SHR RDM PVSCSI drives for random file copies (mixed file sizes). I'll do some more checking (sometime), and test it on another (really crap) ESXi box and see if I encounter anything.
  18. Another successful installation! jukolaut said he was surprised at how many people downloaded his modified patch ... I'm now curious as to how many XPEnology ESXi installations are out there? With the next source release, it might be time to put some real effort into it and update the idiot's guide, and make a few installation helpers. Thinking about it ... This looks suspiciously like the standard networking problems: Otherwise, it could be the Synology Setup you have: If checking all these things doesn't help, and you've eliminated ALL software problems (trust me - od
  19. A serious kick-ass box you're building there! Personally though ... I went SSD for datastores, and I'm not going back. Ever. 'Nuff Sed. So, if you've got the 'spare change', put the core VMs on SSD ... just brilliant. I've had no issues with the M1015 in IT mode ... PVSCSI RDMs all work perfect.
  20. How are you doing? I came across this post and I was wondering what controller you found to be the most stable. I just prefer controller passthrough instead of RDM. I didn't find any real-world advantages to using VMDirectPathIO over the physical RDM capabilities using the PVSCSI driver. Using everything in an abstracted/virtualised environment just "feels" better to me, even if there is a (very slight - imperceptible) performance loss. My feeling is, should anything ever happen to this (old) hardware, I can quite readily replace any of it without affecting anything else operational on the m
  21. 1. Bootstrapping will allow you to add more packages to your Synology VM - ipkg will be available, and you can install any ipkg packages available for the architecture (x64). You can then (manually for now) install the open-vm-tools which will allow you to control startup/shutdown/ip reporting/etc. through vSphere. 2. Performance loss in my limited testing of VMFS based VMDKs was at least 5% ... sometimes more, depending on hardware. It is perfect for quick testing, but not for something "robust" or for performance testing. VMDirectPathIO (physically mapped hardware) was the fastest ... bu
  22. Quick answer ... a RDM is not a file on a Datastore! It must have complete exclusive access to the hardware, since it is using the RAW DISK - the WHOLE DISK. To use the drive exclusively for Synology you must remove it as a DataStore from ESXi. Then you can use a RDM and map the entire disk to the Synology VM. What you probably want/intend is a standard VMDK - virtual Disk. Use the GUI to make one - just make sure you use a Thick disk. Thin Provisioning will just cause you immense grief. This type of disk will have lower performance (about 5%+), but then you can have the Synology boot,
  23. Same forum, same thread ... just a bit earlier on. Search & reading are your friends! Bootstrap ESXi Build ...
  24. VMWare tools will allow you to control the VM (Synology) through the vSphere control panel. Shutdown being the most important one, for those planned (or unplanned / UPS directed) shutdowns. If you've used VMFS drives, then your HD's are virtualised (i.e. files on the VMFS filesystem under ESXi). Performance will be lower, but you can move the files around as you see fit. The biggest downfall is that the data on the drive is not directly usable (i.e. you can't just plug it into a Linux machine or another Synology and read it as EXT4). SSH being enabled is required to use the console (CL
  25. This is probably due to the Synology DSM kernel thinking the drives are physical drives at boot time, and not USB (Removable) drives. As soon as they are removed, then DSM "recognises" that they are removable (probably due to forceful removal - make sure you're not losing data!). Upon re-inserting them, then they become USB drives only, with the removable flag set correctly. [this is a simplification, but you get the point]. The only way around this I can think of - is to have none of the USB devices available at boot time, and then attach them once booted. Not the best solution, but the o