Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Marc_G2

  • Rank
  1. I created a new VM while passing though the SSD. Sustained write speed is now 200+ MB/s. Definitely better, but still not close to bare metal. Crystal diskmark gave bad results due to caching. For perspective, this is what Space Invader One got for a Vdisk. He had similarly bad sequential write speeds. https://youtu.be/QaB9HhpbDAI?t=15m44s Should I still configure the disk to as a "thin provisioned drive"?
  2. I believe the config is correct (see above). The media type says it's a "Solid state drive" and doesn't say it's a thin provisioned drive. So I'm not sure where I went wrong.
  3. Well I managed to get VM booting with VirtIO again. I needed to initialize my newly created disk in Windows Disk Management prior to switching the primary disk to use VirtIO. A quick file copy test shows sustained writes are still less than 100 MB/s. For some reason, Windows won't let me defragment the SSD. It says "Optimization not available" on its status. I'm pretty sure the XML is correct: <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback' discard='unmap'/> <source file='/mnt/disks/Crucial_CT525MX300SSD1_163213963944/Windows 10/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
  4. I will give this a try before trying to pass though the SSD. Although I was only using 50/500 GB I had available.
  5. I noticed I was getting poor SSD (Crucial MX300) write performance (about 100 MB/s or less) in my Windows 10 VM. The SSD was mounted using Unassigned Devices. I noticed Windows referred to the VirtIO drive as a SCSI device. So I tried changing "Primary vDisk Bus" to SATA to see if it would help. That didn't help, and it ended up causing other issues including stuttering/cracking audio. The MSI fix doesn't seem to work. Switching back to VirtIO doesn't allow Windows to boot. What performance should I expect from my SSD? Was my problem a VirtIO configuration issue? EDIT. Will try a fresh install and passing though the SSD.
  6. Nice. It looks like that fixed it for me as well. I actually saw that MSI thread as well. But I couldn't figure out what he was trying to say so I quickly moved on lol.
  7. Sorry I haven't tried it. In the end I decided it made more economic sense to simply not allow the system to go to sleep while I'm on travel (the only time I would need WOL). Does anyone know the specific reason why it doesn't work?
  8. I ran another check and got 0 errors. So I will assume my hardware is good. Does 1 error = 1 wrong bit? How many errors would I normally expect to see from an unclean shutdown?
  9. I ran a parity check (write corrections enabled) and it resulted in more than 3 million errors. I don't believe I've ever had an unclean shutdown. I was having problems with VMs crashing, but that didn't result in a shutdown. I haven't seen any other errors. I have attached my diagnostics. What was the mostly likely cause? What should be my next course of action? nas-ng-diagnostics-20191020-2040.zip
  10. Today (3 times) I've started experiencing seemingly random crashes while in my Windows 10 VM. The system would hard freeze (static image, no response to keyboard, sound freezes and outputs something like a buzzing sound) for about 5 seconds before attempting an automatic reboot. What ends happening is the system just goes to sleep. unRAID appears to be running fine after I wake the system backup. I've been running this VM without issue for about a month. I was thinking the issue might be GPU related, and updated the driver: no luck. Any ideas what might be the cause? Since unRAID itself isn't crashing, does this mean we can say for sure the problem is related to the hardware being passed through? The only thing notable I'm passing through is the GPU. System Info: unRAID 6.7.2 MSI X470 Gaming Plus R 3600X GTX 1070
  11. I have confirmed my BIOS settings are good. WOL is lumped into the wake by pcie device setting. I also disabled Erp for good measure
  12. Well I confirmed that I can get WOL working on Windows, but still can't get it working with unRAID. Is it a driver issue? I couldn't find any information confirming that my Realtek Chipset was known to not work. Where should I be looking for that kind of information?
  13. Thanks for the recommendation. I will buy that if nothing else works. I found some other potential solutions which I'll try first.
  14. Will support ever get added? What are my options for work-arounds?
  15. I've been struggling to get Wake on LAN working for a few days now. Does anyone have any ideas? One potential issue I noticed is how I'm not getting any LED activity with the ethernet port while the system is asleep. I talked to a MSI rep and he had no idea if that was normal behavior or not. Edit: The activity lights remain off always when the system is asleep. Summary: 1) MOBO: MSI X470 Gaming Plus 2) Router is Netgear R6400 3) BIOS ErP set to Disabled 4) BIOS PCIe and USB Wake functions Enabled 5) unRAID 6.7.2 6) S3 Sleep, using S3 Sleep plugin along with the information here http://lime-technology.com/wiki/index.php?title=Setup_Sleep_(S3)_and_Wake_on_Lan_(WOL) 7) I've been using this utility to send the wake packet: https://www.depicus.com/wake-on-lan/wake-on-lan-cmd 8 ) Wake from USB does work Running ethtool eth0 yields this Settings for eth0: Supported ports: [ TP AUI BNC MII FIBRE ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised auto-negotiation: Yes Link partner advertised FEC modes: Not reported Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) drv probe ifdown ifup Link detected: yes