• Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About yale-xpo

  • Rank

Recent Profile Visitors

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

  1. Thanks for your suggestions. I tried removing the LSI card and the issue still persisted, so I think in the end it had nothing to do with it. I don't know why it didn't start showing up until recently, I may have kept some other VMs powered on which kept the CPU active enough not to crash. I'm going to try and return the Ryzen CPU and motherboard under warranty (should get a full refund due to my state's consumer protections) and replace them with these Intel parts: Intel Core i7-7700 3.6GHz Quad-Core Processor ASRock - H270M Pro4 Motherboard
  2. Seems like it's actually just a Ryzen + Linux issue. I have the same issue running ubuntu server on bare metal (tested up to 4.14rc1 kernel).
  3. I'm out of ideas of how to debug this, but perhaps someone else knows what's going on. This is probably not an Xpenology specific issue, but I'm sure others here have experience using the LSI 9211-8i and ESXi together. I recently did a new build for my NAS with the following hardware: Ryzen 5 1600 ASRock B350 Pro 4 Mobo WD Green m.2 SATA SSD (used as VM datastore only) LSI 9211-8i SAS Controller I am running ESXi 6.5u1 on this setup which was perfectly stable until I added the LSI 9211-8i SAS Controller, since adding this card the system crashes if left idle for more than 30 minutes. Timeline of events: Initially using a LSI 3081E-R controller in pass-thru mode (with test drives since I didn't realise >2TB drives were not supported when I picked up the card for $30.) Online - Several weeks without issue until my LSI 9211-8i controller arrived. Added LSI 9211-8i controller to DSM VM in pass-thru mode with 4x 4TB WD RED HDDs Did disk parity check performed on new SHR array. Took about 8 hours. Offline - Less than an hour after parity check completed the system 'hard locks'. Thought it might be a one-off incident. Rebooted the system, did another parity check to make sure everything was ok. Offline - Again, less than an hour after parity check completed the system 'hard locks'. Updated the firmware on the LSI 9211-8i to v20 using IT mode. Thinking the problem was solved as I was now using ESXi supported firmware, started a data transfer task of 8TB of data, this took about 18 hours and the system stayed online the entire time without a hitch. Data transfer finishes, feeling pretty confident the firmware upgrade has worked since it's been online for this long, spend a few hours doing benchmarks and setting things up. System was online for over 24 hours. Offline - An hour or so after I stop 'doing stuff' with the system, it's hard locked again. Thinking the issue might be IOMMU pass-thru support, I disabled pass-thru mode, installed the official driver from the vmware site for the LSI 9211-8i and mounted the disks into the DSM using ESXi Raw Disk Mappings. Offline - An hour or so after I stop 'doing stuff' with the system, it's hard locked again. Realised it's only crashing when the system is 'idle'. Looked into power saving modes, disabled "C-State" and "Cool 'n' Quiet" in the host bios. Also disabled all power saving features in ESXi. Offline - An hour or so after I stop 'doing stuff' with the system, it's hard locked again. This morning I hooked up a screen to the host in an attempt to see if there was a PSOD or any message before it locks, there was not - just a black screen. System not responsive to short-press power button or keyboard. Offline - less than 40 minutes after sitting idle from boot, it's hard locked again. In addition to the steps taken above, I have tried to find a reason for the lock ups in the ESXi logs, there is seemingly nothing, one minute it's working fine, then nothing until it's booting up again after I power cycle the system. There are no core dumps. Each time nothing was displayed on the screen of the host . It just seems odd the system would crash only when sitting idle - it would make more sense if it was crashing under load. Now these issues only started to occur once I added the LSI 9211-8i to the mix, the LSI 3081E-R did not cause these same issues. Do I just have a dodgy card? I don't want to buy another LSI 9211-8i if I'm going to have the same issues. Is there another card I should get instead? Are there any other settings I should try to make this system stable?
  4. I wanted open-vm-tools / vmware tools installed on my xpenology nas running on top of ESXi, mainly so i could press the power button on the host and still have the DSM guest shutdown safely. The thought of compiling and installing a custom spk for open-vm-tools seemed to complicated and risky, so instead I created a Docker image that solves the problem. https://github.com/yale-wp/docker-xpenology-open-vm-tools The only thing required to run this docker container is the Official Synology Docker package and for SSH to be enabled. Once the container is running shutdown/restart from ESXi will work and networking information will be returned.
  5. yale-xpo

    DSM 6.1.x Loader

    I hit the time bomb issue on my system running 1.02b + DS3617xs. Can anyone confirm that the DS3615xs image does in fact solve this problem?
  6. AMD Ryzen ESXi 6.5.0u1 Synoboot 1.02b DSM 6.1.3-15152 Update 4 All working fine after a smooth update.
  7. yale-xpo

    DSM 6.1.x Loader

    I did this recently with ESXi 6.5, DSM 6.1 and the 1.02b loader. The disks attached to my PCIe sata card (in passthru mode) would not show up until I removed all virtual sata and scsi controllers - I told the synology.vmdk to boot using IDE.
  8. yale-xpo

    DSM 6.1.x Loader

    I tested enabling passthrough on an AMD with ESXi 6.5 with the latest loader and DSM 6.1.3 and it still seems to work. I don't have a PCI SAS/SATA controller at the moment so passed through a pci video card instead - but I think that should satisfy the passthrough test. Now time to order a SAS/SATA controller; I'm thinking an LSI 9211-8i.
  9. yale-xpo

    DSM 6.1.x Loader

    Got this to work by using a SATA controller rather than a SCSI controller, I also had to boot xpenology using the default option rather than the vmware/esxi option.
  10. yale-xpo

    DSM 6.1.x Loader

    I'm trying to pass through the raw disk using RDM. It works initially, I can load DSM, but after a reboot the disks are 'not initialized' - it's like they are in non-persistent mode. Using WD Red 4TB + RDM + Physical Mode (It won't let me select virtual mapping) + Independent - Persistent. Anyone know why this would not be working?
  11. yale-xpo

    DSM 6.1.x Loader

    Update. The 6.1 loader is working on AMD Ryzen (with SMT/all cores & threads enabled) via ESXi 6.5 update 1.
  12. yale-xpo

    DSM 6.1.x Loader

    I'm planning on trying this with a Ryzen 5 1600. From what I can tell the latest ESXi update (6.5 update 1) supports the zen type cpu with all cores and threads working. I was hoping to pass through the SAS/Sata controller as well - so it looks like I might be stuck using 6.0 either way.